The Numbers We Have to Estimate

Stories Inc. has $15,000 of valid customer invoices after correcting the premature sale. How much should the close assume it will collect?

Waiting for every customer to pay would settle much of the uncertainty, but it would also delay the result beyond its usefulness. The close needs a supportable estimate now, a reviewer who can challenge it, and a way to learn from what happens next.

Build the allowance rather than announce it

In our fictional October case, the illustrative credit loss allowance is $1,000. Here is an illustrative calculation that produces it. These rates are invented teaching assumptions, not recommendations or findings about real customers.

Every invoice appears once. The separately assessed customer has been removed from both age-based groups, so their risk is not counted twice. Before applying any rate, the accountant ties the group's total back to gross receivables in the ledger. This example assumes that the contractual amounts and delivered performance are valid. Billing errors, price concessions and performance disputes need their own revenue assessment before we estimate losses from failure to collect a valid amount.

The entry records $1,000 of credit loss expense and a $1,000 allowance. Gross receivables remain $15,000; net receivables become $14,000. The allowance does not forgive customers' debts or identify every eventual nonpayment in advance.

Under IFRS 9, ordinary trade receivables without a significant financing component—a material financing arrangement within the payment terms—use a simplified approach based on losses expected over their remaining life. Historical experience needs relevant adjustment for current conditions and supportable forecasts. The IASB's explanation of the trade-receivables approach, on page 23, describes this method.

The reviewer challenges what drives the answer

The arithmetic is easy. Supporting the groups and rates is the work.

The accountant starts with an ageing report: invoices grouped by how long they have been outstanding or overdue. Collection history, customer circumstances and collection correspondence help establish whether the groups contain comparable risks. Later cash receipts may provide relevant evidence about recoverability at the reporting date; new developments need to be distinguished from conditions already present then.

A reviewer can ask why the customer in financial difficulty needs a 50% allowance and what evidence would change it. As a sensitivity illustration only, increasing that assumed rate to 60% adds $100 to the allowance and reduces pretax profit by $100. That is not another adjustment in our October case. It shows which judgment moves the result.

The estimate record should preserve the data date, group definitions, assumptions, calculation, journal reference and approval. Later, compare the estimate with actual collections, write-offs and unresolved invoices. Repeated misses in one direction can expose stale rates or poor groupings; a single different outcome does not prove that the earlier judgment was unreasonable.

Different uncertainties need different support

The $1,500 inventory write-down in our case asks what the books can recover through sale. A count establishes quantity; it does not establish selling proceeds or necessary selling costs. IAS 2's measurement requirements explain why both questions matter.

A warranty or legal obligation raises a different issue: uncertainty about what the business owes. Under IAS 37, a provision requires a present obligation from a past event, a probable outflow and a reliable estimate. Future operating losses alone do not justify one. IAS 37 overview

That provision is an extension, not another charge in Stories Inc.'s October case. In each situation, the amount needs evidence appropriate to the uncertainty. A reserve created merely to smooth future profit has no such foundation.

Later information needs a reporting-status decision

Our delivery invoice arrived before October sign-off: the team replaced the $2,400 accrual with a $2,700 payable and added $300 to expense. If evidence arrives later, “October is closed” is not enough information to decide what happens next.

For IFRS reporting, the events-after-reporting-period window runs to authorization for issue, not simply to the date a monthly ledger is locked. IAS 10's overview explains that boundary.

A revised estimate based on new information generally affects the current and, where relevant, future periods: prospective treatment. Correcting a material error in previously issued statements generally involves restating affected prior-period comparatives under IFRS: retrospective treatment, subject to applicable requirements and exceptions. IAS 8's explanation distinguishes these situations.

The document date, service period and authorized accounting date should remain traceable. Neither automatic backdating nor automatically charging the next month answers the accounting question.

Closing makes uncertainty reviewable. Maya can ask: What information supports this estimate, how sensitive is profit to the judgment, and what will we learn when the outcome arrives?

← Follow consumption and loss | Test the evidence →

Fictional teaching example. Personal views based on public sources; no confidential employer information or employer endorsement. Accounting policies and business circumstances require case-by-case analysis.