Contract evidence sets revenue amount and timing
Contract evidence supplies the expected amount and timing. The ledger shows what was recorded. These rules set up the prepared review that follows.
- Reading contracts for revenue amount and timing uses the promised goods or services, transaction price, and transfer of control to determine revenue amount and timing.
- ASC 606-10-25-27 recognizes revenue over time when one of three conditions is met: the customer receives and consumes benefits as performed, the customer controls the asset as it is created or enhanced, or the asset has no alternative use and the entity has an enforceable right to payment for work completed.
- The no-alternative-use and enforceable-payment conditions require contract-specific judgments, not percentage tests.
- ASC 606-10-25-30 and 25-31 recognize revenue at a point in time when the performance obligation is not satisfied over time and control transfers.
- Point-in-time indicators include a present right to payment, legal title, physical possession, transferred risks and rewards, and customer acceptance.
- ASC 606-10-32-5 and 32-11 include expected variable consideration in the transaction price only when it is probable that a significant reversal will not occur.
- ASC 606 provides no fixed percentage cutoff for probable or significant reversal.
- Compare the analytics expectation with contract and fulfillment evidence, compare the ledger with the same evidence, classify each difference, and post an entry only when the ledger is wrong.
Analytics expectations versus ledger revenue
Prepared by the revenue analyst; it does not tie to the source facts.
Loading diagram…
| Contract | Analytics expected through March 31 | Ledger revenue through March 31 | Difference: analytics minus ledger |
|---|---|---|---|
| A: Support service | $36,000 | $36,000 | $0 |
| B: Equipment delivery | $50,000 | $0 | $50,000 |
| C: Performance bonus | $90,000 | $75,000 | $15,000 |
| D: Custom implementation | $20,000 | $25,000 | ($5,000) |
| Total | $196,000 | $136,000 | $60,000 |
| Contract | Source contract and fulfillment evidence | Ledger detail |
|---|---|---|
| A | Fixed $120,000 stand-ready support from January 1 through December 31. The customer receives support over time. January through March has elapsed. | $12,000 posted in each of the three months, totaling $36,000. |
| B | Equipment price is $50,000. Equipment was delivered and accepted on March 15. Title and possession transferred. | No revenue posted. |
| C | Fixed fee is $75,000. The possible bonus is $15,000. Current evidence does not make including the bonus probable without a significant reversal. | $75,000 posted. |
| D | Fixed price is $80,000. The asset has no alternative use. The contract gives an enforceable right to payment for work completed. Approved progress at March 31 is 25%. | $25,000 posted. |
The reported totals differ, but the cause appears only when each line is traced to its source evidence.
Correcting analytics and ledger errors
A nonzero variance is only a starting point. A zero variance is not proof that both sides are right. The table identifies the wrong side, applies the rule, and determines whether an entry is needed.
| Problem | Where it sits | Correct figure or treatment | Rule or chapter | Error tag |
|---|---|---|---|---|
| A analytics expectation uses $36,000 for three months. | Analytics row A | $30,000. $120,000 divided by 12 months times three months. | Reading contracts for revenue amount and timing; ASC 606-10-25-27. | calculation |
| A ledger repeats the same wrong $36,000. | Ledger row A | Revenue should be $30,000. Reduce the ledger by $6,000. | Reading contracts for revenue amount and timing; ASC 606-10-25-27. | response entry |
| B ledger has no revenue after the accepted delivery. | Ledger row B | Record $50,000 of revenue on March 15. | Reading contracts for revenue amount and timing; ASC 606-10-25-30 and 25-31. | response entry |
| C analytics includes the $15,000 bonus and reports $90,000. | Analytics row C | Use $75,000. Exclude the $15,000 bonus. No ledger entry is needed. | ASC 606-10-32-5 and 32-11. | rule selection |
| D ledger records $25,000 instead of progress-based revenue. | Ledger row D | Revenue is $20,000. $80,000 times 25%. Reduce the ledger by $5,000. | ASC 606-10-25-27 and 25-31. | response entry |
Contract A has a zero reported variance, but both amounts are wrong. Contract C needs an analytics correction, but no ledger entry. Corrected analytics revenue and corrected ledger revenue are both $175,000. Ledger entries reduce A by $6,000, increase B by $50,000, and reduce D by $5,000. The net ledger adjustment is an increase of $39,000.
The smaller review changes the facts. Its differences separate a ledger error, an analytics error, and a shared understatement.
Support, product sales and performance bonuses
The controller prepared this exception review. It still contains errors.
| Contract | Analytics expected | Ledger recorded | Source fact |
|---|---|---|---|
| E: Annual support | $24,000 | $22,000 | The contract is $72,000 for nine months of support. Three months have elapsed. The customer receives support monthly. |
| F: Product sale | $30,000 | $0 | The product price is $30,000 and was shipped on March 28. The contract requires customer acceptance. Acceptance will not occur until May 5. |
| G: Service with bonus | $30,000 | $30,000 | The fixed fee is $30,000 plus a $10,000 bonus. The service is complete. Approval evidence makes inclusion probable with no significant reversal expected. |
Practice
For Contract E, which side contains the error?
For Contract G, what revenue adjustment should be posted to correct the ledger after the analytics output is corrected?
For Contract F, is a revenue entry needed now?
Tracing exceptions and correcting revenue
💎 CHECK:
- Trace every exception to contract evidence and ledger detail; do not rely on the variance alone.
- Repair the analytics logic when its expectation is wrong, and post only the supported ledger difference.
- A zero variance can hide matching errors, while a nonzero variance can disappear without an entry when the ledger is already correct.
Unlock the full lesson and continue reading
Signup to continue reading this lesson and unlimited access questions, flashcards, AI notes, and more

