Why Month End Close Feels Like an Ambush
Most SaaS founders track the business through a cash lens without realising it. The dashboards they check most often, a bank balance, a Stripe payout total, a runway number, all answer the same question: how much money is sitting in the account today. That number is real, but it is also incomplete, and the gap between it and the underlying financial position tends to surface all at once, at month end, when a bookkeeper or finance lead finally reconciles the ledger.
The ambush happens because two different obligations sit outside the cash view. On one side, customers who paid annually in advance have not yet earned that revenue in an accounting sense, so a large share of what looks like income is actually a liability owed back in service. On the other side, costs the business has already incurred, a hosting bill not yet invoiced, a commission not yet paid, sit unrecorded until an invoice physically arrives. Neither of these shows up on a bank statement. Both show up the moment someone closes the books properly.
This exposure begins from the first sale, not only once a company reaches later stages: any SaaS business selling annual or multi-year contracts, running usage-based infrastructure costs, or paying variable commissions is exposed to it immediately. The earlier a founder builds the habit of closing on an accrual basis, the less painful each subsequent close becomes, because the adjustments are made in small monthly increments rather than surfacing as a single large correction right before a funding round.
Cash Basis vs Accrual Accounting for SaaS Operators
Cash basis accounting recognises a transaction when money physically moves: a payment lands, an invoice is settled, cash leaves the account. It is simple, and HMRC allows some small unincorporated businesses to report this way for tax purposes (see the gov.uk guidance on the cash basis scheme). Accrual accounting recognises revenue when it is earned and expenses when they are incurred, regardless of when cash actually changes hands.
For a subscription business the difference is concrete rather than theoretical. Take a contract paid upfront for a full year of service. Under cash accounting, the entire contract value lands as revenue in the month the invoice is paid. Under accrual accounting, that same value is spread evenly across the twelve months of service, with the unearned portion carried on the balance sheet as a liability until it is delivered. A business with several such contracts signed in the same month can look, on a cash basis, like it just had an exceptional quarter, when in accrual terms very little of that value has actually been earned yet.
This is why institutional investors and auditors work almost exclusively from accrual statements. Revenue recognition standards such as IFRS 15 exist specifically to stop revenue being booked before it has actually been earned under the terms of a contract. A founder who only produces cash-basis reports is not just missing detail, they are presenting a set of numbers that a serious investor’s finance team will simply rebuild from scratch during diligence, and any gap between the founder’s story and that rebuilt version becomes a credibility problem during the funding conversation itself.
Deferred Revenue: The Balance Sheet Blind Spot
Deferred revenue is the accounting term for money collected in advance for a service not yet delivered. It sits on the balance sheet as a liability, not as revenue, because the company still owes the customer that service. This is the single most common place SaaS financial reporting goes wrong, because the cash arrives looking exactly like earned income and the temptation to book it as growth is strong.
Consider a company that signs a wave of annual contracts in one quarter and reports the full contract value as revenue in the month of invoicing. On a cash or billings basis, growth looks dramatic. Once an auditor or a diligence team recomputes the same period using recognised revenue, splitting each contract into its true monthly earned value, a large share of that reported growth can disappear back into the deferred revenue balance. This is not fraud in most cases, it is simply a founder conflating billings with revenue, but the effect on investor trust is the same either way.
The mechanics get harder with mid-contract changes. An upgrade partway through a term means the remaining deferred balance has to be recalculated against the new contract value from the change date forward. A downgrade or a partial refund means reducing the deferred revenue liability rather than simply expensing a refund line, otherwise the balance sheet overstates what is still owed to that customer. A deferred revenue schedule that only handles new contracts and never revisits existing ones will drift out of true within a few quarters, and that drift is exactly what an auditor’s revenue recomputation is designed to expose.
Accrued Liabilities and the Obligations Cash Does Not Show
Deferred revenue is the well-known blind spot; accrued liabilities are the less-discussed one, and they distort the numbers in the opposite direction. An accrued liability is a cost the business has already incurred but has not yet paid or even been invoiced for. Usage-based infrastructure spend billed in arrears is a classic example: the compute was consumed in March, but the invoice does not land until the second week of April. Unpaid sales commissions on deals closed but not yet settled, accrued payroll for days worked but not yet paid at the close date, and unbilled contractor time all behave the same way.
The failure mode is predictable once you see it: a month’s expenses look artificially low because a real cost has not been recorded yet, then the following month absorbs that cost on top of its own normal spend, making the trend line jump around for no operational reason. A finance lead reading month-on-month burn without accrual entries will chase phantom cost spikes that are really just last month’s bill landing late, and will miss genuine cost increases that get buried in the noise.
The accounting principle here is not exotic; it is the same statutory accrual basis that UK companies of any size are expected to apply when they file accounts. Equanax itself is registered in England and Wales as company number 13194418, incorporated on 10 February 2021. The discipline scales down to a two-person startup exactly as it scales up to an established consultancy: record the cost in the period it was incurred, not the period the invoice happens to arrive.
A Month End Close Sequence That Holds Under Diligence
A close process that survives investor scrutiny is not a single reconciliation task, it is a fixed sequence run in the same order every month. Skipping a step, or running them out of order, is how errors from one step quietly compound into the next.
- Freeze the ledger at a cut-off date. Nothing gets booked to the closed period after this point without an explicit reopening, or the close date becomes meaningless.
- Reconcile cash and bank feeds. Every bank transaction and payment processor payout is matched to a ledger entry, catching timing gaps before they propagate.
- Update the deferred revenue schedule. New contracts are added, existing schedules are recalculated for upgrades, downgrades and cancellations, and the current month’s recognised slice is released from the liability.
- Post accrued expenses and liabilities. Costs incurred but not yet invoiced, usage-based infrastructure, unpaid commissions, unpaid contractor time, are estimated and booked against the correct period.
- Reconcile balance sheet accounts. Deferred revenue, accrued liabilities, prepaid expenses and accounts payable are checked against supporting schedules, not just against the prior month’s closing figure.
- Produce the investor pack. The accrual income statement, balance sheet and deferred revenue waterfall are compiled together, so any reader can trace recognised revenue back to its underlying contracts.
Each step depends on the one before it. A team that reconciles the balance sheet before finishing the deferred revenue schedule is reconciling against numbers that are about to change, which produces a close that looks complete but is not, and a diligence team’s own reconciliation will find that gap during the round.
Preparing Investor Ready Accrual Statements
An investor-ready pack is judged less on presentation and more on whether its numbers reconcile to something underneath them. Three things a diligence team will check almost every time: whether reported revenue is recognised revenue or billings, whether gross margin properly deducts hosting and support costs rather than treating them as general overhead, and whether net revenue retention is calculated from recognised revenue rather than from cash collected.
A deferred revenue waterfall is the artefact that makes this checkable. It shows, for each contract cohort, how much was billed, how much has been recognised to date, and how much remains deferred. A reader can trace the income statement’s revenue line back to that waterfall and confirm it adds up, rather than taking a single top-line number on trust. Founders who can hand over that waterfall unprompted, before it is asked for, move through financial diligence noticeably faster than those who have to build it from scratch once requested.
The same logic applies to the liabilities side. A schedule of accrued expenses, tied to specific vendors and specific accrual dates, lets an investor trace the balance sheet’s accrued liabilities line back to a real, itemised total rather than accepting it as a plug figure. Statements that cannot be traced this way generate more diligence questions, not fewer, even when the underlying numbers turn out to be correct.
Automating the Close Without Losing Control
Manual month-end close does not scale much past a handful of contracts before reconciliation errors start creeping in, simply from the volume of manual entries required. Automation helps, but it changes what can go wrong rather than removing risk entirely. A workflow tool such as n8n can pull subscription and payment data from a billing system into an accounting ledger automatically, and CRM platforms like HubSpot expose contract and deal data through their own APIs (see the HubSpot developer documentation) that can feed the same reconciliation.
The risk with automation is that an error in the mapping logic, for instance a contract change that is not correctly translated into a revised deferred revenue schedule, now repeats identically every month instead of being caught by a human doing the calculation by hand. This is why an automated close still needs the same reconciliation step as a manual one: a periodic check that compares the automated ledger entries against the underlying contract and invoice data, rather than trusting the pipeline output by default. Equanax has recorded an 86 percent cut in sync errors. Validation checks of this kind are one of the general mechanisms that can produce results like that.
Automation earns its keep by eliminating the manual re-entry of subscription and payment data across systems; it does not replace judgement. A founder still needs to review the deferred revenue schedule and the accrued liabilities list each month, because contract changes, refunds and one-off adjustments require a decision that no workflow can make on its own.
Related Reading
Frequently Asked Questions
How do we know our month end close is actually complete?
Reconciliation is the test: bank statements, the deferred revenue schedule and the accrued liabilities list all need to tie back to the ledger, not just to each other’s prior-month totals. If any one of those cannot be traced to a supporting schedule, the close is not finished yet.
Can an early-stage SaaS startup stay on cash basis accounting for a while longer?
It is possible in the very earliest months, but most institutional investors expect accrual statements before a serious funding conversation, and switching late means rebuilding prior periods under pressure rather than building the habit from the start.
How should an annual contract paid upfront be handled in the books?
The cash is recorded when it arrives, but the revenue is recognised monthly across the contract term, with the unearned portion held as deferred revenue on the balance sheet until it is delivered.
Is automation necessary for a small SaaS finance function?
It is not strictly necessary, but it removes a lot of manual re-entry work as contract volume grows, provided a human still reviews the deferred revenue schedule and accrued liabilities each month rather than trusting the pipeline blindly.
Why do investors care so much about accrual reporting specifically?
Because accrual statements are the only version of the numbers that separates money collected from revenue actually earned, and diligence teams recompute that separation first when checking growth claims.
For more on this, see more on reporting and data, including Building an Automated RevOps Forecasting Pipeline for Scalable SaaS Growth, Automated Lead Scoring with Clearbit, Looker & N8N for RevOps Growth, and How to Automate RevOps Analytics with n8n and Metabase Dashboards.
Leave a Reply