On 27 December 2024, Bench emailed its customers to say operations had ceased, effective immediately. The platform went dark the same day. Thousands of businesses, in the middle of year-end, discovered that their books were not somewhere they could reach.
The company was acquired within days and relaunched under new ownership, and customers were eventually given a window to retrieve their data. But the lesson had already landed, and it is a question almost nobody asks before signing: if this provider disappeared tomorrow, what would I still have?
Why this is a structural question, not a paranoid one
Bookkeeping providers come in two shapes. Some maintain your books inside standard accounting software you own, typically QuickBooks or Xero, where the file is yours and the provider is a user of it. Others maintain your books inside their own proprietary platform, where what you have is an interface to their system.
Both can produce good work. The difference only matters at exactly two moments: when you want to leave, and when they do. Neither is a moment when you want to discover the answer for the first time.
The failure is not usually dramatic. Far more common than a shutdown is a provider you have simply outgrown, where switching means a migration project rather than a handover, and the friction is enough that companies stay put for another year.
What owning your books actually means
Four things, and it is worth checking all of them rather than accepting a general assurance.
- The file lives in software you hold the subscription to. If the provider vanished, you would still log in tomorrow. This is the substantive test; the rest are refinements.
- You can export a complete general ledger, not a set of PDF reports. Statements are output; the ledger is the record, and only the ledger lets a new provider pick up where the last one stopped.
- The historic detail comes with you: transaction-level records, attachments, and reconciliations, rather than summary balances.
- There is no contractual barrier to leaving, such as data being released only after a notice period or a final payment.
The second one catches people out most often. A provider can honestly say you will receive your financials on exit and still hand over a folder of PDFs, which is not something a new bookkeeper can work from without rebuilding the year.
What to ask before you sign
| Ask | What a good answer sounds like |
|---|---|
| Where do my books live? | In your own QuickBooks or Xero file |
| Who holds the subscription? | You do, or it transfers to you on exit |
| What do I get if I leave? | Full ledger access, immediately, no conditions |
| What if you shut down? | Nothing changes, the file is already yours |
| Is there a notice period on data? | No |
If a provider hesitates on the first two, that is the answer. It does not mean they do bad work. It means their platform is the product, and your records are inside it.
If you are on a proprietary platform now
You are not stuck, but do the work before you need to. Export a full general ledger and keep it somewhere you control, and repeat it periodically rather than once. Find out what the exit process actually is in writing rather than in a sales conversation. And if you are planning to switch anyway, do it at a clean period boundary with a parallel close so the handover has a checkable seam.
For the switching mechanics, see what changes in bookkeeping after you raise, and for the Bench episode specifically, what it taught us about owning your books.
Why this matters more after a raise
Before institutional money, losing access to your records is painful and recoverable. After a raise it is a different category of problem, because your books have obligations attached to them.
Investor reporting has dates. Tax filings have deadlines that do not move for vendor difficulties, and some, like the R&D payroll offset election, cannot be made late at all. A future diligence process will ask for transaction-level history going back years, and a folder of PDF statements will not satisfy it. In each case the question is not whether you eventually recover the data, it is whether you have it on the day it is due.
That is why portability belongs on the checklist alongside price and scope rather than in the small print. It costs nothing to confirm at signing and is expensive to discover later.
The quarterly export, specified
Keep an export somewhere you control is easy to agree with and easy to do badly. A folder of PDFs satisfies the instruction and none of the purpose. This is what a genuinely useful export contains, and it takes under an hour a quarter once someone has done it the first time.
- A general ledger export covering all activity to date, at transaction level, in CSV or Excel rather than PDF. This is the record. Everything else is derived from it.
- Trial balance as at the export date. It is what a new provider reconciles your opening balances against.
- Chart of accounts, so account structure and any custom classes or departments survive the move.
- A backup of the accounting file itself where the software supports one, which preserves reconciliation status rather than just the numbers.
- Bank and credit card statements for the period, from the bank rather than the accounting system. If the ledger is ever in doubt, these are the independent source.
- Source documents: invoices, bills and receipts, particularly anything supporting a deduction or a credit claim.
Store it somewhere the provider does not administer, which usually means your own cloud drive rather than a shared workspace they set up. The point of the exercise is independence, and an export sitting in a folder they control is not independent.
The dependencies people forget
Bookkeeping is the one everybody thinks about, because it is where the Bench story landed. The same question applies to three other systems, and in each case the answer is usually worse because nobody has asked.
| System | The question | Why it bites |
|---|---|---|
| Payroll | Can you export year-to-date wages, taxes and deductions per employee? | Without it a mid-year migration produces wrong W-2s, and the error surfaces at year end when correcting it means amended filings |
| Receipts and documents | Are source documents stored where you can reach them? | A deduction or an R&D claim you cannot substantiate is one you may not be able to defend |
| Tax filings | Do you hold copies of every return filed on your behalf? | You need prior-year returns to file the current one, and to answer any notice that arrives later |
| Bank connections | Who holds the credentials to your bank feeds? | Feeds set up under a provider's login break when their access is revoked, silently, mid-month |
The last row is the one that produces the strangest failures. A bank feed configured under a departing bookkeeper's credentials does not announce that it has stopped. Transactions simply stop arriving, and the gap is usually noticed at the next close, by which point it is a reconstruction rather than a reconnection.
Where Zinance fits
Your books live in your own QuickBooks file. Zinance works inside it rather than in a platform of our own, so if you left tomorrow you would keep everything, in a format any accountant can pick up, with no export request and no notice period. That is a deliberate constraint on us rather than a feature, and it is the right way round.