How much of your first audited year is already sitting in deferred revenue?

The first audit starts on the first day of the year.

Most first audit preparation for a subscription business goes into the year being audited: contracts, performance obligations, the rollforward from January to December. That work is right. The balance that most often holds the audit up sits one line above it, on the opening row of that rollforward, and it was produced in a year nobody audited.

The auditing standards are direct about it. AU-C section 510 paragraph .08 requires the auditor in an initial engagement to obtain sufficient appropriate audit evidence about whether the opening balances contain misstatements that materially affect the current period’s financial statements, including whether they reflect appropriate accounting policies. Paragraph .15 says what happens if that evidence cannot be obtained: a qualified opinion or a disclaimer. ISA 510 says the same in paragraphs 6 and 10.

For most balances some of that evidence arrives on its own. AU-C 510.A13 points out that the collection of opening receivables during the year provides some evidence about them. Deferred revenue works differently. It clears by being recognised as revenue, and revenue is the number under audit. Every dollar in the opening balance becomes current year revenue or stays deferred into the next year, so an error in that balance moves straight into the income statement the auditor is signing.

A worked example, run through our calculator.

To size it, we built a small example book and ran every contract through the published schedule logic of the revenue recognition calculator on this site. Twelve customers sign during 2025, one on the first of each month, each at 120,000 dollars a year invoiced annually in advance. In 2026 all twelve renew on their anniversaries and twelve new customers sign on the same pattern, so the book doubles. The company’s first audit is for calendar 2026.

The rollforward itself is ordinary: opening plus invoicing minus recognition equals closing. The number worth looking at is the fourth row. Of 2,220,000 dollars recognised in the audited year, 660,000 dollars came out of a balance that was set in 2025. That is 29.7 percent of the revenue line resting on a figure the auditor has to test from scratch, and it is the growth case. If the same book had only renewed, 2026 revenue would be 1,440,000 dollars and the opening balance would be 45.8 percent of it.

Now take the most common way that opening balance goes wrong in a company that has not been audited before: annual invoices credited straight to revenue when they were raised. The table below shows what that does to the year under audit.

The error runs in both directions from the same cause, and the size is the same either way: the unearned portion of last year’s invoices. That is why a first audit spends time on a balance from before the audit period, and why rebuilding that balance at contract level before fieldwork is the single most useful piece of preparation a subscription business can do.

Billing terms decide how much rides on it.

The proportion is not a property of software companies in general. It follows from how far ahead of delivery you invoice. Running the same twelve customers through the calculator under different billing terms, with the book flat so that only the terms change, gives a clean view of it.

Two things stand out. Contract length on its own changes nothing: a three year term invoiced annually looks exactly like a one year term, because the balance only holds what has been invoiced and not yet delivered. And multi year prepayment changes everything. A company that collected three years upfront in 2025 enters its first audit with the whole of the next year’s revenue already sitting in the opening balance, which is excellent for cash and makes the contract level schedule the most important document in the audit file.

The calculator recognises in whole months from the first of the month, so a real book with mid month starts will land a little differently. The shape holds. If you invoice annually in advance and sign evenly through the year, expect a figure in the region of 40 to 50 percent when the book is steady, lower when it is growing fast.

What you disclose, and what you compute anyway.

Both revenue standards turn this figure into a disclosure. ASC 606-10-50-8 asks for the opening and closing balances of receivables, contract assets and contract liabilities, for revenue recognised in the period that was included in the contract liability balance at the beginning of the period, and for revenue recognised from performance obligations satisfied in previous periods. Paragraph 50-10 adds an explanation of significant changes in the balances. IFRS 15 says the same in paragraphs 116 and 118.

For a private US company there is relief, and it is worth knowing its exact edges. Paragraph 606-10-50-11 lets an entity other than a public business entity, certain not for profit entities and certain employee benefit plans elect not to provide the disclosures in 50-8 to 50-10. It then adds a floor: an entity taking the election still discloses the opening and closing balances in 50-8(a), if they are not presented elsewhere. A parallel election in 606-10-50-16 covers the remaining performance obligation disclosure. IFRS 15 has no equivalent, so an IFRS reporter discloses the 116(b) figure regardless of ownership.

