Software companies don't sell one thing. A single contract might bundle a perpetual license, a multi-year subscription, an implementation project, and ongoing support. Each piece has different revenue recognition rules under ASC 606 (Accounting Standards Codification 606), and those differences don't stay quietly inside the finance team's books. They cascade into how commissions get paid, when they get capitalized, and what happens when a deal cancels early.

The result is a problem most growing software companies underestimate: Revenue recognition rules and commission accounting are joined at the hip, and getting one wrong tends to break the other.

This guide covers how software revenue recognition works under ASC 606, how it varies across the three main licensing models, and what each model means for paying and accounting for sales commissions.

Key Takeaways

• ASC 606 governs all software revenue recognition, replacing the old software-specific ASC 985-605 standard.
• Different licensing models (perpetual, subscription, usage-based) create different recognition timing patterns.
• Revenue recognition timing should drive commission timing and accounting treatment, not the other way around.
• ASC 340-40 (Accounting Standards Codification 340-40) requires sales commissions to be capitalized and amortized in line with the revenue they help generate.
• Finance, Sales Ops, and Legal need to align on commission timing, capitalization, and clawback design before plans go live, or close cycles turn into fire drills.

How ASC 606 Applies to Software Revenue

ASC 606 replaced ASC 985-605, the old software-specific guidance, with a single principles-based five-step model that covers every industry. Software companies now apply the same five steps as everyone else:

1. Identify the contract.
2. Identify the performance obligations.
3. Determine the transaction price.
4. Allocate that price across the obligations.
5. Recognize revenue as each obligation is satisfied.

Steps two and five are where software companies tend to struggle. Identifying performance obligations (step two) gets messy whenever a single contract bundles a license, implementation, support, and training, since each obligation needs its own price and recognition treatment. KPMG's revenue handbook for software treats standalone selling price judgments in bundled arrangements as one of the largest ongoing pain points for software finance teams.

Recognizing revenue as obligations are satisfied (step five) forces a point-in-time versus over-time decision that determines everything downstream, including how and when commissions can be paid against the deal.

Cohen & Co, an accounting firm with a software and SaaS practice, identified three recurring versions of these problems in: deciding whether implementation services are distinct, separating professional services from the underlying license, and handling milestone-based variable consideration in long-running contracts.

Each one comes down to a judgment call rather than a formula. The answer depends on the specific contract terms and how the customer is going to use the product, which means two similarly structured contracts can end up with different recognition treatments. Every judgment cascades into commission accounting: A service classified as distinct moves the related commission onto its own amortization schedule, and variable consideration in milestones forces commission true-ups as the actual numbers land.

That cascade is why the licensing model becomes the deciding factor. Each model creates its own recognition pattern, and that pattern dictates the commission treatment that follows.

Revenue Recognition by Software Licensing Model

How you sell determines when revenue lands, and that should determine when and how you pay your reps. Revenue recognition by software licensing model follows three distinct models:

• Perpetual licenses. Recognize at a point in time, when the customer gets the right to use the software.
• Subscription and SaaS. Recognize ratably over time, across the term of the contract.
• Usage-based models. Recognize as-consumed, when the customer uses the product.

Each model has its own commission implications. Here's how each one plays out.

Perpetual Licenses

Perpetual license revenue is recognized at a point in time, usually when the customer takes control through a delivered license key or provisioned access. It’s the cleanest case: a one-time transfer, a one-time recognition event.

And the commission structure matches. Upfront recognition supports upfront commission payment without creating a revenue-expense mismatch. 

The wrinkle is bundling. If the perpetual license ships with multi-year support, maintenance, or updates, that portion is treated as a separate performance obligation recognized over time. The license commission can be earned up front, but the support-related portion needs to be amortized alongside the revenue it helps produce.

Subscription and SaaS

Subscription and SaaS revenue is recognized ratably over the subscription term. The customer is consuming a service rather than taking control of an asset, so the company books revenue month by month rather than all at once.

This can make commission timing uncomfortable. Reps want to be paid at signature, but the company books revenue over 12 to 36 months. Companies have to decide whether to pay commissions up front (creating a real cash flow mismatch) or align payout timing with recognition. 

