Plain definition
Revenue recognition determines when and how much consideration from customers is reported as revenue. The answer follows the transfer of promised goods or services and the applicable contract terms, not simply when an invoice is issued or cash is collected. It requires finance to identify the contract, promised performance, transaction price, and evidence that performance occurred.
Illustrative example
Monetary examples use Saudi riyals (SAR). The same principles apply in other currencies.
A company receives on 1 June for a three-month managed-service contract. It provides the service evenly in June, July, and August. At 30 June it recognises revenue and retains as a contract liability, rather than reporting the full cash receipt as June sales.
The pattern may differ for a product delivery, milestone service, refund right, variable consideration, or multiple promises. The example does not turn every contract into a straight-line service.
Why it matters
Premature revenue can make growth and margins look stronger and can trigger commissions, dividends, or hiring decisions that the customer performance does not support. Delayed revenue can hide delivery progress and distort monthly trends.
Practical consequence
Maintain a contract register with promised goods or services, price, performance evidence, billing, collection, contract assets or liabilities, and accountable owner. Test significant contracts near period-end and compare recorded revenue with delivery records. Escalate unusual terms, side agreements, refunds, and manual revenue journals.