The practical reading for a private company in its first audit: the election can take the 50-8(b) figure out of your notes, and it cannot take the opening balance out of the audit. You will want the figure anyway. For revenue that runs through deferred revenue, the amount released from the opening balance plus the amount earned on this year’s invoices has to equal the total, and if it does not, something in the schedule is wrong. That check takes a minute on a contract level schedule and cannot be done at all on a single ledger balance.

One presentation point belongs here too. Paragraph 606-10-45-1 presents a contract as a contract asset or a contract liability depending on whether performance or payment came first, and 45-3 defines the contract asset. A contract where recognition has overtaken invoicing is a contract asset. Netting it inside deferred revenue makes the liability look smaller and hides the asset, and it is the kind of thing a contract level schedule surfaces straight away.

# One contract in a deferred revenue schedule, shaped for a first audit.
# A worked example of structure. No real customer, contract or company.

contract:
  number: RC-2025-0012
  customer: CUST-0412
  currency: USD
  recognition_method: STRAIGHT_LINE
  deferred_revenue_account: 2400
  revenue_account: 4000

invoices:
  - number: INV-2025-1207
    invoice_date: 2025-12-01
    # Two dates, deliberately. Recognition follows the service period.
    service_start: 2025-12-01
    service_end: 2026-11-30
    amount: 120_000.00

rollforward_2026:
  opening: 110_000.00        # eleven months still to deliver on 1 January
  additions: 120_000.00      # the renewal invoiced on 1 December 2026
  recognised: 120_000.00     # 110,000 from the opening balance, 10,000 from the renewal
  adjustments: 0.00
  closing: 110_000.00        # opening + additions - recognised + adjustments

  # The figure ASC 606-10-50-8(b) and IFRS 15.116(b) ask for,
  # derived per contract and summed across the schedule.
  recognised_from_opening: 110_000.00

  # Recognition ahead of invoicing would show here as a negative
  # closing, which 606-10-45-3 presents as a contract asset.
  over_recognised: false

How we build the rollforward in Rivane.

Our deferred revenue rollforward is built the way this article argues for, and it is worth being specific about what that means today. The report runs by contract and by month. Every figure on it is derived from posted journal lines on that contract’s deferred revenue account rather than from the schedule: additions are the credits from invoices linked to the contract, recognitions are the debits from the monthly recognition run, and adjustments are the entries posted against that contract. The opening balance is the net of everything posted to the contract before the window, so the opening row of one year is the closing row of the last by construction.

A few design choices do real work in an audit. A revenue contract cannot be saved without both a deferred revenue account and a revenue account, so there is no contract whose postings land somewhere unknown. A manual adjustment to deferred revenue posts as a balanced entry against a contract, is refused if its period is locked, and records the reason and the person who made it. A closing balance that goes negative is shown as negative and flagged as over recognised, rather than rounded to zero, which is how a contract asset candidate becomes visible. Contracts in different currencies roll forward in separate sections and are never added together. Both views export to CSV.

Two limits, stated plainly. Recognition is straight line only today: a contract set to milestone or proportional recognition is refused when it is created rather than being quietly straight lined. And the report does not print the 50-8(b) figure as its own column. It shows opening and recognised side by side for every contract, and for straight line contracts invoiced in advance the figure is the smaller of the two on each line, summed. A balance brought over from a previous system has to arrive against individual contracts to appear in the report, which is the same discipline this article recommends for any opening balance.

What to do before fieldwork.

• Build the opening deferred revenue balance contract by contract, as at the first day of the year under audit, and tie the total to the general ledger account on that date. This is the schedule AU-C 510.08 and ISA 510.6 are ultimately asking about, and it is the one teams most often have only as a single number.
• For every contract in that schedule, hold the invoice, the service start date, the service end date and the amount. Those four facts are enough to recompute a straight line balance, and recomputation is the most direct evidence there is for a liability that clears into revenue.
• Recompute the balance yourself before the auditor does. Run each contract through a schedule from its service start and compare the deferred amount at the opening date with what the ledger carries. Differences at this stage are cheap. The same differences found in fieldwork become adjustments with a paper trail.
• Check how last year’s invoices were booked. If any were credited straight to revenue, the opening balance is understated by whatever was still unearned at year end, and the current year will be short by the same amount unless it is corrected in the right period.
• Produce the rollforward for the year under audit from the same contract list: opening, additions from invoices, revenue recognised, adjustments, closing. The closing balance of one year is the opening of the next, so building it once at contract level pays for every later year too.
• Compute the portion of this year’s revenue that came out of the opening balance, even if you will not disclose it. It is the fastest reasonableness check on the revenue line, and an IFRS reporter or a public business entity has to disclose it anyway.
• Decide your ASC 606 disclosure elections early if you are a private company. Paragraph 606-10-50-11 lets you omit 50-8 to 50-10 except the opening and closing balances, and 606-10-50-16 lets you omit the remaining performance obligation disclosure. Your auditor will want to know which you are taking before they plan their work.
• Look for contracts where recognition has run ahead of invoicing. Paragraph 606-10-45-3 presents those as contract assets, so a negative deferred balance on a contract belongs on the other side of the balance sheet rather than netted inside the liability.

