United States / Blog / From shoebox to Series A: what cleanup actually involves
United States · noteFrom shoebox to Series A: what cleanup actually involves
The shoebox is not a metaphor
Founders use "shoebox" loosely for anything from a bank feed nobody reviewed to a spreadsheet that stopped updating in Q2. What actually shows up when a rebuild starts is more specific: months where the ledger was populated from a bank feed and never checked against a statement, a payroll processor and an accounting system that quietly disagree about the same pay run, and a deferred-revenue balance that stopped moving the week whoever tracked it got pulled onto something else.
None of that looks dramatic inside the software. The P&L opens fine. It falls apart the moment a diligence request asks it to explain itself — why the deferred revenue balance has not changed in five months, why payroll expense on the income statement does not match what the payroll processor actually paid out. The instinct at that point is to redo the whole year. That is not what a rebuild does, and it is not what a diligence reviewer is checking for.
Find the last month that actually reconciled
A rebuild starts by locating the most recent month where every account tied to its source statement to the penny — bank, credit card, any loan balance. That month is the anchor. Everything before it is treated as settled; everything after it is where the work happens.
Finding the anchor is itself diagnostic. A company that reconciled cleanly through October and drifted in November has a two-month problem. A company that has never actually reconciled — where entries exist for every month but nobody checked them against a statement — has a problem that reaches back to whenever the account was connected, regardless of how complete the transaction feed looks. Reconciling forward from a verified anchor beats re-entering a year from scratch, because re-entry just manufactures a second set of numbers that still has not been checked against anything real.
Deferred revenue is the balance investors read first
For a subscription or contract-based business, deferred revenue is one of the first lines a Series A investor's diligence team actually studies, because it is the clearest signal of whether revenue recognition tracks delivery or just cash timing. Under the revenue recognition standard, ASC 606, revenue is recognized as performance obligations are satisfied — not as the invoice clears — which means a prepayment or a multi-year contract collected up front creates a liability that releases into revenue over the service period, not on the day the money lands.
Rebuilding that balance means reconstructing the schedule contract by contract: what was collected, over what period, how much of that period has elapsed, and what should have moved from liability to revenue each month in between. A schedule maintained monthly is a five-minute update. The same schedule abandoned for eight months is a multi-day reconstruction, and the entire distance between those two is a matter of when someone last looked at it — not the complexity of the underlying contracts. Where a specific contract's recognition treatment is genuinely ambiguous, that call is the CPA's to make; the schedule is what puts the question in front of them instead of leaving it buried in an unmoving balance.
Tying payroll to the general ledger
A payroll processor and an accounting system are two separate records of the same activity, and nothing forces them to agree automatically. Tying them out means checking that every payroll run posted to the general ledger matches what the processor actually paid — gross wages, each withholding, each deduction, employer-side tax expense — against the same figures that feed the quarterly Form 941 filing.
The most common failure is a payroll liability account that never zeroes out: withholdings get booked as owed, but the offsetting remittance to the tax agency or benefits provider never gets matched against it, so the balance grows every period instead of resetting. Walking that account back to the anchor month and clearing it against actual remittances is mechanical — the classification calls, like whether a given payment is wages versus contractor pay, stay with the CPA. The tie-out is what gives them a clean base to make that call from, instead of a liability account nobody can explain.
What cannot be recovered — and saying so in writing
Some gaps do not reconstruct cleanly. A receipt that no longer exists, a vendor that closed, a bank feed that had already disconnected before the period anyone was watching it. The move that holds up under diligence is not to plug a number that looks plausible — it is to log the gap: what is missing, why, and what documentation, if any, stands in for it.
A documented gap and an undocumented plug read completely differently to a diligence reviewer. A one-line note next to a reconstructed estimate is a fact they can work with. A suspiciously round balance sitting in an account that should never be round, with no note attached, is the thing that turns a routine diligence pass into a longer one.
Why January is the worst month to start, and what investor-ready means
January is structurally the worst month to begin a rebuild that anything else depends on, because it is also the month W-2s and 1099-NECs are due to recipients — a fixed deadline that does not move for a company still reconciling November and December. A rebuild that starts in Q3 or Q4 has runway to work through the anchor-month process properly; one that starts in the second week of January is competing for the same bookkeeping and CPA capacity every other year-end close in the country is drawing on, with no slack if a deferred-revenue schedule or a missing statement takes longer to chase down than expected.
"Investor-ready" is not a specific software or a specific number on the balance sheet. It is a reconciled balance sheet where every account ties to a source statement, a deferred-revenue schedule and a payroll tie-out that both hold up on inspection, and a written note next to anything that genuinely could not be recovered. That is what a diligence checklist is actually testing for, and it is what needs to be sitting with the CPA well before a term sheet's diligence window starts closing in — not assembled during it.
CapEasy's part in a rebuild is the reconciliation and reconstruction described above: finding the anchor month, clearing the transaction backlog, rebuilding the deferred-revenue schedule, and tying payroll to the general ledger. Revenue recognition judgment calls, the return, and any representation in front of an investor's counsel stay with your CPA, working from the rebuilt books.
Reading about it is optional. The books aren’t.
A named accountant, software underneath, licensed partners where the law wants them.