Money Matters

Is your SaaS business ready for IFRS 15/ASC 606 revenue recognition and AI token-based pricing?

As SaaS pricing evolves, usage-based, hybrid, and AI-driven models can make revenue recognition more complex. Learn how ASC 606 and IFRS 15 apply and what finance teams can do to stay accurate as pricing changes.

Published October 15, 202611 min read Share

AI is changing how SaaS companies monetize their products. Token-based, usage-based, and other consumption models can make revenue less predictable and introduce new complexities for finance teams, particularly as customer usage and pricing structures evolve.

For finance leaders, maintaining IFRS 15 and ASC 606 compliance in this environment goes beyond just applying the right accounting rules. It involves contracts, billing data, deferred revenue schedules, and finance systems working together to keep revenue recognition accurate as pricing models change.

This guide explores the key ASC 606 and IFRS 15 considerations for AI-driven and hybrid SaaS pricing, along with practical steps finance teams can take to prepare for evolving revenue models.

Here’s what we’ll cover: 

Key takeaways 

• Usage-based pricing can make revenue timing less predictable than fixed subscriptions.
• Variable consideration requires ongoing estimates and reassessment as usage changes.
• AI and hybrid pricing models can introduce new revenue recognition and margin complexities.
• Finance processes and systems need to adapt as pricing models, contracts, and usage metrics evolve.
• Connected billing, usage, revenue, and GL data can improve accuracy, reporting, and auditability.

What is usage-based SaaS revenue recognition? 

Usage-based SaaS revenue recognition means recognizing revenue based on how much of a service a customer uses during a reporting period. It’s common for SaaS businesses that charge based on API calls, transactions, active users, storage, or other measurable usage. Unlike a flat subscription, where revenue is often recognized ratably over the contract term, usage-based revenue can fluctuate as customer activity changes.

AI is adding new dimensions to these models. AI-powered products may charge based on tokens, compute time, API calls, or other measures of consumption, making pricing and revenue less predictable. Deloitte Canada notes that AI is creating more dynamic consumption-based cost models, with token usage becoming an important driver of AI costs and value.

Zest AI, an AI-powered lending technology company, illustrates how this complexity can affect finance operations. As its business grew, Zest AI used Sage Intacct to support increasingly complex arrangements, including usage-based billing and different revenue schedules, while gaining greater visibility into its financial data.

For finance teams, the challenge is maintaining accurate revenue recognition as pricing becomes more closely tied to customer consumption. Reliable usage data, clear accounting policies, and connected billing and revenue processes are critical as SaaS companies introduce AI-powered and hybrid pricing models.

Why do Canadian SaaS companies need to understand ASC 606 and IFRS 15?

For Canadian SaaS companies, IFRS 15 is the primary revenue recognition standard for companies reporting under IFRS. ASC 606 is the corresponding US GAAP standard and can also be relevant to Canadian businesses with US operations, subsidiaries, reporting requirements, or other cross-border activities.

The two standards are substantially aligned and use the same five-step framework for determining when and how revenue should be recognized:

1. Identify the contract with the customer.
2. Identify the performance obligations in the contract.
3. Determine the transaction price, including any variable consideration.
4. Allocate the transaction price to the performance obligations.
5. Recognize revenue when or as each performance obligation is satisfied.

For SaaS companies, the complexity often sits in steps two through five. Contracts can contain software access, implementation, support, usage charges, minimum commitments, or other services that require careful assessment. Understanding how both standards address these elements can help Canadian finance teams maintain consistent revenue recognition across different entities and markets. 

How does variable consideration work under ASC 606 and IFRS 15? 

Variable consideration is revenue that can change based on what happens during the contract. For usage-based SaaS, this might include fees based on API calls, transactions, storage tokens, or other customer activity.

Both ASC 606 and IFRS 15 require finance teams to estimate variable consideration when determining the transaction price. The estimate can be based on:

• Expected value: A probability-weighted average of possible outcomes, useful when multiple outcomes are possible.
• Most likely amount: The single outcome most likely to occur, often used when there are only a few possible outcomes.

The estimate feeds into step three: determining the transaction price. Finance must then apply the variable consideration constraint, excluding amounts that could result in a significant revenue reversal.

The estimate can also affect steps four and five: how the transaction price is allocated to performance obligations and when revenue is recognized. Because usage and other contract conditions can change, finance should reassess variable consideration each reporting period and update the revenue recognized as needed.

How should finance prepare for token- and consumption-based AI pricing?  

AI is changing how SaaS companies monetize their products, but the most effective AI pricing models are still evolving.

