Trade receivables can look straightforward on a balance sheet, but the allowance for credit losses depends on much more than an aging report. Customer disputes, payment patterns, concentration risk, changing economic conditions and inconsistent master data can all affect the estimate. A strong close process makes those inputs visible, repeatable and reviewable.
For controllers, the objective is not to predict every customer default perfectly. It is to apply the relevant accounting framework consistently, use reliable data, document material judgments and make sure the allowance reconciles to the receivables ledger and general ledger.
1. Establish a complete and accurate receivables population
Begin with the source population. Reconcile the accounts-receivable subledger to the general ledger and investigate differences before calculating the allowance. Confirm that the aging report includes all relevant legal entities, currencies, customer accounts and open items, and that credits, unapplied cash, disputed invoices and credit memos are treated consistently with the entity’s policy.
Check the aging logic. A report that ages from document date instead of contractual due date—or uses the wrong baseline after a payment-term change—can distort delinquency buckets. Validate key fields such as customer ID, payment terms, due date, invoice date, currency, business unit and dispute status.
Controller example: a customer account appears current because a credit memo was posted to a different customer number. The aging looks healthy, but the underlying balance is overstated. A monthly control should flag unusual credit balances, duplicate customer records and manual reclassifications for investigation.
2. Segment the portfolio by risk, not just by age
Aging is a useful starting point, but customers in the same aging bucket may have very different risk profiles. Consider whether receivables should be grouped by relevant shared characteristics, such as customer type, geography, industry, payment terms, product line, collateral or historical loss experience. Evaluate material or unusually risky exposures individually where appropriate under the applicable framework.
Keep segmentation practical and supportable. Too few pools can hide meaningful risk differences; too many can produce unstable loss rates and excessive administration. Document why each pool is appropriate and what events require a change in segmentation.
3. Build a disciplined estimate from evidence
Under US GAAP, ASC Topic 326 (CECL) requires expected credit losses to be estimated using relevant information about historical experience, current conditions and reasonable and supportable forecasts. FASB explains the model in its Credit Losses overview and discusses the use of historical information and forecasts in its Topic 326 staff Q&A.
For a portfolio using a loss-rate or provision-matrix approach, retain the historical data period, write-off and recovery definitions, calculation logic, adjustments for current conditions, forecast assumptions and rationale for the selected method. Do not apply a blanket percentage merely because it was used last quarter.
Use current collection information, customer-specific developments and relevant market conditions to challenge the model. A forecast adjustment should have a clear link to credit risk and a documented rationale. Avoid arbitrary overlays that cannot be explained or repeated.
4. Review the 2025 US GAAP update before the 2026 close
FASB issued ASU 2025-05, Measurement of Credit Losses for Accounts Receivable and Contract Assets in July 2025. The amendments provide a practical expedient for eligible current accounts receivable and current contract assets arising from revenue transactions: an entity may assume that current conditions as of the balance-sheet date remain unchanged over the remaining life of the assets when developing reasonable and supportable forecasts. The update also permits an entity other than a public business entity, if it elects the practical expedient, to make an accounting policy election to consider certain collection activity after the balance-sheet date.
The amendments are effective for fiscal years beginning after December 15, 2025, including interim periods within those fiscal years; early adoption is permitted. For calendar-year entities, that makes the 2026 reporting cycle an important implementation checkpoint. Do not assume an election is automatic or that it applies to every financial asset. Confirm eligibility, scope, election requirements, transition and disclosures against the ASU and the entity’s reporting circumstances.
Document the accounting policy decision, approval, affected asset population and implementation date. If the entity elects an available expedient, preserve evidence showing that the receivables and contract assets included meet the scope conditions. The update does not remove the need for accurate data, a supportable estimate or effective review controls.
5. Keep IFRS and Canadian ASPE analyses separate
Under IFRS 9 Financial Instruments, expected-credit-loss requirements apply to in-scope financial assets. For qualifying trade receivables and contract assets, IFRS 9 includes a simplified approach that generally recognises lifetime expected credit losses; the precise treatment depends on the asset and applicable requirements. A provision matrix may be a practical technique, but historical rates need to reflect current conditions and reasonable, supportable forward-looking information.
Canadian private enterprises applying ASPE should assess receivables under the applicable requirements in Section 3856, Financial Instruments, and the entity’s accounting policies. Do not import a CECL model or an IFRS 9 provision matrix without assessing whether it meets ASPE requirements. Multinational groups may need a controlled bridge between local statutory reporting and group reporting, with differences identified, approved and reconciled.
Authoritative standards and the current version applicable to the reporting period should govern the final accounting conclusion. The links above are starting points, not substitutes for reviewing the full requirements.
6. Challenge individual accounts and qualitative indicators
Define criteria for escalating exposures for specific review: material balances, long-overdue invoices, insolvency or restructuring notices, repeated broken payment promises, major disputes, customer concentration, requests for extended terms, or adverse developments in a customer’s industry or geography.
For each material exposure, document the balance, known facts, expected recovery, relevant support and reviewer conclusion. Avoid double-counting risk if an account is removed from a pooled calculation and assessed individually. Also review credit enhancements or collateral only to the extent permitted and relevant under the applicable accounting guidance.
7. Reconcile the allowance and control model changes
At each close, reconcile the allowance rollforward: opening balance, provision expense or benefit, write-offs, recoveries, acquisitions or disposals where applicable, foreign-exchange effects and ending balance. Tie the ending allowance to the supporting calculation, subledger or reconciliation schedule, general ledger and financial-statement disclosures.
Separate model changes from changes in portfolio composition and changes in underlying credit risk. Restrict access to formulas, source tables, loss-rate parameters and manual overlays. Retain version history, preparer and reviewer sign-offs, and evidence that the final approved calculation—not a working copy—was posted.
In SAP or another ERP, test the interfaces feeding the aging and allowance calculation. Reconcile record counts and balances, identify rejected or duplicated records, control customer-master changes and confirm that postings use approved accounts and document types. Where the estimate is calculated outside the ERP, reconcile the final journal entry back to the approved model output.
8. Use subsequent collections carefully
Cash received after period-end can be useful evidence about a receivable’s collectibility, but its accounting use depends on the applicable framework, the reporting date and any relevant policy elections. Under US GAAP, ASU 2025-05 includes a specific optional election for eligible entities other than public business entities to consider certain subsequent collection activity when estimating credit losses on in-scope current receivables and contract assets, if the practical expedient is elected.
Do not treat all post-close receipts as proof that there was no credit risk at the reporting date. Match receipts to specific invoices, verify the cash application, and distinguish full settlement from partial payment, disputed deductions, credit notes or payment from a third party. Document the cutoff and methodology applied.
Controller’s close checklist
- Reconcile the receivables subledger and aging report to the general ledger.
- Validate aging logic, payment terms, customer IDs, currencies and open-item completeness.
- Review segmentation and identify material or higher-risk exposures for individual assessment.
- Reperform loss-rate calculations and challenge historical data, overlays and forecast assumptions.
- Assess whether ASU 2025-05 applies and document any US GAAP elections for 2026.
- Keep IFRS 9 and Canadian ASPE analyses separate from the US GAAP model.
- Reconcile the allowance rollforward, model output, journal entry and disclosures.
- Control ERP interfaces, model access, parameter changes and exception resolution.
- Retain supporting evidence, approval, version history and explanations for material movements.
Conclusion
A reliable receivables allowance is built on complete source data, sensible risk segmentation, a supportable estimation method and an auditable close process. The 2026 US GAAP update makes it especially important to review policy elections and documentation for eligible current receivables and contract assets. Controllers should make sure the accounting framework is clear, the assumptions are evidence-based and every reported number can be traced to approved source data.
Informational only: This article is a practical control overview, not accounting, legal or audit advice. Apply the current authoritative literature and obtain qualified advice for your entity’s specific facts and reporting framework.
