Allowance for Doubtful Accounts: Guide for AR and Finance Teams

Allowance for doubtful accounts is the estimate of invoices a company does not expect to collect. AccountingTools describes it as management's estimate of receivables customers will not pay; Wall Street Prep explains that it is a contra-asset tied to accounts receivable. In plain English, it helps finance show receivables at a more realistic collectible amount instead of assuming every open invoice will become cash.

For B2B SaaS finance teams, the allowance is also an operating signal. It reflects receivables health, customer risk, collection follow-up, billing disputes, payment behavior, and how cleanly the contract-to-cash process is running.

Use this as an operating guide, not accounting advice. Your final treatment should follow your accounting policy, materiality thresholds, applicable standards, and auditor guidance.

Quick answer

Allowance for doubtful accounts is a reserve for estimated uncollectible accounts receivable. If a company has $1,000,000 in gross accounts receivable and estimates that $40,000 may not be collected, it records a $40,000 allowance. Net accounts receivable becomes $960,000. This follows the same basic idea AccountingTools gives: subtract the allowance from accounts receivable to get the amount the business expects to collect.

The basic formula is:

Net accounts receivable = gross accounts receivable - allowance for doubtful accounts

Finance uses the allowance to recognize collection risk before a specific customer officially defaults. QuickBooks lists several common estimation methods, including percentage of sales, accounts receivable aging, customer risk classification, Pareto-style review, and specific identification. The right mix depends on the company's policy, data quality, invoice volume, and customer risk profile.

What is allowance for doubtful accounts?

Allowance for doubtful accounts is an estimate of customer invoices that may not be collected. It is paired with accounts receivable and reduces the receivable balance to the amount finance reasonably expects to collect. That is why it is often discussed alongside net accounts receivable, AR aging, bad debt expense, and write-off controls.

A simple example:

The allowance does not mean the company has given up on every invoice in the reserve. It means finance knows that some portion of open AR is at risk and should not be treated as certain cash.

That distinction matters. A customer may still pay after collections follow-up, a dispute may be resolved, or a credit memo may clear part of the balance. The allowance is an estimate that should change as receivables age, payment behavior changes, and new information arrives.

Is allowance for doubtful accounts an asset?

Allowance for doubtful accounts is a contra-asset account. It is linked to accounts receivable, but it has the opposite effect of a normal asset balance because it reduces reported receivables. Wall Street Prep frames the same classification clearly: an increase in the allowance reduces the accounts receivable account.

In plain terms:

• Accounts receivable shows what customers owe.
• Allowance for doubtful accounts shows the portion finance estimates may not be collected.
• Net accounts receivable shows the expected collectible amount.

This is why the allowance commonly carries a credit balance while accounts receivable commonly carries a debit balance. The credit balance offsets the receivable asset. If that treatment differs in a specific system or reporting policy, follow the accounting team's chart of accounts and close process.

Why the allowance matters for AR and finance leaders

A weak allowance process creates two problems at once: financial statements can look cleaner than the receivables really are, and operators can miss the early warning signs that cash collection is getting worse.

For AR and finance leaders, the allowance helps answer practical questions:

• Which invoices are aging into real write-off risk?
• Are late payments concentrated in a few customers, products, regions, or contract types?
• Are disputes, short-pays, credits, or billing errors making the AR balance look collectible when it is not?
• Is the cash forecast assuming invoices will be paid when collections evidence says otherwise?
• Are finance and customer-facing teams reviewing the same receivables risk picture?

The allowance is most useful when it is tied to operating evidence instead of a flat percentage copied from last quarter. If the billing system misses usage charges, payment terms are unclear, disputes sit unresolved, or cash application is messy, the allowance review becomes guesswork.

That is where the topic connects to revenue leakage. Missed billing and weak collections affect cash timing and can hide which receivables are actually at risk.

Allowance vs bad debt expense vs write-off

These terms are related, but they are not interchangeable.

The important control point: if bad debt expense was already estimated through the allowance, a later write-off normally reduces accounts receivable and the allowance. It should not create a second bad debt expense for the same invoice. Cornell's accounting guidance makes this point directly: when an allowance exists, a write-off is charged against the allowance and bad debt expense should not be recorded again.

How to estimate allowance for doubtful accounts

There is no one universal allowance formula. The right method depends on your accounting policy, customer base, historical data, invoice volume, contract complexity, and how much customer-specific evidence you have.

Most companies use one or more of these methods. AccountingTools describes percentage of sales, percentage of receivables, aging, and statistical modeling approaches; QuickBooks also includes risk classification and specific identification as practical methods.

1. Percentage of sales method

The percentage of sales method estimates bad debt as a percentage of credit sales for the period. It is simple, and QuickBooks includes it as one of the standard allowance calculation approaches.

Formula:

Estimated bad debt expense = credit sales x expected uncollectible percentage

Example: if a company has $2,000,000 in credit sales and historically 1.5% becomes uncollectible, estimated bad debt expense is $30,000.