Either way, ASC 340-40 forces capitalization and amortization regardless of when the rep receives the cash. The amortization period for a new-business commission tracks the contract term when renewal commissions are commensurate with new-business commissions. When they're not, the period extends to the expected customer life. A one-year SaaS contract with high renewal rates and an average customer life of four years, for example, could reasonably warrant a four-year amortization period.

Clawback provisions also become standard practice, since early cancellation creates revenue reversal that needs to flow back through the commission asset on the balance sheet. Most SaaS clawback windows run six to 12 months, with sliding-scale percentages that reduce the clawback amount as the customer passes retention milestones. For multi-year enterprise deals, some companies extend the window across the contract life and scale the clawback down each year (a common pattern: 100% in year one, 50% in year two, 25% in year three).

Usage-Based and Consumption Models

Usage-based and consumption-model revenue is recognized as usage occurs, which means both the total revenue and the timing are variable until the period closes. This model dominates cloud infrastructure, API-billed services, and the newer wave of AI and ML platforms, where customers pay for what they consume.

Commission accounting under this model is the most complex of the three because both the revenue amount and the recognition timing depend on customer behavior the company can't predict at signing. Plans typically pay a percentage of consumption as it gets billed (so a rep earns 5% of whatever the customer uses each quarter), or commission on the contracted minimum up front with a true-up at period end on any overage (5% on $500K committed at signing, plus another 5% on usage past the minimum at year-end).

Either way, the deferred commission asset is an estimate that has to be revised as usage data lands. That makes forecasting harder and means the books on a usage-based deal stay open until the contract closes.

The Commission Accounting Bridge: ASC 340-40

ASC 340-40 is the bridge between revenue recognition rules and commission accounting. It requires companies to capitalize the incremental costs of obtaining a contract (primarily sales commissions) and amortize them over the period the customer benefits from that contract. It's the reason software finance teams can't sit as a separate workstream from ASC 606 reporting.

What ASC 340-40 Requires

ASC 340-40 requires capitalization of any commission that's both incremental (it wouldn't have been incurred without the contract) and recoverable (the company expects to earn back the cost over the customer relationship). Once capitalized, the commission becomes a balance sheet asset that gets amortized as the customer benefit period plays out.

There's a practical expedient: If the amortization period is one year or less, the commission can be expensed immediately. That's why month-to-month and short annual contracts often skip capitalization. Multi-year SaaS contracts almost never qualify for the expedient.

Determining the Benefit Period

The benefit period for a capitalized commission isn't always the contract term. If renewal commissions are smaller than new-business commissions, the initial commission is doing more than securing the first contract; it's also seeding the future renewal stream. In that case, the benefit period extends past the original term, and the amortization schedule needs to follow.

Auditors scrutinize this closely. If renewal commissions aren't commensurate with new-business commissions, the original commission must be amortized over the expected customer life rather than the initial contract.

Why This Matters for Commission Plan Design

Commission plan design ripples directly into the balance sheet. Plans that pay 100% of commission up front on multi-year SaaS deals create significant capitalized assets that have to be amortized for years.

Layer aggressive clawback provisions on top, and every customer cancellation triggers a reversal entry that pulls part of the asset back off the books. At higher-deal volumes, those reversals become a steady stream of accounting work and add expense volatility to the P&L.

Renewal differentials compound the issue. When a company pays 10% on new business and 5% on renewals, ASC 340-40 forces the initial commission's amortization period to extend to the expected customer life, sometimes turning a one-year amortization into a four-year one. The result is more capitalized commission assets on the balance sheet, longer audit trails per commission, and bigger year-over-year swings in commission expense.

This is why Finance and Sales Ops have to design comp plans together rather than reviewing them together at the close. Every comp plan is a financial reporting input. Each choice in the plan (payout timing, clawback design, renewal differentials) flows directly into the deferred commission asset on the balance sheet and the amortization schedule on the P&L.

Best Practices for Aligning Revenue Recognition and Commissions

Aligning revenue recognition and commissions comes down to four cross-functional habits. The plan, the policy, and the platform all need to reflect the recognition pattern of the revenue they support.

