Price concession accounting under ASC 606 treats a reduction in what you actually expect to collect, below the contract’s stated price, as variable consideration. That means the reduction comes off the top line as lower revenue, not off the bottom line as an expense. Get the classification wrong and you overstate both revenue and accounts receivable, even when net income looks right.
What Counts as a Price Concession
ASC 606 lists price concessions alongside discounts, rebates, refunds, credits, incentives, performance bonuses, and penalties as items that make contract consideration variable.1FASB. ASU 2014-09 Revenue from Contracts with Customers (Topic 606) What sets concessions apart in practice is timing: the contract states one number, and circumstances push the collectible amount lower.
Two situations make consideration variable even when the contract itself is silent about a possible reduction. First, your customer has a valid expectation that you’ll accept less than the stated price because of your customary business practices, published policies, or specific statements you’ve made. Second, other facts suggest your intention when entering the contract was to offer a price concession.1FASB. ASU 2014-09 Revenue from Contracts with Customers (Topic 606) If you routinely grant reductions to customers in similar situations, the standard treats those reductions as baked into the deal from day one.
Common triggers include a customer in severe financial difficulty that makes full payment unlikely, a legitimate dispute over product quality or delivery, and industry norms where sellers habitually accept less than billed amounts. Healthcare billing is the classic example. The thread through all of them is that you never really expected to collect the full stated price.
Price Concessions vs. Discounts, Rebates, and Contract Modifications
Discounts and volume rebates are negotiated into the deal before or at signing. They incentivize specific customer behavior: buy more, pay faster, commit longer. Because they’re established upfront, they reduce the transaction price from day one as a known element of the pricing structure.
A price concession works as a remedy. It addresses a performance shortfall, a collectibility problem, or a pattern of accepting less than the stated price. The intent isn’t to drive future business; it’s to resolve a situation that already exists.
The line between a price concession and a contract modification is subtler, and it trips a lot of teams. A contract modification creates new rights and obligations or changes existing ones after the original contract was formed. A price concession resolves variability that existed when the contract was signed, even if nobody explicitly named it at the time. If your customer had a valid expectation of a price break based on your past practices, the concession you eventually grant isn’t changing the deal; it’s confirming what the economics always were. You account for it as a change in the transaction price under the variable consideration rules, not as a modification. A true modification, where the parties agree to fundamentally change contract terms, follows separate guidance under ASC 606-10-25-10 through 25-13.
Price Concession vs. Bad Debt
This is where teams most often stumble, and the income statement treatment is completely different. A price concession reduces revenue. A bad debt is an expense under ASC 326, the credit loss standard. Misclassifying one as the other overstates revenue even when the bottom line ties out.
The question to ask: did you always expect to collect less than the stated price, or did you believe you were entitled to the full amount and then the customer simply couldn’t pay? If you never performed a credit assessment before delivering, or if you have a long history of accepting less than the invoiced amount, you’re looking at an implicit price concession. You weren’t extending credit in the traditional sense; you were delivering knowing the final price would land below the invoice. That adjustment comes off the top line.
A genuine bad debt arises when you had a reasonable expectation of full collection at the time of sale and the customer’s financial situation deteriorated afterward. You recognized revenue at the full transaction price and established a receivable. The subsequent inability to collect is an impairment of that receivable, recorded as a credit loss expense below the revenue line.
Where Price Concessions Land in ASC 606
ASC 606’s five-step model gives price concessions two possible homes. Which one applies depends on when the concession surfaces and what it signals about the contract itself.
Step 1: The Collectibility Threshold
Before you recognize any revenue, Step 1 asks whether it’s probable you’ll collect the consideration you’re entitled to under the contract. If the answer is no, the contract doesn’t meet the criteria for revenue recognition at all. When a contract fails this threshold, you can only recognize revenue when specific conditions are met: you’ve finished transferring the goods or services, the contract has been terminated, or you’ve received nonrefundable payment with no remaining obligations.1FASB. ASU 2014-09 Revenue from Contracts with Customers (Topic 606)
If a price concession surfaces early and signals that you never expected to collect the original amount, this is where it lands. It isn’t variable consideration to estimate; it’s evidence that the contract doesn’t pass the front-door test. Once collectibility is established, the standard doesn’t require you to keep reassessing it unless the customer’s ability to pay deteriorates significantly.
Step 3: Variable Consideration
The more common path treats the concession as variable consideration in Step 3. This applies when the contract clears Step 1, but you expect the amount you’ll ultimately collect to be less than the stated price because of a performance dispute, your historical pattern of granting concessions, or similar factors. You estimate the reduction and subtract it from the transaction price before recognizing revenue.1FASB. ASU 2014-09 Revenue from Contracts with Customers (Topic 606)
Estimating the Concession Amount
When you treat a concession as variable consideration, you need a defensible estimate of how much the final price will drop. ASC 606 gives you two methods, and you use whichever one better predicts the amount you’ll actually collect.1FASB. ASU 2014-09 Revenue from Contracts with Customers (Topic 606)
- Expected value. A probability-weighted average across a range of possible outcomes. This works when you have a large portfolio of similar contracts and historical data. If you routinely grant concessions across hundreds of customer accounts, weighting each outcome by its likelihood produces a reliable aggregate estimate.
- Most likely amount. The single outcome you consider most probable. This fits contracts where there are really only two scenarios, such as the customer either gets a $15,000 reduction or pays in full, with no middle ground.
Whichever method you choose, apply it consistently to similar types of contracts. The method isn’t a free choice you make deal by deal to produce a more favorable number; it’s driven by which approach genuinely fits the pattern of possible outcomes.
The Constraint on Variable Consideration
Estimating isn’t the last step. ASC 606 imposes a constraint: you can only include variable consideration in the transaction price to the extent it’s probable that a significant reversal of cumulative revenue won’t occur when the uncertainty is eventually resolved.1FASB. ASU 2014-09 Revenue from Contracts with Customers (Topic 606) In plain terms, if there’s a real chance your estimate is too optimistic and you’d have to walk back a material chunk of revenue later, you need to be more conservative now.
Factors that increase the risk of a significant reversal include situations where the consideration depends heavily on forces outside your control, where the uncertainty will take a long time to resolve, where you have limited experience with similar contracts, or where you have a track record of offering a wide range of concessions in comparable situations.1FASB. ASU 2014-09 Revenue from Contracts with Customers (Topic 606) The more of these that apply, the more aggressively you constrain, which means recognizing less revenue upfront.
A practical example. You have a $100,000 contract and estimate a likely $15,000 price concession. If your estimate is solid and unlikely to shift materially, you record $85,000 as the initial transaction price. If the concession amount is still uncertain because the quality dispute hasn’t been fully assessed, you might constrain further, potentially recognizing less than $85,000 until the picture clarifies.
Updating Estimates Over Time
Your initial estimate isn’t final. ASC 606 requires you to revisit variable consideration estimates at each reporting date throughout the contract period. When the estimate changes, you record the adjustment as a cumulative catch-up in the current period: recalculate what revenue should have been recognized to date under the new estimate and book the difference immediately. You don’t restate prior periods.
A concession you didn’t anticipate, or underestimated, at contract inception shows up as a revenue reduction in the period you revise. If a dispute resolves in your favor and the concession turns out smaller than expected, you recognize the additional revenue in the period the estimate changes. The constraint still applies at each reassessment, so any upward revision still needs to pass the “probable no significant reversal” test.
Recording the Concession
The journal entry is straightforward. Debit a contra-revenue account, often called “implicit price concessions” or “revenue adjustments,” and credit an allowance against accounts receivable. Both reported revenue and the net receivable decrease by the estimated concession amount. No expense account is involved, because the concession isn’t a cost of doing business; it reflects the fact that your selling price was always lower than the stated amount.
For a $100,000 contract with a $15,000 estimated concession, the entry debits the contra-revenue account for $15,000 and credits the allowance for uncollectible accounts receivable for $15,000. Revenue shows up net at $85,000, and the receivable balance reflects only what you actually expect to collect. When the estimate changes in a later period, you adjust both the contra-revenue account and the allowance by the difference.
Disclosure Requirements
ASC 606 requires meaningful disclosure about how variable consideration, including price concessions, affects your financial statements. You need to disclose your significant payment terms and whether the transaction price estimate is typically constrained. You also need to explain the methods, inputs, and assumptions you used to estimate variable consideration and to assess whether the constraint applies.1FASB. ASU 2014-09 Revenue from Contracts with Customers (Topic 606)
If you’ve constrained any variable consideration, disclose that amounts were excluded from the transaction price and explain why. The standard also requires disclosure of the judgments and any changes in judgments used to determine the transaction price. These give investors and auditors visibility into how much of your revenue line relies on management estimates and how sensitive those estimates are to future changes.
Documentation, Controls, and SEC Enforcement Risk
Documentation is what separates a defensible position from an audit finding. For each concession, maintain internal memos explaining why it was granted, the customer circumstances that triggered it, and how the estimated amount was calculated. Keep customer correspondence, signed settlement agreements, and records showing approval at the appropriate management level.
Effective controls start with segregation of duties: the person who processes an adjustment shouldn’t be the same person who initiates or approves it. Written policies should define the specific circumstances under which a concession can be offered and set dollar thresholds that require escalation to senior management or finance before any reduction is finalized.
For public companies the stakes are higher. The SEC has specifically flagged “side agreements” that effectively amend a master contract as a recurring problem in revenue recognition. These arrangements, which can include undisclosed cancellation rights, price adjustments, or other terms that reduce the amount a customer ultimately pays, must be identified and properly accounted for. The SEC requires that companies maintain policies and internal controls providing reasonable assurance that transactions affected by side agreements are properly recorded.2U.S. Securities & Exchange Commission. Codification of Staff Accounting Bulletins – Topic 13: Revenue Recognition Failure can implicate the books-and-records and internal controls provisions of the Securities Exchange Act.
Periodic review of concession trends across your customer base is worth the effort. If concessions are climbing in a particular product line or customer segment, that pattern may signal pricing problems or quality issues that need operational attention, not just accounting adjustments. It also helps calibrate whether your variable consideration estimates are keeping pace with reality.
IFRS 15 Reporters
If you report under IFRS rather than U.S. GAAP, the treatment is largely parallel. IFRS 15 also categorizes price concessions as variable consideration and requires estimation using either the expected value or the most likely amount approach.3IFRS Foundation. Constraining Estimates of Variable Consideration – IFRS 15 The meaningful difference is the constraint threshold. IFRS 15 uses a “highly probable” standard for including variable consideration in the transaction price, while ASC 606 uses “probable.” “Highly probable” under IFRS is generally considered a higher bar, so IFRS reporters may need to constrain more aggressively in borderline situations, potentially recognizing less revenue upfront than a U.S. GAAP reporter with the same facts.
Book-Tax Differences
Revenue recognized under ASC 606 doesn’t automatically match taxable income. When you reduce your GAAP transaction price for an estimated concession, the IRS may not recognize that reduction in the same period, because tax rules generally follow different timing conventions for when income is includable or deductible. That creates a temporary book-tax difference that needs to be tracked and reconciled. Corporations with total assets of $10 million or more reconcile these differences on Schedule M-3 of Form 1120, which maps financial statement net income to taxable income line by line.4Internal Revenue Service. Instructions for Schedule M-3 (Form 1120) Smaller corporations use the simpler Schedule M-1. Either way, your tax team needs to understand the timing and classification of concessions under GAAP for the reconciliation to hold up.