McKinsey found that 63% of software leaders believe AI will fundamentally change their business model over the next three to five years, including a shift toward consumption-based pricing. PwC similarly reports that organizations are rethinking how they price, package, and deliver value as AI drives demand for more flexible monetization approaches.

That experimentation can take different forms. A company might start with a subscription that includes a set amount of AI usage, add usage fees as adoption grows, or move toward pricing based on outputs or outcomes. Each shift can affect contract structure, variable consideration, revenue recognition, and margins. And as AI usage and costs remain difficult to predict, finance teams need processes that can adapt.

For finance teams, that means being prepared to:

• Define billable usage: Establish what counts as a billable token, interaction, output, or other usage event.
• Track consumption: Ensure usage data is complete, accurate, and traceable from source through billing and the GL.
• Manage estimates: Reassess variable consideration as usage changes and apply the appropriate revenue recognition treatment.
• Monitor margins: Track how AI usage and compute costs affect cost-to-serve and profitability.

How is revenue recognized for hybrid pricing models? 

Hybrid SaaS pricing combines two or more pricing approaches, typically a fixed subscription with usage-based charges. For example, a customer might pay a monthly subscription that includes a set amount of usage, then pay additional fees when they exceed that amount.

For revenue recognition, finance needs to identify the performance obligations (the distinct goods or services promised to the customer) and determine how the transaction price should be allocated to them. The fixed and usage components may relate to the same overall SaaS service, but they can have different recognition patterns.

In a typical hybrid model, the fixed subscription is recognized over the service period, while qualifying usage-based fees are recognized as the customer consumes the service. The exact treatment depends on the contract terms and the applicable ASC 606 or IFRS 15 requirements.

Recognizing revenue as usage occurs vs. ratably over the contract term 

Revenue may be recognized as the customer uses the service or over the contract term, depending on the pricing structure and contract terms. The table below shows how these approaches typically apply to different SaaS pricing models. 

Pricing structure	Typical recognition approach
Pay-as-you-go usage	Recognize as usage occurs, when requirements are met
Fixed subscription	Recognize ratably over the service period
Fixed minimum + overages	Minimum generally recognized over the applicable term; overages may be recognized as usage occurs
Prepaid credits	Defer until the customer consumes the underlying service

What are common hybrid contract structures? 

Two hybrid structures highlighted above are prepaid credits and monthly minimums with overage fees. Here’s how revenue recognition typically works for each. 

Prepaid credits with drawdowns 

When a customer prepays for credits, the payment is recorded as deferred revenue rather than revenue because the service has not yet been delivered. Revenue is recognized as the customer uses those credits and receives the related service. 

For example, if a customer prepays $10,000 for 10,000 credits, the $10,000 initially sits in deferred revenue. If the customer uses $2,000 worth of credits, $2,000 can be recognized as revenue, while the remaining $8,000 stays deferred until the credits are used or otherwise accounted for. 

Unused or expired credits may create breakage, which is the portion of prepaid credits a customer does not use. Finance should have a clear policy for estimating and recognizing breakage based on the expected pattern of credit usage. 

Monthly minimums with overage fees 

A monthly or annual minimum is typically recognized ratably over the commitment period. For example, a $120,000 annual minimum would generally result in $10,000 of revenue recognized each month. 

Any usage above that minimum is treated as variable consideration and is generally recognized as the customer incurs the additional usage. For example, if a customer incurs $2,000 in overage fees in a month, that amount may be recognized as revenue when the related usage occurs. 

This means the amount invoiced and the amount recognized as revenue may differ in a given period. 

How do usage-based fees affect deferred revenue schedule accuracy? 

Usage-based fees add another layer to deferred revenue schedules. Finance needs to track both subscription revenue recognized over time and usage revenue recognized as customers consume the service, while making sure the numbers match billing and the general ledger. 

An accurate deferred revenue schedule should clearly show: 

• What was billed or collected 

• What revenue has been recognized 

• What remains deferred and why 

For example, a customer might pay a $120,000 annual subscription upfront while also incurring monthly usage fees. Subscription revenue may be recognized ratably over the year, while usage revenue changes based on actual consumption. If the usage data doesn’t flow correctly into the revenue schedule, the recognized revenue and deferred balance can become out of sync with billing. 

To maintain accuracy, finance should be able to reconcile the deferred revenue schedule to both the billing system and the general ledger, accounting for contract changes, usage thresholds, and prepaid credit drawdowns. Automated schedules can help update these calculations as customer activity changes and provide a clearer audit trail. 

When do spreadsheets and point solutions become too risky? 

Spreadsheets can work for a relatively small and stable contract population. However, risk increases when contract volume, pricing tiers, modifications, and usage events grow faster than finance can manually review them.

