Substantive analytical procedures help an auditor assess accounts receivable (AR) by comparing recorded balances or ratios with a well-supported expectation. They can identify relationships that need investigation, but a ratio or trend alone does not establish that a receivable is collectible, that revenue is properly recorded, or that fraud did not occur. The applicable audit framework, the assertion being tested, and the reliability of the underlying data determine how much weight the analysis can carry.
What substantive analytical procedures do
Analytical procedures evaluate financial information by studying plausible relationships among financial and nonfinancial data. The PCAOB's AS 2305, Substantive Analytical Procedures, describes a range from simple comparisons to more complex models and notes that expectations may draw on prior periods, budgets, industry information, and operational measures. In an AR review, the objective is not to find a preferred number; it is to determine whether the recorded balance and related revenue are consistent with information that should move together.
For example, an expectation for sales may be developed from units shipped and approved prices, while an expectation for receivables may consider credit terms, seasonality, customer mix, aging, and subsequent cash collections. A material difference is a question to resolve, not an automatic finding of error.
Use the audit framework that applies to the engagement
Audit requirements are not interchangeable. The AICPA's current Statements on Auditing Standards resource states that its SASs apply to audit reports for nonissuers and provides the current AU-C sections. PCAOB standards address audits performed under the PCAOB framework. Accordingly, a team auditing a nonissuer should use the standards applicable to that engagement rather than treating a PCAOB example as a substitute for its governing requirements.
This article uses the PCAOB standard as an accessible explanation of the underlying analytical approach. It is educational material, not an audit program or a conclusion about a specific company. Engagement leaders should determine the applicable framework, reporting basis, materiality, risk assessment, and required procedures.
Build a receivables analysis that can be tested
1. Define the question before selecting a metric
Start with the financial-statement assertion or management question. A review of AR may be aimed at valuation and collectibility, the period-end cutoff of sales, the existence of billed balances, or the completeness of recorded revenue. The objective determines which relationship is relevant and which evidence will be needed if the relationship is unusual.
2. Develop an expectation independently
Use information that has a credible connection to the balance. Possible inputs include prior-period trends adjusted for known changes, approved budgets, customer contracts, credit terms, shipping or service records, production data, and prices. An expectation built only from the general ledger adds little independent perspective. The PCAOB explains that the usefulness of a substantive analytical procedure depends in part on the plausibility and predictability of the relationship, the reliability of the data, and the precision of the expectation.
3. Check the information supporting the expectation
Before relying on a calculation, identify the source of every important input and whether it reconciles to the ledger. AS 2305 says an auditor should test controls over the financial information used in the procedure or perform other procedures that support the completeness and accuracy of that information. A clean-looking dashboard does not cure incomplete shipping data, an unapproved price file, or an unreconciled AR subledger.
4. Set an investigation threshold and follow the difference
Document the expected result, the recorded result, the difference, the threshold for follow-up, and the explanation obtained. Then corroborate the explanation with evidence. Depending on the risk, follow-up may include examining invoices and contracts, checking proof of shipment or service, reviewing credit memos, inspecting subsequent collections, or testing selected customer balances. The appropriate mix is a matter of professional judgment and the engagement's risk assessment.
Useful AR relationships to examine
| Comparison | Example relationship | Question raised by an unexpected result |
|---|---|---|
| Revenue and closing AR | Compare the change in net credit sales with the change in AR. | Have collection patterns, credit terms, billing timing, or customer mix changed? |
| Aging composition | Compare current and overdue age buckets with comparable prior periods. | Is the balance becoming older, concentrated, disputed, or otherwise less collectible? |
| Collection period | Compare days sales outstanding (DSO) with prior like-for-like periods. | Is the change explained by seasonality, sales terms, a billing delay, or actual collection performance? |
| Credit memos and returns | Compare post-period-end credits or returns with historical patterns. | Do the items require more work on cutoff, recorded revenue, or valuation? |
| Operational drivers | Compare recorded sales with units shipped, service volume, occupancy, or other relevant drivers. | Does the recorded result align with support outside the general ledger? |
DSO is commonly calculated as average accounts receivable divided by net credit sales, multiplied by the number of days in the period. It is most useful when the numerator, denominator, period length, and sales basis are consistent from one comparison to the next. A rising DSO can prompt inquiry, but it does not by itself prove a collections failure or a misstatement. For a related operating metric, see AR Turnover Ratio: Benchmarking Liquidity & Efficiency.
Connect analytics to collectibility and the allowance
When U.S. GAAP applies, the allowance for credit losses presents the net amount expected to be collected from a financial asset. The FASB's Credit Losses project page explains that expected-credit-loss measurement uses relevant information about past events, historical experience, current conditions, and reasonable and supportable forecasts. AR aging, customer disputes, payment behavior, and changes in commercial conditions may therefore be useful inputs, but they should be evaluated with the entity's facts and accounting policies rather than through a mechanical percentage.
For current accounts receivable and current contract assets arising from Topic 606 transactions, FASB's 2025 update provides an optional practical expedient for all entities and an accounting-policy election for entities other than public business entities in the circumstances described by FASB. See FASB's announcement of Accounting Standards Update 2025-05. Whether an election is available or appropriate depends on the entity, the assets, the reporting framework, and the current authoritative text; it should be assessed by the people responsible for the financial statements and audit.
Know the limits of trend and ratio analysis
Analytics are a way to direct attention, not a replacement for appropriate evidence. In the PCAOB framework, substantive analytical procedures alone are unlikely to provide sufficient evidence for significant risks of material misstatement, and the standard says they are not well suited on their own to detecting fraud. A relationship can look normal even when the underlying records are wrong, particularly if management can affect both sides of the comparison.
That limitation is why an AR analysis should connect to tests of details when warranted. A sharp period-end sales increase, a deterioration in aging, or a large post-close credit memo may have an ordinary explanation. The work is to obtain evidence for that explanation, consider alternatives, and document the conclusion rather than label the pattern as misconduct.
Separate management monitoring from audit evidence
Controllers and finance teams can monitor AR aging, collection period, disputes, credit limits, cash application, and credit memos throughout the year. Regular monitoring can make exception investigation more timely and improve the quality of data available at year-end. An auditor, however, must independently determine whether the information is reliable and whether the procedures provide sufficient appropriate evidence for the audit objective.
Operational choices about aging receivables are also separate from an audit conclusion. For context on a potential disposition decision, read Aged Receivable Liquidation: The DSO Reduction Protocol for CFOs; the decision should be evaluated on its own commercial, accounting, and contractual facts.
A practical documentation checklist
- State the AR assertion or business question and the period covered.
- Identify the recorded amount, the independently developed expectation, and every key data source.
- Reconcile important reports to the relevant ledger or explain the difference.
- Record the comparison, threshold, identified exception, and rationale for the threshold.
- Retain corroborating evidence for the explanation and document any additional testing.
- Conclude on the specific objective without overstating what the analytics can prove.
Frequently asked questions
Why is accounts receivable management important?
Accounts receivable management connects sales to cash collection and helps a company spot overdue balances, disputes, credit-risk changes, or process breakdowns early. It is a management discipline; an audit analytical procedure is a separate evidence-gathering activity performed under the applicable audit standards.
What is the accounts receivable collection period?
The accounts receivable collection period estimates the average time to collect credit sales. A common calculation is average accounts receivable divided by net credit sales, multiplied by the number of days in the period; compare like-for-like periods and investigate material shifts with aging, terms, and cash-collection data.