BusinessThe Management Accountant

Customer Advances and Contract Liabilities: 10 Controls to Keep Deferred Revenue Accurate

Customer deposits, prepaid subscriptions and advance billings can distort revenue and working capital if releases are not controlled. Use these 10 checks to strengthen contract-liability completeness, recognition, reconciliations and disclosures under ASC 606, IFRS 15 and Canadian ASPE.

Customer deposits, prepaid subscriptions, annual support fees, retainers and advance billings are easy to collect—and easy to misstate. Cash arriving today does not automatically mean revenue has been earned. A weak deferred-revenue process can inflate sales, understate obligations, misclassify working capital and leave controllers with a last-minute close adjustment.

The controller’s objective is to maintain a complete, contract-level record of customer consideration received or due before the related goods or services have been transferred, and to release the liability only when the company’s performance supports revenue recognition under the reporting framework.

1. Know what the balance represents

Under US GAAP Topic 606, a contract liability arises when a customer pays—or an amount is due—before the company transfers the promised goods or services. IFRS 15 uses a similar concept. Typical balances include prepaid subscriptions, service retainers, customer deposits, annual maintenance and billings ahead of performance. Labeling every credit balance in accounts receivable “deferred revenue” is not a substitute for understanding the contract.

2. Understand the framework before building the control

  • ASC 606: Uses a five-step model to identify contracts and performance obligations, determine and allocate transaction price, and recognize revenue as obligations are satisfied. A contract liability is recognized when payment is received or due before transfer.
  • IFRS 15: Also applies a five-step framework and recognizes a contract liability when payment is received or due before goods or services are transferred. It is effective for annual periods beginning on or after January 1, 2018.
  • Canadian ASPE Section 3400: Is not simply IFRS 15 copied into a private-enterprise ledger. BDO’s May 2025 summary describes its recognition criteria around transfer of significant risks and rewards, reliable measurement and reasonable assurance of ultimate collection, with separate guidance for services and long-term contracts. Confirm policy against the current CPA Canada Handbook.

Canadian ASPE has also been updated on upfront non-refundable fees. BDO’s October 31, 2025 update says the application guidance previously issued for such fees was indefinitely deferred, but a disclosure requirement remains effective for fiscal years beginning on or after January 1, 2025: disclose the nature and amount of upfront non-refundable fees or payments recognized as revenue when entering an arrangement. See the ASPE 2025 update.

10 controller controls for customer advances and contract liabilities

1. Reconcile the customer-contract population to billing and cash activity

Build a monthly completeness check across sales orders, signed contracts, invoices issued in advance, cash receipts, credit notes and customer portals. Ask Sales Operations, Billing, Treasury and Legal for contract changes and new arrangements. Investigate advance billings or deposits that are absent from the liability subledger, and liability balances with no identifiable contract.

2. Require a unique contract and customer record

Each arrangement should have a traceable contract ID, legal entity, customer, currency, start/end dates, billing terms, performance obligations, refund and cancellation clauses, renewal terms, and business owner. Duplicate customer or contract IDs can cause a receipt to be assigned to the wrong schedule or recognized twice.

3. Document the revenue-release trigger

Define what proves performance for each revenue stream. A SaaS subscription may be delivered over a service period; a product deposit may remain a liability until delivery; a training fee may depend on sessions delivered. Keep the evidence—activation, shipment, acceptance, milestone certification or service records—linked to the contract. Invoice date alone is not evidence that performance occurred.

4. Validate the initial liability booking

When consideration is received or becomes due before performance, verify the amount, contract, account mapping and posting date. Confirm that refundable deposits, taxes collected for others, customer credits and amounts that may be refunded are not automatically mixed into a single deferred-revenue account. Use approved accounting rules rather than ad hoc journal entries.

5. Control the monthly revenue-release schedule

Automated releases should use approved start dates, term, allocation and recognition pattern. A reviewer should inspect manual overrides, unusual acceleration, backdated entries, skipped periods and schedules that continue after contract expiry. Changes to release logic or data should be logged and approved.

6. Review cancellations, refunds, credits and renewals

Monitor contract termination, refund requests, credit notes, service pauses, renewals, price changes and disputed performance. Determine whether the liability, expected refund or revenue estimate needs adjustment. Make sure credit notes do not silently erase an obligation or create an unsupported revenue release.

7. Age the balance and review its expected settlement

Prepare a contract-level aging showing opening liability, additions, revenue releases, refunds, adjustments and ending balance. Flag old deposits, expired contracts, past-due performance, balances without a current owner, and items carried forward without explanation. Review current versus non-current presentation under the applicable accounting and presentation requirements.

8. Reconcile the subledger to the general ledger

Reconcile the detailed contract-liability schedule to GL control accounts monthly. Tie additions to invoices or receipts, releases to revenue, and refunds to cash or credit activity. Investigate differences by entity, currency and contract—not just a single net unexplained plug. Document preparer, reviewer, date and resolution of exceptions.

9. Separate reporting-basis and currency calculations

A US parent may report under ASC 606 while a Canadian subsidiary reports under ASPE. Maintain approved local accounting policies and a documented bridge to group reporting. Do not copy release schedules or recognition assumptions across frameworks without review. Track foreign-currency balances using the relevant policy and keep the contract currency, functional currency and consolidation translation data distinct.

10. Prepare disclosures and trend analytics from controlled data

Support opening and closing contract-liability balances, revenue released from opening balances, timing of performance versus payment, and significant balance changes. The FASB staff educational paper on Topic 606 summarizes required contract-balance disclosures and the public/nonpublic entity distinction. Analyze deferred revenue by product, customer, geography, contract age and release pattern; investigate unusual growth, negative balances or large manual adjustments.

Example: an annual subscription billed in advance

A US business invoices a customer $12,000 for a 12-month service that is delivered evenly, and collects the full amount at the start. If the contract and performance facts support recognition over the service period, the company initially records a contract liability and releases $1,000 each month as it delivers the service. After three months, $3,000 has been recognized and $9,000 remains as a liability, before any other adjustments. A billing schedule, activation record, monthly release, and GL reconciliation provide the evidence for the close.

A Canadian subsidiary should not automatically copy this schedule into an ASPE reporting ledger. It should assess the transaction under Section 3400 and its accounting policy, including the nature of the fee and what performance has occurred. CPA Canada’s Section 3400 briefing is a useful starting point, but the Handbook remains the authority.

Month-end controller checklist

  • ☐ All advance invoices, receipts and contracts are captured in the liability subledger.
  • ☐ Every balance has a contract owner, performance trigger and release schedule.
  • ☐ Current-period releases are supported by service, delivery or milestone evidence.
  • ☐ Refunds, credits, cancellations and amendments were reviewed.
  • ☐ Aged or unusual balances have documented explanations and actions.
  • ☐ Contract-liability subledger ties to the GL by entity and currency.
  • ☐ Local reporting and group reporting differences are reviewed and documented.
  • ☐ Disclosures and analytics are prepared from reconciled data.

Conclusion

Contract liabilities are not just a deferred-revenue account—they are a record of remaining obligations to customers. A disciplined contract register, evidence-based release process, monthly rollforward and independent reconciliation help keep revenue accurate and the close predictable. Controllers who make the liability side of customer contracts visible can reduce cutoff errors, improve audit readiness and give leadership a more reliable view of future revenue.

Informational only; not accounting, audit or legal advice. Apply the authoritative standards and your organization’s approved accounting policies to the facts of each contract.

Sources

Shares: