For informational purposes only — not
professional accounting advice
Content on this website describes general revenue recognition planning concepts and does not
constitute professional accounting, legal, or tax advice applicable to any specific entity's
circumstances.
Five Phases. One Framework.
A Deliberate Process for Revenue That Arrives Before It Is Earned
There was a time when deferred revenue planning meant a spreadsheet, a reasonable assumption, and a hopeful conversation with the auditor. That approach still exists in many finance teams today — and it still fails in the same predictable ways. We built our methodology around the opposite premise: that every recognition decision should be traceable, documented, and defensible before the question is ever asked externally. What follows is a transparent account of how we work — phase by phase, standard by standard, contract by contract.
Standards-grounded at every phase
Auditor-ready documentation
Traceable policy decisions
Built alongside your team
01
Compliance treated as a planning tool, not a reporting afterthought
Most businesses encounter revenue recognition standards as a constraint — a set of rules that arrive uninvited during audit season and demand retroactive justification for decisions already made. We treat those same standards as a planning instrument. When you understand what IFRS 15 requires before a contract is signed, you can structure your arrangements, your billing schedules, and your delivery milestones in ways that make the recognition analysis straightforward rather than contested. Compliance, approached early, reduces cost rather than adding it.
02
Documentation that survives personnel changes and audit rotations
A recognition policy held in one person's memory is not a policy — it is a single point of failure. We have seen finance teams reconstruct their own methodology from scratch when a key team member departed, producing a slightly different answer than the one the prior auditor had accepted. The documentation we produce is written to stand independently of the person who built it: clear enough for a new controller to maintain, specific enough for a new auditor to accept, and current enough to reflect the standard as it applies today rather than as it was interpreted three years ago.
03
Engagement depth proportional to contract complexity, not firm size
A mid-market professional services firm with three complex multi-year
retainers may require a more nuanced recognition analysis than a large
enterprise with a homogeneous portfolio of identical subscription contracts.
We allocate our analytical attention to the complexity of the arrangements
we are reviewing, not to the size of the client. Simple contracts receive
efficient, well-documented treatment. Complex arrangements receive the depth
of analysis they actually require — including consideration of modification
history, variable consideration constraints, and the presentation choices
that affect how the revenue story reads to external reviewers.
04
Transparency about uncertainty, not false confidence in every judgement
Revenue recognition under IFRS 15 requires judgement, and some of those
judgements are genuinely difficult. The standalone selling price of a
service with no observable market transaction. The appropriate progress
measure for a contract where inputs and outputs diverge. The constraint on
variable consideration when the outcome depends on factors outside the
business's control. We name these uncertainties plainly, document the
reasoning behind the position taken, and prepare the significant judgement
disclosures that give auditors and investors an honest account of where
estimation is involved — rather than presenting every line of a recognition
schedule as if it were a mathematical certainty.
Our Five-Phase Engagement Methodology
Each phase builds on the last, moving from diagnostic clarity through to a documentation
package your team can maintain and defend independently.
01
Discovery
Revenue Stream Assessment and Diagnostic
We map every revenue stream in your business to its underlying contract type, payment pattern, and current recognition treatment — surfacing inconsistencies, undocumented policies, and areas of elevated audit risk before any schedule is built.
02
Analysis
Standards Mapping to IFRS 15 or ASPE
Each revenue stream is traced through the applicable five-step model — identifying contracts, performance obligations, transaction prices, allocation methods, and recognition triggers — with explicit documentation of every judgement applied along the way.
03
Design
Recognition Policy and Schedule Design
We draft a written recognition policy for each contract type and construct the supporting schedules, calibrated to your delivery patterns, billing cycles, and contract terms — producing a framework your team can apply consistently across future periods.
04
Integration
System Integration and Handoff Documentation
The recognition schedules and policy framework are translated into workpapers, calculation templates, and process notes your finance team can integrate into existing close workflows — reducing manual effort and creating a repeatable monthly process.
05
Ongoing
Audit Support and Ongoing Advisory Review
We remain available through audit fieldwork to respond to auditor enquiries with supporting documentation, and conduct periodic reviews as contracts evolve, new arrangements are added, or standard interpretations change.
How a Client Moves From Improvised to Defensible Revenue Recognition
The journey from ad hoc recognition practices to a fully documented, auditor-approved framework follows a clear and repeatable path — regardless of how complex your starting point is.
Bring Your Contracts Into the Open
The first thing we ask for is not a balance sheet or a prior-year audit report. It is your contracts — the actual agreements that govern your revenue relationships. Most finance teams have never had someone read their contracts specifically through the lens of performance obligation identification and transaction price allocation. That reading is where the planning work genuinely begins, because the recognition questions your business faces are embedded in the specific language of the arrangements you have signed, not in the generic descriptions of your revenue model that appear in prior-year disclosures. We read carefully, ask pointed questions, and document what we find before recommending anything.
Map Obligations Against the Five-Step Model
Once we understand your contracts, we walk each revenue stream through the five-step recognition model — identifying the contract, the performance obligations within it, the transaction price, the allocation of that price across obligations, and the point or period at which each obligation is satisfied. This analysis is not performed once and filed away. It is documented in a working paper that records the facts considered, the judgements applied, and the standard provisions relied upon — so that the same analysis can be reviewed, updated, and defended by your team or your auditors without requiring our presence to explain it.
Build the Written Policy Your Team Will Actually Use
A recognition schedule without an underlying policy is a number without an
explanation. We translate the analytical conclusions from the standards mapping
phase into a written revenue recognition policy that your finance team can apply
to new contracts as they are signed, to modifications as they arise, and to
disclosure preparation at each reporting date. The policy is written in plain
language, cross-referenced to the relevant standard provisions, and structured
around the specific contract types your business actually uses — not borrowed
from a generic template designed for a different industry with a different
revenue model.
Construct Schedules Calibrated to Your Delivery Patterns
With the policy in place, we build the recognition schedules for your current contract portfolio. The structure of each schedule reflects the economics of the underlying arrangement: straight-line amortization for stand-ready obligations, milestone release for contracts with discrete deliverables, input-based or output-based progress measures for long-term performance arrangements. Every schedule is accompanied by a calculation memo that traces the numbers back to the contract terms and the policy provisions that govern them — giving your team a clear line of sight from the balance sheet entry to the contractual and analytical foundation beneath it.
Hand Off a Package That Holds Up Under External Scrutiny
The engagement closes with a complete documentation package: written recognition
policy, supporting schedules, calculation memos, disclosure drafts, and a
summary of significant judgements. Before handoff, we conduct an internal audit
readiness review — working through the package from an auditor's perspective
to identify any gaps, inconsistencies, or areas where the documentation could
generate questions during fieldwork. The goal is that your team walks into audit
season with answers already prepared for the questions that would otherwise
consume senior finance staff time at the worst possible moment in the reporting
calendar.
What Sets Our Methodology Apart
Proprietary Templates, Standard-Specific Checklists, and Seamless Auditor Handoffs
Our internal template library was developed specifically for the judgements that arise most frequently under IFRS 15 and ASPE Section 3400 in the Canadian context — standalone selling price analyses, variable consideration constraint worksheets, contract modification decision trees, and progress measure documentation forms. These templates are not borrowed from public guidance or adapted from US GAAP frameworks. They reflect the specific analytical steps that Canadian auditors expect to see documented, structured in a format that integrates naturally with standard close workflows.
Each engagement phase is governed by a detailed checklist that tracks every required analytical step, every policy decision, and every disclosure element against the applicable standard provision. The checklists serve a dual purpose: they keep our team disciplined during the engagement, and they become part of the deliverable package your team receives at handoff — so that future periods can be closed against the same checklist without needing to reconstruct the analytical framework from memory or from prior-year workpapers alone.
Having worked through deferred revenue planning across SaaS,
construction, professional services, media, and long-term government
contracts, our team brings a depth of pattern recognition that
generalist advisors cannot replicate. We have seen the same IFRS 15
provision produce very different analytical outcomes in different
industry contexts, and we know where the non-obvious questions tend to
arise in each sector. That cross-industry exposure makes us faster to
identify risk areas and more accurate in predicting the questions your
auditors are likely to raise — before they raise them.
Every workpaper we produce is structured with the external reviewer in mind. Index tabs, cross-references to standard provisions, clearly labelled judgement documentation, and a summary cover memo that orients an auditor to the package without requiring a guided tour from your finance team. This is not a cosmetic consideration — it directly affects how audit fieldwork unfolds. Auditors who receive a well-organised, internally consistent documentation package ask fewer follow-up questions, issue fewer requests for additional information, and complete their review of the deferred revenue balance more efficiently than those who receive a collection of unlabelled spreadsheets.
Standards evolve. The AcSB and IASB issue new guidance, auditors develop
new expectations, and businesses add contract types that the original
policy did not anticipate. Our ongoing advisory service includes a
structured annual review of your recognition policy and schedules
against current standard interpretations and any new contract
arrangements entered during the period — ensuring that the framework we
built continues to reflect both the regulatory environment and the
actual revenue model of your business as both change over time.
Avoiding the Most Common Deferred Revenue Pitfalls
Three mistakes that finance teams make repeatedly — and the planning decisions that prevent
each one from taking root in your financial statements.
Misclassifying Contract Liabilities as Simple Deferred Revenue
The distinction between a contract liability and a refund liability is not semantic — it affects presentation, disclosure, and the analytical framework applied to the underlying obligation. A contract liability arises when performance is still owed. A refund liability arises when the right to consideration is contingent on a future event. Finance teams that treat all advance payments as interchangeable deferred revenue are conflating two different economic positions, and auditors who understand the distinction will ask the question eventually. The fix is a deliberate classification step built into your contract review process from the moment cash is received.
Treating Contract Modifications as Routine Adjustments
When a customer adds scope, exercises an option, or renegotiates pricing, IFRS 15 requires a fresh assessment of whether the modification creates a new contract or changes the existing one — and the answer determines whether you adjust prospectively, apply a cumulative catch-up, or restart the recognition analysis entirely. Most finance teams default to a prospective adjustment because it is operationally convenient, without testing whether the modification actually meets the criteria for that treatment. The result is a growing body of recognition decisions that cannot be consistently justified, each one a potential audit finding waiting for the right reviewer to notice it.
Failing to Document Performance Obligations Before Revenue Moves
The most common deferred revenue disclosure deficiency we encounter is not a calculation error — it is the absence of contemporaneous documentation explaining how performance obligations were identified, why they were assessed as distinct, and what delivery event triggers recognition. Without that documentation, the recognition entries in your general ledger are assertions without evidence. Auditors can accept an assertion supported by a clear analytical memo written at contract inception. They are considerably less comfortable with an assertion reconstructed eighteen months after the fact to satisfy a fieldwork request. Document the obligation analysis when the contract is signed, not when the question arrives.