The revenue recognition principle is simple to say: you count revenue when you earn it, not when the money arrives.
In practice, it gets awkward fast.
Table of Contents
- IFRS or ASPE: which applies in Canada?
- The 5 steps of revenue recognition (IFRS 15)
- What are the 5 criteria for revenue recognition?
- What is an example of revenue recognition?
- What is the difference between GAAP and IFRS revenue recognition?
- Sales tax, the CRA, and where they overlap
- Revenue recognition system: what to look for
- Revenue recognition in Microsoft Dynamics 365 Business Central
- How Dynamics Square Canada help Businesses
A customer pays for a full year upfront. A single contract covers software and support. A project starts in one fiscal year and finishes in the next. Suddenly, "When did we earn this?" has more than one possible answer.
In Canada, the rulebook depends on who you are. Public companies report under IFRS. Private enterprises can use ASPE Section 3400 instead. IFRS 15 has been the revenue standard since 2018, and ASPE's revenue guidance got a serious expansion after 2019.
Below, we go through what each framework expects, how the five steps work, where sales tax gets tangled in, and what your system needs to handle all of it.
Key Takeaways
Revenue is recorded when it is earned. A deposit taken before the work starts is a liability, not income.
Public companies in Canada follow IFRS. Private enterprises can choose ASPE Section 3400, and some go with IFRS anyway.
IFRS 15 runs in five steps: identify the contract, identify the performance obligations, determine the transaction price, allocate it, and recognize revenue as each obligation is met.
Sales tax is never revenue. GST, HST, and PST belong to the government and stay out of your revenue line.
The CRA expects you to keep business records, electronic ones included, for at least six years. Records stored outside Canada but accessed from Canada don't count as being kept in Canada.
Business Central handles deferrals through templates, but someone in finance still must decide how a complex contract gets split.
Start by confirming which framework you report under. Then run your five most common contract types through the five steps.
What is the revenue recognition principle?
The revenue recognition principle is an accrual accounting rule, which means revenue goes in the period you earn it by delivering goods or services, whenever the customer pays. Revenue recognition is the day-to-day work of applying that rule, one contract at a time.
Take a deposit. A customer pays you before you have done anything. That cash is not revenue yet. It sits on your books as a liability until the work is delivered.
It also works the other way. Ship goods on net-60 terms, and you record the revenue from delivery, even though the cash won't show up until next quarter.
Why it matters beyond the accounting team
Finance usually isn't the first to feel a timing mistake. Operations are.
If a quarter is overstated, operations may sign off on new equipment that the cash flow cannot really carry. If it is understood, hiring or expansion gets pushed back when the company could have afforded it.
Outsiders notice too. A Calgary manufacturer applying for equipment financing gets judged partly on how consistently it recognizes revenue. A bank in Ontario or British Columbia may ask which framework you follow before it asks anything about growth.
Also Read: Best Small Business Accounting Software
IFRS or ASPE: which applies in Canada?
Public companies in Canada prepare their financial statements under IFRS, issued by the IASB. Private enterprises and not-for-profits can use ASPE instead. Plenty choose IFRS anyway, usually because a lender or investor expects it.
The two are built differently. IFRS 15 is a five-step model with detailed disclosure requirements. ASPE Section 3400 has no formal five-step structure, asks for lighter disclosure, and recognizes revenue once performance is substantially complete.
Don't assume ASPE is the "easy" option, though. CPA Canada expanded its guidance in December 2019, adding detail on multiple-element arrangements, percentage of completion, gross versus net reporting, bill-and-hold arrangements, and upfront non-refundable fees. The start date for the upfront fees piece was pushed to fiscal years beginning on or after 1 January 2025. Older articles still describe ASPE as light-touch, and that's out of date.
The 5 steps of revenue recognition (IFRS 15)
IFRS 15 applies the same five steps to most contracts with customers:
Identify the contract: Both sides have approved of it and committed to perform. Payment terms are clear, and collection is probable.
Identify the performance obligations: These are the distinct goods or services you've promised. Software access and a separate support service are two obligations, not one.
Determine the transaction price: This is the amount you expect to be entitled to after discounts, rebates and refunds. Sales tax collected for the government isn't part of it.
Allocate the price: Spread it across the obligations based on their standalone selling prices.
Recognize revenue: Do it when, or as, each obligation is satisfied. That can be at a point in time or overtime.
What are the 5 criteria for revenue recognition?
Search this question and you'll get two different answers. Both have some truth in them.
The older IAS 18 framework listed five conditions: risks and rewards transferred, no continuing control, collection reasonably assured, revenue measurable, and costs measurable. A lot of guides still repeat that list.
Under IFRS 15, the five steps above are the model. IFRS 15 also sets five criteria a contract has to meet before it counts as a contract: approval, identifiable rights, payment terms, commercial substance, and probable collection.
Note: If your finance team is still working from the old list, update it. Auditors will be thinking in IFRS 15 terms.
What is an example of revenue recognition?
A Toronto software company signs a 12-month contract for CA$36,000 and invoices the whole amount in January. It also charges 13% Ontario HST, which comes to CA$4,680.
The CA$36,000 is revenue, recognized at CA$3,000 a month as the service is delivered. The CA$4,680 of HST is collected for the CRA and never touches revenue. Once January's CA$3,000 is recognized, the remaining CA$33,000 sits as deferred revenue, which is a liability.
Now add a twist. Say onboarding is a separate, distinct service worth CA$6,000 inside that same contract. That portion gets recognized when onboarding is finished, not spread throughout the year. You'll only catch that by reading the contract. A glance at the invoice won't show it.
What is the difference between GAAP and IFRS revenue recognition?
IFRS 15 and the US standard, ASC 606, were developed together and share the same five-step model. The leftover differences are small. US GAAP has more detailed rules for software and IP licenses, the collectability threshold is slightly different, and the way capitalized contract costs get tested varies.
For most Canadian companies, the bigger gap is IFRS versus ASPE, not Internaltional Financial Reporting Standards IFRS versus US GAAP. If you also report to US investors, though, you could end up juggling all three.
Sales tax, the CRA, and where they overlap
GST/HST and revenue recognition run on different clocks. Revenue follows performance. Tax follows the Excise Tax Act. Both come off the same invoice, which is exactly why your system must keep them separate.
HST, like Ontario's, is one combined tax. British Columbia charges GST plus PST. Alberta has no provincial sales tax. Whichever applies to you, none of it is your revenue.
On filing, for reporting periods that began in 2024, the CRA requires nearly all GST/HST registrants to file electronically. Charities and certain financial institutions are the exceptions. GST/HST NETFILE is one of the filing routes.
On records, the CRA wants business records, electronic ones included, kept for at least six years from the end of the last tax year they relate to. If your records live on a server outside Canada and you only access them from here, the CRA doesn't treat them as being in Canada.
Also Read: HST GST Credit Payment Dates
Revenue recognition system: what to look for
A spreadsheet will do for a handful of contracts. It starts failing when a contract changes mid-term or when two branches apply the policy a little differently and nobody spots it until year-end.
Whatever you use, it should at least:
Store the contract terms that drive the schedule
Generate deferral schedules automatically
keep deferred revenue reconcilable to the ledger
leave an audit trail
An ERP helps because revenue, invoices, and the general ledger live in one place. It helps even more when finance is spread out.
Picture a head office in Calgary, a branch in Vancouver, and a subsidiary in Toronto. On one shared ERP, all three post to the same chart of accounts under the same policy. Nobody must reconcile three versions of the rules when the auditors show up.
Revenue recognition in Microsoft Dynamics 365 Business Central
Business Central handles deferrals through templates. You set one up on an item, resource, or G/L account. When you post a sales document, the revenue is spread across the accounting periods you have defined. There's also a sales deferral summary report, which is handy for reconciling deferred balances and checking the timing.
For the common cases, like annual subscriptions and prepaid service contracts, that works well. Contracts with several obligations are another story. Your finance lead still has to decide how the price is split. Business Central builds the schedule after that decision, not before it.
Because Business Central supports multiple companies in one environment, it also fits group structures.
A Business Central partner in Canada like Dynamics Square can scope the deferral setup, and Business Central partners in Ontario or British Columbia can map it to your reporting standard.
Common mistakes finance teams make
Treating deposits as revenue: Cash in the bank is not earned revenue.
Ignoring bundles: A discount on a package still must be allocated across each obligation.
Missing contract changes: An upgrade or extension can shift the schedule after the fact.
Mixing tax and revenue: HST, you collected, should never sit in the revenue line.
Letting branches improvise: Without one policy, every location slowly drifts its own way.
How Dynamics Square Canada help Businesses
Dynamics Square Canada is a certified Microsoft partner with 14+ years of experience. We work with businesses running Business Central in Toronto, Ontario and British Columbia, and a revenue review usually starts with your actual contracts.
We will look at your current setup, confirm which framework you report under, and tell you plainly whether Business Central deferral templates fit your contract types or whether some of them need a manual call from your finance lead.
If you still any doubts, feel free to call us at +1 778 381 5388 or email info@dynamicssquare.ca.
