A trading company that still provides for bad debts only once they are clearly uncollectible is applying a model that IFRS 9 replaced years ago.

ECL calculations need to be applied consistently across the entities feeding multi-entity consolidation. Questions about how the model applies to a specific, unusual receivable often need technical accounting advisory input beyond the standard model. The work also connects to order-to-cash data, because actual collection patterns are what a defensible model is built on.

Why this is harder than traditional bad debt provisioning

The standard requires a forward-looking estimate that incorporates macroeconomic factors and segments receivables by risk profile, not only by aging bucket. That is a more sophisticated exercise than providing once a debt looks doubtful.

The method for trade receivables

For trade receivables, IFRS 9 allows a simplified approach: lifetime expected credit losses, often estimated with a provision matrix. The matrix starts from historical loss rates by customer segment and adjusts them for current conditions and forecasts.

A common gap

Many companies still use a simple fixed percentage provision by age, with no adjustment for current conditions or forecasts. IFRS 9 allows a provision matrix by age, but only when historical loss rates are adjusted for forward-looking information. A fixed percentage without that adjustment does not meet the requirement, and auditors may question it.

Approach by business type

A trading company with a broad, diverse customer base needs risk segmentation across customer categories instead of one blanket assumption. A contractor with a small number of large customers needs individual assessment of each significant receivable, because a portfolio-level statistical approach does not fit a concentrated customer base.

What the work delivers

A defensible ECL model scaled to your receivables profile, with full documentation your auditors can work from directly. An ongoing process updates the assumptions each reporting period, so the model is not built once and left unchanged.

Why documentation matters as much as the model

An ECL model with sound logic but no documentation trail is difficult for an auditor to rely on. The model and its documentation are built together from the start, because a model that cannot be explained clearly to a reviewer later is almost as weak as no model at all.