SaaS Accounting Explained: Revenue Recognition, Deferred Revenue, MRR
A plain explanation of what makes subscription accounting different, the rules that govern it, the metrics that sit next to the books, and what a ledger has to do to keep up.
SaaS accounting is the accounting of a business that sells access to software over time. The one fact that makes it different from selling a product is timing: the customer usually pays before the service is delivered, often a year in advance, and the revenue may only be recorded as the months of service pass. Everything that is specific to SaaS accounting follows from that gap between the invoice and the delivery.
This article explains what the term covers, the rules that govern it under IFRS 15 and ASC 606, the handful of numbers a subscription company has to keep straight, and what an accounting system needs to do so that none of it is maintained by hand in a spreadsheet.
What SaaS accounting means
In a shop, the sale, the delivery and the revenue happen at the same moment. In a subscription business they come apart:
- The customer signs a contract (a booking).
- You issue an invoice, possibly for twelve months at once (a billing).
- The customer pays (cash).
- You deliver the service one day at a time, and only the delivered part is revenue.
- The part invoiced but not yet delivered sits on the balance sheet as deferred revenue, a liability.
A company that recognizes the whole annual invoice as revenue in January reports eleven months of work it has not done. If the customer cancels in March and is refunded, that revenue was never real. Accrual accounting exists to stop this, and SaaS is the business model where the correction matters most, because almost every sale is paid for before it is delivered.
So "SaaS accounting" is not a separate set of books. It is ordinary double-entry accounting applied to contracts that are performed over time, plus a layer of operating metrics that the financial statements do not show.
Why cash is not revenue
Take a customer who pays €2,400 on 1 January for a twelve-month plan. The bank balance goes up by €2,400 (plus VAT) on day one. The income statement for January shows €200 of revenue, because one twelfth of the service has been delivered. The remaining €2,200 is a liability: you owe the customer eleven months of service.
| What moved in January | Amount |
|---|---|
| Cash received (net of VAT) | 2,400 |
| Revenue recognized | 200 |
| Deferred revenue at 31 January | 2,200 |
Three consequences follow, and all three confuse people who come to SaaS from other businesses:
- A fast-growing SaaS company looks cash-rich and profit-poor. Annual prepayments arrive up front; revenue trails behind by up to a year.
- A shrinking SaaS company looks the opposite. Revenue from old prepayments keeps being recognized while new cash dries up.
- The deferred revenue balance is a forecast. It is revenue you will report in coming months without selling anything new, as long as you keep delivering.
The glossary entry on deferred revenue, unearned revenue and deferred income covers the liability itself in more depth. The companion article on deferred revenue for SaaS with journal entries walks through the entries case by case.
The five numbers, and how they differ
| Number | What it measures | Where it lives |
|---|---|---|
| Bookings | Total contract value signed in a period | Operating report, not the ledger |
| Billings | Amounts invoiced in a period | Sales ledger (accounts receivable) |
| Revenue | Value of service delivered in the period | Income statement |
| Deferred revenue | Invoiced but not yet delivered | Balance sheet, liability |
| MRR / ARR | Normalized monthly (or annual) value of active subscriptions | Operating report, not the ledger |
The rule that ties the first four together is simple: billings − revenue recognized = change in deferred revenue. If your reports do not satisfy that identity, one of the three figures is wrong.
MRR and ARR are the two that are not accounting measures at all. MRR counts only recurring contract value normalized to a month, so a €2,400 annual plan contributes €200 of MRR, and one-off setup fees contribute nothing. Revenue, by contrast, includes the setup fee when it is earned and follows the recognition rules below. The two numbers answer different questions and should never be reconciled to each other, only explained.
The rules: IFRS 15 and ASC 606
Both standards use the same five-step model. For a SaaS contract the steps resolve as follows.
| Step | The rule | Typical SaaS answer |
|---|---|---|
| 1. Identify the contract | An enforceable agreement with commercial substance | The signed order or accepted online terms |
| 2. Identify performance obligations | Distinct promises to the customer | Access to the software; onboarding or implementation if it is distinct; premium support if sold separately |
| 3. Determine the transaction price | The amount you expect to be entitled to, including variable consideration | The subscription fee, less expected refunds or credits |
| 4. Allocate the price | Across obligations in proportion to standalone selling prices | A bundle discount is spread across the software and the onboarding, not left on one line |
| 5. Recognize revenue | When or as each obligation is satisfied | Software access: over time, ratably; onboarding: at a point in time or by milestone |
Three details decide most of the practical work.
Software access is satisfied over time. The customer consumes the service continuously, so revenue is recognized evenly across the service period. A day-weighted straight line is the usual pattern.
Onboarding may or may not be distinct. If a customer could benefit from the software without your implementation service, and the service is sold separately, it is a separate obligation recognized when delivered. If the software is unusable without it, the two are one obligation and the whole price is recognized over the subscription term. This is a judgement the company makes, not the software.
Variable consideration is excluded until it is probable. If you expect 5 % of annual plans to be refunded, the transaction price is 95 % of the invoice; the other 5 % is a refund liability, not revenue. It becomes revenue only when the refund window passes without a claim.
The article on SaaS revenue recognition under IFRS 15 with worked ledger entries applies each step to a numbered example and shows the journal entries.
Common mistakes
- Recognizing the invoice. The most common error: revenue equals billings, and deferred revenue does not exist on the balance sheet. It overstates revenue in growth years and understates it later.
- Leaving the bundle discount on one line. A €3,000 bundle of software and onboarding, with a discount applied only to the onboarding line, recognizes too much revenue up front. The discount belongs across both obligations.
- Treating refunds as a surprise. Known refund rates are variable consideration. Booking the full amount and reversing refunds later overstates revenue every period.
- Mixing MRR into revenue. MRR is a run-rate; revenue is what was delivered. A board deck that labels one as the other will not survive diligence.
- Spreadsheet schedules. A deferred revenue waterfall maintained by hand drifts from the ledger the first month someone upgrades, downgrades or cancels mid-term.
- Closing the month with unreleased deferrals. If the release of deferred income is a manual journal, a month can be closed with revenue earned but not recognized.
Best practices
- Put the recognition method on the invoice line, not in a spreadsheet. The line that carries the price should also carry how its revenue is earned: at a point in time, ratably between two dates, or by milestone.
- Keep deferred revenue as a derived balance. The liability should be the sum of pending schedule tranches, explainable line by line, not a number someone types in at month end.
- Record standalone selling prices. Allocation needs them. Decide them once per product and store them with the catalog item.
- Estimate refunds at issue. Carry the expected share as a refund liability and true it up against actual credit notes.
- Release deferrals as part of the close. The month cannot be locked until every tranche due in it has been recognized.
- Separate VAT from recognition. VAT is due when the invoice is issued or the advance is received, not when the service is delivered. The two schedules must be independent.
- Report the roll-forward. Opening deferred revenue, plus billings, minus revenue recognized, equals closing deferred revenue. Produce it every month.
- Keep MRR in an operating report. Compute it from active subscriptions and their normalized value. Do not derive it from the ledger, and do not let it feed the ledger.
How Nordlet automates the deferral
Nordlet's revenue recognition module implements the rules above as properties of ordinary invoice lines, so there is no separate subledger to reconcile.
Method on the line. Each line of a sales invoice accepts a recognition object with method set to point_in_time (the default, revenue at issue), ratable with a startDate and endDate, milestone with a list of percentages that sum to 100, or percent_complete. When the invoice is issued, the receivable and the VAT post in full, and the net of a deferred line is credited to deferred income instead of revenue.
Schedules are derived, not typed. A ratable line produces one tranche per calendar month, weighted by the days of service in that month. Every tranche is visible through sales/recognition-schedules/list with a status of pending, recognized or cancelled, so the deferred revenue balance can be explained to the cent.
Three triggers, no polling. Recognition posts when a period is locked (everything due through the period end is recognized first, so a month cannot be closed with unreleased revenue), when a delivery act is issued against a milestone line, and when a scheduled tranche falls due. A dry-run endpoint shows what a run would post before it posts.
Allocation and refunds. Setting a standalone selling price on every line allocates the invoice total across lines in proportion. Setting a refund estimate on a line credits that share to a refund liability at issue; later credit notes consume the liability before they touch revenue.
Subscriptions. An agreement with a monthly, quarterly or annual billing period generates each period's draft invoice with ratable lines already set, and a billing run sweeps every active agreement for periods that have fallen due. Short final periods are pro-rated by days.
The limits are documented as plainly as the features: schedules are fixed in euro at the issue-date exchange rate, the residual allocation method is not implemented, and significant financing components are out of scope. The software is capable of IFRS 15 and ASC 606 treatment; deciding which treatment a contract needs remains the company's judgement.
FAQ
What does SaaS accounting mean?
It means applying accrual accounting to a business that sells software access over time. The defining feature is that customers are invoiced, and often pay, before the service is delivered, so revenue is recognized as the service period passes and the undelivered part is carried as deferred revenue.
What are the SaaS accounting rules?
The governing standards are IFRS 15 (used in the EU and most of the world) and ASC 606 (United States). Both use the same five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate it across obligations by standalone selling price, and recognize revenue when or as each obligation is satisfied. For software access that means recognizing revenue over the subscription term.
Is deferred revenue the same as unearned revenue?
Yes. Deferred revenue, unearned revenue, deferred income and contract liability are different names for the same balance: amounts invoiced or received for services not yet delivered. IFRS 15 uses "contract liability"; EU statutory accounts usually say "deferred income".
Is MRR an accounting figure?
No. MRR is an operating metric: the normalized monthly value of active recurring contracts. It does not appear in any accounting standard or financial statement. Revenue is what the income statement shows, and it includes non-recurring items such as setup fees when they are earned.
Do small SaaS companies need to follow IFRS 15?
A company's statutory accounts follow the national GAAP of its country, which for EU companies is derived from the Accounting Directive and may permit simplifications for small entities. Investors, acquirers and auditors, however, expect subscription revenue to be deferred regardless of size, and most national frameworks require accrual accounting in any case. Recognizing the invoice as revenue is wrong under all of them.