Where this goes wrong, and how to see it coming.

• Preparing the current year rollforward and treating the opening figure as given. The auditor has to get comfortable with that figure under AU-C 510 before the revenue line can be relied on, so an opening balance with no contract level support leaves the audit waiting on the one schedule that was never built.
• Holding deferred revenue as a single ledger balance that is trued up to a spreadsheet at year end. It ties at the moment of the true up and cannot say which contracts it belongs to, which means it cannot be recomputed and the 50-8(b) figure cannot be derived.
• Starting recognition on the invoice date instead of the service start date. On an annual invoice raised on 15 December for a service year starting on 1 January, that pulls half a month of revenue into the wrong year on every contract billed that way.
• Netting contracts that are ahead of invoicing against contracts that are behind. The total can look fine while one contract asset hides inside the liability, and 606-10-45-1 asks for the two to be presented separately.
• Letting manual adjustments to deferred revenue arrive as plain journals with no link to a contract. Each one becomes a question in fieldwork. An adjustment that names its contract, its period and its reason answers the question before it is asked.
• Assuming the private company election removes the work. It removes a disclosure. The opening balance still has to be supported, and the figure the election lets you leave out is one you need internally to sanity check the year.

Data and system considerations.

• Link every invoice line that creates deferred revenue to the contract it belongs to. Without that link, additions in the rollforward can only be reported in total, and the per contract opening balance of the following year is impossible to build.
• Store the service period on the invoice line as two dates. The invoice date is when the right to bill arose. The service period is what recognition follows. Keeping one date for both is the root of most cut off errors in subscription revenue.
• Derive the rollforward from posted ledger lines rather than from the schedule. A schedule shows what should have happened. The ledger shows what did. When the rollforward is built from the ledger and split by contract, a difference between the two is visible on the contract where it arose.
• Keep currencies apart. A group invoicing in several currencies should roll forward each currency on its own and translate at the end. Adding balances in different transaction currencies before translation produces a total that nobody can recompute.
• Make the recognition method explicit on each contract, and fail closed when the system cannot compute it. A contract marked as milestone based and quietly recognised straight line gives the wrong revenue every month with nothing to show that anything is wrong.
• Keep an opening balance brought over from a previous system at contract level. A single migration journal to deferred revenue gives the right total on day one and no way to recompute it afterwards, which is exactly the property the first audit tests.

The evidence file for deferred revenue.

• The opening balance schedule by contract as at the first day of the year under audit, tied to the ledger, with the invoice, service period and amount behind each line.
• The rollforward for the year by contract and by month: opening, additions, revenue recognised, adjustments and closing, with the closing total tied to the ledger at each month end you close.
• For each addition, the invoice it came from. For each recognition entry, the contract and period it belongs to. For each adjustment, the reason, who made it, and the period it was posted in.
• The 50-8(b) figure, revenue this year that came from the opening balance, computed from the contract schedule, whether or not you disclose it.
• A list of contracts where cumulative recognition has overtaken cumulative invoicing, which are the contract asset candidates under 606-10-45-3.
• Your disclosure election memo if you are a private company applying 606-10-50-11 or 50-16, and the policy note describing when revenue starts for each type of contract.

Questions worth asking this week.

• Could we list every contract that makes up our deferred revenue balance at the start of this year, and would the list add up to the ledger?
• Were any invoices last year credited straight to revenue, and if so, how much of them was still unearned at year end?
• Does recognition on our annual contracts start from the invoice date or from the service start date?
• How much of this year’s revenue came out of the opening deferred balance, and does that proportion look right against how we bill?
• Are any contracts ahead of billing, and where do they sit on the balance sheet today?
• If we are a private company, which ASC 606 disclosure elections are we taking, and does our auditor know?

