Why the timing of revenue matters
The moment decides which statement the amount lands in. A licence fee collected in January for a year of service is a liability that month and 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. The revenue standard sets out one model for that question, and this article explains it without reproducing the text of the standard.
How the model answers the timing question
- Identify the contract. A contract exists once the parties approve it, each side’s rights are identifiable and the payment terms are set. 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 and allocate it. The transaction price is what the company expects to be entitled to, allocated to each obligation in proportion to what that obligation is worth 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.
Example: revenue recognized over time
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.
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.
Invoicing and collection do not move that figure on their own. Had Camden Rail paid the whole amount in advance, the USD 24,000 earned would be revenue and the remaining USD 72,000 would sit as a liability, which is the balance deferred revenue holds. Had the service been billed after delivery, revenue could already be recognized. An unconditional right to payment is a receivable; 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 the last day.
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.
Turning the recognition policy into controlled entries
A receipt, an invoice and a delivery record can describe the same contract while belonging to different accounting moments. The team first determines the performance obligations, allocation and recognition criteria. Simetrik then supports configured calculations and journal entries using operational data and reconciliation results, with posting into the customer’s ERP.
The model needs the evidence required by that 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.