The short answer: a SaaS company earns subscription revenue as it provides access, not when it invoices or gets paid. An annual subscription paid upfront is recognised evenly over the 12 months, with the unearned part held as deferred revenue on the balance sheet. Set-up fees are usually spread too, usage fees are recognised as the customer uses the service, and sales commissions are often capitalised. GST works differently: it is generally due when you invoice or are paid, whichever comes first. And ARR is a useful KPI, but it is not revenue.
Billings, cash and revenue: three different numbers
Most SaaS founders track three numbers that sound alike but answer different questions:
| Number | What it measures | When it moves |
|---|---|---|
| Billings | What you have invoiced customers | When you issue an invoice |
| Cash collected | What customers have actually paid | When the money arrives |
| Revenue | What you have earned by delivering the service | As you provide access over the subscription period |
In a business where customers pay monthly, the three move together. Once you sell annual or multi-year plans paid upfront, they separate, sometimes by a lot. That gap is why a SaaS company can be cash-rich and loss-making at the same time, and it is the same idea we explain in cash flow vs profit.
Singapore companies recognise revenue under FRS 115 (or SFRS(I) 15 for listed groups), both based on the international standard IFRS 15. Small companies that use SFRS for Small Entities follow a simpler section, covered below.
The five-step model in plain English
FRS 115 asks five questions for every customer contract:
- Is there a contract? An agreement with enforceable rights, often your order form plus online terms.
- What have you promised? List each distinct deliverable: software access, onboarding, training, premium support.
- What is the price? The total the customer has committed to, adjusted for discounts, credits and any usage-based amounts you expect.
- How is the price split? Allocate the price across the deliverables, based on what each would sell for on its own.
- When is each part earned? Software access is usually earned evenly over time; a one-off service such as training is earned when it is delivered.
For a plain subscription, the answer is simple: one promise (access), one price, earned evenly. The complications come from everything sold around the subscription.
Annual prepaid subscriptions and deferred revenue
Take a startup with a 31 December year end. On 1 December 2026 it signs enterprise customers on 12-month plans totalling S$1.2 million, invoiced and paid upfront.
| At 31 December 2026 | S$ |
|---|---|
| Billings in December | 1,200,000 |
| Cash collected | 1,200,000 |
| Revenue for FY2026 (1 month of 12) | 100,000 |
| Deferred revenue on the balance sheet | 1,100,000 |
The S$1.1 million is a contract liability: you owe the customer 11 more months of service. It is released to revenue at S$100,000 a month through 2027. Investors and lenders like deferred revenue because it shows contracted future income, but it is not profit you can distribute.
Multi-year prepayments. If a customer pays upfront for more than a year, FRS 115 may treat part of the price as financing, because you are effectively borrowing from the customer. A practical expedient lets you ignore this when the gap between payment and service is one year or less, which covers most annual plans. For two- or three-year upfront deals, look at why you ask for payment upfront. If the terms exist mainly for reasons other than financing, for example to manage renewal risk and admin costs, there may be no financing component to account for; the standard’s illustrative examples include a three-year upfront support contract that reaches this conclusion. Discuss the analysis with your auditor.
Set-up fees, implementation and bundles
Set-up and onboarding fees. A one-off fee to provision an account or configure the platform usually doesn’t give the customer anything useful on its own; it only makes the subscription work. In that case the fee is not revenue on day one. FRS 115 treats it as an advance payment for the subscription and spreads it over the period the service is provided. The period runs beyond the first term only if customers can renew without paying the fee again and that renewal option gives them a material right, meaning a benefit they would not get without signing the original contract. If the fee is nominal, the renewal price is your normal price, and there is no material right, the fee is simply spread over the first term. The standard’s own illustrative example of a set-up fee for a one-year processing service reaches exactly that answer.
Implementation services. Data migration, integration work or training is a separate deliverable only if two tests are met: the customer can benefit from it on its own or with resources readily available to it (a strong sign is that other providers routinely do the same work), and it is separate from the other promises in the contract. Then that part of the price is recognised as the work is done. If the work significantly modifies or customises the software, or you are integrating everything into one combined output, it is combined with the subscription and recognised over time.
Bundles and discounts. If you sell a package (subscription plus training plus premium support) at a discount, the discount is normally spread across all the elements in proportion to their standalone prices. You can put the whole discount against one element only in narrow cases: when you regularly sell each item on its own, regularly sell part of the bundle at a similar discount, and that pattern shows which element the discount belongs to.
Usage pricing, free months, ramps and credits
- Usage-based fees (per API call, per transaction, per seat added mid-term) are generally recognised in the month the usage happens.
- Free months. If a customer commits to 12 paid months and gets 2 free, the total price is earned over all 14 months of access, not just the paid ones.
- Ramp pricing. A price that steps up each year for the same service is often spread evenly over the committed term, unless the higher price reflects more service delivered.
- Service credits and refunds. Expected uptime credits, refunds or price concessions reduce revenue; estimate them rather than waiting until they are claimed.
Sales commissions
Commissions paid to sales staff or agents only because a contract was signed are costs of obtaining a contract. Under FRS 115, if you expect to recover them, you capitalise them and amortise them over the period you benefit from the contract, which can include renewals you expect. The standard’s example amortises a commission on a five-year contract over seven years because two one-year renewals are anticipated. A practical expedient lets you expense them straight away if that period would be one year or less. Costs you would have incurred anyway, such as travel to pitch or discretionary bonuses based on overall targets, are not incremental and are expensed.
Many early-stage startups simply expense commissions. That is fine while amounts are small, but once commissions on multi-year or renewing contracts become material, expect your auditor to ask for a capitalisation policy.
GST and corporate tax timing
GST follows invoices and cash, not revenue. Under IRAS’s time of supply rules, a supply is generally treated as made at the earlier of when an invoice is issued or when payment is received. IRAS applies the same rule to services supplied continuously with periodic payments. So if you invoice a S$120,000 annual plan in December, GST on the full invoice generally goes into that quarter’s GST return, even though only S$10,000 is December revenue. Plan your cash for the GST bill, and reconcile GST-reported supplies to billings, not to revenue. Our guide to how GST works covers registration and returns.
Corporate income tax broadly follows the accounts. IRAS has an e-Tax Guide on the tax treatment arising from adopting FRS 115, and in most cases taxable revenue follows the accounting timing. There are exceptions, so ask your tax adviser to check any unusual contract terms in your tax computation.
ARR and MRR versus revenue
MRR (monthly recurring revenue) and ARR (annual recurring revenue, usually MRR × 12) are snapshots of your subscription run-rate. They are excellent operating KPIs, and investors ask for them, but they are not accounting numbers: there is no standard definition, they ignore one-off fees, and they count the future, not the past.
Show both in your investor updates and board packs, clearly labelled, and reconcile ARR to revenue so nobody confuses them. Due diligence teams will rebuild revenue from your contracts, so a clean reconciliation saves time; see preparing for a financing round and the financial metrics to monitor. For how FRS 118 changes the layout of the profit and loss statement from 2027, see our FRS 118 guide.
Small companies on SFRS for Small Entities
Many early-stage startups qualify for SFRS for Small Entities, a simpler framework based on the IFRS for SMEs standard. The ASC issued its Third Edition on 18 August 2025, effective for annual periods beginning on or after 1 January 2027, and it includes a revised revenue section aligned with the international IFRS for SMEs third edition. For a typical subscription business the result is usually the same in practice: access is earned evenly over the subscription period. Check the disclosure differences with your accountant if you are switching frameworks, and note that investors raising larger rounds often expect full FRS accounts.
A monthly close checklist for SaaS
- Keep a subscription schedule: customer, start and end dates, price, billing terms, set-up fees.
- Release deferred revenue each month from the schedule, and tie the deferred revenue balance to it.
- Record usage revenue from your platform data for the month, not when it is invoiced.
- Review new contracts for set-up fees, free months, ramps, bundles and non-standard terms.
- Accrue expected credits and refunds against revenue.
- Capitalise and amortise commissions once they are material, per your policy.
- Reconcile GST output tax to billings, not revenue.
- Reconcile ARR and MRR to revenue in the management pack.
Frequently asked questions
When should a SaaS company recognise revenue from an annual subscription?
Evenly over the subscription period. If a customer pays S$120,000 upfront for 12 months, you recognise S$10,000 a month; the rest sits on the balance sheet as deferred revenue.
Is ARR the same as revenue?
No. ARR is a run-rate snapshot, usually MRR × 12. Revenue is what you actually earned in the period under the accounting standards, and in a growth year the two can be very different.
How should set-up or onboarding fees be recognised?
If the set-up work isn’t a separate service the customer can benefit from, the fee is an advance payment for the subscription and is spread over the period of service. That period extends beyond the first term only if the renewal option gives the customer a material right. Distinct implementation work can be recognised as it is performed.
When is GST due on an annual subscription?
Generally at the earlier of the invoice or the payment. Invoicing a full year upfront puts GST on the whole invoice into that period’s return, even though revenue is spread.
Do sales commissions have to be capitalised?
Under FRS 115, incremental commissions you expect to recover are capitalised and amortised over the benefit period. You can expense them immediately if that period is one year or less.
The bottom line
For a SaaS business, revenue is earned by keeping the lights on for your customers, month after month. Invoices and cash tell you about funding and GST; revenue tells investors and auditors what you have actually delivered. Get a subscription schedule in place early, release deferred revenue monthly, and keep ARR clearly separate from revenue, and your first audit and your next fundraise will both go more smoothly.
Sources: IRAS — When to report supplies in GST returns (time of supply rules); IRAS — e-Tax Guide: Tax Treatment Arising from Adoption of FRS 115 or SFRS(I) 15; ACRA — Singapore Financial Reporting Standard for Small Entities; ASC — FRS 115 Revenue from Contracts with Customers and Illustrative Examples (paragraphs 27–29, 35, 62–63, 81–82, 85, 91–94, 99, B40, B48–B49; Examples 11, 30, 36, 37 and 53); IFRS Foundation — IFRS 15 Revenue from Contracts with Customers. This article is general information, not professional advice for your company’s situation.