AU-C Section 505 is the AICPA auditing standard that governs an auditor’s use of external confirmations, the written responses obtained directly from third parties who can independently verify information in a nonpublic client’s financial records. The standard tells the auditor when to consider confirmations, how to design and control the requests, which type of request fits the assessed risk, and what to do when a response is unreliable, contains exceptions, or never arrives. It applies to audits of non-SEC-reporting entities; public company audits follow PCAOB AS 2310 instead.
When Confirmations Fit the Audit
The decision to confirm hinges on the assessed risk of material misstatement at both the financial statement and assertion levels. Higher risk pushes the auditor toward confirmation as a way of driving audit risk down to an acceptable level. The nature of the account matters too. Confirmations produce their strongest evidence for assertions about existence and about rights and obligations.
Accounts receivable is the classic candidate. A direct response from a customer stating what they owe is powerful evidence that the receivable exists and belongs to the entity. Notes payable, loan covenants, inventory held at third-party warehouses, securities held by custodians, and the terms of complex sales contracts are all common targets as well. In each case, an independent party corroborates something the client’s own books cannot prove as persuasively on their own.
Several factors affect whether a confirmation will actually yield useful evidence. An unsophisticated respondent, a respondent without access to the underlying records, or one with a close relationship to the client produces a weaker result. The request should focus on specific information the third party can verify from its own records: an outstanding balance, a due date, an interest rate, a payment term.
Positive and Negative Confirmations
AU-C 505 recognizes two types of requests, each suited to different risk levels.
Positive Confirmations
A positive confirmation asks the recipient to respond in every case, whether they agree or disagree. Silence itself becomes a signal, telling the auditor that alternative procedures are needed. Positive confirmations are the default when the risk of material misstatement is high or when individual balances are large.
A blank confirmation is a variation. The request goes out without stating the balance, and the recipient fills in the figure from their own records. Because the third party supplies the number independently rather than checking one already printed on the form, blank confirmations can be more reliable. Response rates tend to be lower because the recipient has to do more work.
Negative Confirmations
A negative confirmation asks the recipient to respond only if they disagree. No response is treated as agreement, which is the weakness of the format: silence could just as easily mean the party never received the request, never opened it, or set it aside. Because the evidential value is so much lower, AU-C 505 prohibits the auditor from using negative confirmations as the sole substantive procedure unless all four of the following are present at the same time:
- The auditor has assessed the risk of material misstatement as low and has obtained sufficient evidence that relevant controls are operating effectively.
- The population consists of a large number of small, similar balances or transactions.
- Based on prior experience and understanding of the entity, the auditor expects very few exceptions.
- The auditor has no reason to believe recipients will disregard the request.
If negative confirmations are used and the auditor then encounters a significant number of exceptions or non-responses, the initial risk assessment has to be revisited. That reassessment may force a switch to positive confirmations or additional substantive testing.
Designing the Request and Keeping Control
A confirmation is only as good as its design and the auditor’s control over the process.
Form Design
The request should be clearly identified as an audit confirmation and must direct the recipient to send the response straight to the auditor, not to the client. Including the auditor’s specific return address is essential. The form should ask only for information the recipient can verify from its own records, in plain language. For a debt balance, that means the principal, interest rate, and origination date. For a receivable, the outstanding balance and payment terms.
Auditor Control
The auditor must maintain control over three stages: selecting the items to confirm, sending the requests, and receiving the responses. Client staff can help with mechanical tasks such as printing requests on company letterhead, but the auditor verifies every detail before anything goes out and personally seals, addresses, and mails the requests or transmits them through a secure electronic channel. Control at each stage prevents management from tampering with the population selected, intercepting outgoing requests, or altering incoming responses.
Electronic confirmation platforms are widely used and can strengthen control when implemented properly, because the auditor accesses the platform directly and the client never handles the responses. Even then, the auditor must evaluate whether the platform’s security controls are adequate and whether the respondent’s identity has been properly authenticated. An electronic response carries the same reliability requirements as a paper one.
Management Authorization
The auditor must obtain management’s authorization before sending any request, since the process involves contacting third parties about the client’s business relationships. A refusal to authorize is not an inconvenience to work around informally; it triggers a separate set of mandatory steps described below.
Handling Responses, Exceptions, and Non-Responses
Once requests go out, the work shifts to what comes back.
Evaluating Reliability
Every response gets a reliability check. For paper confirmations, the auditor examines letterhead, postmark, and sender information for consistency. Electronic responses call for source verification, which may mean phoning the sender or using another independent method to confirm the response actually came from the intended party. If anything raises doubt about a response’s reliability, the auditor must obtain further audit evidence to resolve it. When a response is determined to be unreliable, the auditor evaluates the implications for the overall risk assessment, including the risk of fraud, and adjusts the nature, timing, and extent of other procedures accordingly.
Disclaimers and Restrictive Language
Third-party respondents increasingly attach legal disclaimers to their responses. A bank might confirm a balance while disclaiming responsibility for its accuracy. When a response carries restrictive language, the auditor must determine whether the disclaimer is so broad that it effectively negates the evidential value of the response. If it does, the confirmation cannot be relied on without additional corroborating procedures.
Non-Responses to Positive Confirmations
When a positive confirmation is not returned, the auditor performs alternative procedures aimed at the same assertions the confirmation was designed to address. For accounts receivable, the most common approach is to examine subsequent cash receipts, tracing the balance to payments received from the customer after the confirmation date. Reviewing shipping documents such as bills of lading or delivery receipts provides evidence that the underlying sale occurred. Similar logic applies to other account types, using subsequent disbursements, vendor statements, or contract documents as the case demands.
If alternative procedures still fail to produce sufficient evidence, the auditor must consider the implications for the audit opinion. A concentration of non-responses in a particular account or customer group can itself be a risk indicator worth further investigation.
Exceptions
An exception arises when the confirming party reports a different amount or different terms than the request stated. Most exceptions turn out to be timing differences: a payment mailed but not yet posted, or goods in transit at the confirmation date. The auditor investigates each exception by communicating with both the client and the third party.
When an exception reveals an actual misstatement rather than a timing issue, the auditor projects that error to the entire population and assesses whether total projected misstatement exceeds the tolerable threshold. Unreconciled exceptions are treated as potential misstatements until resolved. A high rate of exceptions where the client’s records are consistently wrong in the same direction is a strong fraud indicator and should trigger a reassessment of risk.
When Management Refuses to Allow a Confirmation
A management request to block confirmation of a specific account or balance is treated as a potential scope limitation, and AU-C 505 treats it seriously because the restriction comes from the client itself.
The auditor first asks why management objects and evaluates whether the reasons hold up. There is sometimes a legitimate business rationale, such as a delicate negotiation with a customer that a confirmation request might disrupt. Even when the explanation is reasonable, the auditor must evaluate the implications for the risk of material misstatement, including fraud risk, and must still perform alternative procedures to obtain sufficient evidence.
If alternative procedures produce adequate evidence, the audit can proceed without modifying the opinion. If the auditor concludes management’s refusal is unreasonable, or if alternative procedures cannot fill the gap, the matter is escalated to those charged with governance. When the resulting scope limitation is material and pervasive, the auditor must issue either a qualified opinion or a disclaimer of opinion. A management refusal that cannot be adequately worked around is not a footnote in the workpapers; it goes directly to the opinion.
Link to Fraud Risk
Confirmations do not sit apart from the fraud work. AU-C 240 specifically recognizes that auditors may design confirmation requests as a response to assessed risks of material misstatement due to fraud. Several confirmation outcomes should sharpen skepticism. A management refusal without a compelling reason is one. Patterns of exceptions that consistently favor the client’s position are another. Non-responses concentrated in accounts where management has the most incentive to misstate deserve extra scrutiny. None of these alone proves fraud, but each demands a reassessment of fraud risk and a potential expansion of procedures.
Public Company Audits Follow a Different Standard
AU-C 505 does not govern audits of SEC-reporting entities. Those audits follow PCAOB AS 2310, which took effect for audits of fiscal years ending on or after June 15, 2025. The most significant difference is that AS 2310 creates a near-presumption that the auditor will confirm cash held by third parties and accounts receivable arising from the sale of goods or services, or otherwise obtain reliable evidence by directly accessing information from a knowledgeable external source. AU-C 505 takes a purely risk-based approach with no such presumption for any specific account. If the engagement is a public company audit, AS 2310 is the operative standard, not AU-C 505.