Match Commission Timing to Revenue Models

Commission payouts must match how the underlying revenue is recognized. The closer your payout schedule tracks the revenue schedule, the cleaner your books and the lower your clawback exposure.

The right commission structure depends on the licensing model:

• Perpetual licenses. Point-in-time recognition supports a single payout at deal close.
• Subscription and SaaS. For multi-year deals especially, move away from 100% upfront payouts. Split the payout across booking, go-live, and renewal, so sellers stay engaged across the full deal lifecycle.
• Usage-based. Tie commissions to actual consumption rather than the booked contract value. Pay on a quarterly true-up against usage data pulled from the product or billing system.

The result is tighter alignment between cash out the door and revenue on the books, plus a comp plan that reinforces the behaviors finance wants: full implementation, on-time renewal, and expansion. The payoff is lower clawback exposure when customers churn early, smoother commission expense on the P&L, and reps who stay engaged with customer outcomes long after the close.

Build Clawback Provisions That Reflect Recognition Risk

Build clawback windows that match the risk of revenue reversal. Subscription deals with high early-churn risk warrant tighter retention-tied clawbacks; perpetual licenses generally don't. Cap clawbacks (a common ceiling is 50% of quarterly earnings) and use sliding scales by deal size so the policy protects the business without breaking rep retention.

Automate Commission Accounting

Manual tracking breaks the moment you sell across multiple licensing models. Each model creates its own capitalization rules, amortization schedules, and adjustment triggers. Once deal volume scales past what one analyst can hold in a spreadsheet, the audit trail starts to fray, and the close cycle stretches.

CaptivateIQ automates commission calculations across plan types, maintains amortization schedules at the contract level, and produces audit-ready reporting for ASC 606 and ASC 340-40. Financial closes take less time, compliance holds up under audit, and the work doesn't depend on heroic spreadsheet maintenance.

Align Cross-Functional Teams Early

Bring Finance, Sales Ops, and Legal into a joint comp plan review before any commission structure goes live, and trigger another whenever you launch a new product, change pricing models, or adjust renewal commission rates. Finance walks through the recognition and capitalization implications, Sales Ops flags the operational impact, and Legal flags any contract-language risk. 

Catching a misaligned commission structure during plan design is a one-meeting fix. The same issue surfacing during the financial close becomes a quarter-long problem.

FAQS

What is software revenue recognition?

Software revenue recognition is the accounting process of determining when and how a software company books revenue from customer contracts under ASC 606. The timing depends on the licensing model: Perpetual licenses recognize at a point in time, subscriptions over the contract term, and usage-based models as consumption occurs.

How does ASC 606 apply to SaaS companies?

ASC 606 applies to SaaS companies through the same five-step model as any other industry, but recognition is almost always over time because SaaS customers consume a service rather than take control of an asset. SaaS revenue is recognized ratably across the subscription term.

When should commissions be paid on subscription software deals?

Commissions on subscription software deals can be paid up front, at milestones (booking, go-live, renewal), or over the contract term. Regardless of cash timing, ASC 340-40 requires the commission expense to be capitalized and amortized over the customer benefit period.

What is ASC 340-40, and how does it affect sales commissions?

ASC 340-40 is the section of US GAAP that governs contract costs as the companion to ASC 606. It requires companies to capitalize incremental sales commissions as balance sheet assets and amortize them over the period the customer benefits from the contract.

Do perpetual software license commissions need to be capitalized?

Perpetual software license commissions usually don't need to be capitalized when the related revenue is recognized at a point in time, and there's no ongoing customer benefit period beyond the license delivery. Bundled support or maintenance changes the analysis, since those obligations are recognized over time.

Make Revenue Recognition Rules Work for Your Commission Strategy

Software revenue recognition rules shape commission timing, commission accounting, and the design of the plans that produce both. Companies selling across multiple licensing models need commission plans that mirror the recognition pattern for each model, and they need systems that can handle the complexity at scale.

CaptivateIQ automates commission calculations and amortization across complex software revenue models, handling the ASC 606 and ASC 340-40 mechanics so finance teams don't have to. Book a demo to see it in action.