Calculating Accounts Receivable: The Complete Guide

A handful of calculations cover almost everything useful about receivables. Each answers a different question, and knowing which to use matters more than memorising the formulas.

Closing receivables balance

Opening receivables, plus credit sales in the period, less cash collected, less write-offs and credit notes.

This is the reconciliation that proves your receivables balance is explainable. If the calculated figure does not agree with your ledger, something has been posted outside the normal flow, and finding it is worth the time.

Average receivables

Opening balance plus closing balance, divided by two. Used as the denominator in most ratio calculations, because a single point in time can be badly unrepresentative in a seasonal or lumpy business.

Receivables turnover

Credit sales divided by average receivables. It tells you how many times in the period the receivables balance was collected and replaced. Higher generally indicates faster collection.

Use credit sales, not total sales. Including cash sales inflates the ratio and makes collection look better than it is.

Days sales outstanding

Average receivables divided by credit sales, multiplied by days in the period. Or, equivalently, days in the period divided by receivables turnover. This is the most directly interpretable of the ratios because the output is in days, which you can compare against your stated terms.

Average collection period

Effectively the same measure as DSO and frequently used interchangeably. If you see both quoted with different values, check which sales figure and which receivables balance each is using.

Allowance for doubtful accounts

An estimate of receivables not expected to be collected, carried as a reduction against the gross balance. Common approaches estimate it as a percentage of receivables, often varied by aging bucket, or as a percentage of credit sales.

Whether an allowance is required or appropriate for your business depends on your circumstances and reporting requirements, so it is worth confirming rather than adopting by default. What is universally true is that carrying obviously uncollectable balances at full value overstates your assets.

Net realisable value

Gross receivables less the allowance. This is what the balance sheet should show: what you realistically expect to collect, not what you invoiced.

Using them together

Ratios describe the average and hide the distribution. A respectable DSO can conceal the fact that most customers pay promptly while a few are severely overdue. Always read the ratios alongside the aging report, which shows where the balance actually sits.

Start with clean source data

Every receivables calculation depends on the same foundation: customer invoices, credit notes, receipts, write-offs, and opening balances must be complete and posted to the right customer. Before calculating a ratio, reconcile the accounts receivable control account in the general ledger to the detailed customer aging. If the two totals disagree, the ratio may be mathematically correct and operationally useless.

Set a consistent reporting date and decide whether you are measuring a month, quarter, or year. Use the same period for sales and day counts. Separate credit sales from cash sales where possible. Remove non-trade items that do not arise from ordinary customer invoices. Document unusual adjustments so a later reviewer can reproduce the number.

Worked example: calculating the closing balance

Assume a service business starts the month with illustrative accounts receivable of $84,000. It issues $126,000 of credit invoices, collects $109,000, grants $3,000 of credit notes, and writes off $1,000 that is no longer expected to be collected. The calculated closing balance is $84,000 plus $126,000, less $109,000, less $3,000, less $1,000, which equals $97,000.

Compare that $97,000 with both the general ledger and the customer aging. If the ledger shows $100,000, investigate the $3,000 difference before moving on. It may be a receipt posted to a clearing account, a journal entry made directly to receivables, or a credit note dated in another period. The reconciliation identifies completeness problems that an aging report alone cannot reveal.

Worked example: average receivables and turnover

Using the same illustrative balances, average receivables are the opening $84,000 plus closing $97,000, divided by two, or $90,500. If credit sales for a 30-day month were $126,000, monthly receivables turnover is $126,000 divided by $90,500, or about 1.39 times. The figure means the average receivable balance was collected and replaced roughly 1.39 times during the month.

Turnover is most useful as a trend calculated consistently. A change may reflect collection performance, but it may also reflect seasonality, a large invoice near period end, a change in customer mix, or different payment terms. Compare the ratio with the aging and customer-level detail before concluding that the collection process improved or declined.

Worked example: days sales outstanding

Days sales outstanding uses the same inputs in a form that is easier to discuss. Divide average receivables of $90,500 by credit sales of $126,000, then multiply by 30 days. The illustrative DSO is about 21.5 days. If the normal terms are due in 15 days, that result suggests the average collection timing extends beyond the stated terms.

DSO is not the age of every invoice and it is not a promise about when the closing balance will arrive. It compresses a moving portfolio into one average. A single large invoice can move it sharply. Use a rolling trend, the percentage past due, and an aging by customer to show the distribution behind the average.

Calculating the percentage past due

Divide the overdue receivable balance by total receivables. If $31,000 of the $97,000 closing balance is past its due date, the illustrative percentage past due is about 32 percent. Split the overdue amount into aging buckets to distinguish fresh delays from older exposure. The action required for an invoice one day late is different from the action required for an invoice disputed for months.

