CECL for Private Companies: The Receivables Allowance Under ASC 326

What Is CECL?

CECL for private companies is the current expected credit loss model in ASC 326-20, and it applies to ordinary trade receivables, not only to loans. Under that subtopic, a company records an allowance for credit losses on trade receivables and ASC 606 contract assets from the day the asset is recognized, measured over the life of the asset. There’s no loss trigger to wait for.

Indinero’s CPA team runs that scope question against client AR inside the monthly close, and it still catches controllers who have never written off an invoice and assumed that settled it. It doesn’t. ASU 2016-13 replaced the incurred-loss framework, under which a loss had to be probable and reasonably estimable before anyone could book it, with a lifetime expected-loss measurement.

ASC 326-20 applies to financial assets measured at amortized cost. That sweeps in:

• Trade receivables arising from ASC 606 revenue transactions
• Contract assets under ASC 606
• Net investments in leases
• Held-to-maturity debt securities

The private company timeline is settled. ASU 2016-13 was issued in June 2016, and ASU 2019-10 deferred the private company, not-for-profit, and smaller reporting company effective date to fiscal years beginning after December 15, 2022, including interim periods within those years. A calendar-year private company first applied CECL in FY2023 and first reported under it at December 31, 2023. If those statements still carried an allowance for doubtful accounts computed on a probable-loss basis, that’s a GAAP departure sitting in the balance sheet, not a naming convention. It’s the same policy-first discipline behind GAAP accounting for startups.

Zero is a permissible answer, but it’s a conclusion, not a default. ASC 326-20-30-10 lets an entity record no allowance where historical credit loss information, adjusted for current conditions and reasonable and supportable forecasts, supports an expectation that nonpayment of the amortized cost basis is zero. Note the illustration the codification chose. ASC 326-20-55-49 uses U.S. Treasury securities. A receivable from a Series B customer is not a Treasury, and Deloitte’s credit losses roadmap states plainly that an entity is unlikely to support a no-expected-loss assertion on a trade receivable.

A clean history is an input, not an exemption.

The FASB then amended the measurement guidance on July 30, 2025 with ASU 2025-05, which is where most of this year’s work sits.

The ASC 326 Measurement Model

The ASC 326 measurement model prescribes inputs, not a method, which means the aging schedule you already run can carry the estimate. ASC 326-20-30-3 requires the estimate to reflect historical experience, current conditions, and reasonable and supportable forecasts. Everything past those three inputs is method choice, and a loss-rate or provision-matrix approach built on your own aging is expressly acceptable for trade receivables.

Building an ASC 326 accounts receivable estimate is four steps, and you already do the first two.

1. Pool by shared risk characteristics. ASC 326-20-30-2 requires collective measurement wherever financial assets share similar risk.
2. Build the historical loss rate. Write-offs and recoveries by pool and by aging bucket, pulled over a period long enough to mean something.
3. Adjust for current conditions. ASC 326-20-30-9 requires you to ask whether history still describes what you expect over the life of the receivables, and to adjust when it doesn’t.
4. Adjust for reasonable and supportable forecasts. Then revert to historical loss information for periods beyond the horizon you can actually forecast.

The output isn’t a delinquency report, because it’s a lifetime rate on a pool rather than the odds of slipping one bucket further past due. And it isn’t an industry benchmark you can download. The standard starts from your own write-off history and treats external data as a supplement to it.

Measurement also happens at every reporting date, not once at year-end. Current conditions move most between quarters, and they move with things your team already watches. A shift in the mix behind your accounts receivable turnover ratio, a loosening of credit terms, or one large customer entering distress all belong in the estimate the quarter they happen.

Pooling Receivables by Risk

ASC 326-20-30-2 makes pooling mandatory, not optional, wherever receivables share similar risk characteristics. PwC’s guidance on applying CECL to trade receivables and contract assets identifies the usual characteristics: customer credit rating, aging category, industry, geography, product line, and other factors bearing on the likelihood of nonpayment.

