SaaS revenue recognition determines when a software business records revenue as it provides the promised service. Billing and cash collection can follow different schedules, which is why an annual payment does not necessarily become revenue in the month it arrives.
A standard subscription is a useful starting point. The buying test for software should also include the contracts that depart from it.
How does a simple annual subscription work?
Consider an illustrative €12,000 contract for twelve months of service beginning on 1 January, billed upfront. Assume one performance obligation, an even service pattern over twelve equal monthly periods, no tax and no other complications.
Under those assumptions, the schedule recognises €1,000 each month. The invoice may create a receivable before the customer pays; the unearned part of the billed amount remains deferred until the business provides the related service.
At the end of January, the example has €1,000 of recognised revenue and €11,000 remaining on the revenue schedule. Cash depends on when the customer pays. Those figures answer different questions and should remain distinct.
The example illustrates a simple pattern, rather than prescribing the treatment of every SaaS contract. The IFRS 15 framework starts with the contract and its obligations; finance must determine the appropriate treatment for the actual terms.
Which contract terms need closer attention?
A subscription may include implementation services, usage charges, discounts or an option to buy more services later. Finance needs to assess those terms under the relevant accounting framework before configuring a schedule.
An amendment can change the work too. A mid-term upgrade, extension or cancellation should reach both the billing process and the revenue review. Updating the invoice alone may leave the original schedule running unchanged.
Choose the least standard contracts from the last year for a software demonstration. Ask the vendor to show the approved treatment, the schedule and the handling of a subsequent amendment.
How should billing, cash and revenue connect?
Use stable references from the agreement through invoices, credit notes, receipts and revenue postings. Finance should be able to trace each event without treating them as interchangeable.
The order to cash guide covers the operational sequence. The revenue recognition software guide focuses on schedules, changes and ledger reconciliation.
At close, reconcile the relevant opening position, activity, adjustments and closing balance. Keep explanations for manual changes so another reviewer can understand why the schedule moved.
Where does ARR fit?
ARR describes the business's recurring revenue run rate under its chosen definition. It is not the same as revenue recognised during a reporting period or cash collected that month.
Document what the ARR calculation includes and excludes. A management reporting pack should explain the bridge to accounting revenue rather than imply that any difference is an error.
How can Light support the process?
Light's subscription management product connects contract information, billing and revenue schedules with the ledger. Its documented templates support revenue recognition workflows under IFRS 15 and ASC 606.
Bring the actual contract patterns and approved policies to the evaluation. Inspect an amendment, a manual adjustment and a closed-period correction, as well as the standard subscription. The strongest demonstration is one the finance team can reconcile and explain without a separate reconstruction afterwards.
