Why the timing of revenue matters
The moment of recognition decides which period’s statements the revenue lands in. A licence fee collected in January for a year of service is a liability that month and becomes revenue only as the service is delivered, so the same cash can produce two different reports. The moment is settled when the contract is assessed, not at closing, and it shapes how two periods compare, because revenue in the wrong period flatters one and starves the next.
Revenue recognition under ASC 606 and IFRS 15
Two standards set the general revenue recognition rules: ASC 606, issued by the FASB for US GAAP, and IFRS 15, issued by the IASB for companies that report under IFRS. Both describe the same five-step model built on one principle: a company recognizes revenue when it transfers control of promised goods or services to the customer, for the amount it expects to be entitled to. The two standards are largely converged but differ in some details, so each company applies the one its reporting framework requires. Before ASC 606, US GAAP relied on separate guidance for different industries; the current model applies the same steps to every contract with a customer, with specific exceptions such as leases and insurance contracts.
The five steps of revenue recognition
- Identify the contract. A contract exists once the parties approve it, each side’s rights are identifiable, the payment terms are set and collection is probable. Without one there is nothing to measure.
- Identify the performance obligations. Each distinct promise of a good or a service is a performance obligation, and it is the unit revenue is measured against.
- Determine the transaction price. The transaction price is the amount the company expects to be entitled to, including estimates of variable consideration such as discounts or rebates.
- Allocate the price to the obligations. The price is allocated to each obligation in proportion to what that obligation would sell for on its own.
- Recognize revenue when an obligation is satisfied. The obligation is satisfied when control passes to the customer, either over time as the benefit is received or at a single point in time. Invoicing does not set the moment, and neither does collection.
Revenue recognition example with journal entries
The figures are illustrative and stated in US dollars. Wexford Software signs a twelve-month support contract with Camden Rail for USD 96,000, and the service is delivered evenly across the term, so the contract is satisfied over time. Each month of service earns USD 96,000 / 12 = USD 8,000.
At the end of the third month, three of the twelve months have been delivered, which is a quarter of the service. The revenue recognized by then is USD 96,000 times 0.25 = USD 24,000, and the part still to be recognized is USD 96,000 – USD 24,000 = USD 72,000.
| Billing scenario | Event | Debit | Credit |
|---|---|---|---|
| Paid in advance | Camden Rail pays the full year | Cash USD 96,000 | Deferred revenue USD 96,000 |
| Paid in advance | End of each month of service | Deferred revenue USD 8,000 | Revenue USD 8,000 |
| Billed after each month | End of each month of service | Accounts receivable USD 8,000 | Revenue USD 8,000 |
Invoicing and collection do not move the USD 24,000 on their own: revenue after three months is the same in both scenarios. If Camden Rail paid the whole amount in advance, the remaining USD 72,000 sits as a liability, which is the balance deferred revenue holds. If the service is billed after delivery, revenue is recognized before any payment arrives. An unconditional right to payment is a receivable, an asset explained in why accounts receivable is an asset; a right still conditional on further performance is a contract asset.
Over time or at a point in time
The criterion is control. Revenue is recognized over time when the customer receives and consumes the benefit as the work is performed, as in a maintenance service or a subscription. It is recognized at a point in time when the customer obtains control in a single moment, as in the delivery of a good. The classification is settled when the contract is assessed, and it decides whether a period shows a slice of the contract or nothing until control passes.
Common revenue recognition mistakes
- Recognizing revenue on the invoice date or the payment date instead of when the obligation is satisfied.
- Treating a bundle of a product and a service as one obligation when they are distinct, which moves revenue into the wrong period.
- Leaving out variable consideration, such as volume rebates, when the transaction price is determined.
- Losing the link between the recognized amount and its evidence, such as the delivery date or the service period, which makes the figure hard to support at cut-off.
Where revenue recognition stops
Accrual accounting is the wider rule that puts a transaction in the period it belongs to, and revenue recognition applies it to income. The matching principle handles the other side, the cost that corresponds to that revenue. Cut-off is the period boundary where the timing question is settled, a journal entry records the amount once the moment is decided, and the income statement is where the revenue finally appears.
How Simetrik supports revenue recognition entries
A receipt, an invoice and a delivery record can describe the same contract while belonging to different accounting moments. Simetrik does not decide when revenue is recognized: the accounting team determines the performance obligations, allocation and recognition criteria under ASC 606 or IFRS 15. Once that policy is set, Simetrik, an AI-native financial control platform, supports configured calculations and journal entries using operational data and reconciliation results. Its journal entry automation from reconciled data validates each entry before it syncs with the ERP and adapts to how that entry must be posted in the customer’s system.
The model needs the evidence required by the policy, such as the delivery date or the service period, rather than just a payment date. Keeping the source transaction connected to the resulting entry helps explain changes in the period’s financial close and distinguish earned revenue from amounts still deferred. At period end, Simetrik’s balance certification for the close compares the ERP balance of accounts such as deferred revenue with the attached evidence, with a preparer and a certifier for each account, as part of its accounting controls.