For a subscription business, the segmentation that actually predicts loss is usually some combination of:

• Plan tier or contract size, and self-serve versus enterprise
• Billing model, month-to-month versus annual prepaid
• Geography, domestic versus international
• Industry concentration, especially a single regulated vertical or a book weighted toward early-stage venture-backed buyers

One blended matrix across the whole book is usually too blunt to survive review. Deloitte makes the same point, that the matrix frequently has to be applied at a more disaggregated level. A receivable that shares characteristics with no pool gets evaluated individually.

Building the Loss-Rate Estimate

Start with your own write-offs and recoveries by pool, then compute a loss rate per aging bucket. The codification’s illustration is the cleanest template available. ASC 326-20-55-37 through 55-40, Example 5, walks through Entity E, a manufacturer selling to retail stores on 90-day terms with a 2% discount for payment within 60 days. Entity E’s tracked historical credit loss percentages:

Aging bucket	Historical loss rate
Current	0.3%
1-30 days past due	8%
31-60 days past due	26%
61-90 days past due	58%
More than 90 days past due	82%

Two cells matter more than the rest. The current bucket carries 0.3%, not zero, and that one number is the entire CECL idea. The rates further down look steep because they’re lifetime rates on a pool, not point-in-time delinquency probabilities.

ASC 326-20-30-9 then requires the current-conditions adjustment. After that comes the forecast. In Example 5, Entity E adjusts its historical rates down by roughly 10% because unemployment has decreased and it expects a further decrease over the next year, reverting to historical loss information for periods beyond which it can make a reasonable and supportable forecast.

That fourth step drew the most complaints from private companies. It’s also the step ASU 2025-05 takes away.

What ASU 2025-05 Changes

ASU 2025-05, Financial Instruments, Credit Losses (Topic 326): Measurement of Credit Losses for Accounts Receivable and Contract Assets, was issued July 30, 2025 off the Private Company Council agenda. Private company stakeholders told the Board that forecasting expected losses on short-dated receivables was burdensome relative to the outcome.

The full text of the ASU adds ASC 326-20-30-10A through 326-20-30-10H for measurement, ASC 326-20-50-12A and 326-20-50-12B for disclosure, ASC 326-20-55-40A through 326-20-55-40Q for implementation guidance and examples, and transition guidance at ASC 326-10-65-6.

What’s eligible. Current accounts receivable and current contract assets arising from Topic 606 transactions, including balances acquired in a Topic 805 business combination and balances picked up on consolidation of a variable interest entity. ASC 326-20-30-10B defines current using a one-year period unless the entity’s operating cycle exceeds 12 months, in which case the longer period governs. For most SaaS and mid-market companies that’s a 12-month test, and nearly the whole AR book qualifies. A multi-year unbilled balance on a long-term implementation contract would not.

The expedient. ASC 326-20-30-10C lets any entity elect to assume that current conditions as of the balance sheet date don’t change for the remaining life of the asset. It removes the reasonable-and-supportable forecast step for eligible assets.

What it does not do. It does not excuse the current-conditions adjustment. An entity electing the expedient still has to adjust historical loss information where that information doesn’t reflect conditions at the balance sheet date, and the guidance names identified customer financial distress, an expansion of credit policy to lower-quality customers, and the onset of a severe economic recession. The expedient freezes today’s conditions going forward. It doesn’t let you ignore today.

The non-PBE layer. ASC 326-20-30-10E permits an entity other than a public business entity that has elected the expedient to also elect an accounting policy of considering collection activity after the balance sheet date but before the financial statements are available to be issued. ASC 326-20-30-10F sets the sequence. Evaluate subsequent collections first and record no allowance against amounts actually collected, then apply the expedient to the remaining uncollected balances by delinquency status at the evaluation date. Both elections apply to all eligible current accounts receivable and current contract assets. It isn’t a cherry-pick by pool.

