Back to Glossary

Entry · Accounting

Deferred Revenue Release Check

Deferred revenue release check is a review of whether a contract liability for promised future goods or services was reduced, and revenue recognised, in the right amount and period as obligations were satisfied. It compares the contract, performance evidence, schedule and ledger.

Receiving cash is not by itself the trigger for earning revenue, and detailed treatment depends on the applicable standard.

From the Money Master HQ dictionary, founded by Shihan Sheriff (FCMA, VP of Finance at Nomod, CFO at Esanjo Ventures). How these definitions are written.

What it means

A customer pays for twelve months of service in advance, so cash arrives now but the business may still owe service over future months. A deferred revenue release check verifies that reductions in the liability and recognised revenue follow the contract and actual performance.

IFRS describes recognising revenue when or as performance obligations are satisfied, and Sage Intacct documents recognition schedules as a system mechanism, but this entry is a control concept, not a substitute for IFRS, US GAAP or a contract-specific accounting assessment. Identify the contract by matching the advance receipt or invoice to the right customer, service term, transaction price and promised goods or services.

Determine the obligation, since a contract may include access, implementation, support or equipment with different performance patterns and not all amounts should be spread evenly by habit. Set the start date and schedule: revenue release may begin on service activation, delivery or another justified performance event, not automatically on payment date, and milestone-based work needs evidence that the milestone was achieved.

Reconcile the opening balance, because the prior period's contract liability should tie to the general ledger and supporting schedule before current releases are tested. Capture new deferrals from customer prepayments and billings for future performance, then test the recorded debit to liability and credit to revenue against the schedule and performance evidence.

Reconcile movements so that the opening balance plus new deferrals and other valid increases, minus recognised revenue, refunds and transfers, equals the closing balance. Review amendments, since upgrades, downgrades and extensions may change price or term and the schedule should be updated rather than dates edited silently.

Handle cancellations by contract, because refund rights, break fees and remaining obligations require specific treatment and a cancellation does not always mean all deferred revenue becomes income. Watch discounts too, since a discounted annual fee should be allocated under the applicable standard, not released as if the undiscounted list price were paid.

Avoid duplicate recognition, because a manual journal and an automated schedule that both release the same service month can leave the liability understated, while a service delivered without its scheduled release leaves revenue understated and the liability overstated. Consider failed activation, since cash collected but service not yet provided may remain a liability, and separate customer deposits, since a refundable security deposit or unrelated customer credit may not be deferred revenue.

Remember that a customer invoice before payment can create a contract liability under some arrangements, so cash alone does not define the accounting. Sample unusual items such as very long contracts, bundled services and large manual adjustments, and check negative balances, which may signal over-release, missing billing or an amendment error.

Apply a consistent method for month-end cutoffs rather than using journal timing to smooth income, tie each schedule to the right customer record, and retain old versions with the amendment rationale so movements can be audited. For an owner, the check protects against recognising advance cash as earned revenue too early or leaving earned revenue deferred too long, with preparer and reviewer signoff visible.

In practice

Real-world examples.

1

Example

A prepaid twelve-month service fee is released as the defined service obligation is satisfied. Finance compares each month's release with the schedule and the activation record. The remaining liability at each month-end is traced to the customer account.

2

Example

A subscription starts late, so finance checks the activation date before releasing the first month. The invoice date was earlier, but access was not provided until the following month. The schedule is corrected before the period is closed.

3

Example

A manual journal and an automated schedule both post a release; the duplicate is identified and corrected. The reviewer notices that the contract balance is lower than the remaining service months justify. The reversal is documented with the supporting evidence.

Formula

Calculation

Illustrative rollforward: closing deferred revenue = opening balance + qualifying new deferrals - recognised releases - valid refunds or transfers. For an opening balance of $120,000, new deferrals of $60,000 and releases of $50,000 with no other movement, closing is $120,000 + $60,000 - $50,000 = $130,000. A release test at contract level works the same way. A customer pays $12,000 for a twelve-month service that starts on activation, so the expected monthly release is $12,000 / 12 = $1,000. After three months of delivered service, $3,000 should have been recognised and $12,000 - $3,000 = $9,000 should remain as a liability. If the schedule shows $8,000 remaining, one extra month was released and needs investigation.

Case study

Seen in the real world.

This entirely fictional example follows Bayview Software. Its annual customer paid before access was activated. An automated schedule had begun releasing revenue on invoice date, so finance checked the contract and activation record, corrected the schedule and documented the change. It also reconciled the liability movement to the ledger.

The case does not determine revenue treatment for a real software contract. The finance manager then added a monthly control. Each close, a reviewer samples ten contracts, compares the schedule start date with the activation record and signs the checklist. Exceptions are listed with the correcting entry and the person who approved it.

Watch out

Common mistakes.

  • Releasing a prepayment solely because cash arrived.
  • Leaving an automated schedule unchanged after a contract amendment.
  • Posting a manual release on top of an automated one without reconciliation.

Questions

People also ask.

Is every advance receipt deferred revenue?

No. Classify deposits and contract terms under the applicable accounting rules.

What evidence supports a release?

The contract, a justified schedule and proof that the relevant obligation was satisfied.

What should the closing balance tie to?

A reconciled contract-level rollforward and the general ledger.

Was this explanation helpful?

From the founder's library

Accounting Fundamentals: A Non-Finance Manager's Guide to Finance and Accounting, by Shihan Sheriff

Take it further with the book.

Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.

US$2.24US$2.99

25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.

View the book and save 25%
Last updated · October 8, 2026
Browse all terms →

Disclaimer

The information provided in this finance dictionary is for educational and informational purposes only. It should not be construed as financial, investment, legal, or tax advice. Always consult with a qualified professional before making any financial decisions. Money Master HQ makes no representations or warranties about the accuracy, completeness, or suitability of this information. Use of this content is at your own risk.