PursuitBid data & control
Financial planning needs clear permissions, traceable records, and care with sensitive information. PursuitBid enforces organization and entity permissions in the application, with separate controls for compensation data.
Deliberate access
Organization and entity permissions are enforced in the application, with separate access controls for compensation information.
History that holds
Financial revisions and published reports preserve the records and assumptions used to produce them. Later corrections create new editions.
Missing is never zero
Required inputs are checked before they feed a calculation. Gaps are flagged rather than silently filled.
No money movement
PursuitBid supports planning and reporting. It does not post accounting entries, connect to bank accounts, or move money.
Agreed data channels
Sensitive records are exchanged through a channel agreed during onboarding, never through a public contact form.
Please do not include financial statements, payroll, bank details, or credentials in a first inquiry. We agree the data-sharing arrangement before onboarding.
Common questions
Does PursuitBid replace our accounting software?
No. Your accounting system remains the record. PursuitBid supports planning and reporting and does not post entries or move money.
How do records get into PursuitBid?
Through structured CSV and XLSX imports covering accounting, budgets, receivables and payables, payroll and headcount, and drivers. Direct bank feeds and live payroll connections are not included.
What is the difference between the budget and the forecast?
The budget is the target management adopted. The forecast is the current expectation based on recorded evidence and assumptions. One does not silently overwrite the other. See budget vs. forecast.
Want to see PursuitBid on your own work?
Tell us what you would bring to PursuitBid. We’ll arrange a walkthrough and talk through fit, access, and onboarding.