Disclosure and dates. ASC 326-20-50-12A requires disclosure that the practical expedient has been elected, and of the accounting policy election where both are taken. ASC 326-20-50-12B requires a non-PBE electing the subsequent-collections policy to disclose, in annual reporting periods, the date through which it considered collection activity. Transition sits at ASC 326-10-65-6. Effective for annual reporting periods beginning after December 15, 2025 and interim periods within those annual periods, early adoption permitted where financial statements have not yet been issued or made available for issuance, applied prospectively to estimates performed after the date of adoption, and no preferability assessment for a non-PBE adopting after the effective date.

For a calendar-year private company, that makes the December 31, 2026 close the first required application, and Q1 2026 the first interim period under it.

SaaS-Specific Application

For a SaaS company the hard part of ASC 326 isn’t the receivable. It’s the contract asset nobody put in scope. ASC 606-10-45-3 describes a contract asset, where goods or services have transferred but the right to consideration is conditional on something other than the passage of time. ASC 606-10-45-4 describes a receivable, where the right is unconditional and only time stands between you and payment. Both are in scope for ASC 326-20 impairment, and contract assets often take longer to convert to cash.

Where this shows up in a subscription stack:

• Implementation and onboarding revenue recognized over time while billing stays milestone-gated. Revenue is booked. The right to bill is conditional. That’s a contract asset.
• Usage and overage revenue recognized in the period consumed and invoiced the following cycle. It’s usually labeled “unbilled receivable” in the ledger, but the subledger label doesn’t control the classification. ASC 606-10-45-3 and 45-4 do.
• Multi-element arrangements where transaction price allocated to a delivered obligation runs ahead of cumulative billings.
• Ramped or back-loaded annual contracts where straight-line recognition outpaces the invoicing schedule.

Clearing the collectibility threshold in Step 1 of ASC 606 at contract inception doesn’t preclude expected credit losses on the resulting asset. Deloitte says that directly. The two assessments answer different questions at different dates.

Short collection cycles cut both ways. A 30-day cycle shrinks the lifetime horizon, which is exactly why the ASU 2025-05 expedient fits a subscription book so well. It also means one enterprise logo going insolvent can swamp a pool. Concentration matters more than tenure in a SaaS AR book.

Thin history isn’t a pass either. A Series B company with 18 months of billing history and a handful of write-offs has a small sample, not an exemption. Supplement it with customer credit data, default data for the verticals you’re concentrated in, and observable payment behavior inside the pool. Documenting that estimate is one of the first things our SaaS accounting engagements stand up.

And churn is not a credit loss. A customer who cancels at renewal and pays everything owed produced none. A customer who disputes and never pays produced one. Price concessions and service credits granted for commercial reasons are variable consideration under ASC 606, not credit losses under ASC 326. Mixing them inflates the historical loss rate and misstates revenue.

Common Pitfalls

First-year ASC 326 errors cluster around policy, not arithmetic. The spreadsheet is rarely the problem.

1. Renaming the account and calling it done. Changing “allowance for doubtful accounts” to “allowance for credit losses” without changing the measurement is the most common failure. The methodology has to change, not the caption.
2. A zero allowance with no file. ASC 326-20-30-10 permits zero. It doesn’t permit an undocumented zero. The support has to exist before the assertion does.
3. One undifferentiated pool. A single blended rate across self-serve and enterprise, or across a concentrated vertical and a diversified one, won’t survive review under ASC 326-20-30-2.
4. Assuming the ASU 2025-05 expedient removes the current-conditions adjustment. It removes the forecast step only. Getting this backwards is the single most likely technical error in the first year of application.
5. Electing the expedient inconsistently. It applies to all eligible current accounts receivable and current contract assets, not to the pools where it happens to help.
6. Leaving contract assets out of scope. Unbilled balances and implementation contract assets are in scope under ASC 326-20 and are routinely missed entirely.
7. Mixing service credits and commercial concessions into the historical loss rate. Those are variable consideration under ASC 606. They inflate the rate and misstate revenue at the same time.
8. Adopting the subsequent-collections policy without fixing the evaluation date. ASC 326-20-50-12B requires disclosing the date through which collection activity was considered. Pick it, document it, apply it the same way every period.
9. No rollforward. ASC 326-20-50-7 calls for the allowance rollforward by class of financing receivable, and it’s far easier to maintain monthly than to rebuild during fieldwork.

