Revenue can be earned before an invoice is issued—or cash can be collected before the related work is performed. When operational milestones, billing schedules and accounting records do not line up, month-end teams can misstate revenue, contract assets, receivables or deferred revenue.
For financial controllers, the challenge is not simply to reconcile a balance called “unbilled revenue.” It is to understand the contractual right behind the balance, confirm that the underlying performance supports revenue recognition, and ensure the amount moves to the right balance-sheet account when billing or performance changes the facts.
First, distinguish the balances
Under IFRS 15, a contract asset generally represents a right to consideration for goods or services already transferred when that right remains conditional on something other than the passage of time. A receivable is an unconditional right to consideration—only the passage of time is required before payment is due. A contract liability generally arises when the customer pays, or an amount is due, before the entity transfers the related goods or services. See the IFRS 15 text, paragraphs 105–108.
In practice, companies may use labels such as accrued revenue, unbilled receivable, unbilled revenue, contract asset, deferred revenue or contract liability. These labels are not automatically interchangeable. Determine the substance of the right and the applicable reporting framework before mapping a general-ledger account to a financial-statement line.
10 controls to strengthen the month-end close
1. Maintain a complete contract and project population
Start with a controlled population of active customer contracts, projects, service orders and relevant sales arrangements. Reconcile it to approved contract-management, CRM, project-management or ERP reports. Include new contracts, amendments, change orders, cancellations and contracts nearing completion.
- Confirm the report covers all entities, business units, currencies and relevant contract types.
- Check that key identifiers link the contract to project, billing plan, performance evidence and GL postings.
- Investigate active projects missing from the revenue report and closed projects with continuing balances.
In SAP S/4HANA, the precise source depends on the implemented sales, project and revenue-accounting processes. Document the report or application used, its filters, extraction date and reconciliation to a trusted control total.
2. Reassess the revenue-recognition basis—not just the invoice date
For each material contract type, document what must happen for the company to earn revenue and how progress is measured where recognition occurs over time. An invoice schedule is evidence about billing rights; it does not, by itself, prove that revenue has been earned. Likewise, a delayed invoice does not automatically mean revenue should be deferred.
Under US GAAP, the FASB’s Topic 606 overview explains that the revenue model addresses the nature, timing and uncertainty of revenue from customer contracts. For IFRS reporters, assess the relevant performance obligations and recognition requirements in IFRS 15. Require Technical Accounting review when contract terms, acceptance clauses, variable consideration or the pattern of performance make the conclusion unclear.
3. Validate progress and cut-off evidence
For project or service revenue recognized over time, inspect the evidence that supports performance through the reporting date. Depending on the contract, that may include approved milestones, customer acceptance, service logs, project-manager certifications, usage records, labour hours or cost-to-cost calculations.
For example, a systems integrator has completed a defined phase of a customer implementation by September 30, but the contractual billing milestone occurs in October. The controller should verify that the phase represents performance under the applicable accounting policy and that the right to consideration is correctly classified. A project manager’s forecast alone is not sufficient evidence if it is not supported by contract terms and verifiable progress.
4. Test the calculation inputs and estimates
Where the measure of progress relies on inputs, test the data that drives the calculation: eligible costs incurred, total estimated costs, hours, units or other measures. Review changes to the estimate at completion and identify costs that do not depict progress if the relevant standard or policy requires their exclusion from the measure.
Require a reasoned explanation for large period-over-period changes in margin, progress or estimated remaining effort. Look for late cost postings, duplicate time entries, purchase orders not reflected in estimates, unapproved change orders and projects whose forecast cost exceeds expected consideration. Evaluate potential loss-making contracts under the applicable framework and policy.
5. Reconcile earned revenue to billings and cash-related records
Prepare a contract- or project-level bridge between cumulative revenue recognized, invoices issued or amounts due, and the resulting contract asset, receivable or contract liability. Reconcile the subledger or calculation output to the GL, and reconcile material billed receivables separately to accounts receivable records.
Investigate unusual negative unbilled balances, contract assets that remain unchanged for several periods, and projects where revenue and billing move in opposite directions without a documented explanation. Do not net balances across unrelated contracts simply to clear exceptions; follow the applicable presentation requirements and approved accounting policy.
6. Track billing triggers and overdue unbilled amounts
Assign an owner and expected billing date to each material unbilled item. Track whether the item is awaiting a milestone, customer sign-off, a purchase order, a time sheet, a change-order approval or administrative processing. Escalate items that have passed the contractual trigger but remain uninvoiced.
Aging should be based on meaningful dates—such as the date performance was achieved or the billing condition was met—not merely the date a spreadsheet was created. Separately identify items where the company has performed but its right to consideration remains conditional, and items where the right is unconditional but invoicing has been delayed. That distinction affects classification and collection follow-up.
7. Review contract liabilities and advance billings
Reconcile customer deposits, upfront billings and other amounts received or due before performance to the remaining obligations under the contract. Confirm that amounts are released to revenue as performance occurs under the applicable policy, not simply because the invoice has aged or a month-end journal is routinely reversed.
Check contract amendments, cancellations, credits and refunds. A liability balance that declines without corresponding performance or a supported accounting adjustment deserves investigation. For subscriptions and maintenance services, compare the revenue schedule with service periods and the contract’s start and end dates.
8. Control manual journals, interfaces and mapping changes
Manual journals for unbilled revenue can bypass the normal contract calculation. Require preparer and independent reviewer approval, source-level support, a clear calculation, correct entity and currency, and a reversal or settlement plan where appropriate. Review unusual journals posted late in the close, entries to suspense accounts and changes to revenue or contract-balance mapping.
For automated revenue accounting, monitor failed interfaces, rejected events, unprocessed billing plans, duplicate source documents and jobs that did not complete. SAP’s Revenue and Cost Accounting documentation for S/4HANA 2025 FPS02 (October 2026) describes capabilities for calculating contract assets and liabilities and integrating revenue and cost recognition with the General Ledger. Actual functionality and configuration vary by solution, release and activated scope, so validate the process in your own environment.
9. Review collectability, disputes and impairment separately
A contract asset is not proof that the customer will ultimately pay. Identify disputed milestones, customer claims, contract modifications, acceptance issues and deteriorating customer credit. Evaluate the relevant impairment or credit-loss requirements for the balance under the applicable framework; do not assume that a revenue-recognition review replaces credit-risk analysis.
Keep commercial disputes and accounting judgments linked but distinct. Legal or sales teams may own the dispute, while Finance remains responsible for assessing its accounting consequences and recording a supportable conclusion.
10. Document the framework-specific conclusion and reviewer challenge
US GAAP Topic 606 and IFRS 15 have broadly converged revenue-recognition models, but the applicable codification or standard and entity-specific facts still govern the accounting conclusion. Canadian private enterprises applying ASPE should consult the current CPA Canada Handbook—ASPE, including Section 3400 and relevant long-term-contract guidance. ASPE’s framework is not simply a relabelled IFRS 15 model.
CPA Canada’s ASPE Briefing on Section 3400, Revenue discusses long-term contracts, including the relationship between earned revenue and progress billings. For ASPE entities, confirm the policy and facts against current authoritative guidance rather than importing IFRS terminology or conclusions without analysis.
Reviewer sign-off should identify the population and reports reviewed, key movements challenged, material exceptions, evidence inspected, conclusion and follow-up owner. A tick mark alone does not demonstrate a substantive review.
Month-end controller checklist
- Active contract and project population reconciled to source systems.
- Recognition method and contract-specific performance evidence reviewed.
- Progress measures, cost estimates and major changes tested.
- Earned revenue, billings, receivables and contract balances reconciled.
- Unbilled aging, missed billing triggers and long-outstanding balances assigned to owners.
- Advance billings and contract liabilities released only when supported by performance.
- Manual journals, interfaces, failed jobs and mapping changes reviewed.
- Disputes and credit risks assessed separately from revenue recognition.
- US GAAP, IFRS or ASPE policy conclusion and reviewer evidence retained.
Conclusion
The most effective unbilled-revenue control is a contract-level bridge from what the business promised, to what it delivered, to what it has the right to bill, and finally to what the ledger reports. By connecting commercial evidence, project data, billing events and accounting review, controllers can reduce cut-off errors and make contract balances easier to explain to auditors and operating leaders.
Informational only: This article provides a general finance-control overview, not accounting, audit or legal advice. Apply the authoritative standards and professional guidance relevant to the entity, contract facts and reporting period.
