Accounting / Insight
The Customer Has Paid. Have We Earned the Revenue?
An original AC maintenance case follows an upfront IDR 360 million receipt through service delivery, revenue recognition and the remaining customer promise. Learn why cash collected, revenue earned and the closing bank balance answer different questions.
Return to your library resultsA customer can pay in one day while the service promise continues for a year. The receipt tells us that money arrived. It does not, by itself, tell us how much revenue has been earned.
An original hypothetical case
An AC maintenance provider signs a January–December agreement covering 20 retail stores. Before coverage begins, the retailer pays IDR 360 million upfront.
The customer is buying a continuing maintenance service: readiness to respond throughout the coverage period, with routine work integrated into that service. Major replacement parts are ordered separately and are outside this illustration.
For this teaching case, assume a valid contract, one service obligation or qualifying series accounted for as one obligation, and a benefit transferred evenly throughout the year. The agreed progress measure therefore supports equal monthly recognition. Taxes, financing adjustments, refunds and variable consideration are excluded. The businesses and amounts are fictional.
Those assumptions matter. A twelve-month invoice alone would not establish them.
Follow the receipt and the promise
At receipt, the provider has collected IDR 360 million but has not yet provided the service. The simplified entry is:
Debit Cash: IDR 360 million.
Credit Contract liability: IDR 360 million.
The contract liability represents the service still owed to the customer. It is not an extra cash payment, a measure of profit or an automatic right to a refund.
A cash-receipts view asks when the money arrived. The accrual view also asks which part of the customer promise has been fulfilled.
Now follow three months of service
Under the stated even-service assumptions, monthly revenue is IDR 360 million divided by 12: IDR 30 million.
For each month of service provided as assumed, the simplified entry is:
Debit Contract liability: IDR 30 million.
Credit Service revenue: IDR 30 million.
By the end of March, three months have been provided. Cumulative revenue is IDR 90 million and the remaining contract liability is IDR 270 million. Nine months of the agreed service remain.
The roll-forward is: opening liability IDR 360 million, plus additional advances of zero, less revenue recognised of IDR 90 million, equals closing liability of IDR 270 million. There are no other movements in this case.
At the end of December, after the full service has been provided as assumed, cumulative revenue is IDR 360 million and the remaining liability for this illustration is zero.
Why dividing by twelve is not the accounting policy
IFRS 15 connects revenue to the transfer of customer promises. For a promise fulfilled over time, the measure of progress must reflect that transfer. Payment timing does not settle the recognition question.
Here, equal monthly amounts follow the assumed ongoing, evenly transferred service. For a stand-ready promise, a quiet month with fewer call-outs does not by itself show that no service was provided. The nature of the promise matters more than simply counting visits.
A separate installation, distinct scheduled tasks, included replacement equipment or a material interruption could require a different assessment. Do not carry the simple monthly release into a different contract without examining its facts.
What should finance check at month-end?
Start with the effective contract, the covered locations, service dates and the actual promises. Then consider evidence of coverage and availability, relevant service interruptions, and work orders in the context of the agreed service. A bank transfer alone does not demonstrate performance, and a visit log alone may not describe the whole stand-ready promise.
Document why the selected recognition pattern reflects the service. Reconcile opening advances, new receipts, revenue releases and other supported changes to the closing contract liability. Investigate differences before posting a convenient balancing adjustment.
In this case, treating the full advance as revenue immediately would leave end-March cumulative revenue IDR 270 million too high and the remaining liability IDR 270 million too low, assuming no subsequent correcting entries. The original receipt would be unchanged.
Revenue is also different from profit. Technician payroll, transport and other costs are not calculated here. Likewise, IDR 360 million is cumulative cash received under the contract, not a claim that the same amount remains in the bank.
Try the case yourself
Under the same assumptions, what should the position be after six completed months?
Cumulative revenue: IDR 180 million. Remaining contract liability: IDR 180 million. Original contract receipts: IDR 360 million. The closing bank balance still requires information about other receipts and payments.
The useful question is not only whether the customer has paid. It is which promise the payment relates to, what has been provided, and what the business still owes.
Inside Assurance
Beyond the numbers. Inside the business.
Put the perspective to work.
Use these questions to connect the resource to your own business context.
What should this transaction or balance represent?
Which recognition, measurement or cutoff decision is involved?
What records support the amount and its treatment?
What judgment or reconciliation should be documented?
References & context.
IFRS Foundation — IFRS 15 Revenue from Contracts with Customers: official overview
https://www.ifrs.org/issued-standards/list-of-standards/ifrs-15-revenue-from-contracts-with-customers/
AASB 15 — Recognition (Australian IFRS-based corroborating guidance; jurisdiction-specific)
https://standards.aasb.gov.au/node/4000
AASB 15 — Presentation, paragraph 106 (Australian corroborating guidance on advances)
https://standards.aasb.gov.au/node/3026
Background reading: Stephen H. Penman, Financial Statement Analysis and Security Valuation, 4th edition (2010), Chapter 4, printed pages 129–131. The fictional case, numbers and visuals are original Inside Assurance teaching material.
Use the framework and jurisdiction applicable to your work. Original examples and templates do not imply endorsement by the referenced organisations.
A question, correction or missing source?
The resource link will be included in your message form.
