A customer signs a three-year service agreement. In year two the customer asks for a lower fee and a longer term. The client's bookkeeper signs an amendment, keeps billing, and keeps booking revenue at the new monthly invoice amount. Nobody asks whether the amendment changed the revenue the client had already recorded.
Contract modifications are where a clean revenue model turns into a judgment area. The answer is not one rule. It is a three-way decision, and each branch produces different journal entries. This guide walks through the decision, shows an entry for each outcome with illustrative numbers, and lists what an auditor should ask for.
What counts as a contract modification?
A modification is a change to an existing contract that alters its scope, its price, or both. It exists once the parties approve it, whether in writing, orally or through customary business practice. A modification is approved when it creates or changes enforceable rights and obligations. Until then, the existing terms keep applying.
Two points matter in practice:
- Disputes do not stop a modification. A modification can exist even when the parties dispute the scope or price, so the entity weighs the enforceable rights and obligations on all relevant facts (ASC 606-10-25-11).
- Unpriced change orders are approved changes in scope with no agreed price. The entity estimates the change in transaction price using the variable consideration guidance, which brings in the constraint (ASC 606-10-25-11). See /us/blog/asc-606-variable-consideration-and-constraint-audit-procedures.
When is a modification a separate contract?
A modification is a separate contract only when both conditions are met (ASC 606-10-25-12): the scope increases because distinct goods or services are added, and the price increases by an amount that reflects the standalone selling price (SSP) of those additions, adjusted for the circumstances of the contract. The original contract is then untouched, and the new items are accounted for on their own.
A blend-and-extend amendment is the common failure. The parties extend the term and set one blended price for old and new units. If the extension is priced below SSP, the price does not reflect SSP, the first condition alone is not enough, and the modification is not a separate contract.
What happens when it is not a separate contract?
The treatment depends on the nature of the goods or services still to be delivered.
| Remaining goods or services | Treatment | Effect on revenue already recorded |
|---|---|---|
| Distinct from those already delivered | Prospective: treated as if the old contract ended and a new one began | None |
| Not distinct, part of a partially satisfied performance obligation | Cumulative catch-up: treated as part of the original contract | Adjusted up or down in the period |
| A mix of both | Apply each method to the portion it fits | Adjusted only for the non-distinct portion |
A series of distinct services, such as monthly managed services, is accounted for prospectively even when the series is a single performance obligation.
Worked entries
All figures are illustrations.
1. Separate contract: added units at SSP
A manufacturer agrees to sell 100 units at $100. In month four the customer orders 20 more at $95, which is the SSP. Both conditions are met. The 20 units are a new contract, and the original 100 units are unchanged.
| Account | Debit | Credit |
|---|---|---|
| Accounts receivable | 1,900 | |
| Revenue | 1,900 |
Entry shown for delivery of the 20 additional units (20 x $95).
2. Prospective: price cut and extension of a service series
A three-year service contract pays $36,000 a year. After 24 months the parties cut the year-three fee to $24,000 and add a two-year extension for $48,000, prepaid at signing. SSP is $30,000 a year, so the extension price does not reflect SSP. The services are distinct, so the treatment is prospective. Revenue already recorded ($72,000 for 24 months) stays as it is.
Remaining consideration is $24,000 plus $48,000, or $72,000, spread over the remaining 36 months: $2,000 a month.
| Account | Debit | Credit |
|---|---|---|
| Cash | 48,000 | |
| Contract liability | 48,000 |
Entry at modification for the prepaid extension. Each month of year three, the entry is Cash $2,000 debit and Revenue $2,000 credit. In years four and five it is Contract liability $2,000 debit and Revenue $2,000 credit.
3. Cumulative catch-up: change order on a single performance obligation
A builder has a $300,000 fixed-price contract with expected total cost of $240,000. At the reporting date it has incurred $120,000 (50 percent complete) and has recognized $150,000 of revenue. The customer then approves a floor plan change. The price rises $80,000 to $380,000 and expected total cost rises $80,000 to $320,000. The remaining work is not distinct from the work done, so the change is treated as part of the original contract.
Progress is now $120,000 / $320,000 = 37.5 percent. Cumulative revenue is 37.5 percent x $380,000 = $142,500. Revenue already recognized was $150,000, so the catch-up is a $7,500 reduction.
| Account | Debit | Credit |
|---|---|---|
| Revenue | 7,500 | |
| Contract asset | 7,500 |
The entry assumes recognized revenue exceeded billings. Notice the direction: a price increase can still reduce revenue to date, because the larger cost estimate lowers the percent complete.
Audit angle
The documents that matter are amendments, order forms, change orders, emails that approve scope, and side letters. Modifications can live outside the contract file.
What the auditor tests:
- Completeness. Ask for a list of amendments in the period and agree it to billing changes and to customer correspondence. A price change in the billing system with no signed amendment is a lead.
- Approval. Confirm the change created enforceable rights. For unpriced change orders, inspect the support for the estimated price and test the constraint.
- Separate contract claims. Obtain SSP support for the added items. A modification priced at a discount is not a separate contract.
- Distinct or not. For prospective treatment, confirm the remaining items are distinct. For catch-up, recompute progress and transaction price.
- Allocation. For prospective treatment, recompute the consideration allocated to the remaining items as the consideration not yet recognized as revenue plus the consideration promised in the modification (ASC 606-10-25-13(a)).
Common misstatements: booking a blend-and-extend price as a new contract at the blended rate, recording billing changes as revenue changes, treating a scope reduction as separate, and ignoring approved change orders until the customer pays.
Related reading: /us/blog/asc-606-revenue-recognition, /us/blog/construction-contractor-audits-asc-606 and /us/blog/saas-revenue-recognition-audit-multi-element-contracts.
CORAA prepares ready-to-review audit files for US CPA firms from QuickBooks books; you review and sign. See /us.
Sources
- FASB, ASU 2014-09, full text via PwC Viewpoint (text of ASC 606-10-25-10 to 25-13: modification definition, separate contract test, prospective and cumulative catch-up treatment): https://viewpoint.pwc.com/dt/us/en/fasb_financial_accou/asus_fulltext/2014/asu_201409revenue_fr/asu_201409revenue_fr_US/asu_201409revenue_fr_US.html
- PwC Viewpoint, Revenue from contracts with customers guide, 2.9 Contract modifications: https://viewpoint.pwc.com/dt/us/en/pwc/accounting_guides/revenue_from_contrac/revenue_from_contrac_US/chapter_2_scope_and__US/29contract_modificat_US.html
- PwC Viewpoint, FASB Transition Resource Group staff paper, Evaluating contract modifications (January 26, 2015): https://viewpoint.pwc.com/dt/us/en/fasb_financial_accou/trg_revenue/trg_revenue_US/evaluating_contract__US.html
Part of CORAA University · US GAAP for private companies: related guides, calculators and templates.
AU-C references are to AICPA Professional Standards, paraphrased here; read the standard itself before relying on a requirement. This page is guidance, not professional advice. Report an error