This method can work when customer mix and collection behavior are stable. It is weaker when the business changes quickly, enterprise contract sizes vary widely, or one large customer can distort the risk profile.

2. Percentage of accounts receivable method

The percentage of accounts receivable method estimates the allowance as a percentage of the ending AR balance. AccountingTools frames this type of approach around estimating the uncollectible portion of the receivables balance.

Formula:

Target allowance = ending accounts receivable x expected uncollectible percentage

This method focuses on the balance sheet. It can be useful for a high-level reserve, but it treats all open receivables as if they carry similar risk unless you add more detail.

For B2B SaaS, that is often too blunt. A current invoice from a customer with autopay and no disputes is not the same risk as a 120-day invoice from a customer with unresolved implementation issues.

3. Accounts receivable aging method

The AR aging method groups receivables by how long invoices have been outstanding, then applies a different estimated loss rate to each bucket. VersaPay's guide and QuickBooks both describe aging as a way to estimate default or uncollectible risk from aged receivable buckets.

In this example, the target allowance is $57,500.

Aging is often the most useful starting point for AR teams because it reflects a practical collection pattern: older invoices tend to need more scrutiny. But the aging report should not be the only signal. A 90-day invoice with an approved payment plan may be safer than a 45-day invoice tied to a serious dispute.

4. Customer risk classification

Risk classification groups customers or invoices by expected collectability. QuickBooks includes risk classification as an allowance method, and it is especially useful when collectability depends on customer-specific facts rather than invoice age alone.

Risk signals may include:

• payment history,
• contract value,
• customer segment,
• credit profile,
• dispute history,
• invoice size,
• payment method,
• procurement portal behavior,
• customer health,
• and whether the account has open credits, short-pays, or unresolved billing exceptions.

This method is useful when a few large accounts can change the allowance materially. It is also useful for B2B SaaS teams with enterprise customers, custom contracts, usage overages, annual commitments, or negotiated payment terms.

5. Specific identification

Specific identification reserves for known at-risk invoices or customers. QuickBooks also lists specific identification as a method, which is the right concept when finance has clear evidence that a particular customer or invoice is higher risk than the portfolio average.

For example, finance may reserve against a customer that has entered bankruptcy, disputed a large invoice, stopped responding to collections, or announced a major restructuring.

This method should not replace portfolio-level analysis, because finance still needs to estimate risk across the rest of AR. But it prevents known problems from being hidden inside a broad average.

6. Model-based or historical trend methods

More mature teams may use statistical models or structured historical trend analysis. AccountingTools notes statistical modeling as an allowance-estimation approach; in practice, the model should be explainable enough for finance to defend during close, audit, and board reporting.

Useful inputs can include payment behavior, invoice age, customer cohort, product line, contract type, macroeconomic conditions, and collections activity. A model only helps when it uses clean, current, explainable data.

Example allowance calculation

Suppose a B2B SaaS company reviews its open accounts receivable at month-end:

The company would target an allowance of $94,500. If the existing allowance balance is $70,000, it may need to record an additional $24,500, depending on accounting policy and prior entries.

Adjustment needed = target allowance - existing allowance balance

In this case:

$94,500 - $70,000 = $24,500 adjustment

The example is intentionally simple. Real allowance work should account for recoveries, credits, write-offs, customer-specific evidence, and any policy requirements your accounting team follows.

Journal entries for allowance for doubtful accounts

Journal entries depend on your accounting policy, but the common allowance-method flow looks like this. Wall Street Prep's journal-entry walkthrough and HighRadius's explainer both frame the allowance setup as a debit to bad debt expense and a credit to allowance for doubtful accounts.

Initial allowance estimate

When finance records estimated bad debt:

This records the expected loss and increases the allowance.

Write off a specific invoice

When a specific invoice is deemed uncollectible and the allowance already exists:

This removes the receivable and uses the allowance. Cornell's guidance supports the same control logic: when an allowance exists, the write-off is charged against the allowance instead of recording bad debt expense again.

Recover a previously written-off invoice

If a customer later pays an invoice that was written off, finance may need to reverse the write-off and record the cash receipt. Treatment varies by accounting policy, but the operating lesson is consistent: recoveries need a clean audit trail so AR, cash, and the general ledger agree.

Operational signals that make the allowance more reliable

The allowance gets better when finance can see why invoices are unpaid and how old they are. Paystand's allowance guide also connects allowance estimates to AR and payments data, which is why the operating signal matters for SaaS finance teams.

Useful operating signals include:

• Invoice age. How many days the invoice has been open and whether it crossed the company's review threshold.
• Dispute reason. Whether the customer is disputing price, usage, service delivery, tax, procurement setup, or contract terms.
• Collections activity. Whether the customer has been contacted, promised payment, requested a credit, or gone silent.
• Contract terms. Whether the invoice matches signed payment terms, usage rules, implementation fees, renewals, discounts, and credits.
• Cash application status. Whether a payment has arrived but is unapplied, partially applied, or sitting in a suspense process.
• Customer health. Whether the customer is active, renewing, expanding, downsizing, or at churn risk.
• Payment behavior. Whether the customer often pays late but reliably, pays only after portal submission, or repeatedly short-pays invoices.
• Credit memo and write-off history. Whether the customer or segment regularly generates adjustments.