The challenge is that spreadsheets remain deeply rooted in finance even as businesses demand more connected, real-time data. In fact, a 2025 Deloitte and IMA survey found that spreadsheets were still the most used performance-modeling tool among finance and accounting professionals, used by 30% of respondents.

For SaaS businesses, the challenge is knowing when those complexities have outgrown the processes designed to manage them. Common signs include:

• Manual journal entries for individual contracts
• Frequent revenue adjustments or restatements
• A longer close as the business grows
• Difficulty modelling upgrades, downgrades, or renewals
• Manual quote-to-cash reconciliation
• Limited visibility into usage-driven revenue
• Audit requests requiring spreadsheet reconstruction

These signs often point to deeper challenges with billing, revenue recognition, allocation, and reconciliation as complexity grows.

Where billing and rev rec tools break down at scale 

The warning signs become more pronounced when billing, usage, and revenue recognition data sit in separate systems. If usage data lives in one system, contract terms in another, and accounting schedules in spreadsheets, finance may have to manually confirm that every transaction flowed correctly into the GL. 

Connecting these systems and automating the flow of data can reduce reconciliation work and improve accuracy as volume grows. 

Standalone selling price (SSP) allocation challenges 

When a contract includes multiple distinct goods or services, the transaction price may need to be allocated based on each item’s standalone selling price (SSP)—the price the company would charge if it sold that good or service separately. 

Pricing tiers, bundled products, and implementation services can make these calculations harder to manage manually. A documented SSP methodology and automated allocation logic can help standardize the process. 

Audit trail and reconciliation gaps 

As these processes become more complex, maintaining a clear audit trail becomes another challenge. Finance should be able to trace recognized revenue back through the contract terms, usage event, invoice, and accounting entry.

Reliable usage records, documented policies, controlled recognition rules, and clear sub-ledger-to-GL reconciliations help establish that traceability. Automating these processes can make them easier to maintain and audit at scale.

How can subscription management software for contract billing help? 

As pricing models become more complex, finance teams need systems that can keep contract, billing, usage, and revenue data connected. The right subscription and revenue management software can automate revenue schedules, track usage, manage contract changes, and reconcile billing to the GL, reducing the need for disconnected spreadsheets. 

Sage revenue recognition software helps finance teams manage this complexity with configurable templates and schedules that adapt as contracts change, supporting more consistent revenue recognition and clearer visibility as pricing evolves. 

FAQs about usage-based SaaS revenue recognition 

How do contract modifications like upgrades, downgrades, or renewals affect revenue recognition? 

The treatment depends on what changes in the contract. A modification may be treated as a separate contract, a replacement contract, or through a cumulative catch-up adjustment. A documented policy helps ensure consistent treatment. 

How does milestone-based revenue recognition work when a contract includes ongoing customization? 

Revenue is recognized when the related performance obligation is satisfied, not simply when a milestone is reached. Clear milestones, acceptance criteria, and completion requirements can help determine when that occurs. 

What’s the difference between ASC 606 and IFRS 15 for SaaS companies? 

ASC 606 and IFRS 15 are substantially aligned and use the same five-step model, but some requirements differ. Canadian companies reporting under IFRS should apply IFRS 15 requirements, including its guidance on areas such as collectability and contract costs. 

How do you automate a deferred revenue schedule? 

Automation can use contract, billing, and usage data to apply recognition rules, update schedules when terms change, and reconcile results to the GL. This reduces manual calculations and improves traceability. 

What internal controls should SaaS finance teams have in place to stay audit-ready under ASC 606/IFRS 15? 

Key controls include documented accounting policies, segregation of duties, controlled changes to contracts and recognition rules, regular billing and usage reconciliations, and periodic reviews of variable consideration. 

What should finance teams look for when evaluating revenue recognition automation software? 

Look for software that can adapt as your business introduces new pricing models or changes existing ones, including hybrid, usage-based, and AI-driven billing. It should also support configurable recognition rules, automated schedules, contract modifications, reconciliation, and audit trails, while providing reporting and visibility into billing models, usage, and revenue.

Is your finance team ready? 

As SaaS companies introduce new pricing models, finance needs a system that can adapt alongside the business. Sage Intacct supports more than 500 subscription, usage, and hybrid billing scenarios, with revenue recognition, billing, and reporting connected in one financial system. Finance teams can track revenue across contracts, products, usage, and other dimensions while adapting billing and recognition as pricing models change.

Explore Sage Intacct revenue management and see how it can support your evolving revenue models.

Browse more topics from this article

• Accounting 101
• AI
• financial insights
• pricing
• Revenue