ASC 606 Commission Amortization: What Finance Actually Needs from RevOps

ASC 606 is where sales compensation and accounting bump into each other, usually with friction. The friction is almost always at the handoff: finance needs specific fields, in a specific structure, and RevOps is often supplying whatever the CRM happens to expose. This post is the translation layer.

Here is what finance actually needs, in the format they need it.

Why does ASC 606 apply to commissions in the first place?

ASC 606 governs revenue recognition for contracts with customers. Section 340-40 extends the same matching principle to the costs of obtaining and fulfilling those contracts. Sales commissions on new business are, in almost every SaaS case, an incremental cost of obtaining a contract, which means they cannot be expensed on close. They have to be capitalized as an asset and amortized over the period the underlying revenue is recognized.

The intent is matching. If the revenue from a three-year contract is recognized ratably over three years, the commission expense that acquired that contract should be recognized ratably over three years too. Expensing the full commission on close would distort profitability in the month of close and misrepresent the economics of the customer relationship.

For finance teams, this is not optional. For RevOps teams, this is where the calculation has to feed the accounting system with fields they may not currently produce.

What fields does finance actually need per deal?

The minimum useful record has seven fields.

If the commission engine cannot produce these seven, finance either has to reconstruct them manually or accept that the amortization schedule is approximate. Neither is good.

What counts as the incremental cost portion?

This is where interpretation happens, and where finance and RevOps have to align in writing.

The general rule: only the portion of commission that would not have been incurred if the contract had not been obtained is incremental. In practice, this usually means.

• Base commission rate on the new-business deal. Incremental.
• Accelerator paid above quota. Usually incremental, because the deal contributed to hitting the threshold.
• SPIF tied to a specific deal or contract type. Incremental if it would not have paid without this deal.
• Team-level or company-level bonuses. Not incremental, expense as earned.
• SDR commission on the same deal. Incremental, and capitalizes alongside the AE portion.
• CS commission on renewal. Incremental for the renewal contract, capitalized over the renewal period.

Your specific auditor will have a view on gray-area cases. Get that view in writing, apply it consistently, and revisit only when the plan changes materially.

What is the amortization period, deal by deal?

The period of benefit is not always obvious. Three common patterns.

• 1-year contract with commission on renewal. Amortization period is the initial contract term. Renewal commissions get their own capitalization when the renewal closes.
• 1-year contract with no commission on renewal. Amortization period is the expected customer life, often 3 to 5 years for SaaS. Rep gets paid once, but the commission cost matches revenue across the whole relationship.
• Multi-year contract with escalating commission. Amortization period is the contract term, with the commission allocated across the term in proportion to revenue recognition.

The expected customer life is usually a corporate assumption, not a deal-specific number. Finance sets it based on cohort retention analysis. But RevOps needs to know the assumption to feed the right period into the capitalization record. If customer life is assumed to be 48 months, every new-business commission with no renewal comp gets a 48-month amortization schedule.

How does churn interact with the amortization schedule?

Churn is where the schedule updates. When a customer cancels, the remaining deferred commission balance related to that customer's contracts has to be dealt with.

Two treatments, depending on the fact pattern.

• Full write-off in the churn period. If the customer relationship is fully terminated and no further revenue is expected, the remaining deferred commission balance is expensed in full in the churn period. This is the most common treatment.
• Accelerated amortization over remaining service period. If the customer will continue paying through the end of a term and then leave, the remaining balance amortizes over the shortened remaining period.

RevOps has to feed churn events to finance monthly, ideally daily, with the customer ID, churn date, and the reason. Without that data, finance's deferred commission balance quietly overstates the true asset value.

What audit trail do external auditors actually want?

Auditors will pick a sample of deals, usually 20 to 40, and ask specific questions about each.

• Show me the commission calculation. Which plan version applied, which rules fired, what fields drove the number.
• Show me the capitalization entry. How much was capitalized versus expensed on close, and why.
• Show me the amortization schedule. Original balance, prior period amortization, current period amortization, remaining balance.
• Show me the churn adjustment, if any. Original balance, adjusted balance, entry to the P&L.
• Show me the change log for the plan. All edits to the plan between plan drop and today, with author and timestamp.

If any of these takes more than a click or two to produce, the audit will drag. If they require reconstructing history from a spreadsheet, the audit will run over the fee estimate and produce findings.

A commission system that stores plan versions as data, tags each calculation with the version in force, and produces the amortization schedule directly is what makes this audit process an hour instead of a week.

What does a clean monthly ASC 606 process look like?

Six steps, in this order, every month.

1. RevOps closes the commission run for the period. All statements approved, all disputes either resolved or reserved. Day 4 of the accounting close.
2. Commission records exported to finance with the seven required fields. Includes new capitalizations, current-period amortization on prior capitalizations, and any churn adjustments.
3. Finance posts the capitalization entry. New commission expense capitalized as deferred commission asset, current-period portion moved to commission expense.
4. Deferred commission asset roll-forward reconciled. Opening balance plus additions minus amortization plus adjustments equals closing balance. Any variance investigated.
5. Journal entries reviewed by controller. Sign-off before books close.
6. Audit trail archived for the period. Plan version snapshot, commission records, amortization schedule, journal entries, all stored together.

Done consistently, ASC 606 becomes a predictable monthly process rather than a quarterly panic. The controller stops chasing RevOps for reconstruction requests, and the external auditor stops asking questions that require archaeology.

What actually matters

ASC 606 commission compliance is not a plan design problem or an accounting theory problem. It is a data handoff problem between RevOps and finance. RevOps has to produce a per-deal commission record with seven specific fields, versioned against the plan that applied, and updated when churn changes the schedule. Finance has to run the amortization mechanics on that record and reconcile the roll-forward monthly. When the handoff is clean, the audit is a lookup. When the handoff is missing fields, the audit becomes a rebuild. The fix is to design the commission engine to produce what finance needs, not to reconcile what the CRM happens to expose.