Why deferred revenue is on every list
Deferred revenue is what you have billed but not yet earned. A customer pays for a year and you have delivered a quarter of it; the rest is a liability, money owed back in service. Auditing standards presume that revenue carries a risk of fraud, so the auditor tests it hard, and deferred revenue is where the testing starts. It is the balance that turns billing into revenue, and an error in it moves both the P&L and the balance sheet. If the difference between what you billed and what you earned is new to you, the article for your board walks through it with one invoice.
If you are preparing for an audit with one or two people in finance, the questions below are the ones you will be asked. None of them is difficult to answer if the answer already exists per invoice, and all of them are painful if it has to be reconstructed from a spreadsheet at year end.
The roll-forward
The first request is the roll-forward. The opening deferred revenue balance, plus what was billed in the period, less what was recognised, equals the closing balance. The auditor wants that as a schedule, and wants the closing balance to agree to the ledger.
What makes it hard is not the arithmetic. It is that a roll-forward only holds if every line in it comes from a real invoice with a real service period. A schedule built once a year from memory and a billing export tends not to agree to the ledger, and the difference has to be explained.
The contract behind each balance
The second question is: show me the contract. For a sample of balances, the auditor picks an invoice and asks for the agreement behind it. What did the customer buy, what period does it cover, and does the deferred amount at period end match the months still to deliver?
The auditor is testing whether recognition follows the agreement, as ASC 606 and IFRS 15 require, rather than the invoice date. If the answer is "we recognise when we invoice", the auditor will recompute the balance from the contracts and propose an adjustment. If a balance rests on what someone remembers rather than on a document, expect a note in the management letter.
Cut-off at period end
The third question is cut-off. Was every invoice dated in the period for a service that belongs to it? An invoice sent on 28 December for a service starting in January is December billing and January revenue. An invoice held back to 3 January for December work is the reverse. The auditor tests the last invoices before period end and the first ones after it, against the delivery or service dates the documents show.
Cut-off is where the most common revenue adjustments come from, and it is the easiest to get wrong under pressure to close a quarter.
The policy in writing
The fourth question is the policy. How do you recognise revenue, in writing? Straight-line over the service period, monthly or daily? Is there a floor below which you do not bother to defer? The auditor is not judging the policy so much as checking that you have one and apply it the same way to every contract. A stated policy that is followed is defensible. An unstated one that changes by invoice is not.
How a per-invoice finding answers all four
Ressura's Order-to-Cash module tests recognition invoice by invoice, judged against the standard for your jurisdiction, and the result is a finding with the agreement and the invoice behind each number.
The check that answers the auditor is Owed to customers. For every invoice, it reports what was billed, what should have been recognised by period end, and the balance still owed to customers at that date, which is the deferred revenue for that invoice. The service period comes from the agreement first. Where there is no agreement, it comes from what you tell Ressura about the term, and the finding says so, marked as resting on your answer rather than a document.
That shape answers the four questions in turn. The roll-forward is the sum of the per-invoice balances at two dates, with the billing and recognition between them. The contract behind each balance is already attached, because the finding was built from it. Cut-off is tested beside it, in the same module, against the service dates the documents give. And the policy is applied and stated: where you have a stated policy, or a floor below which a small timing difference is not raised, the finding applies it, says so, and cites the standard it judged against.
The finding body uses the auditor's words: recognised, deferred revenue, ASC 606 or IFRS 15. The headline uses yours. Either way the number is per invoice, recomputed, and you can check the arithmetic.
Owed to customers is the check that answers the auditor. Read what Order-to-Cash checks.