Most generalist firms never revisit the measurement once the account was renamed. Indinero’s CPA team catches these during monthly close review, which is also where the rollforward gets maintained instead of reconstructed. If your close process doesn’t touch the allowance every month, the estimate is an annual guess wearing a GAAP label.

Book Versus Tax: The Allowance You Can’t Deduct

The CECL allowance is a book number. Federally, it buys you nothing until an invoice actually goes bad.

IRC Section 166 governs the business bad debt deduction. Section 166(a)(1) allows a deduction for a debt that becomes wholly worthless within the taxable year, and Section 166(a)(2) allows one for a partially worthless debt, limited to the amount charged off within the taxable year. Worthlessness is a facts-and-circumstances determination with no bright-line test. The reserve method has been gone for four decades, since the Tax Reform Act of 1986, Pub. L. 99-514, Section 805(a), struck former Section 166(c) for taxable years beginning after December 31, 1986. The specific charge-off method governs.

Mechanically, the allowance is added back as a book-tax difference on Schedule M-1 or M-3 and creates a deductible temporary difference, which produces a deferred tax asset under ASC 740 subject to the usual valuation allowance assessment. Electing the ASU 2025-05 expedient changes the size of the book allowance, and therefore the size of that deferred tax asset. It changes nothing on the return.

One narrow exception is worth raising with your tax advisor rather than acting on from an article. IRC Section 448(d)(5) provides a nonaccrual-experience method for accrual-method service providers that charge no interest or late penalty on overdue invoices, and an amount not accrued under it can’t also be deducted under Section 166 when it later goes bad. States conforming to federal taxable income inherit the Section 166 treatment.

The Audit-Ready Standard

An audit-ready ASC 326 file is contemporaneous, not reconstructed. The memo predates the number, and the support predates the assertion. Here’s what gets requested on a first-year private company engagement:

• The written CECL policy memo
• Pool definitions and the rationale for the shared risk characteristics chosen
• The write-off and recovery history supporting the loss rates by bucket
• The current-conditions adjustment and its support
• The forecast adjustment and its support, or the documented ASU 2025-05 expedient election in its place
• The subsequent-collections evaluation date and the cash-application evidence, if the non-PBE policy is elected
• The allowance rollforward
• The credit quality indicator disclosure

ASC 326-20-50-7 calls for that rollforward by class of financing receivable. For most non-financial companies, trade receivables and contract assets form a single class, so it’s one schedule running from beginning balance to ending balance rather than a matrix by portfolio segment. The AICPA’s Center for Plain English Accounting publishes a CECL trade receivables disclosure checklist with illustrative language, which is the fastest way to pressure-test a footnote you’ve already drafted.

Disclosure is where a first-year adoption gets exposed. Elect the expedient and ASC 326-20-50-12A requires you to say so. Take the subsequent-collections policy on top of it as a non-PBE and ASC 326-20-50-12B requires the evaluation date in annual periods. Neither is hard. Both are easy to forget in the week the footnotes get assembled.

Indinero’s books are audit-ready by default, because GAAP discipline is baked into how the team operates, not added later. The same principle runs through audit preparation generally. A schedule prepared in the month it describes is evidence. The same schedule prepared in March is a reconstruction.

How Indinero Approaches Credit Loss Reserves

