What a confirmation is
US rule. An external confirmation is audit evidence obtained as a direct written response to the auditor from a third party, the confirming party, on paper or by electronic or other medium (AU-C 505.06). It is used because evidence from external parties, obtained directly by the auditor and in documentary form, is generally more reliable than evidence generated inside the entity (AU-C 505.02).
This page explains how the confirmation process works in an audit file under the AICPA's AU-C 505 and what a contributor can safely do. It is general information. The firm's audit plan decides which items are confirmed. The standard's current edition governs, and note that amendments from SAS No. 150 on external confirmations take effect for periods ending on or after December 15, 2028, as the AICPA's AU-C download states.
When confirmations are required
AU-C 330 requires the auditor to consider whether external confirmation procedures should be performed as substantive procedures (AU-C 330.19). For accounts receivable, the auditor should use confirmations unless the overall balance is immaterial, confirmation would be ineffective, or the assessed risk of material misstatement at the assertion level is low and other planned substantive procedures address the risk (AU-C 330.20). Confirmations can also cover terms of agreements and the absence of certain conditions, such as side agreements (AU-C 505.03).
Which accounts, which parties and what to ask are decisions in the audit plan. Do not add or drop items from the sample on your own.
What the auditor controls
When using confirmations, the auditor maintains control over the requests (AU-C 505.07):
- determining the information to be confirmed or requested;
- selecting the appropriate confirming party;
- designing the requests, including checking they go to the right party and provide for responses directly to the auditor;
- sending the requests, including follow-ups.
The explanatory material adds that determining requests are properly addressed includes checking the accuracy of addresses, including testing some or all of the addresses on requests before they go out, and for email, testing the validity of email addresses supplied by management (AU-C 505.A7).
The practical result for you: the client does not send the requests, collect the replies, or handle the envelopes. If someone at the client offers to "just send them out for you", the answer is no, and you tell the manager. The firm's method for sending and receiving, whether paper, a secure electronic channel or the confirming party's own system, is set by the firm.
A tracking schedule
Whoever handles the logistics keeps a schedule. A usable one has one row per request:
| Column | Purpose |
|---|---|
| Reference | Confirmation number, linked to the workpaper |
| Confirming party and address | As selected by the auditor, with how the address was checked |
| Item and amount | What is being confirmed, and the ledger figure |
| Type | Positive or negative; blank or filled-in |
| Sent date, method | When and how it went |
| Follow-up dates | Second request, third request |
| Reply date, method | When it came back, and that it came directly |
| Result | Agreed, exception, no reply |
| Alternative procedures | If no reply, what was done |
| Prepared, reviewed | Who and when |
Keep the schedule current. A confirmation process that cannot show what was sent and when is hard to defend.
Positive and negative requests
A positive request asks the confirming party to respond directly in all cases, either giving the information or saying whether they agree. A negative request asks for a response only if they disagree (AU-C 505.06).
Negative confirmations provide less persuasive evidence. The standard says they should not be the sole substantive procedure for an assessed risk at the assertion level unless all four conditions hold: low assessed risk with sufficient evidence about controls, a large number of small homogeneous balances, a very low expected exception rate, and no known circumstances that would cause recipients to disregard the requests (AU-C 505.15). Which type to use is decided in the plan.
A response to a positive request can still be unreliable if the party answers without checking. The explanatory material notes that "blank" requests that ask the party to fill in the amount reduce that risk, though they may reduce the response rate (AU-C 505.A6).
Replies
Check each reply for:
- Direct receipt. The standard notes factors that may cast doubt on reliability include that the response was received indirectly or appeared not to come from the intended party (AU-C 505.A12). If doubts arise, the auditor obtains further evidence to resolve them (AU-C 505.10).
- Authenticity. The explanatory material lists risks that the information may not come from an authentic source, the respondent may not be knowledgeable, and the integrity of the information may have been compromised (AU-C 505.A13).
- Agreement. Compare the confirmed information to the ledger.
If you receive a reply by any route that was not the agreed one, do not use it. Report it to the manager and keep the original.
Nonresponses
For each nonresponse, the auditor performs alternative audit procedures to obtain relevant and reliable evidence (AU-C 505.12). Sending a follow-up request is part of the control the auditor maintains (AU-C 505.07d), and the standard notes that an additional request may be sent when no reply has been received within a reasonable time, after reverifying the address (AU-C 505.A8). The standard's examples for receivables include examining specific subsequent cash receipts, matching them to the items paid, and examining shipping documentation (AU-C 505.A24). The plan sets the procedures. Record what you did and what it showed.
If a written response to a positive request is necessary to obtain sufficient appropriate evidence, alternative procedures will not do. The auditor determines the implications for the audit and opinion (AU-C 505.13). That is a decision for the signer.
Exceptions
An exception is a response indicating a difference between the information requested or in the entity's records and the information the confirming party provided (AU-C 505.06). The auditor investigates exceptions to determine whether they indicate misstatements (AU-C 505.14).
Illustrative example, invented figures: a customer's reply shows a balance of 8,200. The ledger shows 12,200. The difference is 4,000. The customer's note says an invoice was paid on 30 December. The bank statement shows the credit on 3 January, after year-end. The entity recorded the receipt on 3 January. At 31 December the entity had not received the payment, so the ledger balance was right at that date and the difference is a reconciling item, not a misstatement, on this evidence. The note records the difference, the evidence, the reasoning and the conclusion, and the reviewer decides whether it clears. The clearing a finding page shows how to write it.
When management refuses
If management refuses to allow confirmation procedures, the auditor asks why and seeks evidence on whether the reasons are valid and reasonable, evaluates the effect on risk assessment, including fraud risk, and performs alternative procedures (AU-C 505.08). If the refusal is unreasonable or alternative procedures cannot provide reliable evidence, the auditor communicates with those charged with governance and considers the effect on the opinion (AU-C 505.09). This is entirely for the firm. If a client tells you they do not want a confirmation sent, report it to the manager the same day and do not negotiate.
Documentation
The confirmation file should let an experienced auditor with no previous connection to the audit understand what was requested, from whom, what came back, and how each exception and nonresponse was resolved (AU-C 230.08). Record who performed the work and when, and who reviewed it and when (AU-C 230.09).
What a contributor must not do
- Send or receive requests through the client.
- Change an address because the client says it is out of date, without telling the manager.
- Accept a reply sent by the client rather than by the confirming party.
- Treat a missing reply as agreement.
- Mark an exception cleared on the client's explanation alone.
FAQ
Can I phone the confirming party?
Only if the firm's procedure allows it, and record the call. An oral response is not an external confirmation because it is not a direct written response to the auditor, though the auditor may take it into account in deciding on alternative procedures (AU-C 505.A27).
Are bank confirmations different?
The control principles in AU-C 505.07 apply to them as to any other request. Use the route the firm sets.
What if the party replies by email from a personal address?
Treat it as a reliability question (AU-C 505.A12 and .A13). Tell the manager and do not rely on it until the firm decides.
Who decides what to confirm?
The audit plan. Your role is logistics, tracking, comparison and documentation.
Sources
- AICPA, AU-C Section 505, External Confirmations (AU-C sections, currently effective): https://www.aicpa-cima.com/resources/download/aicpa-statements-on-auditing-standards-currently-effective
- AICPA, AU-C Section 330, Performing Audit Procedures in Response to Assessed Risks (same download): https://www.aicpa-cima.com/resources/download/aicpa-statements-on-auditing-standards-currently-effective
- AICPA, AU-C Section 230, Audit Documentation (same download): https://www.aicpa-cima.com/resources/download/aicpa-statements-on-auditing-standards-currently-effective