This is why allowance reviews should connect to billing reconciliation. If the contract, invoice, payment, and accounting record do not match, finance cannot confidently tell whether an invoice is collectible, disputed, incorrectly billed, already paid, or ready for write-off review.

How B2B SaaS teams reduce doubtful-account risk

The allowance measures risk. It does not reduce risk by itself.

To reduce doubtful accounts, finance needs a tighter contract-to-cash control loop:

1. Bill from the contract, not memory. Pull payment terms, usage rules, one-time fees, renewals, discounts, and portal requirements from the signed agreement.
2. Catch invoice errors early. Incorrect prices, missed credits, missing purchase orders, and stale usage data create disputes that age into collection risk.
3. Prioritize collections by risk. A $100,000 invoice with no response and a past dispute deserves different treatment than a $2,000 invoice three days late.
4. Separate willingness-to-pay from process problems. Some invoices are unpaid because the customer cannot or will not pay. Others are unpaid because a portal rejected the invoice, a credit memo is pending, or cash was not applied.
5. Reconcile before the close. Tie invoices, payments, credits, disputes, and write-offs back to the general ledger before allowance review starts.
6. Review the allowance on a defined cadence. The cadence should follow accounting policy, materiality, and close requirements; the review should explain what changed in aging mix, customer risk, disputes, recoveries, write-offs, and new collection evidence.

LedgerUp's AI revenue teammate, Ari, fits this workflow by keeping contracts, invoices, payments, collections activity, and reconciliation evidence in sync. Ari reads contract terms, flags billing exceptions, chases past-due customers, routes approvals, and gives finance a clearer view of which receivables are collectible and which need review.

That does not replace accounting judgment. It gives the team cleaner evidence for that judgment.

Monthly allowance review checklist

Use this checklist before recording or adjusting the allowance:

• Export the current AR aging report.
• Reconcile unapplied cash and partial payments.
• Review invoices over the company's risk threshold.
• Identify disputed invoices and classify dispute reasons.
• Check whether late invoices match contract terms and purchase-order requirements.
• Review customers with repeated short-pays, credits, or failed payments.
• Add specific reserves for known high-risk accounts when policy requires it.
• Compare current loss assumptions with recent write-offs and recoveries.
• Document why the allowance changed from the prior period.
• Confirm the final entry with accounting policy and approval requirements.

A good review makes the allowance explainable instead of mechanically bigger or smaller.

FAQ

Is allowance for doubtful accounts a debit or credit?

Allowance for doubtful accounts commonly has a credit balance because it offsets accounts receivable, which commonly has a debit balance. Wall Street Prep's journal-entry example shows bad debt expense as the debit and allowance for doubtful accounts as the credit when the allowance is increased.

Is allowance for doubtful accounts the same as bad debt expense?

No. Allowance for doubtful accounts is the balance sheet reserve for estimated uncollectible receivables. Bad debt expense is the income statement expense recorded for expected credit losses. VersaPay makes the same distinction: allowance for doubtful accounts is a balance sheet contra-asset, while bad debt expense is an income statement account.

Does allowance for doubtful accounts reduce revenue?

In the common allowance-method flow, allowance for doubtful accounts reduces net accounts receivable and is paired with bad debt expense; it does not directly change the original revenue line. Wall Street Prep explains that credit sales are still recorded as revenue and accounts receivable, while the allowance estimates the uncollectible portion of AR. Revenue recognition, credit memos, refunds, concessions, and invoice corrections are separate questions that should follow the company's accounting policy.

How often should finance update the allowance?

Set the required cadence in the company's accounting policy and close calendar. From an operating perspective, many SaaS finance teams review it during monthly or quarterly close because allowance changes depend on fresh aging, dispute, payment, write-off, and recovery evidence. Review it more often when AR is growing quickly, large invoices age past due, disputes increase, or customer payment behavior changes materially.

What is the best method for estimating doubtful accounts?

There is no universal best method. For many B2B SaaS teams, AR aging plus customer-specific risk review is a stronger starting point than a flat percentage alone because it combines invoice age with customer-specific facts. That recommendation is an operating perspective, not a rule: QuickBooks lists aging, risk classification, and specific identification as separate methods, and the right mix should follow accounting policy and data quality.

When should an invoice be written off?

An invoice should be written off when the company determines it is no longer collectible under its policy. Cornell's guidance says an uncollectible account should be written off against the allowance when an allowance exists, without recording bad debt expense again. The operating decision should consider age, collections activity, dispute status, customer communication, legal or bankruptcy information, and approval requirements.