Multiple performance obligations
Subscription, implementation, support, and training identified separately and allocated on standalone selling price — the step most spreadsheets skip because it is tedious.
Platform · financial core
Revenue recognition is the reason most software and services companies leave QuickBooks, and it arrives on a deadline — a round, an acquisition, or an auditor. A schedule nobody can reproduce is not wrong, it is unverifiable, and in diligence that costs the same.
Your contract types and billing system. We will tell you what will not survive a diligence review.
What it handles
Subscription, implementation, support, and training identified separately and allocated on standalone selling price — the step most spreadsheets skip because it is tedious.
A contract that steps up in year two recognises evenly where the goods or services are delivered evenly, not on the billing curve. This is the most common error we find.
Upgrades, downgrades, and extensions treated as prospective or cumulative catch-up according to which they are, with the reasoning recorded.
Recognised as consumed, tied to the billing system rather than estimated at period end and trued up later.
For services and fixed-fee engagements, driven from approved time against an agreed budget rather than from a project manager’s estimate.
Opening balance, additions, recognition, adjustments, closing balance — reconciling automatically, with every movement traceable to a contract.
ASC 606 is a five-step model and most finance teams can recite it. The failures are not conceptual — they are that steps two and four are laborious, so they get approximated.
Capturing obligations at signature, by the person who negotiated the contract, is what removes the approximation. Finance reconstructing them from a PDF a quarter later is where the errors originate, and no amount of care downstream fixes an obligation that was never identified.
In our experience, three things, in this order. The deferred revenue rollforward, because it is the fastest way to find out whether the schedules are real. A sample of contracts traced from the signed document to the revenue recognised, because that tests whether obligations were identified consistently. And the treatment of modifications, because it is where judgement lives and where a company under pressure is most likely to have been optimistic.
All three are answerable in minutes when the schedules are driven from contract records, and take a week of spreadsheet archaeology when they are not. The difference shows up as discount rather than as a finding — reviewers price uncertainty rather than arguing about it.
ARR, bookings, and recognised revenue measure different things and should never be equal, but they should be reconcilable. Because contracts, invoices, payments, and schedules are objects on one graph here, the bridge between them is computed: bookings to ARR to recognised revenue to cash, each step explainable.
That is what stops the board pack from being a two-day assembly exercise, and it is why the numbers in it survive being questioned.
Under roughly $3M ARR with simple annual subscriptions and no implementation revenue, QuickBooks plus a well-built spreadsheet is genuinely adequate and we will tell you so. The threshold is not size — it is whether contracts have multiple obligations or modifications happen mid-term.
Questions
Send your contract types and a billing export. We will tell you what will not survive diligence.