Revenue recognition is the single accounting topic most likely to blow up in diligence. A company that has been booking revenue the wrong way for two years can find its ARR restated downward by 20 or 30 percent the week before a term sheet. The good news: the rules are knowable, and the habits that prevent the problem are cheap to build early.
1. Identify the contract. Signed order form, click-through terms, or a fully-executed MSA plus SOW. A verbal commitment is not a contract. 2. Identify the performance obligations. What did you promise? Software access, implementation, training, support — each is potentially a separate obligation. 3. Determine the transaction price. The total consideration, adjusted for discounts, refunds, and variable consideration. 4. Allocate the price to the obligations. If you sold software + implementation for $120K, and implementation standalone would cost $30K, you allocate accordingly. 5. Recognize revenue when the obligation is satisfied. Software access — ratably over the term. Implementation — as delivered. One-time services — on completion.
Auto-renew with an opt-out window. Fine, but the renewal is not booked ARR until the window closes.
Success-based fees. Cannot be recognized until the success criteria are met.
Free months or ramping pricing. Revenue is straight-lined across the full contract term, not recognized as billed.
Termination for convenience. If the customer can walk away with 30 days notice, only 30 days of revenue is contractually committed.
Right of return or refund. Requires a reserve — you cannot recognize the portion you might have to give back.
Recognizing annual contracts upfront instead of ratably. This is the most common error and the one auditors catch first.
Booking usage-based revenue based on forecast rather than actuals.
Ignoring variable consideration (rebates, tiered discounts, credits).
Every contract needs a one-page revenue memo: performance obligations identified, transaction price, allocation, recognition schedule. Auditors will ask for this in the first Series B diligence. Building the habit at 20 customers is trivial. Rebuilding it at 500 customers is a six-figure project.
By the time the company crosses $2M in ARR or takes an audit, a fractional revenue accountant or a controller with SaaS experience is worth the cost. Before that, the CFO or head of finance can own it with a good template.
Revenue recognition is not the most exciting topic. It is one of the highest-leverage ones. The founders who take it seriously early avoid the six-figure diligence surprise that ends careers of finance leaders and delays rounds.
