IFRS 15 in 2018: Separate invoices, cash and revenue in a SaaS system
A business retrospective on how subscription contract changes affect software records, finance workflows and reconciliation.
Archive retrospective · Topic year 2018
One sale can have several material dates
IFRS 15 became effective for annual periods beginning on or after January 1, 2018. A subscription sale can have separate invoice, collection and revenue recognition dates. Combining those in a single commercial total blurs cash management and service delivery. Finance determines the applicable treatment of obligations and transfer. Software should provide durable evidence for that judgment rather than deriving it from an invoice flag.
Retain evidence when terms change
A customer may move to a higher plan after six months. Overwriting the old plan loses information needed to explain a prior calculation. Track orders, contract versions and billing events with separate identities. Record effective dates and terms. Preserve the reason for adjustments. If finance changes an accounting rule, it should remain possible to identify which rule version was used by an earlier report.
Reconcile a complete scenario
Create a sale, upgrade and cancellation for an illustrative customer. Compare collected funds, outstanding invoices and the inputs to period reporting. Import the same event twice and check for duplicate effects. When a month-end discrepancy appears, the total should trace back to a specific contract event. Explain why a support cancellation date and the end of service might differ instead of forcing all systems to use one field.
Keep operational metrics distinct
A manager may use monthly recurring revenue to evaluate growth. Its definition does not automatically equal recognized revenue or collected cash. Document the calculation, owner and refresh time for each measure. A reporting difference is easier to investigate when both sides preserve versioned events. Shorten period-close work by improving that trace, rather than reconciling unexplained differences with manual adjustments.
Separate a claim from its evidence
A demo or experiment does not prove that an approach works in every context. Record measurement conditions, versions, data samples and assumptions. Compare a new method with the current one under the same workload before claiming a performance or quality improvement. Explicit uncertainty is more useful than false precision.
Keep tests and evidence for long-term value
Investigate root causes rather than symptoms. Check downstream components, stored records and user actions affected by a change. Test both successful and failed paths. Record dates, versions, measurements and references so later decisions can be reviewed without reconstructing the entire history.
Comments
No comments yet. Be the first to contribute.
Discussion question from the editor Which fields distinguish an invoice date from a period of service in your system?
Reading “IFRS 15 in 2018: Separate invoices, cash and revenue in a SaaS system” raised this question for me: data lineage and model correctness need verification.
Editor note: Product claims and measured outcomes should be assessed separately. A small pilot with defined metrics is a useful first step.
We should also discuss maintenance cost. An easy rollout does not guarantee trouble-free upgrades.
I would start with a pilot and measurable success criteria rather than assuming a launch means proven value.
✎ Write a comment