What the standard says, read from the text.
Most current answers, such as Breaking Into Wall Street and Zenskar, book receivables and deferred revenue together on the day the invoice goes out. That is how most billing systems post, and for an invoice due on receipt it gives the right answer. The standard ties the timing to something else: when the customer has to pay.
IFRS 15 paragraph 106says a contract liability arises “when the payment is made or the payment is due (whichever is earlier)”. Paragraph 108 calls a receivable a right to consideration that is unconditional, and it is unconditional once only the passage of time stands between you and the due date. A receivable can exist even if the amount might be refunded later.
Example 38 then works it through. A product is due to the customer on 31 March, and 1,000 is payable in advance on 31 January. On a non-cancellable contract the entity records the receivable and the contract liability on 31 January, the due date. Paragraph IE200 adds the case most SaaS teams meet: if the invoice went out before 31 January, the entity would not present the receivable and the contract liability gross, because its right to the money is not yet unconditional. On a cancellable contract, nothing is recorded until the cash comes in.
| At the balance sheet date | What you show | Where it comes from |
|---|---|---|
| Non-cancellable, invoice due on or before the balance sheet date, unpaid | Receivable and deferred revenue, both shown | IFRS 15 IE199 |
| Non-cancellable, invoice sent but not yet due | Neither shown gross | IFRS 15 IE200 |
| Cancellable, unpaid | Nothing until the cash arrives | IFRS 15 IE198 |
| Paid in advance, any contract | Cash and deferred revenue | IFRS 15 paragraph 106 |
One year end, six renewal invoices.
The common trigger is the renewal invoice. Many SaaS companies send it a month ahead so the customer has time to process it, with payment due on the renewal date. At a December year end, every January renewal is an invoice that has gone out and is not yet due.
The example company
A SaaS company closes its year on 31 December 2026.
Every contract is annual, non-cancellable, invoiced in
advance. Renewal invoices go out 30 days before the
renewal date and are due on the renewal date.
Revenue for 2026 4,200,000
January 2027 renewals, invoiced in December,
due in January, none paid by 31 December
Customer 1 120,000
Customer 2 96,000
Customer 3 96,000
Customer 4 84,000
Customer 5 72,000
Customer 6 72,000
-------
540,000
A December renewal, due 1 December, still unpaid
Invoice 96,000
Revenue recognised in December 8,000
Still deferred 88,000
The rest of the book at 31 December
Receivables past their due date 214,000
Deferred revenue on earlier invoices 1,180,000
Cash 1,650,000
Other current assets 60,000
Payables and accruals 340,000Every customer, date and amount is an example. The point is the timing, and the timing is ordinary.
The same company, two balance sheets.
| Posted on the invoice date | Shown by due date | |
|---|---|---|
| Accounts receivable | 850,000 | 310,000 |
| Deferred revenue | 1,808,000 | 1,268,000 |
| Revenue for 2026 | 4,200,000 | 4,200,000 |
| Days sales outstanding | 73.9 days | 26.9 days |
| Current ratio | 1.19 | 1.26 |
Revenue does not move, because both sides of the entry sit on the balance sheet. Everything built on those two lines does. 540,000 is 64% of the receivables on the left, and none of it is money any customer was yet required to pay. Days sales outstanding reads 73.9 days against 26.9. Deferred revenue jumps by the same 540,000, which a board pack can easily read as growth in contracted revenue.
It also reaches the audit. Receivables are often tested by confirming balances with customers, and here six of those balances are invoices the customers do not owe until January. An aging report shows them as current, so any allowance built from aging sits on a larger base than it should.
The December renewal is different. It fell due on 1 December, so the 96,000 receivable is real even though it is unpaid, and so is the 88,000 still deferred. That one stays on both sides.
The entries, without changing how you bill.
You do not need to hold invoices back or post them on their due dates. Keep billing as you do, and add one presentation entry at each balance sheet date for invoices issued and not yet due on non-cancellable contracts.
Posting by invoice date, presenting by due date
2 December, renewal invoices sent (as most systems post them)
Dr Accounts receivable 540,000
Cr Deferred revenue 540,000
31 December, year end presentation entry
Invoices issued, not yet due, non-cancellable
Dr Deferred revenue 540,000
Cr Accounts receivable 540,000
1 January, reverse the presentation entry
Dr Accounts receivable 540,000
Cr Deferred revenue 540,000
Each due date in January
Nothing to post. The receivable is now real.
Each month from January
Dr Deferred revenue 45,000
Cr Revenue 45,000
(540,000 / 12)
The December renewal is left alone at year end.
It was due on 1 December, so the 96,000 receivable
and the 88,000 still deferred are both shown.The 31 December entry comes from a list: open invoices whose due date is after the balance sheet date, with their contracts checked for a cancellation right. Reversing it on 1 January puts the ledger back to the state your billing system expects, so collections in January clear the receivables as usual. If any of those contracts can be cancelled before the term starts, take those invoices out the same way and keep them out until they are paid.
Three checks at each quarter and year end.
- The not yet due list ties to the aging report’s not yet due column on non-cancellable contracts: 540,000 here.
- Deferred revenue after the presentation entry equals the sum of the contract schedules for invoices that are paid or due: 1,268,000 here.
- Every contract with a right to cancel before the term starts is flagged in the billing system, so its unpaid invoices never reach the balance sheet.
How Rivane posts contract invoices today.
In Rivane, an invoice linked to a revenue contract posts straight to that contract’s deferred revenue account rather than to revenue, so billing never puts a full year into the income statement at once.
Contract invoices in Rivane, as built
# Contract invoices in Rivane, as built.
invoice a sales invoice linked to a revenue contract
posts Dr accounts receivable
Cr the contract's deferred revenue account
dated the invoice date
refused if the linked contract cannot be found or
has no deferred revenue account
recognise a monthly run releases deferred revenue
straight line by calendar month; the final
month takes the rounding remainder so the
contract releases exactly its total
reconcile a check per contract compares the deferred
balance in the ledger with the contract
schedule and reports any differenceIn the example, each January renewal posts receivable and deferred revenue on the day it is sent, in December. The monthly run then releases 45,000 a month from January, and the reconciliation check, run for a contract, reports any difference between its deferred balance in the ledger and its schedule.
Some limits, as of today. Rivane posts on the invoice date and does not look at the due date or at any cancellation clause when it does. The year end presentation entry is a manual journal you post and reverse yourself, built from the open invoices with a due date after the balance sheet date. Recognition is straight line by month only.
The short version.
Show an unpaid annual invoice on both sides once it is due on a non-cancellable contract. Before the due date, take it off both sides at the balance sheet date. On a cancellable contract, wait for the cash. Revenue is the same every way; your receivables, deferred revenue and the ratios built on them are not.
To see how Rivane runs contract schedules and deferred revenue, read Rivane revenue recognition.
Frequently asked questions.
Does grossing up an unpaid invoice change revenue?
No. Both sides of the entry are on the balance sheet, receivable and deferred revenue, so revenue for the year is the same either way. What changes is the size of receivables and deferred revenue, and every figure built on them, such as days sales outstanding, the current ratio and an aging report.
Can we keep posting invoices on the date we send them?
Yes. The billing system needs the invoice, and the customer needs to see it. Keep posting as you do, then at each balance sheet date post one entry that takes invoices issued but not yet due off both receivables and deferred revenue, and reverse it on the first day of the next period.
What if the contract can be cancelled before the term starts?
Then there is no receivable until the customer pays, even after the due date passes. In IFRS 15 Example 38, Case A, the entity records nothing for the cancellable contract until the cash arrives, and then records cash and a contract liability.
Is US GAAP different?
The model is shared. ASC 606 carries its own Example 38 on contract liabilities and receivables, at 606-10-55-284 to 55-286, with the same cancellable and non-cancellable cases. Check the wording with your auditor, since this article quotes the IFRS text.
Sources
- IFRS 15, the examples published with the standard, Example 38, Contract liability and receivable, paragraphs IE198 to IE200 (2026 issued text, read directly). Case A is a cancellable contract, Case B a non-cancellable one, and IE200 covers an invoice issued before the due date.
- IFRS 15 Revenue from Contracts with Customers, paragraphs 105 to 108 (2026 issued text, read directly). A contract liability arises when payment is made or due, whichever is earlier; a right to consideration is unconditional if only the passage of time is required before payment is due.
- Deloitte, Revenue Recognition Roadmap, Codification example index. Places the US GAAP version of Example 38 at ASC 606-10-55-284 (cancellable) and 55-285 to 55-286 (non-cancellable).
- Breaking Into Wall Street, SaaS Accounting: Bookings, Billings, Revenue, Deferred Revenue, and Accounts Receivable. Read as a current answer.
- Zenskar, Deferred Revenue in SaaS. Read as a current answer.
A note on how this was researched. IFRS 15 and the examples published with it were read from the IFRS Foundation’s published text, not from a summary. The FASB text of ASC 606 was not available to read for this article, so the US GAAP reference is to where Deloitte’s index places the matching example. The two current answers were read as they stand today. The company, the customers and every amount are examples. The Rivane section describes the product as built today, checked against the invoicing and revenue recognition code rather than marketing copy. This is not accounting advice for your specific case.
On embedded social posts: we looked for public posts from standard setters or practitioners on presenting unpaid advance invoices and found none we could verify as current and relevant, so this article uses ordinary citations instead.