On this page
Lesson details
- Estimated study time
- 110 min
Learning objectives (3)
Cedar Trail estimated warranty claims at 1.8 percent of sales on December 31. On February 4, the claims administrator reported a manufacturing defect. On February 9, the controller found a November quality report describing the same defect. The year-end estimate cannot be classified from the February headline. The November report may have existed, been available, reached the wrong owner, or been ignored. Each possibility changes the evidence analysis.
Build the information record before naming the route
Use one row for each source, not one row for each conclusion.
| Fact or document | Economic fact existed | Evidence created | Reasonably available to reporting | Actually used | Open question |
|---|---|---|---|---|---|
| November quality report | Nov. 18 | Nov. 20 | disputed | no | distribution and escalation log |
| December claim register | through Dec. 31 | Jan. 3 | Jan. 3 | yes | completeness control |
| February administrator analysis | through Feb. 4 | Feb. 4 | Feb. 4 | not at year-end | later evidence or confirmation of earlier condition? |
Do not compress “reasonably available” into the date a controller opened an email. Record systems, recipients, close instructions, escalation thresholds, review controls, and contradictions. If availability is unresolved, retain both classifications as conditional paths and stop the final entry.
The timeline serves two questions without deciding either automatically:
- Did new information revise an earlier supportable estimate?
- Did the earlier file overlook or misuse a fact that existed when the statements were prepared?
A later unfavorable outcome answers neither by itself. Hindsight can test how an estimate performed; it cannot be inserted into the earlier information set.
Freeze the reporting surface
Next record the entity, fiscal calendar, reporting date, statements already issued, comparative periods to be presented, earliest period presented, currency, display units, audit status, filing status, and applicable public-company scope. Those coordinates determine where a supported effect appears.
A January discovery can arise before issuance of the December statements, after issuance but before the next quarter, or years later. The ledger mechanics may look similar while the statement, audit, filing, and communication response is different. The module receives those response conclusions from the appropriate owners; it does not infer them from discovery date alone.
Build the standards clock
For every potentially relevant pronouncement, keep these dates distinct:
- proposal date and comment deadline;
- final issue date;
- effective date by entity class;
- permitted early-adoption date and conditions;
- the entity's elected adoption date;
- transition date defined by the pronouncement; and
- disclosure periods.
ASU 2025-11, for example, is issued but remains pending for entities that have not reached or elected its effective date. ASU 2025-12 is also issued, but its technical amendments do not become a blanket Topic 250 rewrite. A proposal has no current-ledger authority. The clock keeps current, pending, early-adopted, and proposed content from collapsing into one column.
Evidence owners and stop conditions
The accounting team owns the route memo and statement bridge. Business owners provide transaction and operational facts. Tax supplies law and basis. Legal addresses contracts and legal consequences. Audit owns its procedures and report response. SEC reporting owns the covered filing analysis. Control owners assess deficiencies. A missing owner is not a zero-value assumption.
The information phase closes only when the file can answer, or explicitly leave open, what existed, what was available, what was used, which statements and periods are affected, which authority was current, and which specialized conclusions remain outside accounting's calculation model.