Almadar A lender headquartered near KAFD still providing for bad debts only once they're clearly uncollectible is applying a standard IFRS 9 replaced years ago.
ECL calculations need to be applied consistently across entities feeding into multi-entity consolidation, and questions about how the model should be applied to a specific, unusual receivable often need technical accounting advisory input beyond the standard model itself. It also directly connects to order-to-cash data, since actual collection patterns are exactly what a defensible model needs to be built on.
Why this is harder than traditional bad debt provisioning
The standard requires a genuinely forward-looking estimate, incorporating macroeconomic factors and segmenting receivables by actual risk profile rather than simply aging buckets, which is a meaningfully more sophisticated exercise than the traditional practice of providing once a debt looks doubtful.
A common gap we find
Many companies still use simple aging-based provisioning, ninety days overdue equals a fixed provision percentage, which technically doesn't satisfy IFRS 9's forward-looking requirement and increasingly draws audit findings as auditors apply more scrutiny to this specific area.
A common pattern by business type
A Riyadh trading company with a broad, diverse customer base needs genuine risk segmentation across customer categories rather than one blanket assumption. An Riyadh contractor with a small number of large, concentrated customers needs individual assessment of each significant receivable rather than a portfolio-level statistical approach that doesn't fit a concentrated customer base.
What we deliver
A defensible ECL model appropriately scaled to your actual receivables profile, full documentation your auditors can work from directly, and an ongoing process for updating the underlying assumptions each reporting period rather than a model built once and left unchanged.
Why documentation matters as much as the model itself
An ECL model with sound logic but no supporting documentation trail is difficult for an auditor to actually rely on. We build the model and its documentation together from the start, since a model that can't be explained clearly to a reviewer months later is functionally almost as weak as no model at all.
Riyadh trading businesses with diverse customer bases need portfolio-level segmentation by risk category, while Riyadh contractors with concentrated large customers need individual receivable assessment, which means the two business types genuinely need different modeling approaches rather than one standard template applied uniformly.