A balance you can recompute is a balance you can show.

The encouraging part of all this is how finite it is. The opening deferred revenue balance is a list of contracts, each with an invoice, a service period and an amount. Build that list once, tie it to the ledger, and the hardest question in a first subscription revenue audit becomes a recomputation the auditor can repeat. Every later year gets the benefit, because this year’s closing row is next year’s opening row.

If you want a quick way to see the shape of your own balance, take one annual contract invoiced late last year and put it through the Rivane revenue recognition calculator. It shows the deferred balance month by month, which tells you how much of that invoice was still unearned on the first day of the year. Do the same for your largest ten contracts and you will have a good estimate of how much of this year’s revenue depends on last year’s books. It runs in the browser and it is free to use.

Sources

• FASB Accounting Standards Update No. 2014-09, Revenue from Contracts with Customers (Topic 606), Section A. The PDF was downloaded from FASB and read directly. Source for the presentation of a contract as a contract asset or a contract liability in paragraphs 606-10-45-1 to 45-3, for the contract balance disclosures in 606-10-50-8, including 50-8(b), revenue recognised in the period that was included in the contract liability balance at the beginning of the period, for the explanation of significant changes in 606-10-50-10, for the election in 606-10-50-11 that lets an entity other than a public business entity and the other named entities omit 50-8 to 50-10 while still disclosing the opening and closing balances in 50-8(a), and for the remaining performance obligation disclosure, its one year practical expedient and the matching private company election in 606-10-50-13 to 50-16.
• IFRS 15 Revenue from Contracts with Customers, as adopted in the EU by Commission Regulation (EU) 2016/1905, read on EUR-Lex. Source for paragraph 116, which requires the opening and closing balances of receivables, contract assets and contract liabilities, revenue recognised in the period that was included in the opening contract liability, and revenue recognised from performance obligations satisfied in previous periods, for paragraph 118 on explaining significant changes in the balances, and for paragraphs 120 to 122 on remaining performance obligations and the one year practical expedient. IFRS 15 carries no private company election equivalent to 606-10-50-11.
• AICPA Professional Standards, AU-C section 510, Opening Balances: Initial Audit Engagements, Including Reaudit Engagements, from the 2025 compilation of the clarified US auditing standards. Downloaded and read. Source for paragraph .08 on the evidence the auditor must obtain about opening balances, paragraph .15 on the qualified opinion or disclaimer that follows when that evidence cannot be obtained, and paragraph .A13 on how the collection of opening receivables provides some evidence about them during the current period.
• International Standard on Auditing 510, Initial Audit Engagements: Opening Balances, IAASB handbook edition. Downloaded and read. Source for the equivalent international requirements in paragraphs 6 and 10 and the application material in A6 and A8.
• Truewind, Deferred Revenue Accounting Guide: Rollforward, ASC 606 and Edge Cases. Read as one of the current top answers to this question. It covers the rollforward formula, journal entries and SaaS billing patterns well, and does not address opening balances in a first audit or the 50-8(b) figure.
• Ordway, Revenue Recognition Audit Preparation for Finance Leaders. Read as a second current answer. It gives a useful documentation checklist for a revenue audit and likewise does not address the opening balance or the 50-8(b) disclosure.
• Rivane revenue recognition calculator, published on this site. Every figure in the worked example and the billing terms table was produced by running its published schedule logic, which recognises a contract straight line by month and carries the rounding remainder into the final period.

A note on how this was researched. Every paragraph reference to ASC 606 comes from ASU 2014-09 as issued, downloaded from FASB and read as text. They are quoted as issued, so check the current Codification for later amendments before relying on the exact wording. The IFRS 15 references come from the EU adopted text on EUR-Lex. AU-C 510 and ISA 510 were downloaded and read. The two practitioner guides are cited only to describe what current answers to this question cover. No suitable public posts on X were found on this topic during research, so none are embedded. Every figure in the example tables was produced by running the published logic of the revenue recognition calculator on this site against the example book described, which is synthetic and describes no real company, customer or contract. Statements about Rivane describe what is built and shipped today, including the straight line only limit. Rivane has no public customers to cite and none are implied. Nothing here is audit, accounting or legal advice, and your own auditor decides what they need from you.