The Liability and the Expense Are Two Different Numbers
What goes wrong in a commission close is almost never the arithmetic. It goes wrong because there are two numbers: the accrued commission liability — what the company owes sellers for service already rendered — and the commission charge to the period, which may be operating expense or a capitalised contract-cost asset. Different literature governs each; most teams reconcile one, so errors in the other are invisible.
The cause is an absence: there is no ASC topic titled “commissions.” Recognition comes from ASC 710 read with ASC 450-20 — ASC 710 puts the cost in the service period, ASC 450-20 supplies the threshold and the measurement rule. Only then is the debit classified, and ASC 340-40 intercepts any commission that is an incremental cost of obtaining a contract — the sequence the FASB staff confirmed at the Transition Resource Group. Reconcile only the liability and you miss capitalisation and expedient errors in the P&L; reconcile only the expense and you miss completeness failures in the liability, the assertion auditors weight most heavily.
Three further arguments run through this report.
- Accruing on recognised revenue is structurally wrong wherever splits or bookings-based crediting exist. Alexander Group survey data via WorldatWork puts 68% of companies on some duplicate crediting and 16% above 112% of actual revenue. A revenue-derived rate under-accrues by the duplication factor every month, in one direction — and plan terms and credited volume existed at close. That is an error, not a change in estimate.
- You cannot cost-plus a cross-border sales-comp recharge. OECD Transfer Pricing Guidelines Chapter VII, ¶7.47 excludes sales, marketing and distribution from the simplified low-value-adding regime behind the familiar 5% markup. A substantive functional analysis is required — a tax-adviser question with GAAP consequences.
- The control most likely to fail is completeness of the CRM-derived population, not the calculation. A flawless recomputation of the deals in the file says nothing about the deals not in it. And the control most commonly missing is the look-back: prior accrual against actual, with a trend.
CFO Shortlist Take
Run two reconciliations, not one. Key the accrual to credited volume, not recognised revenue. Put a look-back on it before your auditor asks. An accrual trued up in the same direction every month is a methodology problem, not an estimation problem — at a listed company, a bias question.
What this report is, and what we will not tell you
This is information, not advice: much of commission accounting depends on your plan documents, contract population and entity structure, and where it does we point you to your own auditors — on the cross-border recharge, a tax adviser.
We also decline four things: a day-count for how long commissions add to a close, close-cycle benchmark percentiles, any “reduces close time by X%” vendor claim, and an enforcement history — the first three unverifiable at source, and no SEC action or AAER we could find centred on a sales-commission accrual.
There Is No ASC Topic for Commissions
Sales commissions are cash compensation for employee service, which is why no single Codification topic addresses them. ASC 710 accrues cash bonus and incentive benefits over the period of service once the performance condition is probable of achievement, and PwC's employee-benefits guidance cross-references ASC 450 for the meaning of “probable.” Both conditions of ASC 450-20-25-2 must then be met: information available before issuance indicates a liability had probably been incurred, and the amount is reasonably estimable.
The decisive rule: you may not wait until you can calculate it
“The entity should not delay accrual of a loss because of the inability to estimate a single amount.”
ASC 450-20-30-1, as reproduced in Deloitte's Roadmap on contingencies.
The same paragraph gives the range rule: accrue the better estimate, or the minimum of the range where no point in it is better. There is no third option in which you accrue nothing. The obligating event sits inside the period; only the computation is late.
The trap: “we book it when the comp run closes”
This is usually described as a policy. It is not — it is a timing misstatement whenever the amount is material. Because the deals, the plan and the rates were knowable at the balance sheet date, the correction is usually characterised as an error, not a change in estimate. Accrue-then-true-up is the same work on the correct side of the cutoff.
Only then classify the debit — ASC 340-40 intercepts
ASC 340-40-25-1 requires an entity to capitalise the incremental costs of obtaining a contract it expects to recover, and ASC 340-40-25-2 defines those as costs that would not have been incurred had the contract not been obtained — giving a sales commission as its example. Recognition is at incurrence, not payment: per the TRG summary, a commission earned on signature is capitalised when the contract is obtained. And the liability comes first: on the tiered and pooled fact pattern (TRG Agenda Ref. 57, Example 5) the staff concluded a liability should be recognised under other GAAP first.
The ASC 340-40-25-4 expedient permits expensing where the amortisation period would be one year or less, but Deloitte's technology guidance is emphatic about its limits: apply it across contracts with similar characteristics, not contract by contract, and it fails for the whole asset if any obligation runs beyond a year. Because the election is disclosable under ASC 606-10-50-22, a mis-scoped population is both a measurement error and a disclosure failure.
The correct sequence
1. Establish that a liability was incurred for service rendered in the period (ASC 710; ASC 450-20-25-2).
2. Measure at the best estimate within the range, or the minimum where no point is better (ASC 450-20-30-1).
3. Then classify the debit: contract-cost asset under ASC 340-40-25-1, or expense where the ASC 340-40-25-4 expedient applies.
Estimating the Accrual Before the Payout Run Finishes
The literature prescribes no method. ASC 450-20-25-2(b) requires the amount to be reasonably estimable and ASC 450-20-30-1 requires best-estimate-within-range measurement; for public filers, PCAOB AS 2501 is the operational definition of “reasonable.” An auditor evaluates the method against the applicable framework (¶.10), the accuracy and completeness of the data (¶.12–.14), the significant assumptions and their consistency with external factors (¶.15–.16), and management bias assessed cumulatively (¶.30–.31). Hence one documented method, applied consistently: an estimate rebuilt each period cannot be shown to be unbiased.
The approaches in use are practice, not an authoritative taxonomy — no FASB, Big Four or national-firm source we could locate names or ranks them. A deal-level bottom-up build from the CRM bookings population has the highest fidelity and best meets the data-completeness expectation in AS 2501 ¶.12–.14. An attainment-based effective rate is necessary wherever plans are tiered. A trailing rate is cheapest, but ¶.16 requires historical assumptions to be consistent with current conditions.
Tiered plans force a policy election. Deloitte's technology guide gives two acceptable attributions: Approach A attributes commission to the contract that triggers payment; Approach B accrues ratably at an average expected rate. Intra-year expense curves differ materially, so align the liability policy with whichever is elected — a question for your auditors. Either way an effective-rate method must be attainment-aware, or it understates the second half for every rep who crosses an accelerator.
True-Ups: Change in Estimate, or Error?
Every estimated accrual gets trued up; what matters is what the true-up is. One answer flows through the current period and is forgotten; the other reaches an Item 4.02 filing and the recovery of executive pay. Under ASC 250 a change in estimate arises from new information and is prospective.
The line to an error is information availability, and it is a hard line
“If the information was known, or could have been known, as of the prior period, it is generally indicative of an error in the previous accounting.”
PwC, on differentiating a change in estimate from a correction of an error under ASC 250.
“Could have been known” is doing the work. ASC 250-10-20 defines an error as one resulting from mathematical mistakes, mistakes in applying GAAP, or oversight or misuse of facts that existed when the statements were prepared — and BDO lands squarely here: using outdated data when current data exists is error correction, not an estimation change. A split adjudicated next month is new information. A rate table not updated at fiscal-year start, splits the model has no field for, a SPIF never fed to accounting — those existed at close. That is an error.
An accrual trued up in the same direction every month is not noise; it signals methodology bias, which AS 2501 ¶.30–.31 directs auditors to evaluate cumulatively rather than one estimate at a time — and invites a bias finding, a control deficiency and the could-have-been-known argument at once.
If it is an error: materiality first
The standard is the familiar one — a substantial likelihood the reasonable investor would view the fact as significantly altering the total mix of information. The SEC's 2022 Munter statement adds a discipline: the consequences of restating must not influence a conclusion of immateriality, and a large error is hard to talk down on qualitative grounds.
| Route | When it applies | What it means in practice |
|---|---|---|
| Big R restatement | Material to one or more prior periods. | Reissue the affected prior filings; file an Item 4.02 Form 8-K within four business days. |
| little r revision | Immaterial to prior periods, but correcting it all currently would materially misstate current results. | Adjust comparatives without amending historical reports. Can still trigger Rule 10D-1 recovery. |
| Out-of-period adjustment | Clearly immaterial to both periods. | Correct currently; generally no disclosure. Still aggregated — SAB 108 governs prior-year effects. |
Munter is also explicit that material errors indicate material weaknesses in ICFR, and that material weaknesses can exist without material errors. And Rule 10D-1, implementing Dodd-Frank Section 954, requires recovery of erroneously awarded incentive pay after a restatement, including a little r revision.
Plan Mechanics: Where the Accounting Actually Lives
Treatment follows the plan document; where a plan is ambiguous the accounting is ambiguous, and the fix is to amend the plan. Whether a draw is an asset depends on one word: recoverable. A recoverable draw is recovered out of future incentive payments, so it is a current asset net of allowance. A guarantee is compensation, and because it is payable whether or not a contract is obtained it generally fails the ASC 340-40-25-2 incremental-cost test. Recoverability is a collectibility judgment, and law caps it: in Stein v. hhgregg, Inc., 873 F.3d 523 (6th Cir. 2017) the Sixth Circuit held that post-termination recoupment of draw deficits violated the FLSA. We found no Big Four guidance on draws; confirm yours with your auditors.
The trap: an accrual keyed to revenue in a business that credits more than revenue
Total credited volume can exceed actual revenue, so any accrual keyed to revenue rather than credited volume understates by the duplication factor. It is mechanical, not a judgment call, and the cleanest example of a difference that could have been known — plan rules and credit records both existed at close. That puts it on the error side of the ASC 250 line.
Currency and legal entity, compressed
On currency, ASC 830-30-45-3 requires the balance sheet date rate for assets and liabilities and the rate at the dates of recognition for revenues and expenses, with weighted averages permitted as approximations under ASC 830-10-55-10 and 55-11. Expense therefore translates at an average rate and the liability at the closing rate: they will not tie, and the difference is a translation effect, not an accrual error. Separately, a liability denominated outside the recording entity's functional currency is monetary and is remeasured each balance sheet date under ASC 830-20-35-2, with the change in earnings under ASC 830-20-35-1; nonmonetary items stay at historical rates (ASC 830-10-45-17), so the capitalised ASC 340-40 asset does not remeasure — an extension by classification, not something any source we located states. On entity, the employer bears the obligation: a rep employed by Entity A selling into Entity B leaves it in A, and the recharge belongs in the accrual period.
The trap: cost-plus-five on a cross-border sales-comp recharge
The familiar 5% markup comes from the OECD's simplified approach for low-value-adding intra-group services, and sales compensation is not in scope: OECD Transfer Pricing Guidelines Chapter VII, ¶7.47 expressly excludes sales, marketing and distribution activities. Sales activity requires a substantive functional analysis, and allocation keys must reflect the expected benefit. Get it wrong and the exposure is permanent-establishment, deductibility and withholding risk on top of a misstated entity P&L. Settle it with a tax adviser before coding the convention into the close.
The Close Calendar: Entries and Controls
Commissions are late because the inputs are, and the dependency is serial: bookings cutoff before credit and split resolution, credit before attainment, attainment before the payout run, the run before payroll cutoff. WorldatWork's list of comp error sources puts unapproved quotas first. The only lever is moving work earlier, which is what automation buys — cheap reprocessing, so a day-5 accrual and a day-9 true-up are affordable, plus one fewer error class, since a broken formula is an error rather than a change in estimate. It buys no judgment.
The journal pattern that encodes the sequence
Where the commission is an incremental cost of obtaining a contract, the liability is recognised first under ASC 710 and ASC 450-20; the debit is then classified to the ASC 340-40 asset and amortised. Accrue employer payroll taxes alongside it.
The controls auditors test
The commission accrual is a management review control, and Grant Thornton's design expectations are the ones to meet: precision appropriate to the risk of material misstatement; pre-defined criteria for what gets investigated; evidence of the depth at which the review operated — specific items questioned, not a sign-off; and documented resolution of each. It also stresses the reliability of the information the control runs on, brutal here because the population comes from CRM: rarely inside ITGC scope, editable after the fact. AS 2501 ¶.12–.14 makes data accuracy and completeness an explicit audit focus.
A defensible set reconciles the commissionable population to the revenue subledger; change-approves the rep master, quota master and rate tables; relies on ITGCs or recomputes a sample; reviews manual overrides; searches for unrecorded liabilities including off-system SPIFs; and reconciles the deferred-commission roll-forward under ASC 340-40-35-3. And it runs a look-back comparing prior-period accrual to actual, with a trend — management's defence against the cumulative bias finding in AS 2501 ¶.30–.31, and the most commonly missing control here.
The trap: controls aimed at the calculation, none aimed at the population
A perfect recomputation of the deals in the file says nothing about the deals not in it. Understated accruals are almost always completeness failures, not arithmetic failures. If your matrix has three controls over calculation, none over the CRM-to-subledger reconciliation and no look-back, you have documented the wrong risk.
Eight recurring errors and what each one costs you
Find three of these in your process and the accrual is not the number you think it is.
| # | Error | GAAP consequence |
|---|---|---|
| 01 | No accrual until the commission run completes | Cut-off misstatement, foreclosed by ASC 450-20-30-1. Where material, an error. |
| 02 | Accrual keyed to recognised revenue, not credited volume | Understates by booked-but-unrecognised volume plus the duplication factor, monthly, in one direction. The plan terms were known — an error. |
| 03 | Target rate applied where accelerators are in effect | Second-half understatement compounding into a large Q4 true-up. |
| 04 | Stale rate tables or broken spreadsheet formulas | An error. BDO: using outdated data when current data exists is error correction. |
| 05 | Expedient applied to a population that does not qualify | Measurement error plus disclosure failure — the election is disclosable under ASC 606-10-50-22. |
| 06 | Off-system SPIFs and manual exceptions never accrued | The classic unrecorded-liability finding. |
| 07 | Cross-border recharge marked up as a low-value service | Misstated entity P&L plus transfer-pricing exposure — OECD ¶7.47 excludes sales from the simplified regime. |
| 08 | CRM population never reconciled to the revenue subledger | An IPE and completeness deficiency — the highest-probability finding here. |
Where you must ask your own auditors
GAAP does not give one answer to these: each depends on your plan documents, contract population, entity structure or materiality. None should be settled from an article, including this one.
- Whether a continued-employment condition in your plan is substantive, and therefore defers recognition.
- Which commissions are incremental costs under ASC 340-40-25-2, whether the ASC 340-40-25-4 expedient is available, and the amortisation period implied by the commensurate-renewal-commission analysis.
- Approach A versus B for tiered plans, and whether the liability policy aligns with it.
- Whether a prior-period difference is an error, and whether the accrual needs ASC 275-10-50-8 and 50-9 disclosure.
- Whether draws are recoverable in fact and in law, and each obligation's denomination currency for ASC 830-20.
- Markup on a cross-border recharge — a tax adviser, not your auditor — and IRC §461 book-tax timing.
Frequently Asked Questions
Would your commission accrual survive a look-back?
Bring us your accrual method, your crediting rules and your close calendar. A free Direction Session gets you an independent read on where the accrual breaks and whether software is the answer — with no vendor on the other side of the table.