Indinero’s accounting team is CPA-led, and every monthly close gets a GAAP-discipline review before it ships. For credit loss reserves, that means the pooling, the loss-rate build, and the memo behind the number get produced inside the close, not reconstructed the week the auditor’s request list lands.

The reserve is one of the places where a bookkeeping vendor and a separate tax preparer both look away. The book allowance belongs to accounting. The M-1 add-back and the ASC 740 deferred tax asset belong to tax. With indinero, your bookkeeping team and tax team are the same team, so the book-tax difference gets booked once, reconciled once, and carried to the return by people who already know how the estimate was built.

This year puts a specific decision in front of every calendar-year private company. Whether to elect the ASU 2025-05 practical expedient. Whether a non-PBE also elects the subsequent-collections policy. What evaluation date you commit to and can actually hit every period. What the footnote says. That’s a memo, and it belongs in the file before the December 31, 2026 close, not during it.

We’ve maintained continuous operations since 2009, we serve 500+ regular customers, and we bring 100+ years combined team experience to work like this. Pricing starts at $750/mo, with month-to-month engagements available.

You’re not just looking for someone to post the entry. You’re looking for a finance partner who can defend the number to your auditor and carry the difference through to the return. If you’re still carrying a legacy doubtful-accounts reserve, accounting services is the right place to start. Reach out for a free consultation, or get in touch with a question about your own AR book. We’d love to learn about your business.

Frequently asked questions

These questions come up on every first-year ASC 326 engagement. They cluster around the same few edges: thin loss history, contract assets, whether the ASU 2025-05 expedient is worth electing early, and what any of it does to the tax return. The short answers are below. The paragraph references above are there if you need to take one of them into a conversation with your auditor.

Do we need a reserve when every customer has always paid on time?

Yes, CECL measures expected credit losses over the asset’s life, so a flawless collection history lowers the rate rather than removing the allowance. ASC 326-20 replaced the incurred-loss model, so there’s no trigger event to wait for, and zero is a conclusion that needs documented support rather than a default. Indinero’s CPA team builds that support inside the monthly close, so the memo exists before the number does.

How do we estimate credit losses with only two years of billing history?

Pool receivables by shared risk characteristics under ASC 326-20-30-2, build a loss rate from the write-off history you have, then adjust for current conditions. Thin history is a small sample, not an exemption, so the current-conditions adjustment carries more weight. Supplement with customer credit data, default rates for your concentrated verticals, and observable payment behavior inside each pool. Indinero’s CPA team writes that basis into the close file, so the support predates the number an auditor tests.

Does the allowance apply to unbilled contract assets as well?

Yes, ASC 326-20 covers ASC 606 contract assets, including unbilled usage revenue and milestone-gated implementation balances, not only billed trade receivables. The ledger label doesn’t control the classification. ASC 606-10-45-3 and 45-4 do, so an account tagged unbilled receivable is often a contract asset in scope. The ASU 2025-05 expedient covers current contract assets too, and indinero’s team runs that scope test on the subledger during close.

Should we early adopt the ASU 2025-05 practical expedient?

ASU 2025-05 early adoption is permitted, and the expedient removes only the reasonable-and-supportable forecast step, not the current-conditions adjustment. Issued July 30, 2025, it’s effective for annual periods beginning after December 15, 2025 plus interim periods within them, applied prospectively. A non-PBE adopting after the effective date needs no preferability assessment, and indinero’s CPA team documents the election and its footnote disclosure before the close. Assuming the expedient erases the current-conditions adjustment is the most likely first-year error.

Is the book reserve deductible on our federal tax return?

No, the CECL allowance isn’t deductible on a federal return, since IRC Section 166’s specific charge-off method governs the business bad debt deduction. The deduction lands when a specific receivable becomes wholly or partially worthless, so the reserve is added back on Schedule M-1 or M-3. That temporary difference produces a deferred tax asset under ASC 740. With indinero, the same team books the allowance and carries the difference to the return.