In plain words
A customer starts a monthly plan on 20 December, but the company's year ends on 31 December. How much of the fee is December revenue? Under IFRS 15, revenue follows service actually delivered, so only the days or usage within the period count, prorated on a consistent basis. For usage fees, the company uses metering data at period end rather than waiting for next month's invoice.
Why it matters
Cut-off errors at period end simultaneously misstate revenue and the related contract asset or liability, and because usage-based and mid-month-start billing are routine in SaaS, this is a recurring, high-frequency risk rather than a rare edge case, making it a perennial audit focus and a common source of restatement in fast-growing companies.
Diagnostic questions
Are any billing cycles or go-lives misaligned with the reporting period end, requiring proration of revenue for partial periods delivered? For usage-based fees, is a reliable estimate of period-end usage obtained (e.g., extrapolation or system data) rather than defaulting to the full period's fee? Is the proration method (daily versus monthly rounding) applied consistently across periods and material enough transactions to avoid a recurring cut-off error?
Recognition
- Determine the exact date access or service delivery began or ended relative to the reporting date, not the invoice or billing cycle date.
- For mid-period starts, prorate revenue based on the actual number of days or units of service delivered within the period, using a consistent and supportable proration method (daily, not monthly rounding, unless immaterial).
- For usage-based fees, obtain system-generated metering or consumption data as of period end rather than waiting for the next billing cycle's invoice to determine the amount earned.
- Reconcile revenue recognized to the underlying operational data (active users, API calls, GB processed) as an independent check, not just to the billing system output.
- Ensure the contract asset/liability roll-forward ties out consistently with the revenue recognized, since a cut-off error in one will mechanically misstate the other.
Measurement
Measure the period's revenue as the actual service delivered (days of access, units consumed) multiplied by the applicable rate, not the full period's fee regardless of start/end date. Where system usage data is not available exactly at period end, use the most reliable estimate (e.g., extrapolation from the days available plus historical pattern) and true up promptly once actual data is available, treating any difference as a change in estimate in the following period rather than a prior-period error if the original estimate was reasonable.
Presentation & disclosure
Disclose: (1) the policy for recognizing revenue for partial periods and estimating unbilled usage at cut-off; (2) consistency of the revenue, contract asset, and contract liability roll-forwards; (3) any material cut-off adjustments or estimate changes and their effect; (4) reliance on system-generated usage data and controls over its completeness and accuracy.
Common mistakes
- Recognizing a full month of revenue for a customer who went live mid-month
- leaving late-period usage entirely out of the current period and pushing it into the following month'
- s revenue instead of accruing it
- using arbitrary flat proration (e.g., always assuming 30 days) instead of actual calendar days, distorting short months
- relying solely on the billing system'
- s invoice date rather than the underlying service delivery date
- failing to reconcile contract asset/liability movements to the revenue recognized, masking offsetting cut-off errors.
Simple example
A customer activates a monthly SAR 31,000 subscription plan on 20 December (a 31-day month); 11 days of service (20-31 December) were delivered in December. Journal entry at 31 December recognizing the prorated portion (11/31 x SAR 31,000 = SAR 11,000): Dr Contract asset / Accounts receivable 11,000 Cr Revenue - subscription 11,000 The remaining SAR 20,000 relates to January service and is deferred: Dr Cash / Accounts receivable 20,000 Cr Contract liability (deferred revenue) 20,000 (if the full month was invoiced/collected in December) This avoids both recognizing zero revenue in December (understating the period) and recognizing the full SAR 31,000 (overstating it).
Professional judgment
Estimating unbilled usage at period end is not conceptually difficult but is operationally demanding: it requires reliable, timely system reports, and the genuine judgment lies in deciding what proration method and estimation approach is supportable when perfect real-time metering data is not available at close, and how much reliance can be placed on extrapolation from partial-period data. A further judgment is materiality, daily proration is best practice, but for very short gaps or highly homogeneous customer cohorts, a reasonable approximation may be acceptable if consistently applied and immaterial in aggregate.
Source basis
IFRS 15 · Revenue from Contracts with Customers
Paragraph references
Verified against the official standard texts used in the IFRS Expert skill.
Related issues
Educational and navigation content only. Not professional advice. Does not reproduce official IFRS/IAS text. Consult the authoritative standards and qualified professionals; professional judgment may still be required.