Track both amount and customer count. A small number of large overdue accounts creates concentration risk, while many small overdue accounts may indicate a weak invoicing or reminder process. Compare the result with the prior period using the same aging rules. Changing the bucket definitions makes the trend appear to move even when customer behavior has not changed.

Customer concentration calculations

Customer concentration is the balance owed by one customer or a selected group of customers divided by total receivables. If the largest customer owes $29,000 of a $97,000 balance, that customer represents about 30 percent of total receivables. The calculation does not say the balance is bad. It shows how much cash timing depends on one payer.

Review concentration alongside credit quality, dispute status, and expected payment date. A concentrated balance with a reliable customer may be manageable, while the same percentage with a disputed customer may threaten the cash plan. Also compare concentration in receivables with concentration in revenue, because a growing customer can create both opportunity and working-capital pressure.

Estimating expected collections

A cash forecast should start with individual open invoices where the balance is material. Assign a realistic collection date based on due date, customer behavior, confirmed promises, and disputes. Smaller invoices can be grouped by aging bucket and assigned a collection pattern. Keep the assumptions separate from the accounting balance so the forecast can change without rewriting the ledger.

Reconcile forecasted collections to gross receivables, then identify amounts excluded because they are disputed, subject to credit, or considered unlikely to collect. Update the forecast with actual receipts each week. A forecast becomes more useful when the team records why an expected payment moved instead of merely pushing every missed amount into the next week.

Building an aging-based allowance

An aging approach applies a different estimated loss rate to each age bucket. The rates should be supported by the business’s own collection history and adjusted for current conditions. Multiply each bucket by its selected rate, then sum the results. The calculation is an estimate of expected noncollection, not a list of invoices that should automatically be written off.

Keep the accounting estimate separate from the collections workflow. A customer can remain in active collection even when an allowance is recorded. Conversely, an old balance should not remain at full value merely because no one has formally approved a write-off. The appropriate accounting and tax treatment depends on the reporting framework and facts, so confirm it for the business.

A monthly receivables dashboard

• Closing gross receivables and the reconciliation to the ledger
• Cash collected during the period
• Days sales outstanding on a consistent basis
• Total and percentage past due
• Balance by aging bucket
• Largest customer balances and concentration
• Disputed invoices and promised payment dates
• Credits and unapplied cash waiting to be resolved
• Write-offs and changes in any allowance

The dashboard should connect to action. List who owns each material overdue balance and the next scheduled contact. Show invoices blocked by an internal issue, such as missing support or incorrect billing, separately from customers that simply have not paid. That distinction prevents collections from blaming customers for problems the business must correct.

Reconcile the dashboard from report to source

For each reported metric, record the report name, date range, filters, sales definition, receivable balance, day count, and any exclusions. Reperform the calculation outside the accounting system for one period. This documentation prevents a software setting from silently changing the trend and makes the number understandable to someone who did not build it.

Tie closing receivables to the aging and general ledger. Tie credit sales to the selected revenue accounts and remove cash sales only when the distinction is supported. Tie collections to customer receipts rather than total bank deposits. Record credit notes, write-offs, and allowance changes separately so collection performance is not confused with accounting adjustments.

Interpret changes with a bridge

When receivables rise, separate the movement into sales volume, collection timing, large invoices, disputes, credits, and write-offs. When DSO changes, show whether the numerator, denominator, or both caused it. A bridge explains why the metric moved and whether the change is expected to reverse.

Compare the closing aging with the next period’s actual receipts. This back-test shows which forecast assumptions were realistic and which customers or aging buckets behave differently. Refine expected collection dates from evidence rather than moving every missed receipt forward by one week.

Minimum monthly review questions

• Does the aging equal the general ledger?
• Which customers created most of the change?
• How much is overdue, disputed, or unapplied?
• Which promised payments were missed?
• Are credit sales and days defined consistently?
• Does the cash forecast agree with invoice-level expectations?
• Are any balances unlikely to be collected at recorded value?

Keep definitions stable over time

Create a short metric dictionary for receivables, credit sales, past due, dispute, write-off, allowance, DSO, and collection date. State whether credit balances and unapplied cash are included. Use the same definitions in the accounting report, management dashboard, and cash forecast.

When a definition must change, calculate the prior period on the new basis when practical and disclose the change. Otherwise, a trend line may reflect reporting design rather than customer payment behavior. Retain the calculation file or report settings with the monthly close so another person can reproduce the result.

Use the metrics to choose actions. Contact a customer, correct a billing defect, revise a credit limit, update a forecast, or review collectibility. A number that produces no decision is usually more detailed than the process needs.

Treat every formula as a controlled report. Name the owner, reporting date, source reports, exclusions, and review evidence. Reconcile the inputs before discussing the result, and retain enough detail to explain a change by customer and invoice. This discipline matters more than adding another ratio.