Why is payment not a complete answer?
The official IFRS 15 overview describes revenue recognition through transfer of the promised good or service to the customer and the consideration to which the organization expects to be entitled. This is a general framework for contracts within the standard’s scope, not a claim that every monetary transaction falls within it.
Start with a plain description: who promises what to whom, what counts as performance and how payment is determined. Only then move to the accounting amount. A signed document does not remove the need to analyze the substance of the promises.
Which five questions organize the review?
The standard overview presents a five-step sequence: which customer contract is being analyzed; which separate performance obligations exist; how the transaction price is determined, including variable consideration; how that price is allocated; and when each obligation is satisfied and control passes to the customer.
This is not a questionnaire that automatically produces a correct journal entry. Each question may require contract terms, evidence of performance and additional standard guidance. A single bundled price does not settle whether promises must be separated.
Does performance happen at once or over time?
IFRS 15 allows an obligation to be satisfied at a point in time or over time. The standard overview connects over-time recognition with an appropriate measure of progress. A service lasting several months is not automatically uniform merely because the contract lasts several months.
Identify the promised result and how its transfer is measured. A calendar may be a suitable educational assumption, but a real contract requires the standard’s criteria and facts. The service name, invoice schedule and payment date may be insufficient.
How does an advance payment work in a simple model?
Synthetic educational example. All amounts and conditions are fictional and the currency is notional. A customer pays 120 at the beginning of the year for twelve months of service. Assume one obligation satisfied over time, uniform delivery, no refunds, variable consideration or other promises.
The model recognizes 120 / 12 = 10 per month. After three months, recognized revenue is 30, while cash received is 120. The unperformed portion is 90. That difference is not missing cash; it is the remaining service promise.
If the service instead transfers one combined result at a specific point, monthly allocation no longer follows from the assumptions. The example is not a rule that every annual contract is divided into months; it shows why explicit assumptions must match economic substance.
How should revenue be checked together with cash?
Find the explanation of recognition and compare it with the contract. Then separate payment questions. The IAS 7 overview concerns changes in cash and cash equivalents, a different side of the same educational problem. One positive cash flow cannot prove that revenue recognition is correct.
Use three columns: promised to the customer, transferred to the customer and paid by the customer. Mark unknown terms and locate documents that can test them. Pay particular attention to returns, contract changes and price elements dependent on future events.
What is often accepted as evidence too early?
People may recognize an advance in full as revenue, treat an invoice as proof of completed work, read a signed contract as proof that the result has already transferred, or apply uniform recognition to every service without checking the obligation. Each substitution skips the performance question.
Do not confuse higher cash receipts with higher current sales. Cash may relate to previously recognized revenue or future service.
Which limits are essential?
This guide does not cover every IFRS 15 exception, contract criterion or special situation. It does not confirm that the standard applies to a particular transaction and does not replace professional accounting analysis. The sources support educational understanding, not a conclusion about the legality of a specific entry.