ASA 505 sets out how auditors must obtain and treat external confirmations — written responses from third parties (for example, banks or customers) — as audit evidence. It requires auditors to control request design and delivery, select appropriate confirming parties, manage non‑responses and unreliable replies, and distinguish between positive and negative confirmations.
The Standard affects auditors (who carry the procedural and evidence burden) and audited entities (whose management may restrict confirmations). It matters because external confirmations are often more persuasive evidence and can change an auditor’s further procedures or opinion.
Auditing Standard ASA 505 External Confirmations (as amended to 3 March 2020) sets out how an auditor is to design and perform external confirmation procedures to obtain audit evidence. Mechanically, it applies to audits of financial reports under the Corporations Act 2001 and to other audits of financial reports or complete sets of financial statements, and, as appropriate, to other historical financial information (Aus 0.1-Aus 0.2). The standard is operative for financial reporting periods commencing on or after 1 January 2010 (Aus 0.3) and this compiled version incorporates AUASB amendments up to 3 March 2020 (Compilation Details).
The standard’s stated objective is narrow and procedural: "The objective of the auditor, when using external confirmation procedures, is to design and perform such procedures to obtain relevant and reliable audit evidence" (Objective, para.1). It defines core terms used throughout the standard: external confirmation; positive and negative confirmation requests; non-response; and exception (Definitions, para.1(i)-(v)). It requires that, when using external confirmations, the auditor shall maintain control over confirmation requests by (a) determining what information to confirm, (b) selecting the confirming party, (c) designing the request so responses are addressed to and returnable directly to the auditor, and (d) sending the requests and follow-ups as applicable (Requirements, External Confirmation Procedures, para.1(a)-(d); Ref: Para. A1-A7).
The standard prescribes a response path where management refuses requests: the auditor must enquire into management’s reasons, seek evidence as to their validity, evaluate the implications for risk assessment and other procedures, and perform alternative audit procedures (Requirements, Management’s Refusal, para.1(a)-(c); Ref: Para. A8-A10). If the refusal is unreasonable or alternative procedures do not produce relevant and reliable evidence, the auditor must communicate with those charged with governance under ASA 260 and consider the audit and opinion implications under ASA 705 (Requirements, para.2).
Current sections
Direct links to the current provisions in ASA 505 - External Confirmations - October 2009.
29
Obtaining a Copy of this Auditing Standa
Obtaining a Copy of this Auditing Standard
Obtaining a Copy of this Auditing Standard
The most recently compiled versions of Auditing Standards, original Standards and amending Standards (see Compilation Details) are available on the AUASB website: www.auasb.gov.au
Contact Details
Contact Details
Contact Details
Auditing and Assurance Standards BoardPodium Level 14, 530 Collins StreetMelbourne Victoria 3000AUSTRALIA
Phone: (03) 8080 7400E-mail: enquiries@auasb.gov.auPostal Address:PO Box 204Collins Street WestMelbourne Victoria 8007AUSTRALIA
Requests and enquiries concerning reproduction and rights for commercial purposes within Australia should be addressed to the Technical Director, Auditing and Assurance Standards Board, PO Box 204, Collins Street West, Melbourne, Victoria 8007 or sent to enquiries@auasb.gov.au. Otherwise, no part of this Auditing Standard may be reproduced, stored or transmitted in any form or by any means without the prior written permission of the AUASB except as permitted by law.
This Auditing Standard reproduces substantial parts of the corresponding International Standard on Auditing issued by the International Auditing and Assurance Standards Board (IAASB) and published by the International Federation of Accountants (IFAC), in the manner described in the statement on Conformity with International Standards on Auditing. The AUASB acknowledges that IFAC is the owner of copyright in the International Standard on Auditing incorporated in this Auditing Standard throughout the world.
All existing rights in this material are reserved outside Australia. Reproduction outside Australia in unaltered form (retaining this notice) is permitted for personal and non-commercial use only.
Further information and requests for authorisation to reproduce this Auditing Standard for commercial purposes outside Australia should be addressed to the Technical Director, Auditing and Assurance Standards Board, PO Box 204, Collins Street West, Melbourne, Victoria 8007 or sent to enquiries@auasb.gov.au. Any decision to approve a request may also require the agreement of IFAC.
ISSN 1833-4393
CONTENTS
CONTENTS
CONTENTS
COMPILATION DETAILS
AUTHORITY STATEMENT
CONFORMITY WITH INTERNATIONAL STANDARDS ON AUDITING
Evaluating the Evidence Obtained...........................................A24-A25
COMPILATION DETAILS
COMPILATION DETAILS
Obtaining a Copy of this Auditing Standard
The most recently compiled versions of Auditing Standards, original Standards and amending Standards (see Compilation Details) are available on the AUASB website: www.auasb.gov.au
Contact Details
Auditing and Assurance Standards BoardPodium Level 14, 530 Collins StreetMelbourne Victoria 3000AUSTRALIA
Phone: (03) 8080 7400E-mail: enquiries@auasb.gov.auPostal Address:PO Box 204Collins Street WestMelbourne Victoria 8007AUSTRALIA
Requests and enquiries concerning reproduction and rights for commercial purposes within Australia should be addressed to the Technical Director, Auditing and Assurance Standards Board, PO Box 204, Collins Street West, Melbourne, Victoria 8007 or sent to enquiries@auasb.gov.au. Otherwise, no part of this Auditing Standard may be reproduced, stored or transmitted in any form or by any means without the prior written permission of the AUASB except as permitted by law.
This Auditing Standard reproduces substantial parts of the corresponding International Standard on Auditing issued by the International Auditing and Assurance Standards Board (IAASB) and published by the International Federation of Accountants (IFAC), in the manner described in the statement on Conformity with International Standards on Auditing. The AUASB acknowledges that IFAC is the owner of copyright in the International Standard on Auditing incorporated in this Auditing Standard throughout the world.
All existing rights in this material are reserved outside Australia. Reproduction outside Australia in unaltered form (retaining this notice) is permitted for personal and non-commercial use only.
Further information and requests for authorisation to reproduce this Auditing Standard for commercial purposes outside Australia should be addressed to the Technical Director, Auditing and Assurance Standards Board, PO Box 204, Collins Street West, Melbourne, Victoria 8007 or sent to enquiries@auasb.gov.au. Any decision to approve a request may also require the agreement of IFAC.
ISSN 1833-4393
CONTENTS
COMPILATION DETAILS
AUTHORITY STATEMENT
CONFORMITY WITH INTERNATIONAL STANDARDS ON AUDITING
Evaluating the Evidence Obtained...........................................A24-A25
COMPILATION DETAILS
Auditing Standard ASA 505 External Confirmations (as Amended)
This compilation takes into account amendments made up to and including 3 March 2020 and was prepared on 10 November 2021 by the Auditing and Assurance Standards Board (AUASB).
This compilation is not a separate Auditing Standard made by the AUASB. Instead, it is a representation of ASA 505 (October 2009) as amended by other Auditing Standards which are listed in the Table below.
Table of Standards
Standard
Date made
Operative Date
ASA 505 [A]
27 October 2009
Financial reporting periods commencing on or after 1 January 2010.
ASA 2018-1 [B]
5 December 2018
Financial reporting periods commencing on or after 15 December 2019, with early adoption permitted[*].
ASA 2020-1 [C]
3 March 2020
Financial reporting periods commencing on or after 15 December 2021[#]
[A] Federal Register of Legislation – registration number F2009L04088, 12 November 2009
[B] Federal Register of Legislation – registration number F2019L00016, 3 January 2019
[C] Federal Register of Legislation – registration number F2020L00252, 13 March 2020
Table of Amendments
Paragraph affected
How affected
By … [paragraph]
2Footnote 4
Amended
ASA 2018-1 [50]
2Footnote 5
Amended
ASA 2018-1 [51]
3Footnote 11
Amended
ASA 2018-1 [52]
A9Footnote 14
Amended
ASA 2020-1 [130]
A17Footnote 18
Amended
ASA 2020-1 [131]
A19Footnote 20
Amended
ASA 2020-1 [132]
AUTHORITY STATEMENT
Auditing Standard ASA 505 External Confirmations (as amended to 3 March 2020) is set out in paragraphs Aus 0.1 to A25.
This Auditing Standard is to be read in conjunction with ASA 101 Preamble to AUASB Standards, which sets out how AUASB Standards are to be understood, interpreted and applied. This Auditing Standard is to be read also in conjunction with ASA 200 Overall Objectives of the Independent Auditor and the Conduct of an Audit in Accordance with Australian Auditing Standards.
Conformity with International Standards on Auditing
This Auditing Standard conforms with International Standard on Auditing ISA 505 External Confirmations, issued by the International Auditing and Assurance Standards Board (IAASB), an independent standard‑setting board of the International Federation of Accountants (IFAC).
Paragraphs that have been added to this Auditing Standard (and do not appear in the text of the equivalent ISA) are identified with the prefix “Aus”.
Compliance with this Auditing Standard enables compliance with ISA 505.
Auditing Standard ASA 505 External Confi
Auditing Standard ASA 505 External Confirmations (as Amended)
Auditing Standard ASA 505 External Confirmations (as Amended)
This compilation takes into account amendments made up to and including 3 March 2020 and was prepared on 10 November 2021 by the Auditing and Assurance Standards Board (AUASB).
This compilation is not a separate Auditing Standard made by the AUASB. Instead, it is a representation of ASA 505 (October 2009) as amended by other Auditing Standards which are listed in the Table below.
Table of Standards
Table of Standards
Table of Standards
Standard
Date made
Operative Date
ASA 505 [A]
27 October 2009
Financial reporting periods commencing on or after 1 January 2010.
ASA 2018-1 [B]
5 December 2018
Financial reporting periods commencing on or after 15 December 2019, with early adoption permitted[*].
ASA 2020-1 [C]
3 March 2020
Financial reporting periods commencing on or after 15 December 2021[#]
[A] Federal Register of Legislation – registration number F2009L04088, 12 November 2009
[B] Federal Register of Legislation – registration number F2019L00016, 3 January 2019
[C] Federal Register of Legislation – registration number F2020L00252, 13 March 2020
Table of Amendments
Table of Amendments
Table of Amendments
Paragraph affected
How affected
By … [paragraph]
2Footnote 4
Amended
ASA 2018-1 [50]
2Footnote 5
Amended
ASA 2018-1 [51]
3Footnote 11
Amended
ASA 2018-1 [52]
A9Footnote 14
Amended
ASA 2020-1 [130]
A17Footnote 18
Amended
ASA 2020-1 [131]
A19Footnote 20
Amended
ASA 2020-1 [132]
AUTHORITY STATEMENT
Auditing Standard ASA 505 External Confirmations (as amended to 3 March 2020) is set out in paragraphs Aus 0.1 to A25.
This Auditing Standard is to be read in conjunction with ASA 101 Preamble to AUASB Standards, which sets out how AUASB Standards are to be understood, interpreted and applied. This Auditing Standard is to be read also in conjunction with ASA 200 Overall Objectives of the Independent Auditor and the Conduct of an Audit in Accordance with Australian Auditing Standards.
Conformity with International Standards on Auditing
This Auditing Standard conforms with International Standard on Auditing ISA 505 External Confirmations, issued by the International Auditing and Assurance Standards Board (IAASB), an independent standard‑setting board of the International Federation of Accountants (IFAC).
Paragraphs that have been added to this Auditing Standard (and do not appear in the text of the equivalent ISA) are identified with the prefix “Aus”.
Compliance with this Auditing Standard enables compliance with ISA 505.
AUTHORITY STATEMENT
AUTHORITY STATEMENT
AUTHORITY STATEMENT
Auditing Standard ASA 505 External Confirmations (as amended to 3 March 2020) is set out in paragraphs Aus 0.1 to A25.
This Auditing Standard is to be read in conjunction with ASA 101 Preamble to AUASB Standards, which sets out how AUASB Standards are to be understood, interpreted and applied. This Auditing Standard is to be read also in conjunction with ASA 200 Overall Objectives of the Independent Auditor and the Conduct of an Audit in Accordance with Australian Auditing Standards.
Conformity with International Standards
Conformity with International Standards on Auditing
Conformity with International Standards on Auditing
This Auditing Standard conforms with International Standard on Auditing ISA 505 External Confirmations, issued by the International Auditing and Assurance Standards Board (IAASB), an independent standard‑setting board of the International Federation of Accountants (IFAC).
Paragraphs that have been added to this Auditing Standard (and do not appear in the text of the equivalent ISA) are identified with the prefix “Aus”.
Compliance with this Auditing Standard enables compliance with ISA 505.
Auditing Standard ASA 505
Auditing Standard ASA 505
Auditing Standard ASA 505
The Auditing and Assurance Standards Board (AUASB) made Auditing Standard ASA 505 External Confirmations pursuant to section 227B of the Australian Securities and Investments Commission Act 2001 and section 336 of the Corporations Act 2001, on 27 October 2009.
This compiled version of ASA 505 incorporates subsequent amendments contained in other Auditing Standards made by the AUASB up to and including 3 March 2020 (see Compilation Details).
Auditing Standard ASA 505
External Confirmations
Application
Aus 0.1 This Auditing Standard applies to:
(a) an audit of a financial report for a financial year, or an audit of a financial report for a half-year, in accordance with the Corporations Act 2001; and
(b) an audit of a financial report, or a complete set of financial statements, for any other purpose.
Aus 0.2 This Auditing Standard also applies, as appropriate, to an audit of other historical financial information.
Operative Date
Aus 0.3 This Auditing Standard is operative for financial reporting periods commencing on or after 1 January 2010. [Note: For operative dates of paragraphs changed or added by an Amending Standard, see Compilation Details.]
Introduction
Scope of this Auditing Standard
This Auditing Standard deals with the auditor’s use of external confirmation procedures to obtain audit evidence in accordance with the requirements of ASA 330[1] and ASA 500[2]. It does not address enquiries regarding litigation and claims, which are dealt with in ASA 502.[3]
External Confirmation Procedures to Obtain Audit Evidence
ASA 500 indicates that the reliability of audit evidence is influenced by its source and by its nature, and is dependent on the individual circumstances under which it is obtained.[4] That Auditing Standard also includes the following generalisations applicable to audit evidence:[5]
Audit evidence is more reliable when it is obtained from independent sources outside the entity.
Audit evidence obtained directly by the auditor is more reliable than audit evidence obtained indirectly or by inference.
Audit evidence is more reliable when it exists in documentary form, whether paper, electronic or other medium.
Accordingly, depending on the circumstances of the audit, audit evidence in the form of external confirmations received directly by the auditor from confirming parties may be more reliable than evidence generated internally by the entity. This Auditing Standard is intended to assist the auditor in designing and performing external confirmation procedures to obtain relevant and reliable audit evidence.
Other Auditing Standards recognise the importance of external confirmations as audit evidence, for example:
ASA 330 discusses the auditor’s responsibility to design and implement overall responses to address the assessed risks of material misstatement at the financial statement level, and to design and perform further audit procedures whose nature, timing and extent are based on, and are responsive to, the assessed risks of material misstatement at the assertion level.[6] In addition, ASA 330 requires that, irrespective of the assessed risks of material misstatement, the auditor designs and performs substantive procedures for each material class of transactions, account balance, and disclosure. The auditor is also required to consider whether external confirmation procedures are to be performed as substantive audit procedures.[7]
ASA 330 requires that the auditor obtain more persuasive audit evidence the higher the auditor’s assessment of risk.[8] To do this, the auditor may increase the quantity of the evidence or obtain evidence that is more relevant or reliable, or both. For example, the auditor may place more emphasis on obtaining evidence directly from third parties or obtaining corroborating evidence from a number of independent sources. ASA 330 also indicates that external confirmation procedures may assist the auditor in obtaining audit evidence with the high level of reliability that the auditor requires to respond to significant risks of material misstatement, whether due to fraud or error.[9]
ASA 240 indicates that the auditor may design confirmation requests to obtain additional corroborative information as a response to address the assessed risks of material misstatement due to fraud at the assertion level.[10]
ASA 500 indicates that corroborating information obtained from a source independent of the entity, such as external confirmations, may increase the assurance the auditor obtains from evidence existing within the accounting records or from representations made by management.[11]
Effective Date
[Deleted by the AUASB. Refer Aus 0.3]
Objective
The objective of the auditor, when using external confirmation procedures, is to design and perform such procedures to obtain relevant and reliable audit evidence.
Definitions
For purposes of the Australian Auditing Standards, the following terms have the meanings attributed below:
External confirmation means audit evidence obtained as a direct written response to the auditor from a third party (the confirming party), in paper form, or by electronic or other medium.
Positive confirmation request means a request that the confirming party respond directly to the auditor indicating whether the confirming party agrees or disagrees with the information in the request, or providing the requested information.
Negative confirmation request means a request that the confirming party respond directly to the auditor only if the confirming party disagrees with the information provided in the request.
Non-response means a failure of the confirming party to respond, or fully respond, to a positive confirmation request, or a confirmation request returned undelivered.
Exception means a response that indicates a difference between information requested to be confirmed, or contained in the entity’s records, and information provided by the confirming party.
Requirements
External Confirmation Procedures
When using external confirmation procedures, the auditor shall maintain control over external confirmation requests, including:
Determining the information to be confirmed or requested; (Ref: Para. A1)
Selecting the appropriate confirming party; (Ref: Para. A2)
Designing the confirmation requests, including determining that requests are properly addressed and contain return information for responses to be sent directly to the auditor; and (Ref: Para. A3-A6)
Sending the requests, including follow-up requests when applicable, to the confirming party. (Ref: Para. A7)
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
If management refuses to allow the auditor to send a confirmation request, the auditor shall:
Enquire as to management’s reasons for the refusal, and seek audit evidence as to their validity and reasonableness; (Ref: Para. A8)
Evaluate the implications of management’s refusal on the auditor’s assessment of the relevant risks of material misstatement, including the risk of fraud, and on the nature, timing and extent of other audit procedures; and (Ref: Para. A9)
Perform alternative audit procedures designed to obtain relevant and reliable audit evidence. (Ref: Para. A10)
If the auditor concludes that management’s refusal to allow the auditor to send a confirmation request is unreasonable, or the auditor is unable to obtain relevant and reliable audit evidence from alternative audit procedures, the auditor shall communicate with those charged with governance in accordance with ASA 260.[12] The auditor also shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705.[13]
Results of the External Confirmation Procedures
Reliability of Responses to Confirmation Requests
If the auditor identifies factors that give rise to doubts about the reliability of the response to a confirmation request, the auditor shall obtain further audit evidence to resolve those doubts.
(Ref: Para. A11-A16)
If the auditor determines that a response to a confirmation request is not reliable, the auditor shall evaluate the implications on the assessment of the relevant risks of material misstatement, including the risk of fraud, and on the related nature, timing and extent of other audit procedures. (Ref: Para. A17)
Non-Responses
In the case of each non-response, the auditor shall perform alternative audit procedures to obtain relevant and reliable audit evidence. (Ref: Para A18-A19)
When a Response to a Positive Confirmation Request Is Necessary to Obtain Sufficient Appropriate Audit Evidence
If the auditor has determined that a response to a positive confirmation request is necessary to obtain sufficient appropriate audit evidence, alternative audit procedures will not provide the audit evidence the auditor requires. If the auditor does not obtain such confirmation, the auditor shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705. (Ref: Para A20)
Exceptions
The auditor shall investigate exceptions to determine whether or not they are indicative of misstatements. (Ref: Para. A21-A22)
Negative Confirmations
Negative confirmations provide less persuasive audit evidence than positive confirmations. Accordingly, the auditor shall not use negative confirmation requests as the sole substantive audit procedure to address an assessed risk of material misstatement at the assertion level unless all of the following are present: (Ref: Para. A23)
The auditor has assessed the risk of material misstatement as low and has obtained sufficient appropriate audit evidence regarding the operating effectiveness of controls relevant to the assertion;
The population of items subject to negative confirmation procedures comprises a large number of small, homogeneous, account balances, transactions or conditions;
A very low exception rate is expected; and
The auditor is not aware of circumstances or conditions that would cause recipients of negative confirmation requests to disregard such requests.
Evaluating the Evidence Obtained
The auditor shall evaluate whether the results of the external confirmation procedures provide relevant and reliable audit evidence, or whether further audit evidence is necessary.
(Ref: Para A24-A25)
* * *
Application and Other Explanatory Material
External Confirmation Procedures
Determining the Information to Be Confirmed or Requested (Ref: Para. 7(a))
External confirmation procedures frequently are performed to confirm or request information regarding account balances and their elements. They may also be used to confirm terms of agreements, contracts, or transactions between an entity and other parties, or to confirm the absence of certain conditions, such as a “side agreement.”
Selecting the Appropriate Confirming Party (Ref: Para. 7(b))
Responses to confirmation requests provide more relevant and reliable audit evidence when confirmation requests are sent to a confirming party the auditor believes is knowledgeable about the information to be confirmed. For example, a financial institution official who is knowledgeable about the transactions or arrangements for which confirmation is requested may be the most appropriate person at the financial institution from whom to request confirmation.
Designing Confirmation Requests (Ref: Para. 7(c))
The design of a confirmation request may directly affect the confirmation response rate, and the reliability and the nature of the audit evidence obtained from responses.
Factors to consider when designing confirmation requests include:
The assertions being addressed.
Specific identified risks of material misstatement, including fraud risks.
The layout and presentation of the confirmation request.
Prior experience on the audit or similar engagements.
The method of communication (for example, in paper form, or by electronic or other medium).
Management’s authorisation or encouragement to the confirming parties to respond to the auditor. Confirming parties may only be willing to respond to a confirmation request containing management’s authorisation.
The ability of the intended confirming party to confirm or provide the requested information (for example, individual invoice amount versus total balance).
A positive external confirmation request asks the confirming party to reply to the auditor in all cases, either by indicating the confirming party’s agreement with the given information, or by asking the confirming party to provide information. A response to a positive confirmation request ordinarily is expected to provide reliable audit evidence. There is a risk, however, that a confirming party may reply to the confirmation request without verifying that the information is correct. The auditor may reduce this risk by using positive confirmation requests that do not state the amount (or other information) on the confirmation request, and ask the confirming party to fill in the amount or furnish other information. On the other hand, use of this type of “blank” confirmation request may result in lower response rates because additional effort is required of the confirming parties.
Determining that requests are properly addressed includes testing the validity of some or all of the addresses on confirmation requests before they are sent out.
Follow-Up on Confirmation Requests (Ref: Para. 7(d))
The auditor may send an additional confirmation request when a reply to a previous request has not been received within a reasonable time. For example, the auditor may, having re-verified the accuracy of the original address, send an additional or follow-up request.
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
Reasonableness of Management’s Refusal (Ref: Para. 8(a))
A refusal by management to allow the auditor to send a confirmation request is a limitation on the audit evidence the auditor may wish to obtain. The auditor is therefore required to enquire as to the reasons for the limitation. A common reason advanced is the existence of a legal dispute or ongoing negotiation with the intended confirming party, the resolution of which may be affected by an untimely confirmation request. The auditor is required to seek audit evidence as to the validity and reasonableness of the reasons because of the risk that management may be attempting to deny the auditor access to audit evidence that may reveal fraud or error.
Implications for the Assessment of Risks of Material Misstatement (Ref: Para. 8(b))
The auditor may conclude from the evaluation in paragraph 8(b) that it would be appropriate to revise the assessment of the risks of material misstatement at the assertion level and modify planned audit procedures in accordance with ASA 315.[14] For example, if management’s request to not confirm is unreasonable, this may indicate a fraud risk factor that requires evaluation in accordance with ASA 240.[15]
Alternative Audit Procedures (Ref: Para. 8(c))
The alternative audit procedures performed may be similar to those appropriate for a non-response as set out in paragraphs A18-A19 of this Auditing Standard. Such procedures also would take account of the results of the auditor’s evaluation in paragraph 8(b) of this Auditing Standard.
Results of the External Confirmation Procedures
Reliability of Responses to Confirmation Requests (Ref: Para. 10)
ASA 500 indicates that even when audit evidence is obtained from sources external to the entity, circumstances may exist that affect its reliability.[16] All responses carry some risk of interception, alteration or fraud. Such risk exists regardless of whether a response is obtained in paper form, or by electronic or other medium. Factors that may indicate doubts about the reliability of a response include that it:
Was received by the auditor indirectly; or
Appeared not to come from the originally intended confirming party.
Responses received electronically, for example by facsimile or electronic mail, involve risks as to reliability because proof of origin and authority of the respondent may be difficult to establish, and alterations may be difficult to detect. A process used by the auditor and the respondent that creates a secure environment for responses received electronically may mitigate these risks. If the auditor is satisfied that such a process is secure and properly controlled, the reliability of the related responses is enhanced. An electronic confirmation process might incorporate various techniques for validating the identity of a sender of information in electronic form, for example, through the use of encryption, electronic digital signatures, and procedures to verify web site authenticity.
If a confirming party uses a third party to coordinate and provide responses to confirmation requests, the auditor may perform procedures to address the risks that:
The response may not be from the proper source;
A respondent may not be authorised to respond; and
The integrity of the transmission may have been compromised.
The auditor is required by ASA 500 to determine whether to modify or add procedures to resolve doubts over the reliability of information to be used as audit evidence.[17] The auditor may choose to verify the source and contents of a response to a confirmation request by contacting the confirming party. For example, when a confirming party responds by electronic mail, the auditor may telephone the confirming party to determine whether the confirming party did, in fact, send the response. When a response has been returned to the auditor indirectly (for example, because the confirming party incorrectly addressed it to the entity rather than to the auditor), the auditor may request the confirming party to respond in writing directly to the auditor.
On its own, an oral response to a confirmation request does not meet the definition of an external confirmation because it is not a direct written response to the auditor. However, upon obtaining an oral response to a confirmation request, the auditor may, depending on the circumstances, request the confirming party to respond in writing directly to the auditor. If no such response is received, in accordance with paragraph 12, the auditor seeks other audit evidence to support the information in the oral response.
A response to a confirmation request may contain restrictive language regarding its use. Such restrictions do not necessarily invalidate the reliability of the response as audit evidence.
Unreliable Responses (Ref: Para. 11)
When the auditor concludes that a response is unreliable, the auditor may need to revise the assessment of the risks of material misstatement at the assertion level and modify planned audit procedures accordingly, in accordance with ASA 315.[18] For example, an unreliable response may indicate a fraud risk factor that requires evaluation in accordance with ASA 240.[19]
Non-Responses (Ref: Para. 12)
Examples of alternative audit procedures the auditor may perform include:
For accounts receivable balances – examining specific subsequent cash receipts, shipping documentation, and sales near the period-end.
For accounts payable balances – examining subsequent cash disbursements or correspondence from third parties, and other records, such as goods received notes.
The nature and extent of alternative audit procedures are affected by the account and assertion in question. A non-response to a confirmation request may indicate a previously unidentified risk of material misstatement. In such situations, the auditor may need to revise the assessed risk of material misstatement at the assertion level, and modify planned audit procedures, in accordance with ASA 315.[20] For example, fewer responses to confirmation requests than anticipated, or a greater number of responses than anticipated, may indicate a previously unidentified fraud risk factor that requires evaluation in accordance with ASA 240.[21]
When a Response to a Positive Confirmation Request Is Necessary to Obtain Sufficient Appropriate Audit Evidence (Ref. Para. 13)
In certain circumstances, the auditor may identify an assessed risk of material misstatement at the assertion level for which a response to a positive confirmation request is necessary to obtain sufficient appropriate audit evidence. Such circumstances may include where:
The information available to corroborate management’s assertion(s) is only available outside the entity.
Specific fraud risk factors, such as the risk of management override of controls, or the risk of collusion which can involve employee(s) and/or management, prevent the auditor from relying on evidence from the entity.
Exceptions (Ref: Para. 14)
Exceptions noted in responses to confirmation requests may indicate misstatements or potential misstatements in the financial statements. When a misstatement is identified, the auditor is required by ASA 240 to evaluate whether such misstatement is indicative of fraud.[22] Exceptions may provide a guide to the quality of responses from similar confirming parties or for similar accounts. Exceptions also may indicate a deficiency, or deficiencies, in the entity’s internal control over financial reporting.
Some exceptions do not represent misstatements. For example, the auditor may conclude that differences in responses to confirmation requests are due to timing, measurement, or clerical errors in the external confirmation procedures.
Negative Confirmations (Ref: Para. 15)
The failure to receive a response to a negative confirmation request does not explicitly indicate receipt by the intended confirming party of the confirmation request or verification of the accuracy of the information contained in the request. Accordingly, a failure of a confirming party to respond to a negative confirmation request provides significantly less persuasive audit evidence than does a response to a positive confirmation request. Confirming parties also may be more likely to respond indicating their disagreement with a confirmation request when the information in the request is not in their favour, and less likely to respond otherwise. For example, holders of bank deposit accounts may be more likely to respond if they believe that the balance in their account is understated in the confirmation request, but may be less likely to respond when they believe the balance is overstated. Therefore, sending negative confirmation requests to holders of bank deposit accounts may be a useful procedure in considering whether such balances may be understated, but is unlikely to be effective if the auditor is seeking evidence regarding overstatement.
Evaluating the Evidence Obtained (Ref: Para. 16)
When evaluating the results of individual external confirmation requests, the auditor may categorise such results as follows:
A response by the appropriate confirming party indicating agreement with the information provided in the confirmation request, or providing requested information without exception;
A response deemed unreliable;
A non-response; or
A response indicating an exception.
The auditor’s evaluation, when taken into account with other audit procedures the auditor may have performed, may assist the auditor in concluding whether sufficient appropriate audit evidence has been obtained or whether further audit evidence is necessary, as required by ASA 330.[23]
External Confirmations
External Confirmations
Auditing Standard ASA 505
The Auditing and Assurance Standards Board (AUASB) made Auditing Standard ASA 505 External Confirmations pursuant to section 227B of the Australian Securities and Investments Commission Act 2001 and section 336 of the Corporations Act 2001, on 27 October 2009.
This compiled version of ASA 505 incorporates subsequent amendments contained in other Auditing Standards made by the AUASB up to and including 3 March 2020 (see Compilation Details).
Auditing Standard ASA 505
External Confirmations
Application
Aus 0.1 This Auditing Standard applies to:
(a) an audit of a financial report for a financial year, or an audit of a financial report for a half-year, in accordance with the Corporations Act 2001; and
(b) an audit of a financial report, or a complete set of financial statements, for any other purpose.
Aus 0.2 This Auditing Standard also applies, as appropriate, to an audit of other historical financial information.
Operative Date
Aus 0.3 This Auditing Standard is operative for financial reporting periods commencing on or after 1 January 2010. [Note: For operative dates of paragraphs changed or added by an Amending Standard, see Compilation Details.]
Introduction
Scope of this Auditing Standard
This Auditing Standard deals with the auditor’s use of external confirmation procedures to obtain audit evidence in accordance with the requirements of ASA 330[1] and ASA 500[2]. It does not address enquiries regarding litigation and claims, which are dealt with in ASA 502.[3]
External Confirmation Procedures to Obtain Audit Evidence
ASA 500 indicates that the reliability of audit evidence is influenced by its source and by its nature, and is dependent on the individual circumstances under which it is obtained.[4] That Auditing Standard also includes the following generalisations applicable to audit evidence:[5]
Audit evidence is more reliable when it is obtained from independent sources outside the entity.
Audit evidence obtained directly by the auditor is more reliable than audit evidence obtained indirectly or by inference.
Audit evidence is more reliable when it exists in documentary form, whether paper, electronic or other medium.
Accordingly, depending on the circumstances of the audit, audit evidence in the form of external confirmations received directly by the auditor from confirming parties may be more reliable than evidence generated internally by the entity. This Auditing Standard is intended to assist the auditor in designing and performing external confirmation procedures to obtain relevant and reliable audit evidence.
Other Auditing Standards recognise the importance of external confirmations as audit evidence, for example:
ASA 330 discusses the auditor’s responsibility to design and implement overall responses to address the assessed risks of material misstatement at the financial statement level, and to design and perform further audit procedures whose nature, timing and extent are based on, and are responsive to, the assessed risks of material misstatement at the assertion level.[6] In addition, ASA 330 requires that, irrespective of the assessed risks of material misstatement, the auditor designs and performs substantive procedures for each material class of transactions, account balance, and disclosure. The auditor is also required to consider whether external confirmation procedures are to be performed as substantive audit procedures.[7]
ASA 330 requires that the auditor obtain more persuasive audit evidence the higher the auditor’s assessment of risk.[8] To do this, the auditor may increase the quantity of the evidence or obtain evidence that is more relevant or reliable, or both. For example, the auditor may place more emphasis on obtaining evidence directly from third parties or obtaining corroborating evidence from a number of independent sources. ASA 330 also indicates that external confirmation procedures may assist the auditor in obtaining audit evidence with the high level of reliability that the auditor requires to respond to significant risks of material misstatement, whether due to fraud or error.[9]
ASA 240 indicates that the auditor may design confirmation requests to obtain additional corroborative information as a response to address the assessed risks of material misstatement due to fraud at the assertion level.[10]
ASA 500 indicates that corroborating information obtained from a source independent of the entity, such as external confirmations, may increase the assurance the auditor obtains from evidence existing within the accounting records or from representations made by management.[11]
Effective Date
[Deleted by the AUASB. Refer Aus 0.3]
Objective
The objective of the auditor, when using external confirmation procedures, is to design and perform such procedures to obtain relevant and reliable audit evidence.
Definitions
For purposes of the Australian Auditing Standards, the following terms have the meanings attributed below:
External confirmation means audit evidence obtained as a direct written response to the auditor from a third party (the confirming party), in paper form, or by electronic or other medium.
Positive confirmation request means a request that the confirming party respond directly to the auditor indicating whether the confirming party agrees or disagrees with the information in the request, or providing the requested information.
Negative confirmation request means a request that the confirming party respond directly to the auditor only if the confirming party disagrees with the information provided in the request.
Non-response means a failure of the confirming party to respond, or fully respond, to a positive confirmation request, or a confirmation request returned undelivered.
Exception means a response that indicates a difference between information requested to be confirmed, or contained in the entity’s records, and information provided by the confirming party.
Requirements
External Confirmation Procedures
When using external confirmation procedures, the auditor shall maintain control over external confirmation requests, including:
Determining the information to be confirmed or requested; (Ref: Para. A1)
Selecting the appropriate confirming party; (Ref: Para. A2)
Designing the confirmation requests, including determining that requests are properly addressed and contain return information for responses to be sent directly to the auditor; and (Ref: Para. A3-A6)
Sending the requests, including follow-up requests when applicable, to the confirming party. (Ref: Para. A7)
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
If management refuses to allow the auditor to send a confirmation request, the auditor shall:
Enquire as to management’s reasons for the refusal, and seek audit evidence as to their validity and reasonableness; (Ref: Para. A8)
Evaluate the implications of management’s refusal on the auditor’s assessment of the relevant risks of material misstatement, including the risk of fraud, and on the nature, timing and extent of other audit procedures; and (Ref: Para. A9)
Perform alternative audit procedures designed to obtain relevant and reliable audit evidence. (Ref: Para. A10)
If the auditor concludes that management’s refusal to allow the auditor to send a confirmation request is unreasonable, or the auditor is unable to obtain relevant and reliable audit evidence from alternative audit procedures, the auditor shall communicate with those charged with governance in accordance with ASA 260.[12] The auditor also shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705.[13]
Results of the External Confirmation Procedures
Reliability of Responses to Confirmation Requests
If the auditor identifies factors that give rise to doubts about the reliability of the response to a confirmation request, the auditor shall obtain further audit evidence to resolve those doubts.
(Ref: Para. A11-A16)
If the auditor determines that a response to a confirmation request is not reliable, the auditor shall evaluate the implications on the assessment of the relevant risks of material misstatement, including the risk of fraud, and on the related nature, timing and extent of other audit procedures. (Ref: Para. A17)
Non-Responses
In the case of each non-response, the auditor shall perform alternative audit procedures to obtain relevant and reliable audit evidence. (Ref: Para A18-A19)
When a Response to a Positive Confirmation Request Is Necessary to Obtain Sufficient Appropriate Audit Evidence
If the auditor has determined that a response to a positive confirmation request is necessary to obtain sufficient appropriate audit evidence, alternative audit procedures will not provide the audit evidence the auditor requires. If the auditor does not obtain such confirmation, the auditor shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705. (Ref: Para A20)
Exceptions
The auditor shall investigate exceptions to determine whether or not they are indicative of misstatements. (Ref: Para. A21-A22)
Negative Confirmations
Negative confirmations provide less persuasive audit evidence than positive confirmations. Accordingly, the auditor shall not use negative confirmation requests as the sole substantive audit procedure to address an assessed risk of material misstatement at the assertion level unless all of the following are present: (Ref: Para. A23)
The auditor has assessed the risk of material misstatement as low and has obtained sufficient appropriate audit evidence regarding the operating effectiveness of controls relevant to the assertion;
The population of items subject to negative confirmation procedures comprises a large number of small, homogeneous, account balances, transactions or conditions;
A very low exception rate is expected; and
The auditor is not aware of circumstances or conditions that would cause recipients of negative confirmation requests to disregard such requests.
Evaluating the Evidence Obtained
The auditor shall evaluate whether the results of the external confirmation procedures provide relevant and reliable audit evidence, or whether further audit evidence is necessary.
(Ref: Para A24-A25)
* * *
Application and Other Explanatory Material
External Confirmation Procedures
Determining the Information to Be Confirmed or Requested (Ref: Para. 7(a))
External confirmation procedures frequently are performed to confirm or request information regarding account balances and their elements. They may also be used to confirm terms of agreements, contracts, or transactions between an entity and other parties, or to confirm the absence of certain conditions, such as a “side agreement.”
Selecting the Appropriate Confirming Party (Ref: Para. 7(b))
Responses to confirmation requests provide more relevant and reliable audit evidence when confirmation requests are sent to a confirming party the auditor believes is knowledgeable about the information to be confirmed. For example, a financial institution official who is knowledgeable about the transactions or arrangements for which confirmation is requested may be the most appropriate person at the financial institution from whom to request confirmation.
Designing Confirmation Requests (Ref: Para. 7(c))
The design of a confirmation request may directly affect the confirmation response rate, and the reliability and the nature of the audit evidence obtained from responses.
Factors to consider when designing confirmation requests include:
The assertions being addressed.
Specific identified risks of material misstatement, including fraud risks.
The layout and presentation of the confirmation request.
Prior experience on the audit or similar engagements.
The method of communication (for example, in paper form, or by electronic or other medium).
Management’s authorisation or encouragement to the confirming parties to respond to the auditor. Confirming parties may only be willing to respond to a confirmation request containing management’s authorisation.
The ability of the intended confirming party to confirm or provide the requested information (for example, individual invoice amount versus total balance).
A positive external confirmation request asks the confirming party to reply to the auditor in all cases, either by indicating the confirming party’s agreement with the given information, or by asking the confirming party to provide information. A response to a positive confirmation request ordinarily is expected to provide reliable audit evidence. There is a risk, however, that a confirming party may reply to the confirmation request without verifying that the information is correct. The auditor may reduce this risk by using positive confirmation requests that do not state the amount (or other information) on the confirmation request, and ask the confirming party to fill in the amount or furnish other information. On the other hand, use of this type of “blank” confirmation request may result in lower response rates because additional effort is required of the confirming parties.
Determining that requests are properly addressed includes testing the validity of some or all of the addresses on confirmation requests before they are sent out.
Follow-Up on Confirmation Requests (Ref: Para. 7(d))
The auditor may send an additional confirmation request when a reply to a previous request has not been received within a reasonable time. For example, the auditor may, having re-verified the accuracy of the original address, send an additional or follow-up request.
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
Reasonableness of Management’s Refusal (Ref: Para. 8(a))
A refusal by management to allow the auditor to send a confirmation request is a limitation on the audit evidence the auditor may wish to obtain. The auditor is therefore required to enquire as to the reasons for the limitation. A common reason advanced is the existence of a legal dispute or ongoing negotiation with the intended confirming party, the resolution of which may be affected by an untimely confirmation request. The auditor is required to seek audit evidence as to the validity and reasonableness of the reasons because of the risk that management may be attempting to deny the auditor access to audit evidence that may reveal fraud or error.
Implications for the Assessment of Risks of Material Misstatement (Ref: Para. 8(b))
The auditor may conclude from the evaluation in paragraph 8(b) that it would be appropriate to revise the assessment of the risks of material misstatement at the assertion level and modify planned audit procedures in accordance with ASA 315.[14] For example, if management’s request to not confirm is unreasonable, this may indicate a fraud risk factor that requires evaluation in accordance with ASA 240.[15]
Alternative Audit Procedures (Ref: Para. 8(c))
The alternative audit procedures performed may be similar to those appropriate for a non-response as set out in paragraphs A18-A19 of this Auditing Standard. Such procedures also would take account of the results of the auditor’s evaluation in paragraph 8(b) of this Auditing Standard.
Results of the External Confirmation Procedures
Reliability of Responses to Confirmation Requests (Ref: Para. 10)
ASA 500 indicates that even when audit evidence is obtained from sources external to the entity, circumstances may exist that affect its reliability.[16] All responses carry some risk of interception, alteration or fraud. Such risk exists regardless of whether a response is obtained in paper form, or by electronic or other medium. Factors that may indicate doubts about the reliability of a response include that it:
Was received by the auditor indirectly; or
Appeared not to come from the originally intended confirming party.
Responses received electronically, for example by facsimile or electronic mail, involve risks as to reliability because proof of origin and authority of the respondent may be difficult to establish, and alterations may be difficult to detect. A process used by the auditor and the respondent that creates a secure environment for responses received electronically may mitigate these risks. If the auditor is satisfied that such a process is secure and properly controlled, the reliability of the related responses is enhanced. An electronic confirmation process might incorporate various techniques for validating the identity of a sender of information in electronic form, for example, through the use of encryption, electronic digital signatures, and procedures to verify web site authenticity.
If a confirming party uses a third party to coordinate and provide responses to confirmation requests, the auditor may perform procedures to address the risks that:
The response may not be from the proper source;
A respondent may not be authorised to respond; and
The integrity of the transmission may have been compromised.
The auditor is required by ASA 500 to determine whether to modify or add procedures to resolve doubts over the reliability of information to be used as audit evidence.[17] The auditor may choose to verify the source and contents of a response to a confirmation request by contacting the confirming party. For example, when a confirming party responds by electronic mail, the auditor may telephone the confirming party to determine whether the confirming party did, in fact, send the response. When a response has been returned to the auditor indirectly (for example, because the confirming party incorrectly addressed it to the entity rather than to the auditor), the auditor may request the confirming party to respond in writing directly to the auditor.
On its own, an oral response to a confirmation request does not meet the definition of an external confirmation because it is not a direct written response to the auditor. However, upon obtaining an oral response to a confirmation request, the auditor may, depending on the circumstances, request the confirming party to respond in writing directly to the auditor. If no such response is received, in accordance with paragraph 12, the auditor seeks other audit evidence to support the information in the oral response.
A response to a confirmation request may contain restrictive language regarding its use. Such restrictions do not necessarily invalidate the reliability of the response as audit evidence.
Unreliable Responses (Ref: Para. 11)
When the auditor concludes that a response is unreliable, the auditor may need to revise the assessment of the risks of material misstatement at the assertion level and modify planned audit procedures accordingly, in accordance with ASA 315.[18] For example, an unreliable response may indicate a fraud risk factor that requires evaluation in accordance with ASA 240.[19]
Non-Responses (Ref: Para. 12)
Examples of alternative audit procedures the auditor may perform include:
For accounts receivable balances – examining specific subsequent cash receipts, shipping documentation, and sales near the period-end.
For accounts payable balances – examining subsequent cash disbursements or correspondence from third parties, and other records, such as goods received notes.
The nature and extent of alternative audit procedures are affected by the account and assertion in question. A non-response to a confirmation request may indicate a previously unidentified risk of material misstatement. In such situations, the auditor may need to revise the assessed risk of material misstatement at the assertion level, and modify planned audit procedures, in accordance with ASA 315.[20] For example, fewer responses to confirmation requests than anticipated, or a greater number of responses than anticipated, may indicate a previously unidentified fraud risk factor that requires evaluation in accordance with ASA 240.[21]
When a Response to a Positive Confirmation Request Is Necessary to Obtain Sufficient Appropriate Audit Evidence (Ref. Para. 13)
In certain circumstances, the auditor may identify an assessed risk of material misstatement at the assertion level for which a response to a positive confirmation request is necessary to obtain sufficient appropriate audit evidence. Such circumstances may include where:
The information available to corroborate management’s assertion(s) is only available outside the entity.
Specific fraud risk factors, such as the risk of management override of controls, or the risk of collusion which can involve employee(s) and/or management, prevent the auditor from relying on evidence from the entity.
Exceptions (Ref: Para. 14)
Exceptions noted in responses to confirmation requests may indicate misstatements or potential misstatements in the financial statements. When a misstatement is identified, the auditor is required by ASA 240 to evaluate whether such misstatement is indicative of fraud.[22] Exceptions may provide a guide to the quality of responses from similar confirming parties or for similar accounts. Exceptions also may indicate a deficiency, or deficiencies, in the entity’s internal control over financial reporting.
Some exceptions do not represent misstatements. For example, the auditor may conclude that differences in responses to confirmation requests are due to timing, measurement, or clerical errors in the external confirmation procedures.
Negative Confirmations (Ref: Para. 15)
The failure to receive a response to a negative confirmation request does not explicitly indicate receipt by the intended confirming party of the confirmation request or verification of the accuracy of the information contained in the request. Accordingly, a failure of a confirming party to respond to a negative confirmation request provides significantly less persuasive audit evidence than does a response to a positive confirmation request. Confirming parties also may be more likely to respond indicating their disagreement with a confirmation request when the information in the request is not in their favour, and less likely to respond otherwise. For example, holders of bank deposit accounts may be more likely to respond if they believe that the balance in their account is understated in the confirmation request, but may be less likely to respond when they believe the balance is overstated. Therefore, sending negative confirmation requests to holders of bank deposit accounts may be a useful procedure in considering whether such balances may be understated, but is unlikely to be effective if the auditor is seeking evidence regarding overstatement.
Evaluating the Evidence Obtained (Ref: Para. 16)
When evaluating the results of individual external confirmation requests, the auditor may categorise such results as follows:
A response by the appropriate confirming party indicating agreement with the information provided in the confirmation request, or providing requested information without exception;
A response deemed unreliable;
A non-response; or
A response indicating an exception.
The auditor’s evaluation, when taken into account with other audit procedures the auditor may have performed, may assist the auditor in concluding whether sufficient appropriate audit evidence has been obtained or whether further audit evidence is necessary, as required by ASA 330.[23]
Application
Application
Application
Aus 0.1 This Auditing Standard applies to:
(a) an audit of a financial report for a financial year, or an audit of a financial report for a half-year, in accordance with the Corporations Act 2001; and
(b) an audit of a financial report, or a complete set of financial statements, for any other purpose.
Aus 0.2 This Auditing Standard also applies, as appropriate, to an audit of other historical financial information.
Operative Date
Operative Date
Operative Date
Aus 0.3 This Auditing Standard is operative for financial reporting periods commencing on or after 1 January 2010. [Note: For operative dates of paragraphs changed or added by an Amending Standard, see Compilation Details.]
Introduction
Introduction
Auditing Standard ASA 505
The Auditing and Assurance Standards Board (AUASB) made Auditing Standard ASA 505 External Confirmations pursuant to section 227B of the Australian Securities and Investments Commission Act 2001 and section 336 of the Corporations Act 2001, on 27 October 2009.
This compiled version of ASA 505 incorporates subsequent amendments contained in other Auditing Standards made by the AUASB up to and including 3 March 2020 (see Compilation Details).
Auditing Standard ASA 505
External Confirmations
Application
Aus 0.1 This Auditing Standard applies to:
(a) an audit of a financial report for a financial year, or an audit of a financial report for a half-year, in accordance with the Corporations Act 2001; and
(b) an audit of a financial report, or a complete set of financial statements, for any other purpose.
Aus 0.2 This Auditing Standard also applies, as appropriate, to an audit of other historical financial information.
Operative Date
Aus 0.3 This Auditing Standard is operative for financial reporting periods commencing on or after 1 January 2010. [Note: For operative dates of paragraphs changed or added by an Amending Standard, see Compilation Details.]
Introduction
Scope of this Auditing Standard
This Auditing Standard deals with the auditor’s use of external confirmation procedures to obtain audit evidence in accordance with the requirements of ASA 330[1] and ASA 500[2]. It does not address enquiries regarding litigation and claims, which are dealt with in ASA 502.[3]
External Confirmation Procedures to Obtain Audit Evidence
ASA 500 indicates that the reliability of audit evidence is influenced by its source and by its nature, and is dependent on the individual circumstances under which it is obtained.[4] That Auditing Standard also includes the following generalisations applicable to audit evidence:[5]
Audit evidence is more reliable when it is obtained from independent sources outside the entity.
Audit evidence obtained directly by the auditor is more reliable than audit evidence obtained indirectly or by inference.
Audit evidence is more reliable when it exists in documentary form, whether paper, electronic or other medium.
Accordingly, depending on the circumstances of the audit, audit evidence in the form of external confirmations received directly by the auditor from confirming parties may be more reliable than evidence generated internally by the entity. This Auditing Standard is intended to assist the auditor in designing and performing external confirmation procedures to obtain relevant and reliable audit evidence.
Other Auditing Standards recognise the importance of external confirmations as audit evidence, for example:
ASA 330 discusses the auditor’s responsibility to design and implement overall responses to address the assessed risks of material misstatement at the financial statement level, and to design and perform further audit procedures whose nature, timing and extent are based on, and are responsive to, the assessed risks of material misstatement at the assertion level.[6] In addition, ASA 330 requires that, irrespective of the assessed risks of material misstatement, the auditor designs and performs substantive procedures for each material class of transactions, account balance, and disclosure. The auditor is also required to consider whether external confirmation procedures are to be performed as substantive audit procedures.[7]
ASA 330 requires that the auditor obtain more persuasive audit evidence the higher the auditor’s assessment of risk.[8] To do this, the auditor may increase the quantity of the evidence or obtain evidence that is more relevant or reliable, or both. For example, the auditor may place more emphasis on obtaining evidence directly from third parties or obtaining corroborating evidence from a number of independent sources. ASA 330 also indicates that external confirmation procedures may assist the auditor in obtaining audit evidence with the high level of reliability that the auditor requires to respond to significant risks of material misstatement, whether due to fraud or error.[9]
ASA 240 indicates that the auditor may design confirmation requests to obtain additional corroborative information as a response to address the assessed risks of material misstatement due to fraud at the assertion level.[10]
ASA 500 indicates that corroborating information obtained from a source independent of the entity, such as external confirmations, may increase the assurance the auditor obtains from evidence existing within the accounting records or from representations made by management.[11]
Effective Date
[Deleted by the AUASB. Refer Aus 0.3]
Objective
The objective of the auditor, when using external confirmation procedures, is to design and perform such procedures to obtain relevant and reliable audit evidence.
Definitions
For purposes of the Australian Auditing Standards, the following terms have the meanings attributed below:
External confirmation means audit evidence obtained as a direct written response to the auditor from a third party (the confirming party), in paper form, or by electronic or other medium.
Positive confirmation request means a request that the confirming party respond directly to the auditor indicating whether the confirming party agrees or disagrees with the information in the request, or providing the requested information.
Negative confirmation request means a request that the confirming party respond directly to the auditor only if the confirming party disagrees with the information provided in the request.
Non-response means a failure of the confirming party to respond, or fully respond, to a positive confirmation request, or a confirmation request returned undelivered.
Exception means a response that indicates a difference between information requested to be confirmed, or contained in the entity’s records, and information provided by the confirming party.
Requirements
External Confirmation Procedures
When using external confirmation procedures, the auditor shall maintain control over external confirmation requests, including:
Determining the information to be confirmed or requested; (Ref: Para. A1)
Selecting the appropriate confirming party; (Ref: Para. A2)
Designing the confirmation requests, including determining that requests are properly addressed and contain return information for responses to be sent directly to the auditor; and (Ref: Para. A3-A6)
Sending the requests, including follow-up requests when applicable, to the confirming party. (Ref: Para. A7)
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
If management refuses to allow the auditor to send a confirmation request, the auditor shall:
Enquire as to management’s reasons for the refusal, and seek audit evidence as to their validity and reasonableness; (Ref: Para. A8)
Evaluate the implications of management’s refusal on the auditor’s assessment of the relevant risks of material misstatement, including the risk of fraud, and on the nature, timing and extent of other audit procedures; and (Ref: Para. A9)
Perform alternative audit procedures designed to obtain relevant and reliable audit evidence. (Ref: Para. A10)
If the auditor concludes that management’s refusal to allow the auditor to send a confirmation request is unreasonable, or the auditor is unable to obtain relevant and reliable audit evidence from alternative audit procedures, the auditor shall communicate with those charged with governance in accordance with ASA 260.[12] The auditor also shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705.[13]
Results of the External Confirmation Procedures
Reliability of Responses to Confirmation Requests
If the auditor identifies factors that give rise to doubts about the reliability of the response to a confirmation request, the auditor shall obtain further audit evidence to resolve those doubts.
(Ref: Para. A11-A16)
If the auditor determines that a response to a confirmation request is not reliable, the auditor shall evaluate the implications on the assessment of the relevant risks of material misstatement, including the risk of fraud, and on the related nature, timing and extent of other audit procedures. (Ref: Para. A17)
Non-Responses
In the case of each non-response, the auditor shall perform alternative audit procedures to obtain relevant and reliable audit evidence. (Ref: Para A18-A19)
When a Response to a Positive Confirmation Request Is Necessary to Obtain Sufficient Appropriate Audit Evidence
If the auditor has determined that a response to a positive confirmation request is necessary to obtain sufficient appropriate audit evidence, alternative audit procedures will not provide the audit evidence the auditor requires. If the auditor does not obtain such confirmation, the auditor shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705. (Ref: Para A20)
Exceptions
The auditor shall investigate exceptions to determine whether or not they are indicative of misstatements. (Ref: Para. A21-A22)
Negative Confirmations
Negative confirmations provide less persuasive audit evidence than positive confirmations. Accordingly, the auditor shall not use negative confirmation requests as the sole substantive audit procedure to address an assessed risk of material misstatement at the assertion level unless all of the following are present: (Ref: Para. A23)
The auditor has assessed the risk of material misstatement as low and has obtained sufficient appropriate audit evidence regarding the operating effectiveness of controls relevant to the assertion;
The population of items subject to negative confirmation procedures comprises a large number of small, homogeneous, account balances, transactions or conditions;
A very low exception rate is expected; and
The auditor is not aware of circumstances or conditions that would cause recipients of negative confirmation requests to disregard such requests.
Evaluating the Evidence Obtained
The auditor shall evaluate whether the results of the external confirmation procedures provide relevant and reliable audit evidence, or whether further audit evidence is necessary.
(Ref: Para A24-A25)
* * *
Application and Other Explanatory Material
External Confirmation Procedures
Determining the Information to Be Confirmed or Requested (Ref: Para. 7(a))
External confirmation procedures frequently are performed to confirm or request information regarding account balances and their elements. They may also be used to confirm terms of agreements, contracts, or transactions between an entity and other parties, or to confirm the absence of certain conditions, such as a “side agreement.”
Selecting the Appropriate Confirming Party (Ref: Para. 7(b))
Responses to confirmation requests provide more relevant and reliable audit evidence when confirmation requests are sent to a confirming party the auditor believes is knowledgeable about the information to be confirmed. For example, a financial institution official who is knowledgeable about the transactions or arrangements for which confirmation is requested may be the most appropriate person at the financial institution from whom to request confirmation.
Designing Confirmation Requests (Ref: Para. 7(c))
The design of a confirmation request may directly affect the confirmation response rate, and the reliability and the nature of the audit evidence obtained from responses.
Factors to consider when designing confirmation requests include:
The assertions being addressed.
Specific identified risks of material misstatement, including fraud risks.
The layout and presentation of the confirmation request.
Prior experience on the audit or similar engagements.
The method of communication (for example, in paper form, or by electronic or other medium).
Management’s authorisation or encouragement to the confirming parties to respond to the auditor. Confirming parties may only be willing to respond to a confirmation request containing management’s authorisation.
The ability of the intended confirming party to confirm or provide the requested information (for example, individual invoice amount versus total balance).
A positive external confirmation request asks the confirming party to reply to the auditor in all cases, either by indicating the confirming party’s agreement with the given information, or by asking the confirming party to provide information. A response to a positive confirmation request ordinarily is expected to provide reliable audit evidence. There is a risk, however, that a confirming party may reply to the confirmation request without verifying that the information is correct. The auditor may reduce this risk by using positive confirmation requests that do not state the amount (or other information) on the confirmation request, and ask the confirming party to fill in the amount or furnish other information. On the other hand, use of this type of “blank” confirmation request may result in lower response rates because additional effort is required of the confirming parties.
Determining that requests are properly addressed includes testing the validity of some or all of the addresses on confirmation requests before they are sent out.
Follow-Up on Confirmation Requests (Ref: Para. 7(d))
The auditor may send an additional confirmation request when a reply to a previous request has not been received within a reasonable time. For example, the auditor may, having re-verified the accuracy of the original address, send an additional or follow-up request.
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
Reasonableness of Management’s Refusal (Ref: Para. 8(a))
A refusal by management to allow the auditor to send a confirmation request is a limitation on the audit evidence the auditor may wish to obtain. The auditor is therefore required to enquire as to the reasons for the limitation. A common reason advanced is the existence of a legal dispute or ongoing negotiation with the intended confirming party, the resolution of which may be affected by an untimely confirmation request. The auditor is required to seek audit evidence as to the validity and reasonableness of the reasons because of the risk that management may be attempting to deny the auditor access to audit evidence that may reveal fraud or error.
Implications for the Assessment of Risks of Material Misstatement (Ref: Para. 8(b))
The auditor may conclude from the evaluation in paragraph 8(b) that it would be appropriate to revise the assessment of the risks of material misstatement at the assertion level and modify planned audit procedures in accordance with ASA 315.[14] For example, if management’s request to not confirm is unreasonable, this may indicate a fraud risk factor that requires evaluation in accordance with ASA 240.[15]
Alternative Audit Procedures (Ref: Para. 8(c))
The alternative audit procedures performed may be similar to those appropriate for a non-response as set out in paragraphs A18-A19 of this Auditing Standard. Such procedures also would take account of the results of the auditor’s evaluation in paragraph 8(b) of this Auditing Standard.
Results of the External Confirmation Procedures
Reliability of Responses to Confirmation Requests (Ref: Para. 10)
ASA 500 indicates that even when audit evidence is obtained from sources external to the entity, circumstances may exist that affect its reliability.[16] All responses carry some risk of interception, alteration or fraud. Such risk exists regardless of whether a response is obtained in paper form, or by electronic or other medium. Factors that may indicate doubts about the reliability of a response include that it:
Was received by the auditor indirectly; or
Appeared not to come from the originally intended confirming party.
Responses received electronically, for example by facsimile or electronic mail, involve risks as to reliability because proof of origin and authority of the respondent may be difficult to establish, and alterations may be difficult to detect. A process used by the auditor and the respondent that creates a secure environment for responses received electronically may mitigate these risks. If the auditor is satisfied that such a process is secure and properly controlled, the reliability of the related responses is enhanced. An electronic confirmation process might incorporate various techniques for validating the identity of a sender of information in electronic form, for example, through the use of encryption, electronic digital signatures, and procedures to verify web site authenticity.
If a confirming party uses a third party to coordinate and provide responses to confirmation requests, the auditor may perform procedures to address the risks that:
The response may not be from the proper source;
A respondent may not be authorised to respond; and
The integrity of the transmission may have been compromised.
The auditor is required by ASA 500 to determine whether to modify or add procedures to resolve doubts over the reliability of information to be used as audit evidence.[17] The auditor may choose to verify the source and contents of a response to a confirmation request by contacting the confirming party. For example, when a confirming party responds by electronic mail, the auditor may telephone the confirming party to determine whether the confirming party did, in fact, send the response. When a response has been returned to the auditor indirectly (for example, because the confirming party incorrectly addressed it to the entity rather than to the auditor), the auditor may request the confirming party to respond in writing directly to the auditor.
On its own, an oral response to a confirmation request does not meet the definition of an external confirmation because it is not a direct written response to the auditor. However, upon obtaining an oral response to a confirmation request, the auditor may, depending on the circumstances, request the confirming party to respond in writing directly to the auditor. If no such response is received, in accordance with paragraph 12, the auditor seeks other audit evidence to support the information in the oral response.
A response to a confirmation request may contain restrictive language regarding its use. Such restrictions do not necessarily invalidate the reliability of the response as audit evidence.
Unreliable Responses (Ref: Para. 11)
When the auditor concludes that a response is unreliable, the auditor may need to revise the assessment of the risks of material misstatement at the assertion level and modify planned audit procedures accordingly, in accordance with ASA 315.[18] For example, an unreliable response may indicate a fraud risk factor that requires evaluation in accordance with ASA 240.[19]
Non-Responses (Ref: Para. 12)
Examples of alternative audit procedures the auditor may perform include:
For accounts receivable balances – examining specific subsequent cash receipts, shipping documentation, and sales near the period-end.
For accounts payable balances – examining subsequent cash disbursements or correspondence from third parties, and other records, such as goods received notes.
The nature and extent of alternative audit procedures are affected by the account and assertion in question. A non-response to a confirmation request may indicate a previously unidentified risk of material misstatement. In such situations, the auditor may need to revise the assessed risk of material misstatement at the assertion level, and modify planned audit procedures, in accordance with ASA 315.[20] For example, fewer responses to confirmation requests than anticipated, or a greater number of responses than anticipated, may indicate a previously unidentified fraud risk factor that requires evaluation in accordance with ASA 240.[21]
When a Response to a Positive Confirmation Request Is Necessary to Obtain Sufficient Appropriate Audit Evidence (Ref. Para. 13)
In certain circumstances, the auditor may identify an assessed risk of material misstatement at the assertion level for which a response to a positive confirmation request is necessary to obtain sufficient appropriate audit evidence. Such circumstances may include where:
The information available to corroborate management’s assertion(s) is only available outside the entity.
Specific fraud risk factors, such as the risk of management override of controls, or the risk of collusion which can involve employee(s) and/or management, prevent the auditor from relying on evidence from the entity.
Exceptions (Ref: Para. 14)
Exceptions noted in responses to confirmation requests may indicate misstatements or potential misstatements in the financial statements. When a misstatement is identified, the auditor is required by ASA 240 to evaluate whether such misstatement is indicative of fraud.[22] Exceptions may provide a guide to the quality of responses from similar confirming parties or for similar accounts. Exceptions also may indicate a deficiency, or deficiencies, in the entity’s internal control over financial reporting.
Some exceptions do not represent misstatements. For example, the auditor may conclude that differences in responses to confirmation requests are due to timing, measurement, or clerical errors in the external confirmation procedures.
Negative Confirmations (Ref: Para. 15)
The failure to receive a response to a negative confirmation request does not explicitly indicate receipt by the intended confirming party of the confirmation request or verification of the accuracy of the information contained in the request. Accordingly, a failure of a confirming party to respond to a negative confirmation request provides significantly less persuasive audit evidence than does a response to a positive confirmation request. Confirming parties also may be more likely to respond indicating their disagreement with a confirmation request when the information in the request is not in their favour, and less likely to respond otherwise. For example, holders of bank deposit accounts may be more likely to respond if they believe that the balance in their account is understated in the confirmation request, but may be less likely to respond when they believe the balance is overstated. Therefore, sending negative confirmation requests to holders of bank deposit accounts may be a useful procedure in considering whether such balances may be understated, but is unlikely to be effective if the auditor is seeking evidence regarding overstatement.
Evaluating the Evidence Obtained (Ref: Para. 16)
When evaluating the results of individual external confirmation requests, the auditor may categorise such results as follows:
A response by the appropriate confirming party indicating agreement with the information provided in the confirmation request, or providing requested information without exception;
A response deemed unreliable;
A non-response; or
A response indicating an exception.
The auditor’s evaluation, when taken into account with other audit procedures the auditor may have performed, may assist the auditor in concluding whether sufficient appropriate audit evidence has been obtained or whether further audit evidence is necessary, as required by ASA 330.[23]
Scope of this Auditing Standard
Scope of this Auditing Standard
Scope of this Auditing Standard
This Auditing Standard deals with the auditor’s use of external confirmation procedures to obtain audit evidence in accordance with the requirements of ASA 330[1] and ASA 500[2]. It does not address enquiries regarding litigation and claims, which are dealt with in ASA 502.[3]
External Confirmation Procedures to Obta
External Confirmation Procedures to Obtain Audit Evidence
External Confirmation Procedures to Obtain Audit Evidence
ASA 500 indicates that the reliability of audit evidence is influenced by its source and by its nature, and is dependent on the individual circumstances under which it is obtained.[4] That Auditing Standard also includes the following generalisations applicable to audit evidence:[5]
Audit evidence is more reliable when it is obtained from independent sources outside the entity.
Audit evidence obtained directly by the auditor is more reliable than audit evidence obtained indirectly or by inference.
Audit evidence is more reliable when it exists in documentary form, whether paper, electronic or other medium.
Accordingly, depending on the circumstances of the audit, audit evidence in the form of external confirmations received directly by the auditor from confirming parties may be more reliable than evidence generated internally by the entity. This Auditing Standard is intended to assist the auditor in designing and performing external confirmation procedures to obtain relevant and reliable audit evidence.
Other Auditing Standards recognise the importance of external confirmations as audit evidence, for example:
ASA 330 discusses the auditor’s responsibility to design and implement overall responses to address the assessed risks of material misstatement at the financial statement level, and to design and perform further audit procedures whose nature, timing and extent are based on, and are responsive to, the assessed risks of material misstatement at the assertion level.[6] In addition, ASA 330 requires that, irrespective of the assessed risks of material misstatement, the auditor designs and performs substantive procedures for each material class of transactions, account balance, and disclosure. The auditor is also required to consider whether external confirmation procedures are to be performed as substantive audit procedures.[7]
ASA 330 requires that the auditor obtain more persuasive audit evidence the higher the auditor’s assessment of risk.[8] To do this, the auditor may increase the quantity of the evidence or obtain evidence that is more relevant or reliable, or both. For example, the auditor may place more emphasis on obtaining evidence directly from third parties or obtaining corroborating evidence from a number of independent sources. ASA 330 also indicates that external confirmation procedures may assist the auditor in obtaining audit evidence with the high level of reliability that the auditor requires to respond to significant risks of material misstatement, whether due to fraud or error.[9]
ASA 240 indicates that the auditor may design confirmation requests to obtain additional corroborative information as a response to address the assessed risks of material misstatement due to fraud at the assertion level.[10]
ASA 500 indicates that corroborating information obtained from a source independent of the entity, such as external confirmations, may increase the assurance the auditor obtains from evidence existing within the accounting records or from representations made by management.[11]
Effective Date
Effective Date
Effective Date
[Deleted by the AUASB. Refer Aus 0.3]
Objective
Objective
Objective
The objective of the auditor, when using external confirmation procedures, is to design and perform such procedures to obtain relevant and reliable audit evidence.
Definitions
Definitions
Definitions
For purposes of the Australian Auditing Standards, the following terms have the meanings attributed below:
External confirmation means audit evidence obtained as a direct written response to the auditor from a third party (the confirming party), in paper form, or by electronic or other medium.
Positive confirmation request means a request that the confirming party respond directly to the auditor indicating whether the confirming party agrees or disagrees with the information in the request, or providing the requested information.
Negative confirmation request means a request that the confirming party respond directly to the auditor only if the confirming party disagrees with the information provided in the request.
Non-response means a failure of the confirming party to respond, or fully respond, to a positive confirmation request, or a confirmation request returned undelivered.
Exception means a response that indicates a difference between information requested to be confirmed, or contained in the entity’s records, and information provided by the confirming party.
Requirements
Requirements
Auditing Standard ASA 505
The Auditing and Assurance Standards Board (AUASB) made Auditing Standard ASA 505 External Confirmations pursuant to section 227B of the Australian Securities and Investments Commission Act 2001 and section 336 of the Corporations Act 2001, on 27 October 2009.
This compiled version of ASA 505 incorporates subsequent amendments contained in other Auditing Standards made by the AUASB up to and including 3 March 2020 (see Compilation Details).
Auditing Standard ASA 505
External Confirmations
Application
Aus 0.1 This Auditing Standard applies to:
(a) an audit of a financial report for a financial year, or an audit of a financial report for a half-year, in accordance with the Corporations Act 2001; and
(b) an audit of a financial report, or a complete set of financial statements, for any other purpose.
Aus 0.2 This Auditing Standard also applies, as appropriate, to an audit of other historical financial information.
Operative Date
Aus 0.3 This Auditing Standard is operative for financial reporting periods commencing on or after 1 January 2010. [Note: For operative dates of paragraphs changed or added by an Amending Standard, see Compilation Details.]
Introduction
Scope of this Auditing Standard
This Auditing Standard deals with the auditor’s use of external confirmation procedures to obtain audit evidence in accordance with the requirements of ASA 330[1] and ASA 500[2]. It does not address enquiries regarding litigation and claims, which are dealt with in ASA 502.[3]
External Confirmation Procedures to Obtain Audit Evidence
ASA 500 indicates that the reliability of audit evidence is influenced by its source and by its nature, and is dependent on the individual circumstances under which it is obtained.[4] That Auditing Standard also includes the following generalisations applicable to audit evidence:[5]
Audit evidence is more reliable when it is obtained from independent sources outside the entity.
Audit evidence obtained directly by the auditor is more reliable than audit evidence obtained indirectly or by inference.
Audit evidence is more reliable when it exists in documentary form, whether paper, electronic or other medium.
Accordingly, depending on the circumstances of the audit, audit evidence in the form of external confirmations received directly by the auditor from confirming parties may be more reliable than evidence generated internally by the entity. This Auditing Standard is intended to assist the auditor in designing and performing external confirmation procedures to obtain relevant and reliable audit evidence.
Other Auditing Standards recognise the importance of external confirmations as audit evidence, for example:
ASA 330 discusses the auditor’s responsibility to design and implement overall responses to address the assessed risks of material misstatement at the financial statement level, and to design and perform further audit procedures whose nature, timing and extent are based on, and are responsive to, the assessed risks of material misstatement at the assertion level.[6] In addition, ASA 330 requires that, irrespective of the assessed risks of material misstatement, the auditor designs and performs substantive procedures for each material class of transactions, account balance, and disclosure. The auditor is also required to consider whether external confirmation procedures are to be performed as substantive audit procedures.[7]
ASA 330 requires that the auditor obtain more persuasive audit evidence the higher the auditor’s assessment of risk.[8] To do this, the auditor may increase the quantity of the evidence or obtain evidence that is more relevant or reliable, or both. For example, the auditor may place more emphasis on obtaining evidence directly from third parties or obtaining corroborating evidence from a number of independent sources. ASA 330 also indicates that external confirmation procedures may assist the auditor in obtaining audit evidence with the high level of reliability that the auditor requires to respond to significant risks of material misstatement, whether due to fraud or error.[9]
ASA 240 indicates that the auditor may design confirmation requests to obtain additional corroborative information as a response to address the assessed risks of material misstatement due to fraud at the assertion level.[10]
ASA 500 indicates that corroborating information obtained from a source independent of the entity, such as external confirmations, may increase the assurance the auditor obtains from evidence existing within the accounting records or from representations made by management.[11]
Effective Date
[Deleted by the AUASB. Refer Aus 0.3]
Objective
The objective of the auditor, when using external confirmation procedures, is to design and perform such procedures to obtain relevant and reliable audit evidence.
Definitions
For purposes of the Australian Auditing Standards, the following terms have the meanings attributed below:
External confirmation means audit evidence obtained as a direct written response to the auditor from a third party (the confirming party), in paper form, or by electronic or other medium.
Positive confirmation request means a request that the confirming party respond directly to the auditor indicating whether the confirming party agrees or disagrees with the information in the request, or providing the requested information.
Negative confirmation request means a request that the confirming party respond directly to the auditor only if the confirming party disagrees with the information provided in the request.
Non-response means a failure of the confirming party to respond, or fully respond, to a positive confirmation request, or a confirmation request returned undelivered.
Exception means a response that indicates a difference between information requested to be confirmed, or contained in the entity’s records, and information provided by the confirming party.
Requirements
External Confirmation Procedures
When using external confirmation procedures, the auditor shall maintain control over external confirmation requests, including:
Determining the information to be confirmed or requested; (Ref: Para. A1)
Selecting the appropriate confirming party; (Ref: Para. A2)
Designing the confirmation requests, including determining that requests are properly addressed and contain return information for responses to be sent directly to the auditor; and (Ref: Para. A3-A6)
Sending the requests, including follow-up requests when applicable, to the confirming party. (Ref: Para. A7)
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
If management refuses to allow the auditor to send a confirmation request, the auditor shall:
Enquire as to management’s reasons for the refusal, and seek audit evidence as to their validity and reasonableness; (Ref: Para. A8)
Evaluate the implications of management’s refusal on the auditor’s assessment of the relevant risks of material misstatement, including the risk of fraud, and on the nature, timing and extent of other audit procedures; and (Ref: Para. A9)
Perform alternative audit procedures designed to obtain relevant and reliable audit evidence. (Ref: Para. A10)
If the auditor concludes that management’s refusal to allow the auditor to send a confirmation request is unreasonable, or the auditor is unable to obtain relevant and reliable audit evidence from alternative audit procedures, the auditor shall communicate with those charged with governance in accordance with ASA 260.[12] The auditor also shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705.[13]
Results of the External Confirmation Procedures
Reliability of Responses to Confirmation Requests
If the auditor identifies factors that give rise to doubts about the reliability of the response to a confirmation request, the auditor shall obtain further audit evidence to resolve those doubts.
(Ref: Para. A11-A16)
If the auditor determines that a response to a confirmation request is not reliable, the auditor shall evaluate the implications on the assessment of the relevant risks of material misstatement, including the risk of fraud, and on the related nature, timing and extent of other audit procedures. (Ref: Para. A17)
Non-Responses
In the case of each non-response, the auditor shall perform alternative audit procedures to obtain relevant and reliable audit evidence. (Ref: Para A18-A19)
When a Response to a Positive Confirmation Request Is Necessary to Obtain Sufficient Appropriate Audit Evidence
If the auditor has determined that a response to a positive confirmation request is necessary to obtain sufficient appropriate audit evidence, alternative audit procedures will not provide the audit evidence the auditor requires. If the auditor does not obtain such confirmation, the auditor shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705. (Ref: Para A20)
Exceptions
The auditor shall investigate exceptions to determine whether or not they are indicative of misstatements. (Ref: Para. A21-A22)
Negative Confirmations
Negative confirmations provide less persuasive audit evidence than positive confirmations. Accordingly, the auditor shall not use negative confirmation requests as the sole substantive audit procedure to address an assessed risk of material misstatement at the assertion level unless all of the following are present: (Ref: Para. A23)
The auditor has assessed the risk of material misstatement as low and has obtained sufficient appropriate audit evidence regarding the operating effectiveness of controls relevant to the assertion;
The population of items subject to negative confirmation procedures comprises a large number of small, homogeneous, account balances, transactions or conditions;
A very low exception rate is expected; and
The auditor is not aware of circumstances or conditions that would cause recipients of negative confirmation requests to disregard such requests.
Evaluating the Evidence Obtained
The auditor shall evaluate whether the results of the external confirmation procedures provide relevant and reliable audit evidence, or whether further audit evidence is necessary.
(Ref: Para A24-A25)
* * *
Application and Other Explanatory Material
External Confirmation Procedures
Determining the Information to Be Confirmed or Requested (Ref: Para. 7(a))
External confirmation procedures frequently are performed to confirm or request information regarding account balances and their elements. They may also be used to confirm terms of agreements, contracts, or transactions between an entity and other parties, or to confirm the absence of certain conditions, such as a “side agreement.”
Selecting the Appropriate Confirming Party (Ref: Para. 7(b))
Responses to confirmation requests provide more relevant and reliable audit evidence when confirmation requests are sent to a confirming party the auditor believes is knowledgeable about the information to be confirmed. For example, a financial institution official who is knowledgeable about the transactions or arrangements for which confirmation is requested may be the most appropriate person at the financial institution from whom to request confirmation.
Designing Confirmation Requests (Ref: Para. 7(c))
The design of a confirmation request may directly affect the confirmation response rate, and the reliability and the nature of the audit evidence obtained from responses.
Factors to consider when designing confirmation requests include:
The assertions being addressed.
Specific identified risks of material misstatement, including fraud risks.
The layout and presentation of the confirmation request.
Prior experience on the audit or similar engagements.
The method of communication (for example, in paper form, or by electronic or other medium).
Management’s authorisation or encouragement to the confirming parties to respond to the auditor. Confirming parties may only be willing to respond to a confirmation request containing management’s authorisation.
The ability of the intended confirming party to confirm or provide the requested information (for example, individual invoice amount versus total balance).
A positive external confirmation request asks the confirming party to reply to the auditor in all cases, either by indicating the confirming party’s agreement with the given information, or by asking the confirming party to provide information. A response to a positive confirmation request ordinarily is expected to provide reliable audit evidence. There is a risk, however, that a confirming party may reply to the confirmation request without verifying that the information is correct. The auditor may reduce this risk by using positive confirmation requests that do not state the amount (or other information) on the confirmation request, and ask the confirming party to fill in the amount or furnish other information. On the other hand, use of this type of “blank” confirmation request may result in lower response rates because additional effort is required of the confirming parties.
Determining that requests are properly addressed includes testing the validity of some or all of the addresses on confirmation requests before they are sent out.
Follow-Up on Confirmation Requests (Ref: Para. 7(d))
The auditor may send an additional confirmation request when a reply to a previous request has not been received within a reasonable time. For example, the auditor may, having re-verified the accuracy of the original address, send an additional or follow-up request.
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
Reasonableness of Management’s Refusal (Ref: Para. 8(a))
A refusal by management to allow the auditor to send a confirmation request is a limitation on the audit evidence the auditor may wish to obtain. The auditor is therefore required to enquire as to the reasons for the limitation. A common reason advanced is the existence of a legal dispute or ongoing negotiation with the intended confirming party, the resolution of which may be affected by an untimely confirmation request. The auditor is required to seek audit evidence as to the validity and reasonableness of the reasons because of the risk that management may be attempting to deny the auditor access to audit evidence that may reveal fraud or error.
Implications for the Assessment of Risks of Material Misstatement (Ref: Para. 8(b))
The auditor may conclude from the evaluation in paragraph 8(b) that it would be appropriate to revise the assessment of the risks of material misstatement at the assertion level and modify planned audit procedures in accordance with ASA 315.[14] For example, if management’s request to not confirm is unreasonable, this may indicate a fraud risk factor that requires evaluation in accordance with ASA 240.[15]
Alternative Audit Procedures (Ref: Para. 8(c))
The alternative audit procedures performed may be similar to those appropriate for a non-response as set out in paragraphs A18-A19 of this Auditing Standard. Such procedures also would take account of the results of the auditor’s evaluation in paragraph 8(b) of this Auditing Standard.
Results of the External Confirmation Procedures
Reliability of Responses to Confirmation Requests (Ref: Para. 10)
ASA 500 indicates that even when audit evidence is obtained from sources external to the entity, circumstances may exist that affect its reliability.[16] All responses carry some risk of interception, alteration or fraud. Such risk exists regardless of whether a response is obtained in paper form, or by electronic or other medium. Factors that may indicate doubts about the reliability of a response include that it:
Was received by the auditor indirectly; or
Appeared not to come from the originally intended confirming party.
Responses received electronically, for example by facsimile or electronic mail, involve risks as to reliability because proof of origin and authority of the respondent may be difficult to establish, and alterations may be difficult to detect. A process used by the auditor and the respondent that creates a secure environment for responses received electronically may mitigate these risks. If the auditor is satisfied that such a process is secure and properly controlled, the reliability of the related responses is enhanced. An electronic confirmation process might incorporate various techniques for validating the identity of a sender of information in electronic form, for example, through the use of encryption, electronic digital signatures, and procedures to verify web site authenticity.
If a confirming party uses a third party to coordinate and provide responses to confirmation requests, the auditor may perform procedures to address the risks that:
The response may not be from the proper source;
A respondent may not be authorised to respond; and
The integrity of the transmission may have been compromised.
The auditor is required by ASA 500 to determine whether to modify or add procedures to resolve doubts over the reliability of information to be used as audit evidence.[17] The auditor may choose to verify the source and contents of a response to a confirmation request by contacting the confirming party. For example, when a confirming party responds by electronic mail, the auditor may telephone the confirming party to determine whether the confirming party did, in fact, send the response. When a response has been returned to the auditor indirectly (for example, because the confirming party incorrectly addressed it to the entity rather than to the auditor), the auditor may request the confirming party to respond in writing directly to the auditor.
On its own, an oral response to a confirmation request does not meet the definition of an external confirmation because it is not a direct written response to the auditor. However, upon obtaining an oral response to a confirmation request, the auditor may, depending on the circumstances, request the confirming party to respond in writing directly to the auditor. If no such response is received, in accordance with paragraph 12, the auditor seeks other audit evidence to support the information in the oral response.
A response to a confirmation request may contain restrictive language regarding its use. Such restrictions do not necessarily invalidate the reliability of the response as audit evidence.
Unreliable Responses (Ref: Para. 11)
When the auditor concludes that a response is unreliable, the auditor may need to revise the assessment of the risks of material misstatement at the assertion level and modify planned audit procedures accordingly, in accordance with ASA 315.[18] For example, an unreliable response may indicate a fraud risk factor that requires evaluation in accordance with ASA 240.[19]
Non-Responses (Ref: Para. 12)
Examples of alternative audit procedures the auditor may perform include:
For accounts receivable balances – examining specific subsequent cash receipts, shipping documentation, and sales near the period-end.
For accounts payable balances – examining subsequent cash disbursements or correspondence from third parties, and other records, such as goods received notes.
The nature and extent of alternative audit procedures are affected by the account and assertion in question. A non-response to a confirmation request may indicate a previously unidentified risk of material misstatement. In such situations, the auditor may need to revise the assessed risk of material misstatement at the assertion level, and modify planned audit procedures, in accordance with ASA 315.[20] For example, fewer responses to confirmation requests than anticipated, or a greater number of responses than anticipated, may indicate a previously unidentified fraud risk factor that requires evaluation in accordance with ASA 240.[21]
When a Response to a Positive Confirmation Request Is Necessary to Obtain Sufficient Appropriate Audit Evidence (Ref. Para. 13)
In certain circumstances, the auditor may identify an assessed risk of material misstatement at the assertion level for which a response to a positive confirmation request is necessary to obtain sufficient appropriate audit evidence. Such circumstances may include where:
The information available to corroborate management’s assertion(s) is only available outside the entity.
Specific fraud risk factors, such as the risk of management override of controls, or the risk of collusion which can involve employee(s) and/or management, prevent the auditor from relying on evidence from the entity.
Exceptions (Ref: Para. 14)
Exceptions noted in responses to confirmation requests may indicate misstatements or potential misstatements in the financial statements. When a misstatement is identified, the auditor is required by ASA 240 to evaluate whether such misstatement is indicative of fraud.[22] Exceptions may provide a guide to the quality of responses from similar confirming parties or for similar accounts. Exceptions also may indicate a deficiency, or deficiencies, in the entity’s internal control over financial reporting.
Some exceptions do not represent misstatements. For example, the auditor may conclude that differences in responses to confirmation requests are due to timing, measurement, or clerical errors in the external confirmation procedures.
Negative Confirmations (Ref: Para. 15)
The failure to receive a response to a negative confirmation request does not explicitly indicate receipt by the intended confirming party of the confirmation request or verification of the accuracy of the information contained in the request. Accordingly, a failure of a confirming party to respond to a negative confirmation request provides significantly less persuasive audit evidence than does a response to a positive confirmation request. Confirming parties also may be more likely to respond indicating their disagreement with a confirmation request when the information in the request is not in their favour, and less likely to respond otherwise. For example, holders of bank deposit accounts may be more likely to respond if they believe that the balance in their account is understated in the confirmation request, but may be less likely to respond when they believe the balance is overstated. Therefore, sending negative confirmation requests to holders of bank deposit accounts may be a useful procedure in considering whether such balances may be understated, but is unlikely to be effective if the auditor is seeking evidence regarding overstatement.
Evaluating the Evidence Obtained (Ref: Para. 16)
When evaluating the results of individual external confirmation requests, the auditor may categorise such results as follows:
A response by the appropriate confirming party indicating agreement with the information provided in the confirmation request, or providing requested information without exception;
A response deemed unreliable;
A non-response; or
A response indicating an exception.
The auditor’s evaluation, when taken into account with other audit procedures the auditor may have performed, may assist the auditor in concluding whether sufficient appropriate audit evidence has been obtained or whether further audit evidence is necessary, as required by ASA 330.[23]
External Confirmation Procedures
External Confirmation Procedures
External Confirmation Procedures
When using external confirmation procedures, the auditor shall maintain control over external confirmation requests, including:
Determining the information to be confirmed or requested; (Ref: Para. A1)
Selecting the appropriate confirming party; (Ref: Para. A2)
Designing the confirmation requests, including determining that requests are properly addressed and contain return information for responses to be sent directly to the auditor; and (Ref: Para. A3-A6)
Sending the requests, including follow-up requests when applicable, to the confirming party. (Ref: Para. A7)
Management’s Refusal to Allow the Audito
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
If management refuses to allow the auditor to send a confirmation request, the auditor shall:
Enquire as to management’s reasons for the refusal, and seek audit evidence as to their validity and reasonableness; (Ref: Para. A8)
Evaluate the implications of management’s refusal on the auditor’s assessment of the relevant risks of material misstatement, including the risk of fraud, and on the nature, timing and extent of other audit procedures; and (Ref: Para. A9)
Perform alternative audit procedures designed to obtain relevant and reliable audit evidence. (Ref: Para. A10)
If the auditor concludes that management’s refusal to allow the auditor to send a confirmation request is unreasonable, or the auditor is unable to obtain relevant and reliable audit evidence from alternative audit procedures, the auditor shall communicate with those charged with governance in accordance with ASA 260.[12] The auditor also shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705.[13]
Results of the External Confirmation Pro
Results of the External Confirmation Procedures
Results of the External Confirmation Procedures
Reliability of Responses to Confirmation Requests
If the auditor identifies factors that give rise to doubts about the reliability of the response to a confirmation request, the auditor shall obtain further audit evidence to resolve those doubts.
(Ref: Para. A11-A16)
If the auditor determines that a response to a confirmation request is not reliable, the auditor shall evaluate the implications on the assessment of the relevant risks of material misstatement, including the risk of fraud, and on the related nature, timing and extent of other audit procedures. (Ref: Para. A17)
Non-Responses
In the case of each non-response, the auditor shall perform alternative audit procedures to obtain relevant and reliable audit evidence. (Ref: Para A18-A19)
When a Response to a Positive Confirmation Request Is Necessary to Obtain Sufficient Appropriate Audit Evidence
If the auditor has determined that a response to a positive confirmation request is necessary to obtain sufficient appropriate audit evidence, alternative audit procedures will not provide the audit evidence the auditor requires. If the auditor does not obtain such confirmation, the auditor shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705. (Ref: Para A20)
Exceptions
The auditor shall investigate exceptions to determine whether or not they are indicative of misstatements. (Ref: Para. A21-A22)
Negative Confirmations
Negative Confirmations
Negative Confirmations
Negative confirmations provide less persuasive audit evidence than positive confirmations. Accordingly, the auditor shall not use negative confirmation requests as the sole substantive audit procedure to address an assessed risk of material misstatement at the assertion level unless all of the following are present: (Ref: Para. A23)
The auditor has assessed the risk of material misstatement as low and has obtained sufficient appropriate audit evidence regarding the operating effectiveness of controls relevant to the assertion;
The population of items subject to negative confirmation procedures comprises a large number of small, homogeneous, account balances, transactions or conditions;
A very low exception rate is expected; and
The auditor is not aware of circumstances or conditions that would cause recipients of negative confirmation requests to disregard such requests.
Evaluating the Evidence Obtained
Evaluating the Evidence Obtained
Evaluating the Evidence Obtained
The auditor shall evaluate whether the results of the external confirmation procedures provide relevant and reliable audit evidence, or whether further audit evidence is necessary.
(Ref: Para A24-A25)
* * *
Application and Other Explanatory Materi
Application and Other Explanatory Material
Auditing Standard ASA 505
The Auditing and Assurance Standards Board (AUASB) made Auditing Standard ASA 505 External Confirmations pursuant to section 227B of the Australian Securities and Investments Commission Act 2001 and section 336 of the Corporations Act 2001, on 27 October 2009.
This compiled version of ASA 505 incorporates subsequent amendments contained in other Auditing Standards made by the AUASB up to and including 3 March 2020 (see Compilation Details).
Auditing Standard ASA 505
External Confirmations
Application
Aus 0.1 This Auditing Standard applies to:
(a) an audit of a financial report for a financial year, or an audit of a financial report for a half-year, in accordance with the Corporations Act 2001; and
(b) an audit of a financial report, or a complete set of financial statements, for any other purpose.
Aus 0.2 This Auditing Standard also applies, as appropriate, to an audit of other historical financial information.
Operative Date
Aus 0.3 This Auditing Standard is operative for financial reporting periods commencing on or after 1 January 2010. [Note: For operative dates of paragraphs changed or added by an Amending Standard, see Compilation Details.]
Introduction
Scope of this Auditing Standard
This Auditing Standard deals with the auditor’s use of external confirmation procedures to obtain audit evidence in accordance with the requirements of ASA 330[1] and ASA 500[2]. It does not address enquiries regarding litigation and claims, which are dealt with in ASA 502.[3]
External Confirmation Procedures to Obtain Audit Evidence
ASA 500 indicates that the reliability of audit evidence is influenced by its source and by its nature, and is dependent on the individual circumstances under which it is obtained.[4] That Auditing Standard also includes the following generalisations applicable to audit evidence:[5]
Audit evidence is more reliable when it is obtained from independent sources outside the entity.
Audit evidence obtained directly by the auditor is more reliable than audit evidence obtained indirectly or by inference.
Audit evidence is more reliable when it exists in documentary form, whether paper, electronic or other medium.
Accordingly, depending on the circumstances of the audit, audit evidence in the form of external confirmations received directly by the auditor from confirming parties may be more reliable than evidence generated internally by the entity. This Auditing Standard is intended to assist the auditor in designing and performing external confirmation procedures to obtain relevant and reliable audit evidence.
Other Auditing Standards recognise the importance of external confirmations as audit evidence, for example:
ASA 330 discusses the auditor’s responsibility to design and implement overall responses to address the assessed risks of material misstatement at the financial statement level, and to design and perform further audit procedures whose nature, timing and extent are based on, and are responsive to, the assessed risks of material misstatement at the assertion level.[6] In addition, ASA 330 requires that, irrespective of the assessed risks of material misstatement, the auditor designs and performs substantive procedures for each material class of transactions, account balance, and disclosure. The auditor is also required to consider whether external confirmation procedures are to be performed as substantive audit procedures.[7]
ASA 330 requires that the auditor obtain more persuasive audit evidence the higher the auditor’s assessment of risk.[8] To do this, the auditor may increase the quantity of the evidence or obtain evidence that is more relevant or reliable, or both. For example, the auditor may place more emphasis on obtaining evidence directly from third parties or obtaining corroborating evidence from a number of independent sources. ASA 330 also indicates that external confirmation procedures may assist the auditor in obtaining audit evidence with the high level of reliability that the auditor requires to respond to significant risks of material misstatement, whether due to fraud or error.[9]
ASA 240 indicates that the auditor may design confirmation requests to obtain additional corroborative information as a response to address the assessed risks of material misstatement due to fraud at the assertion level.[10]
ASA 500 indicates that corroborating information obtained from a source independent of the entity, such as external confirmations, may increase the assurance the auditor obtains from evidence existing within the accounting records or from representations made by management.[11]
Effective Date
[Deleted by the AUASB. Refer Aus 0.3]
Objective
The objective of the auditor, when using external confirmation procedures, is to design and perform such procedures to obtain relevant and reliable audit evidence.
Definitions
For purposes of the Australian Auditing Standards, the following terms have the meanings attributed below:
External confirmation means audit evidence obtained as a direct written response to the auditor from a third party (the confirming party), in paper form, or by electronic or other medium.
Positive confirmation request means a request that the confirming party respond directly to the auditor indicating whether the confirming party agrees or disagrees with the information in the request, or providing the requested information.
Negative confirmation request means a request that the confirming party respond directly to the auditor only if the confirming party disagrees with the information provided in the request.
Non-response means a failure of the confirming party to respond, or fully respond, to a positive confirmation request, or a confirmation request returned undelivered.
Exception means a response that indicates a difference between information requested to be confirmed, or contained in the entity’s records, and information provided by the confirming party.
Requirements
External Confirmation Procedures
When using external confirmation procedures, the auditor shall maintain control over external confirmation requests, including:
Determining the information to be confirmed or requested; (Ref: Para. A1)
Selecting the appropriate confirming party; (Ref: Para. A2)
Designing the confirmation requests, including determining that requests are properly addressed and contain return information for responses to be sent directly to the auditor; and (Ref: Para. A3-A6)
Sending the requests, including follow-up requests when applicable, to the confirming party. (Ref: Para. A7)
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
If management refuses to allow the auditor to send a confirmation request, the auditor shall:
Enquire as to management’s reasons for the refusal, and seek audit evidence as to their validity and reasonableness; (Ref: Para. A8)
Evaluate the implications of management’s refusal on the auditor’s assessment of the relevant risks of material misstatement, including the risk of fraud, and on the nature, timing and extent of other audit procedures; and (Ref: Para. A9)
Perform alternative audit procedures designed to obtain relevant and reliable audit evidence. (Ref: Para. A10)
If the auditor concludes that management’s refusal to allow the auditor to send a confirmation request is unreasonable, or the auditor is unable to obtain relevant and reliable audit evidence from alternative audit procedures, the auditor shall communicate with those charged with governance in accordance with ASA 260.[12] The auditor also shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705.[13]
Results of the External Confirmation Procedures
Reliability of Responses to Confirmation Requests
If the auditor identifies factors that give rise to doubts about the reliability of the response to a confirmation request, the auditor shall obtain further audit evidence to resolve those doubts.
(Ref: Para. A11-A16)
If the auditor determines that a response to a confirmation request is not reliable, the auditor shall evaluate the implications on the assessment of the relevant risks of material misstatement, including the risk of fraud, and on the related nature, timing and extent of other audit procedures. (Ref: Para. A17)
Non-Responses
In the case of each non-response, the auditor shall perform alternative audit procedures to obtain relevant and reliable audit evidence. (Ref: Para A18-A19)
When a Response to a Positive Confirmation Request Is Necessary to Obtain Sufficient Appropriate Audit Evidence
If the auditor has determined that a response to a positive confirmation request is necessary to obtain sufficient appropriate audit evidence, alternative audit procedures will not provide the audit evidence the auditor requires. If the auditor does not obtain such confirmation, the auditor shall determine the implications for the audit and the auditor’s opinion in accordance with ASA 705. (Ref: Para A20)
Exceptions
The auditor shall investigate exceptions to determine whether or not they are indicative of misstatements. (Ref: Para. A21-A22)
Negative Confirmations
Negative confirmations provide less persuasive audit evidence than positive confirmations. Accordingly, the auditor shall not use negative confirmation requests as the sole substantive audit procedure to address an assessed risk of material misstatement at the assertion level unless all of the following are present: (Ref: Para. A23)
The auditor has assessed the risk of material misstatement as low and has obtained sufficient appropriate audit evidence regarding the operating effectiveness of controls relevant to the assertion;
The population of items subject to negative confirmation procedures comprises a large number of small, homogeneous, account balances, transactions or conditions;
A very low exception rate is expected; and
The auditor is not aware of circumstances or conditions that would cause recipients of negative confirmation requests to disregard such requests.
Evaluating the Evidence Obtained
The auditor shall evaluate whether the results of the external confirmation procedures provide relevant and reliable audit evidence, or whether further audit evidence is necessary.
(Ref: Para A24-A25)
* * *
Application and Other Explanatory Material
External Confirmation Procedures
Determining the Information to Be Confirmed or Requested (Ref: Para. 7(a))
External confirmation procedures frequently are performed to confirm or request information regarding account balances and their elements. They may also be used to confirm terms of agreements, contracts, or transactions between an entity and other parties, or to confirm the absence of certain conditions, such as a “side agreement.”
Selecting the Appropriate Confirming Party (Ref: Para. 7(b))
Responses to confirmation requests provide more relevant and reliable audit evidence when confirmation requests are sent to a confirming party the auditor believes is knowledgeable about the information to be confirmed. For example, a financial institution official who is knowledgeable about the transactions or arrangements for which confirmation is requested may be the most appropriate person at the financial institution from whom to request confirmation.
Designing Confirmation Requests (Ref: Para. 7(c))
The design of a confirmation request may directly affect the confirmation response rate, and the reliability and the nature of the audit evidence obtained from responses.
Factors to consider when designing confirmation requests include:
The assertions being addressed.
Specific identified risks of material misstatement, including fraud risks.
The layout and presentation of the confirmation request.
Prior experience on the audit or similar engagements.
The method of communication (for example, in paper form, or by electronic or other medium).
Management’s authorisation or encouragement to the confirming parties to respond to the auditor. Confirming parties may only be willing to respond to a confirmation request containing management’s authorisation.
The ability of the intended confirming party to confirm or provide the requested information (for example, individual invoice amount versus total balance).
A positive external confirmation request asks the confirming party to reply to the auditor in all cases, either by indicating the confirming party’s agreement with the given information, or by asking the confirming party to provide information. A response to a positive confirmation request ordinarily is expected to provide reliable audit evidence. There is a risk, however, that a confirming party may reply to the confirmation request without verifying that the information is correct. The auditor may reduce this risk by using positive confirmation requests that do not state the amount (or other information) on the confirmation request, and ask the confirming party to fill in the amount or furnish other information. On the other hand, use of this type of “blank” confirmation request may result in lower response rates because additional effort is required of the confirming parties.
Determining that requests are properly addressed includes testing the validity of some or all of the addresses on confirmation requests before they are sent out.
Follow-Up on Confirmation Requests (Ref: Para. 7(d))
The auditor may send an additional confirmation request when a reply to a previous request has not been received within a reasonable time. For example, the auditor may, having re-verified the accuracy of the original address, send an additional or follow-up request.
Management’s Refusal to Allow the Auditor to Send a Confirmation Request
Reasonableness of Management’s Refusal (Ref: Para. 8(a))
A refusal by management to allow the auditor to send a confirmation request is a limitation on the audit evidence the auditor may wish to obtain. The auditor is therefore required to enquire as to the reasons for the limitation. A common reason advanced is the existence of a legal dispute or ongoing negotiation with the intended confirming party, the resolution of which may be affected by an untimely confirmation request. The auditor is required to seek audit evidence as to the validity and reasonableness of the reasons because of the risk that management may be attempting to deny the auditor access to audit evidence that may reveal fraud or error.
Implications for the Assessment of Risks of Material Misstatement (Ref: Para. 8(b))
The auditor may conclude from the evaluation in paragraph 8(b) that it would be appropriate to revise the assessment of the risks of material misstatement at the assertion level and modify planned audit procedures in accordance with ASA 315.[14] For example, if management’s request to not confirm is unreasonable, this may indicate a fraud risk factor that requires evaluation in accordance with ASA 240.[15]
Alternative Audit Procedures (Ref: Para. 8(c))
The alternative audit procedures performed may be similar to those appropriate for a non-response as set out in paragraphs A18-A19 of this Auditing Standard. Such procedures also would take account of the results of the auditor’s evaluation in paragraph 8(b) of this Auditing Standard.
Results of the External Confirmation Procedures
Reliability of Responses to Confirmation Requests (Ref: Para. 10)
ASA 500 indicates that even when audit evidence is obtained from sources external to the entity, circumstances may exist that affect its reliability.[16] All responses carry some risk of interception, alteration or fraud. Such risk exists regardless of whether a response is obtained in paper form, or by electronic or other medium. Factors that may indicate doubts about the reliability of a response include that it:
Was received by the auditor indirectly; or
Appeared not to come from the originally intended confirming party.
Responses received electronically, for example by facsimile or electronic mail, involve risks as to reliability because proof of origin and authority of the respondent may be difficult to establish, and alterations may be difficult to detect. A process used by the auditor and the respondent that creates a secure environment for responses received electronically may mitigate these risks. If the auditor is satisfied that such a process is secure and properly controlled, the reliability of the related responses is enhanced. An electronic confirmation process might incorporate various techniques for validating the identity of a sender of information in electronic form, for example, through the use of encryption, electronic digital signatures, and procedures to verify web site authenticity.
If a confirming party uses a third party to coordinate and provide responses to confirmation requests, the auditor may perform procedures to address the risks that:
The response may not be from the proper source;
A respondent may not be authorised to respond; and
The integrity of the transmission may have been compromised.
The auditor is required by ASA 500 to determine whether to modify or add procedures to resolve doubts over the reliability of information to be used as audit evidence.[17] The auditor may choose to verify the source and contents of a response to a confirmation request by contacting the confirming party. For example, when a confirming party responds by electronic mail, the auditor may telephone the confirming party to determine whether the confirming party did, in fact, send the response. When a response has been returned to the auditor indirectly (for example, because the confirming party incorrectly addressed it to the entity rather than to the auditor), the auditor may request the confirming party to respond in writing directly to the auditor.
On its own, an oral response to a confirmation request does not meet the definition of an external confirmation because it is not a direct written response to the auditor. However, upon obtaining an oral response to a confirmation request, the auditor may, depending on the circumstances, request the confirming party to respond in writing directly to the auditor. If no such response is received, in accordance with paragraph 12, the auditor seeks other audit evidence to support the information in the oral response.
A response to a confirmation request may contain restrictive language regarding its use. Such restrictions do not necessarily invalidate the reliability of the response as audit evidence.
Unreliable Responses (Ref: Para. 11)
When the auditor concludes that a response is unreliable, the auditor may need to revise the assessment of the risks of material misstatement at the assertion level and modify planned audit procedures accordingly, in accordance with ASA 315.[18] For example, an unreliable response may indicate a fraud risk factor that requires evaluation in accordance with ASA 240.[19]
Non-Responses (Ref: Para. 12)
Examples of alternative audit procedures the auditor may perform include:
For accounts receivable balances – examining specific subsequent cash receipts, shipping documentation, and sales near the period-end.
For accounts payable balances – examining subsequent cash disbursements or correspondence from third parties, and other records, such as goods received notes.
The nature and extent of alternative audit procedures are affected by the account and assertion in question. A non-response to a confirmation request may indicate a previously unidentified risk of material misstatement. In such situations, the auditor may need to revise the assessed risk of material misstatement at the assertion level, and modify planned audit procedures, in accordance with ASA 315.[20] For example, fewer responses to confirmation requests than anticipated, or a greater number of responses than anticipated, may indicate a previously unidentified fraud risk factor that requires evaluation in accordance with ASA 240.[21]
When a Response to a Positive Confirmation Request Is Necessary to Obtain Sufficient Appropriate Audit Evidence (Ref. Para. 13)
In certain circumstances, the auditor may identify an assessed risk of material misstatement at the assertion level for which a response to a positive confirmation request is necessary to obtain sufficient appropriate audit evidence. Such circumstances may include where:
The information available to corroborate management’s assertion(s) is only available outside the entity.
Specific fraud risk factors, such as the risk of management override of controls, or the risk of collusion which can involve employee(s) and/or management, prevent the auditor from relying on evidence from the entity.
Exceptions (Ref: Para. 14)
Exceptions noted in responses to confirmation requests may indicate misstatements or potential misstatements in the financial statements. When a misstatement is identified, the auditor is required by ASA 240 to evaluate whether such misstatement is indicative of fraud.[22] Exceptions may provide a guide to the quality of responses from similar confirming parties or for similar accounts. Exceptions also may indicate a deficiency, or deficiencies, in the entity’s internal control over financial reporting.
Some exceptions do not represent misstatements. For example, the auditor may conclude that differences in responses to confirmation requests are due to timing, measurement, or clerical errors in the external confirmation procedures.
Negative Confirmations (Ref: Para. 15)
The failure to receive a response to a negative confirmation request does not explicitly indicate receipt by the intended confirming party of the confirmation request or verification of the accuracy of the information contained in the request. Accordingly, a failure of a confirming party to respond to a negative confirmation request provides significantly less persuasive audit evidence than does a response to a positive confirmation request. Confirming parties also may be more likely to respond indicating their disagreement with a confirmation request when the information in the request is not in their favour, and less likely to respond otherwise. For example, holders of bank deposit accounts may be more likely to respond if they believe that the balance in their account is understated in the confirmation request, but may be less likely to respond when they believe the balance is overstated. Therefore, sending negative confirmation requests to holders of bank deposit accounts may be a useful procedure in considering whether such balances may be understated, but is unlikely to be effective if the auditor is seeking evidence regarding overstatement.
Evaluating the Evidence Obtained (Ref: Para. 16)
When evaluating the results of individual external confirmation requests, the auditor may categorise such results as follows:
A response by the appropriate confirming party indicating agreement with the information provided in the confirmation request, or providing requested information without exception;
A response deemed unreliable;
A non-response; or
A response indicating an exception.
The auditor’s evaluation, when taken into account with other audit procedures the auditor may have performed, may assist the auditor in concluding whether sufficient appropriate audit evidence has been obtained or whether further audit evidence is necessary, as required by ASA 330.[23]
Negative Confirmations (Ref: Para. 15)
Negative Confirmations (Ref: Para. 15)
Negative Confirmations (Ref: Para. 15)
The failure to receive a response to a negative confirmation request does not explicitly indicate receipt by the intended confirming party of the confirmation request or verification of the accuracy of the information contained in the request. Accordingly, a failure of a confirming party to respond to a negative confirmation request provides significantly less persuasive audit evidence than does a response to a positive confirmation request. Confirming parties also may be more likely to respond indicating their disagreement with a confirmation request when the information in the request is not in their favour, and less likely to respond otherwise. For example, holders of bank deposit accounts may be more likely to respond if they believe that the balance in their account is understated in the confirmation request, but may be less likely to respond when they believe the balance is overstated. Therefore, sending negative confirmation requests to holders of bank deposit accounts may be a useful procedure in considering whether such balances may be understated, but is unlikely to be effective if the auditor is seeking evidence regarding overstatement.
More sections below
Source text: opening excerpt
Sourced from the Federal Register of Legislation (legislation.gov.au), CC BY 4.0.
Obtaining a Copy of this Auditing Standa Obtaining a Copy of this Auditing Standard
Obtaining a Copy of this Auditing Standard
The most recently compiled versions of Auditing Standards, original Standards and amending Standards (see Compilation Details) are available on the AUASB website: www.auasb.gov.au
Contact Details Contact Details
Contact Details
Auditing and Assurance Standards BoardPodium Level 14, 530 Collins StreetMelbourne Victoria 3000AUSTRALIA
Phone: (03) 8080 7400E-mail: enquiries@auasb.gov.auPostal Address:PO Box 204Collins Street WestMelbourne Victoria 8007AUSTRALIA
Requests and enquiries concerning reproduction and rights for commercial purposes within Australia should be addressed to the Technical Director, Auditing and Assurance Standards Board, PO Box 204, Collins Street West, Melbourne, Victoria 8007 or sent to enquiries@auasb.gov.au. Otherwise, no part of this Auditing Standard may be reproduced, stored or transmitted in any form or by any means without the prior written permission of the AUASB except as permitted by law.
This Auditing Standard reproduces substantial parts of the corresponding International Standard on Auditing issued by the International Auditing and Assurance Standards Board (IAASB) and published by the International Federation of Accountants (IFAC), in the manner described in the statement on Conformity with International Standards on Auditing. The AUASB acknowledges that IFAC is the owner of copyright in the International Standard on Auditing incorporated in this Auditing Standard throughout the world.
All existing rights in this material are reserved outside Australia. Reproduction outside Australia in unaltered form (retaining this notice) is permitted for personal and non-commercial use only.
Further information and requests for authorisation to reproduce this Auditing Standard for commercial purposes outside Australia should be addressed to the Technical Director, Auditing and Assurance Standards Board, PO Box 204, Collins Street West, Melbourne, Victoria 8007 or sent to . Any decision to approve a request may also require the agreement of IFAC.
ASA 505 sets out how to treat results: auditors must obtain further evidence if doubts arise about the reliability of responses (Results, para.1-2; Ref: A11-A17), perform alternative procedures for every non-response (Results, para.3; Ref: A18-A19), and investigate exceptions to determine whether they indicate misstatements (Results, Exceptions, para.1; Ref: A21-A22). It draws a clear distinction between positive and negative confirmations: negative confirmations provide less persuasive evidence and must not be used as the sole substantive procedure for an assessed risk unless strict conditions are met (Requirements, Negative Confirmations, para.1; Ref: Para. A23).
The standard is to be read with ASA 101 Preamble, ASA 200 Overall Objectives, ASA 330, ASA 500, ASA 240, ASA 260, ASA 315 and ASA 705, and it conforms with International Standard on Auditing ISA 505 (Authority Statement; Conformity). ASA 505 was made by the AUASB pursuant to s 227B of the Australian Securities and Investments Commission Act 2001 and s 336 of the Corporations Act 2001 (Auditing Standard ASA 505 header). The compilation emphasises that compliance with ASA 505 enables compliance with ISA 505.
In short, ASA 505 prescribes an auditor-controlled process for external confirmations, requires enquiries and alternative procedures when management limits access, specifies how results and non-responses must be handled, and restricts reliance on negative confirmations except in narrowly defined circumstances. The standard does not create statutory penalties; it operates through audit methodology, reporting obligations, and links to other Auditing Standards governing opinion and governance communication (see Requirements and Authority Statement).
Main concepts
ASA 505 organises around a set of interlocking concepts: sources and reliability of audit evidence, control of confirmation procedures, the distinction between positive and negative confirmations, handling of management interference, and the auditor’s obligations when responses are unreliable or absent.
Reliability and source. ASA 505 starts from the general propositions in ASA 500 that audit evidence is more reliable when obtained from independent sources outside the entity, that evidence obtained directly by the auditor is more reliable than indirect evidence, and that documentary evidence is more reliable than non-documentary (Introduction, External Confirmation Procedures to Obtain Audit Evidence, para.1; see also ASA 500 references). That framework explains why external confirmations directed to the auditor are valued: they are both external and direct written responses (Definitions, para.1(i)).
Control over confirmation requests. The auditor "shall maintain control over external confirmation requests" (Requirements, External Confirmation Procedures, para.1). Control is decomposed into four duties: (a) determine the information to be confirmed (Ref: Para. A1), (b) select the appropriate confirming party (Ref: Para. A2), (c) design requests so they are properly addressed and contain return information for responses to be sent directly to the auditor (Ref: Para. A3-A6), and (d) send requests and follow-up where applicable (Ref: Para. A7). The standard emphasises that design decisions , for example whether to use "blank" confirmations that omit amounts , affect response rates and reliability (Application and Other Explanatory Material, Designing Confirmation Requests, A3-A4).
Positive versus negative confirmations. Definitions (para.1(ii)-(iii)) differentiate the two forms. A positive confirmation requires the confirming party to respond indicating agreement or disagreement or providing requested information. A negative confirmation asks for a reply only if the recipient disagrees. The standard states negative confirmations provide less persuasive evidence and limits their sole use to situations meeting four conditions: low assessed risk, large homogeneous population of small items, expected very low exception rate, and no circumstances encouraging recipients to ignore requests (Requirements, Negative Confirmations, para.1; Ref: Para. A23). The explanatory material explains behavioural asymmetry: recipients are more likely to reply when information is unfavourable to them (A23).
Non-responses and exceptions. A non-response is defined (Definitions, para.1(iv)). For each non-response, the auditor "shall perform alternative audit procedures" (Results, Non-Responses, para.1; Ref: Para A18-A19). An exception , a response indicating a difference , must be investigated to determine whether it indicates a misstatement (Results, Exceptions, para.1; Ref: Para. A21-A22). The standard provides examples of alternative procedures (A18) and notes that non-responses or a pattern of exceptions may require a revised risk assessment (A12, A19).
Management refusal and implications. If management refuses to allow the auditor to send confirmation requests, the auditor must enquire into reasons and seek evidence of validity, assess implications for risk and audit procedures, and perform alternative procedures (Requirements, Management’s Refusal, para.1(a)-(c); Ref: A8-A10). If refusal is unreasonable or alternative procedures do not provide evidence, the auditor must communicate with those charged with governance under ASA 260 and determine audit/opinion implications under ASA 705 (Requirements, para.2). The explanatory material characterises management refusal as a "limitation on the audit evidence" that may signal fraud risk (A8-A9).
Electronic responses and third-party coordinators. Responses received electronically carry specific reliability risks , origin, authorisation and alteration are harder to establish (Application, Reliability of Responses, A11.1-A11.3). The standard advises the auditor to consider secure electronic processes (encryption, digital signatures, website authenticity) to enhance reliability (A11.1). It also flags the risk where a confirming party uses a third-party coordinator, and directs the auditor to perform procedures to address whether responses come from the proper source and are authorised (A11.2).
Interaction with other Auditing Standards. ASA 505 situates external confirmations within broader audit requirements: ASA 330 (design of substantive procedures and the need for more persuasive evidence with higher assessed risk), ASA 500 (reliability considerations), ASA 240 (fraud response), ASA 260 (communications with governance), ASA 315 (risk assessment), and ASA 705 (audit opinion implications) (Introduction and Authority Statement). The standard’s compliance with ISA 505 is explicitly stated (Authority Statement, Conformity).
Categories of outcomes. When evaluating results the auditor may categorise them as agreement, unreliable response, non-response, or exception (Evaluating the Evidence Obtained, para.1(i)-(iv); Ref: Para A24-A25). The auditor must then decide whether further evidence is needed to meet ASA 330’s requirement for sufficient appropriate evidence (Evaluating the Evidence Obtained, para.2).
In sum, the main concepts are procedural control, a hierarchy of evidence reliability, targeted use of positive confirmations for higher-risk assertions, strict limits on sole reliance on negative confirmations, handling of management obstruction, and processes to resolve doubts about electronic or third-party-coordinated responses. All these concepts are framed as duties of the auditor with cross‑references to other AUASB Standards.
Who it affects
ASA 505 primarily affects three groups: auditors, the audited entity (management and those charged with governance), and confirming parties (third parties such as banks, customers, suppliers, and third‑party confirmation service providers). It also implicates standard setters and regulators through its legal footing.
Auditors. The standard imposes affirmative duties on auditors: to plan and maintain control of confirmation procedures (Requirements, External Confirmation Procedures, para.1), to evaluate and respond to management refusal (para.1-2), to verify reliability of responses (Results, para.1-2), and to perform alternative procedures for non-responses (Results, Non-Responses, para.1). Auditors decide what to confirm, who to ask, how to design requests, and whether responses are sufficiently reliable (Requirements, para.1(a)-(d); Ref: Para. A1-A7). The auditor also decides whether a response to a positive confirmation is necessary to obtain sufficient appropriate audit evidence, and, if not obtained, whether to modify the opinion in accordance with ASA 705 (Results, para.13; Ref: Para A20).
Management and those charged with governance. ASA 505 recognises management’s role and limited rights. Management may refuse to allow confirmation requests, but that refusal is treated as a limitation on audit evidence and the auditor must enquire into reasons and seek evidence as to validity and reasonableness (Requirements, Management’s Refusal, para.1(a); Ref: Para. A8). If refusal is unreasonable, the auditor must communicate with those charged with governance under ASA 260 (Requirements, para.2). Thus management’s actions can trigger escalations to governance, revision of risk assessments, and potential implications for the auditor’s opinion (Requirements, para.2; Ref: Para. A9-A10).
Confirming parties. Entities that are asked to confirm information are impacted operationally: they may be requested to reply directly to the auditor, possibly after being presented with management’s authorisation or encouragement (Application, Designing Confirmation Requests, A3-A4). Confirming parties that use third-party coordinators introduce additional verification responsibilities for auditors because the response may not be directly from the intended source (Application, Reliability of Responses, A11.2). Confirming parties may include restrictive language regarding use of responses, which the standard notes does not necessarily invalidate the evidence but is a factor for auditors to consider (A11.5).
Third-party confirmation service providers and electronic platforms. The explanatory material contemplates secure electronic confirmation processes, encryption, digital signatures, and website authentication as methods to mitigate electronic response risks (A11.1). Where responses are routed through a third-party coordinator, auditors must perform procedures to address origin, authorisation and transmission integrity (A11.2-A11.3). Therefore providers of confirmation services face indirect compliance and security expectations because their processes will affect auditors’ assessment of evidence reliability.
Regulators and AUASB. ASA 505 was made by the AUASB pursuant to s 227B of the ASIC Act and s 336 of the Corporations Act (Auditing Standard ASA 505 header). The AUASB sets the standard but enforcement falls primarily through audit oversight regimes and professional regulation rather than penalties specified in ASA 505 itself. The standard’s conformity with ISA 505 also implicates international standard‑setting and IFAC copyright (Authority Statement; COPYRIGHT), which affects reuse and reproduction of the standard text.
Costs and who bears them. The standard implies direct compliance costs for auditors: designing confirmation requests, verifying addresses, sending and following up, phoning confirming parties to verify electronic responses, and performing alternative procedures where responses are unreliable or absent (Requirements, External Confirmation Procedures, para.1; Application, Follow-Up on Confirmation Requests, A7; Reliability of Responses, A11-A13; Non-Responses, A18-A19). Confirming parties incur the cost of responding, and third-party coordinators must ensure secure transmission processes if they wish their responses to be treated as reliable evidence (A11.1-A11.3). Management faces the cost of cooperation and potential governance escalation if they restrict access (Management’s Refusal, para.1-2).
Who decides. The auditor decides whether to use confirmations, what form (positive or negative), what information to seek, and who to send requests to (Requirements, para.1). Management can refuse but must justify that decision and supply evidence if the auditor asks (Requirements, Management’s Refusal, para.1). Those charged with governance are the escalation point when refusal is judged unreasonable (Requirements, para.2).
In short, ASA 505 affects the audit firm in terms of procedures and resource allocation, the audited entity through obligations and escalation risks, confirming parties through the mechanics of responses and (where applicable) the security of electronic response channels, and regulatory/standard‑setting bodies through the legal and conformity framework under which the standard operates.
Key duties and rights
ASA 505 assigns specific duties to the auditor and sets out the limited rights and responsibilities of management and confirming parties. Below are the key obligations and entitlements as set out in the standard, with the relevant cross‑references.
Auditor duties , planning and control. The auditor shall maintain control over external confirmation requests (Requirements, External Confirmation Procedures, para.1). This control explicitly includes four tasks: determine the information to confirm (Ref: Para. A1), select the appropriate confirming party (Ref: Para. A2), design the confirmation requests so they are properly addressed and contain return instructions for the auditor (Ref: Para. A3-A6), and send the requests including follow-up when applicable (Ref: Para. A7). The auditor must design requests that address the relevant assertions and risks (Application, Designing Confirmation Requests, A3).
Auditor duties , response verification and follow-up. When the auditor identifies factors that cast doubt on the reliability of a response, the auditor shall obtain further audit evidence to resolve those doubts (Results, Reliability, para.1; Ref: A11-A16). For non-responses, the auditor shall perform alternative audit procedures (Results, Non-Responses, para.1; Ref: A18-A19). If a response to a positive confirmation is necessary and not obtained, the auditor shall determine implications for the audit and the auditor’s opinion under ASA 705 (Results, para.13; Ref: A20). The auditor must investigate exceptions to determine whether they are indicative of misstatements (Results, Exceptions, para.1; Ref: A21-A22). Auditors are permitted and encouraged to verify electronic responses by independent contact with the confirming party (A11.3).
Auditor duties , responding to management refusal. If management refuses to allow sending a confirmation request the auditor shall enquire about reasons and seek evidence for their validity and reasonableness, evaluate implications for risk assessment and other audit procedures, and perform alternative audit procedures designed to obtain relevant and reliable evidence (Requirements, Management’s Refusal, para.1(a)-(c); Ref: Para. A8-A10). Where refusal is unreasonable or alternative procedures do not yield sufficient evidence, the auditor must communicate with those charged with governance under ASA 260 and consider implications for the auditor’s opinion under ASA 705 (Requirements, para.2).
Auditor duties , limitation on negative confirmations. The auditor shall not use negative confirmations as the sole substantive audit procedure for an assessed risk of material misstatement at the assertion level unless all four conditions in Requirements, Negative Confirmations, para.1 are met (Ref: Para. A23). The auditor must assess whether a very low exception rate can be expected and whether recipients might disregard requests.
Rights and obligations of management. Management may refuse to allow the auditor to send a confirmation request, but the standard treats that refusal as a limitation on audit evidence that requires enquiry by the auditor and justification from management (Requirements, Management’s Refusal, para.1; Ref: Para. A8). Management can provide reasons such as ongoing negotiations or legal disputes; the auditor must seek evidence as to the validity and reasonableness of those reasons (A8).
Rights and constraints of confirming parties. Confirming parties are parties external to the entity who respond directly to the auditor (Definitions, para.1(i)). They have practical rights to determine the form and content of responses, including attaching restrictive language regarding use, which the standard notes does not necessarily invalidate the evidence but is a factor to consider (Application, Reliability, A11.5). Confirming parties may require management authorisation to respond; the standard recognises that some confirming parties will only respond if the request contains management’s authorisation (Application, Designing Confirmation Requests, A3).
Procedural rights for auditors. Auditors have the right to follow up non-responses, to re-verify addresses before re-sending (Application, Follow-Up on Confirmation Requests, A7), to request a confirming party to respond in writing after obtaining an oral response (A11.4), and to contact the confirming party by telephone to verify the source of an electronic response (A11.3). The auditor also has a duty to categorise and evaluate results (Evaluating the Evidence Obtained, para.1-2).
Cross-references to other Auditing Standards. When duties under ASA 505 point to implications for risk assessment and audit opinion, the auditor must apply ASA 315 (revising risk assessments), ASA 240 (fraud considerations), ASA 260 (communication with governance), ASA 330 (sufficiency of substantive procedures) and ASA 705 (implications for opinion) (Introduction, Requirements, various Refs).
Documentation obligations (implicit). The standard implicitly requires documentation by the auditor of the confirmation design, selection of confirming parties, follow-ups, reasons for management refusal and the auditor’s evaluation of reliability, although explicit documentation paragraphs are located in other AUASB Standards (ASA 101, ASA 200). The standard’s repeated remit to "obtain audit evidence" and to evaluate sufficiency (Evaluating the Evidence Obtained, para.2) carries an evidential documentation implication.
Limits on auditor duties. ASA 505 does not prescribe statutory sanctions or specify investigatory powers outside the audit. It prescribes procedural obligations within the audit process and links failure to obtain sufficient evidence to ASA 705 audit opinion outcomes and ASA 260 communication obligations (Requirements, para.2; Results, para.13). The standard does not itself impose civil or criminal penalties.
In practical terms the “duties” are prescriptive obligation words: "shall" for auditors’ actions and "shall not" for the negative confirmation limitation. Management has a conditional prerogative to refuse, but that right is constrained by the auditor’s obligation to test reasonableness and to escalate as necessary. Confirming parties have discretion in responding and may attach restrictions, but auditors must assess reliability and, if necessary, seek further corroboration.
Penalties and enforcement
ASA 505 itself is an Auditing Standard and does not create statutory penalties or criminal offences within its text. The document repeatedly frames obligations as "shall" requirements for auditors and prescribes follow-on actions (such as communication with those charged with governance under ASA 260 and determining audit opinion implications in accordance with ASA 705) where the auditor cannot obtain sufficient appropriate audit evidence (Requirements, Management’s Refusal, para.2; Results, para.13). The standard was made by the AUASB under s 227B of the Australian Securities and Investments Commission Act 2001 and s 336 of the Corporations Act 2001 (Auditing Standard ASA 505 header), which is the legal authority for the standard-setting power. However, ASA 505 does not itself set out enforcement mechanisms, sanction levels, or specific administrative penalties.
Enforcement mechanisms arise indirectly through:
Professional and regulatory oversight. Auditors’ compliance with AUASB Standards is monitored through professional bodies, audit quality reviews, and regulator oversight; failure to follow AUASB Standards can be the basis for regulatory action or professional discipline, but such mechanisms are outside the text of ASA 505. The standard points to other Auditing Standards (ASA 260, ASA 705) that set procedural consequences within the audit process for limitations on evidence, including communicating to governance bodies and considering modifications to the auditor’s opinion.
Audit opinion outcomes. ASA 505 explicitly links the failure to obtain a required external confirmation (for example, when a response to a positive confirmation is necessary and not obtained) to implications for the audit and the auditor’s opinion under ASA 705 (Results, para.13; Ref: Para A20). Practically, this means the auditor may have to issue a modified opinion or a disclaimer if sufficient appropriate evidence cannot be obtained. While not a legal penalty, a modified opinion has reputational and contractual consequences for both auditor and auditee.
Communication duties. If management unreasonably refuses confirmation requests and alternative procedures do not provide reliable evidence, auditors "shall communicate with those charged with governance in accordance with ASA 260" (Requirements, Management’s Refusal, para.2). Failure to make required communications could be cited in professional review or regulator actions.
Contractual and legal exposure. Although ASA 505 does not specify civil liability, auditors who fail to follow standards run the risk of adverse findings in civil proceedings or disciplinary reviews; such outcomes depend on external legal or regulatory processes not defined in the standard.
What ASA 505 does specify are consequence pathways within the audit structure: the auditor must undertake further procedures, re-assess risks under ASA 315, consider fraud under ASA 240, communicate under ASA 260, and determine whether the opinion must be modified under ASA 705. These are procedural enforcement levers that translate non‑compliance or limitations into practical audit outcomes (Requirements, various Refs; Results, para.13).
The standard’s Authority Statement also clarifies conformity with ISA 505 and notes that compliance with ASA 505 enables compliance with ISA 505. The standard’s publication and copyright notice (COPYRIGHT) set conditions on reproduction and use, including that reproduction for commercial purposes requires AUASB and possibly IFAC permission, but these are intellectual property restrictions rather than penalties for audit process non-compliance.
In short, ASA 505 itself contains no statutory fines or sanctions; enforcement is exercised through audit quality control systems, professional regulation, the practical consequence of modified audit opinions, and intellectual property controls over the standard text. The standard instructs auditors on procedural remedies and escalation paths where evidence is limited or unreliable, thereby shaping the practical enforcement of audit quality rather than specifying statutory penalties.
How it interacts with other laws
ASA 505 is part of the AUASB suite and is explicitly to be read in conjunction with other AUASB Standards and the Acts under which the AUASB derives authority. The Authority Statement mandates reading ASA 505 with ASA 101 Preamble to AUASB Standards and ASA 200 Overall Objectives, and the Introduction and cross‑references integrate ASA 505 with ASA 330, ASA 500, ASA 240, ASA 315, ASA 260 and ASA 705 (Authority Statement; Introduction; Requirements; Results). The standard also states that it was made pursuant to s 227B of the Australian Securities and Investments Commission Act 2001 and s 336 of the Corporations Act 2001 (Auditing Standard ASA 505 header), which locates its legal authorisation.
Specific interactions and their mechanics:
ASA 101 and ASA 200. ASA 505 should be understood and applied in the context of the AUASB’s preamble and the overall objectives and conduct of an audit (Authority Statement). Those Standards set out interpretive principles, obligations to obtain sufficient appropriate evidence, and auditor responsibilities; ASA 505 provides specific procedures for external confirmations within that framework.
ASA 330 (Responses to assessed risk and substantive procedures). ASA 505 is explicitly linked to ASA 330: ASA 330 requires substantive procedures for each material class of transactions and account balance irrespective of assessed risk and asks auditors to consider whether external confirmations are necessary as substantive procedures (Introduction, para.1; see also Requirements). Practically, an auditor’s decision to use confirmations flows from ASA 330’s risk assessment and response design requirements; if ASA 330 requires more persuasive evidence, that may push the auditor toward positive confirmations (Introduction).
ASA 500 (Reliability of audit evidence). ASA 505 adopts ASA 500’s generalisations that external, direct and documentary evidence is more reliable (Introduction, para.1). ASA 505 uses those principles to explain why confirmations are relatively persuasive and to identify when reliability may be compromised (e.g., electronic transmission risks) and must be corroborated (Results, A11-A16).
ASA 240 (Fraud considerations). The standard instructs auditors to design confirmation requests to address fraud risks when appropriate and to evaluate whether management’s refusal signals fraud risk factors (Introduction; Management’s Refusal, para.1-2; Ref: Para. A8-A9). The auditor must consider ASA 240 when exceptions or unreliable responses could indicate fraud.
ASA 260 (Communication with those charged with governance). ASA 505 requires communication with those charged with governance if management’s refusal to permit confirmations is unreasonable or if alternative procedures do not produce sufficient evidence (Requirements, para.2). Thus ASA 505 uses ASA 260 as the escalation mechanism for unresolved limitations.
ASA 315 (Risk assessment) and ASA 705 (Modifications to opinion). ASA 505 instructs auditors to revise risk assessments if confirmation results indicate risks of material misstatement (Results, Unreliable Responses, para.1). If the auditor cannot obtain necessary confirmations and alternative procedures are insufficient, ASA 705 governs the implications for the audit report (Results, para.13; Ref: Para A20).
ASA 502 (Litigation and claims). The scope clause of ASA 505 notes that enquiries about litigation and claims are dealt with in ASA 502 (Scope, para.1), meaning auditors should not use ASA 505 as the primary standard for confirmation procedures related to litigation issues.
Corporations Act and ASIC Act. ASA 505 was made under s 227B of the ASIC Act and s 336 of the Corporations Act (Auditing Standard ASA 505 header). These statutory provisions are the AUASB’s powers to issue auditing standards. The interplay is that auditors performing audits under the Corporations Act must follow AUASB Standards, including ASA 505, so ASA 505 affects statutory audits through the standard-setting mechanism rather than by altering the Corporations Act text itself.
ISA 505 and international conformity. ASA 505 conforms with ISA 505 and states that compliance with ASA 505 enables compliance with ISA 505 (Authority Statement). The standard indicates that paragraphs added by AUASB that do not appear in ISA are prefixed "Aus" (Authority Statement). This matters for multinational firms and cross‑jurisdiction audits where ISA conformity is relevant.
Intellectual property and IFAC. The COPYRIGHT section notes the Auditing Standard reproduces substantial parts of ISA 505 and acknowledges IFAC copyright, which affects reproduction rights (COPYRIGHT). This is interaction with international standard‑setting and IP law rather than audit procedure.
Practical effect of these interactions. ASA 505 does not stand alone. It operates as the external confirmation component of the audit methodology mandated by ASA 101 and ASA 200, feeds into ASA 330’s evidence sufficiency calculus, uses ASA 500’s reliability criteria, and triggers ASA 240/ASA 315/ASA 260/ASA 705 procedures when confirmations raise fraud concerns, risk reassessment needs, governance notification requirements, or reporting consequences. For audits under the Corporations Act, compliance with ASA 505 is part of the auditor’s compliance obligations because the AUASB made the standard under statutory authority.
Amendment history
The compilation details in the standard set out the amendment history and operative dates for the relevant AUASB instruments that have altered ASA 505. The compilation was prepared on 10 November 2021 and takes into account amendments up to and including 3 March 2020. The compilation document expressly states that it is a representation of ASA 505 as amended and is not a separate Auditing Standard (Compilation Details).
Table of Standards (Compilation Details) records:
ASA 505 [A], made 27 October 2009, operative for financial reporting periods commencing on or after 1 January 2010 (Federal Register registration F2009L04088, 12 November 2009).
ASA 2018-1 [B], made 5 December 2018, operative for financial reporting periods commencing on or after 15 December 2019, with early adoption permitted.
ASA 2020-1 [C], made 3 March 2020, operative for financial reporting periods commencing on or after 15 December 2021.
The Table of Amendments lists specific paragraphs affected by those amending Standards:
The compiled standard identifies the full paragraph range Aus 0.1 to A25 as constituting ASA 505 as amended (Authority Statement). Operative date for the body of the standard is Aus 0.3 (operative for periods commencing on or after 1 January 2010), with a note to see Compilation Details for operative dates of paragraphs changed or added by amending Standards (Aus 0.3).
The compilation emphasises that paragraphs added by the AUASB that are not in the ISA are identified with the prefix "Aus" (Authority Statement). That label signals where the AUASB introduced Australian‑specific guidance or modifications.
In short, ASA 505 originated in October 2009 (operative 2010), with substantive amending Standards in 2018 and 2020 reflected in the compilation as at 3 March 2020 and prepared on 10 November 2021. The compilation's Table of Amendments shows the targeted paragraphs altered by those amending Standards. Users must consult Compilation Details to determine operative dates for specific amended paragraphs, and observe which paragraphs are AUASB additions labelled "Aus".
Litigation history
The text of ASA 505 as provided contains no references to litigation, case law or judicial interpretation. The standard does not cite or rely upon court decisions; instead it cross‑references other Auditing Standards (ASA 101, ASA 200, ASA 330, ASA 500, ASA 240, ASA 260, ASA 315, ASA 705, ASA 502) and cites conformity with ISA 505 (Authority Statement; Introduction). The standard’s explanatory material contains examples, procedural guidance, and references to audit risks and fraud considerations, but it does not record any litigation history, regulatory enforcement actions, or judicial rulings interpreting ASA 505.
Therefore, based solely on the provided text, there is no litigation history contained within ASA 505. Practitioners should note that the absence of litigation citations in the standard does not imply there are no legal cases involving confirmation procedures; it only reflects that the standard itself does not discuss or catalogue such cases. All case law, regulatory enforcement decisions, or litigation that might interpret or rely upon ASA 505 would need to be sourced from external legal and regulatory databases, which are outside this document.
Gotchas
ASA 505 contains several practical pitfalls and implementation risks that auditors and audit clients should plan for. Each “gotcha” below is grounded in the standard’s text and explanatory material.
Management refusal is a red flag, not merely an administrative inconvenience. When management refuses to allow confirmations, ASA 505 treats the refusal as a "limitation on the audit evidence" and requires the auditor to seek documentary reasons and evaluate whether the refusal is reasonable (Management’s Refusal, para.1; Ref: A8). The explanatory text warns management may be attempting to deny access to evidence that could reveal fraud or error (A8). If refusal is judged unreasonable or alternative procedures are insufficient, the auditor must escalate under ASA 260 and consider opinion implications under ASA 705 (Requirements, para.2). Practical risk: management refusal can rapidly change the audit’s risk profile and require significant additional work.
Non-responses require alternative procedures for each item. A non-response is defined and for each non-response the auditor "shall perform alternative audit procedures" (Definitions, para.1(iv); Results, Non-Responses, para.1; Ref: A18-A19). Practically, that can be time‑consuming: examples include examining subsequent cash receipts for accounts receivable or correspondence for accounts payable (A18). Auditors should budget time and resources for follow-up and alternative evidence gathering.
Electronic responses and third-party coordinators create authentication burdens. Responses received electronically (fax, email) are riskier because origin and authority are harder to establish and alterations harder to detect (Application, Reliability, A11.1). If a confirming party uses a third-party coordinator, the auditor must address risks that the response may not be from the proper source or authorised and that transmission integrity may be compromised (A11.2). Mitigation requires additional procedures (telephone verification, secure electronic processes, digital signatures) and adds operational cost and complexity.
“Blank” confirmations reduce reliability trade-offs and can lower response rates. A "blank" positive confirmation , one that requires the confirmer to fill in an amount rather than confirm a management-provided amount , can reduce the risk that a confirming party replies without verifying the information (Designing Confirmation Requests, A3.1). However, the same paragraph warns that blank confirmations may reduce response rates because they demand more effort from recipients. Auditors must trade off higher reliability per response against lower response rates and increased follow-up.
Negative confirmations are weak evidence and constrained in use. Negative confirmations provide substantially less persuasive evidence than positive confirmations and must not be used as the sole substantive procedure unless all four strict conditions are met: low assessed risk, large number of small homogeneous items, very low expected exception rate, and no circumstances to cause recipients to disregard requests (Requirements, Negative Confirmations, para.1; Ref: Para. A23). Using negative confirmations improperly risks an inadequate audit evidence base.
Oral responses do not meet the definition of an external confirmation. The standard states an oral response on its own does not constitute an external confirmation because it is not a direct written response (Application, Reliability, A11.4). If an oral response is obtained, the auditor should request written confirmation; absent that, the auditor must seek other corroborating evidence (A11.4, A12). Auditors should avoid treating phone assurances as substitutes for written confirmations.
Restrictions on use in responses do not automatically invalidate the evidence but complicate reliance. A confirming party may include restrictive language regarding use of its response; the standard notes such restrictions do not necessarily invalidate the response as audit evidence (A11.5). However, auditors must still consider whether restrictions affect the sufficiency or utility of the evidence.
Response reliability doubts require further evidence and may alter the audit plan. If the auditor identifies indicators that a response may not be reliable (received indirectly, appears not to come from the intended party), ASA 505 requires the auditor to obtain further evidence to resolve doubts (Results, Reliability, para.1; Ref: A11-A16). This may trigger changes in nature, timing and extent of other procedures per ASA 315 and ASA 330, and may lead to fraud evaluation per ASA 240 (A11, A17).
Positive confirmations can be "necessary" evidence; failure to obtain them can force a modified opinion. ASA 505 contemplates circumstances where a response to a positive confirmation is necessary to obtain sufficient appropriate evidence, for example where corroboration is only available from outside the entity or where fraud risk factors preclude reliance on entity evidence (Results, When Necessary, para.1; Ref: A20). If such confirmation is not obtained, ASA 705 considerations apply , a potential modified opinion or disclaimer. Auditors must identify these situations early.
Address validity and return-to-auditor controls matter. The auditor must determine that requests are properly addressed and contain return information for responses to be sent directly to the auditor (Requirements, para.1(c); Ref: Para. A3-A6). The explanatory material notes determining that requests are properly addressed includes testing the validity of some or all addresses before sending (A3.2). Failure to verify addresses can result in misdirected confirmations and false non-response findings.
Patterns of unexpected responses can indicate broader control deficiencies. ASA 505 notes that fewer responses than anticipated, or a greater number than anticipated, may indicate previously unidentified fraud risk factors (Application, Non-Responses, A12). Similarly, exceptions may indicate deficiencies in internal control over financial reporting (A21). Auditors should watch for patterns rather than treat each confirmation in isolation.
Administrative and cost burdens are non-trivial. The standard requires follow-ups, verification contacts, and alternative procedures which consume auditor time and client cooperation. Confirming parties also bear the burden of responding and possibly using secure electronic channels. Budgeting both time and costs is essential.
These "gotchas" are not theoretical; they are direct consequences of the standard’s procedural prescriptions and explanatory commentary. The standard anticipates many of these risks and prescribes responsive steps, but the operational and cost impacts fall to auditors, confirming parties, and management.
How to comply
Compliance with ASA 505 requires integrating the standard’s procedural prescriptions into audit planning, execution and documentation. The steps below paraphrase and sequence the standard’s requirements and explanatory material to create a practical compliance checklist. Each step cites the relevant paragraphs in the standard.
Confirm applicability and legal framework. Verify that ASA 505 applies to the engagement (Aus 0.1-Aus 0.2), and be aware that ASA 505 is to be read with ASA 101 and ASA 200 (Authority Statement). Note operative date (Aus 0.3) and ensure you are working with the compiled text as amended.
Risk-based decision to use confirmations. As part of the risk assessment under ASA 315 and response design under ASA 330, decide whether external confirmations are appropriate and necessary for particular assertions and account balances (Introduction; ASA 330 cross-references). Consider whether the evidence needed is more persuasive when obtained externally and directly (Introduction, para.1).
Determine the information to be confirmed. Identify specific account balances, transaction elements, contract terms or absence of conditions (e.g., side agreements) for confirmation (Requirements, para.1(a); Application, Determining the Information to Be Confirmed, A1). Tailor the content to the assertion and risk (A3).
Select appropriate confirming parties. Choose parties the auditor believes are knowledgeable about the information sought, for example appropriate officials at financial institutions for bank balances (Requirements, para.1(b); Application, Selecting the Appropriate Confirming Party, A2). Document the rationale for selecting or excluding particular confirmers.
Design confirmation requests. Prepare positive or negative confirmation requests depending on risk and expected response reliability (Definitions; Requirements, para.1(c); Application, Designing Confirmation Requests, A3-A4). Ensure:
Requests are addressed to the appropriate person within the confirming party.
Requests contain explicit return instructions for responses to be sent directly to the auditor.
The layout addresses the assertions and identified fraud risks.
Consider whether to use "blank" confirmations (trade-off: reliability per response versus likely lower response rate).
If management authorisation may be required by the confirming party, plan to include it if necessary (A3).
Verify addresses and mode of delivery. Test the validity of addresses for a sample of confirmations before sending (A3.2). Decide on paper, facsimile or secure electronic channels and document why the chosen method is appropriate. For electronic methods, ensure secure processes (encryption, digital signatures, website authentication) are available or plan corroborating steps if not (A11.1).
Maintain control over sending and follow-up. Send requests and ensure control over the process (Requirements, para.1(d); A7). Re-verify addresses if follow-up is required. Track sent requests, responses, non-responses and any returned undelivered mail.
Plan for follow-ups and verification of electronic responses. Include follow-up procedures for non-responses and procedures to verify electronic responses’ origin and authority, including telephone verification with the confirming party if necessary (A11.3; A7). If a confirming party uses a third-party coordinator, perform additional procedures to confirm source and authorisation (A11.2).
Handle management refusal. If management refuses permission, immediately:
Enquire into reasons and obtain evidence for their validity and reasonableness (Management’s Refusal, para.1(a); A8).
Evaluate implications for risk assessment and planned procedures (para.1(b); A9).
Perform alternative procedures appropriate for the specific account and assertion (para.1(c); A10; see A18-A19 for examples).
If refusal is unreasonable or alternatives do not provide reliable evidence, communicate with those charged with governance under ASA 260 and consider implications under ASA 705 (Requirements, para.2).
Deal with non-responses and exceptions. For each non-response, perform alternative audit procedures (Results, Non-Responses, para.1; A18-A19). For each exception, investigate to determine whether it indicates a misstatement and consider whether it shows internal control deficiencies or fraud risk (Results, Exceptions, para.1; A21-A22). Document all steps and conclusions.
Treat negative confirmations cautiously. Use negative confirmations only where all four conditions in Requirements, Negative Confirmations, para.1 are present (low risk, large homogeneous population, very low expected exception rate, no circumstances causing recipients to disregard requests). Otherwise use positive confirmations or alternative substantive procedures (A23).
Evaluate results and sufficiency of evidence. Categorise results as agreement, unreliable response, non-response, or exception (Evaluating the Evidence Obtained, para.1(i)-(iv)). Decide whether the collective results, in conjunction with other audit evidence, are sufficient for the assertion under ASA 330. If not, perform additional procedures (Evaluating the Evidence Obtained, para.2).
Consider fraud implications. If confirmations or refusals indicate fraud risk factors (e.g., management overriding controls, collusion), design confirmation requests and supplementary procedures to address fraud under ASA 240 (Introduction; A13-A14; A20).
Document thoroughly. Maintain records of the confirmation design, party selection rationale, requests sent (and addresses), follow-ups, responses received (including their form and any restrictive language), investigations into reliability, alternative procedures performed, communications with governance, and conclusions on sufficiency of evidence. Documentation supports audit conclusions on sufficiency and provides an evidentiary trail should ASA 260/ASA 705 escalation be required.
Integrate with other Standards. Ensure actions align with ASA 101 (application and interpretation of AUASB Standards), ASA 200 (overall objectives), ASA 315 (risk assessment revisions), ASA 330 (substantive procedure design), ASA 500 (criteria for evidence reliability), ASA 240 (fraud), ASA 260 (communication), and ASA 705 (audit opinion consequences). The Authority Statement and Introduction emphasise these links.
Address IP and publication constraints. When reproducing or using the standard text commercially, observe the COPYRIGHT notice and AUASB/IFAC permissions (COPYRIGHT).
Practical checklist summary (minimum actions):
Identify assertions where external confirmations add value (e.g., bank balances, receivables, liabilities).
Decide positive vs negative confirmations based on risk and conditions.
Draft confirmations to return directly to the auditor; test sample addresses before sending.
Use secure electronic processes or plan verification for electronic responses.
Log and follow up non-responses; perform specified alternative procedures for each.
Investigate exceptions, consider fraud indicators, revise risk assessments as needed.
Escalate unreasonable refusals to governance and consider opinion implications under ASA 705.
Archive documentation of all above steps and the auditor’s evaluation.
Following these steps aligns practical audit execution with the prescriptive "shall" language of ASA 505 and its explanatory material. Compliance requires both procedural rigour and resourcing for potential follow-up and alternative procedures, particularly where confirmations are central to the evidence base for significant assertions.
Evaluating the Evidence Obtained...........................................A24-A25
COMPILATION DETAILS COMPILATION DETAILS
Obtaining a Copy of this Auditing Standard
The most recently compiled versions of Auditing Standards, original Standards and amending Standards (see Compilation Details) are available on the AUASB website: www.auasb.gov.au
Contact Details
Auditing and Assurance Standards BoardPodium Level 14, 530 Collins StreetMelbourne Victoria 3000AUSTRALIA
Phone: (03) 8080 7400E-mail: enquiries@auasb.gov.auPostal Address:PO Box 204Collins Street WestMelbourne Victoria 8007AUSTRALIA
Requests and enquiries concerning reproduction and rights for commercial purposes within Australia should be addressed to the Technical Director, Auditing and Assurance Standards Board, PO Box 204, Collins Street West, Melbourne, Victoria 8007 or sent to enquiries@auasb.gov.au. Otherwise, no part of this Auditing Standard may be reproduced, stored or transmitted in any form or by any means without the prior written permission of the AUASB except as permitted by law.
This Auditing Standard reproduces substantial parts of the corresponding International Standard on Auditing issued by the International Auditing and Assurance Standards Board (IAASB) and published by the International Federation of Accountants (IFAC), in the manner described in the statement on Conformity with International Standards on Auditing. The AUASB acknowledges that IFAC is the owner of copyright in the International Standard on Auditing incorporated in this Auditing Standard throughout the world.
All existing rights in this material are reserved outside Australia. Reproduction outside Australia in unaltered form (retaining this notice) is permitted for personal and non-commercial use only.
Further information and requests for authorisation to reproduce this Auditing Standard for commercial purposes outside Australia should be addressed to the Technical Director, Auditing and Assurance Standards Board, PO Box 204, Collins Street West, Melbourne, Victoria 8007 or sent to enquiries@auasb.gov.au. Any decision to approve a request may also require the agreement of IFAC.
ISSN 1833-4393
CONTENTS
COMPILATION DETAILS
AUTHORITY STATEMENT
CONFORMITY WITH INTERNATIONAL STANDARDS ON AUDITING
Evaluating the Evidence Obtained...........................................A24-A25
COMPILATION DETAILS
Auditing Standard ASA 505 External Confirmations (as Amended)
This compilation takes into account amendments made up to and including 3 March 2020 and was prepared on 10 November 2021 by the Auditing and Assurance Standards Board (AUASB).
This compilation is not a separate Auditing Standard made by the AUASB. Instead, it is a representation of ASA 505 (October 2009) as amended by other Auditing Standards which are listed in the Table below.
Table of Standards
Standard
Date made
Operative Date
ASA 505 [A]
27 October 2009
Financial reporting periods commencing on or after 1 January 2010.
ASA 2018-1 [B]
5 December 2018
Financial reporting periods commencing on or after 15 December 2019, with early adoption permitted[*].
ASA 2020-1 [C]
3 March 2020
Financial reporting periods commencing on or after 15 December 2021[#]
[A] Federal Register of Legislation – registration number F2009L04088, 12 November 2009
[B] Federal Register of Legislation – registration number F2019L00016, 3 January 2019
[C] Federal Register of Legislation – registration number F2020L00252, 13 March 2020
Table of Amendments
Paragraph affected
How affected
By … [paragraph]
2Footnote 4
Amended
ASA 2018-1 [50]
2Footnote 5
Amended
ASA 2018-1 [51]
3Footnote 11
Amended
ASA 2018-1 [52]
A9Footnote 14
Amended
ASA 2020-1 [130]
A17Footnote 18
Amended
ASA 2020-1 [131]
A19Footnote 20
Amended
ASA 2020-1 [132]
AUTHORITY STATEMENT
Auditing Standard ASA 505 External Confirmations (as amended to 3 March 2020) is set out in paragraphs Aus 0.1 to A25.
This Auditing Standard is to be read in conjunction with ASA 101 Preamble to AUASB Standards, which sets out how AUASB Standards are to be understood, interpreted and applied. This Auditing Standard is to be read also in conjunction with ASA 200 Overall Objectives of the Independent Auditor and the Conduct of an Audit in Accordance with Australian Auditing Standards.
Conformity with International Standards on Auditing
This Auditing Standard conforms with International Standard on Auditing ISA 505 External Confirmations, issued by the International Auditing and Assurance Standards Board (IAASB), an independent standard‑setting board of the International Federation of Accountants (IFAC).
Paragraphs that have been added to this Auditing Standard (and do not appear in the text of the equivalent ISA) are identified with the prefix “Aus”.
Compliance with this Auditing Standard enables compliance with ISA 505.
Auditing Standard ASA 505 External Confi Auditing Standard ASA 505 External Confirmations (as Amended)
Auditing Standard ASA 505 External Confirmations (as Amended)
This compilation takes into account amendments made up to and including 3 March 2020 and was prepared on 10 November 2021 by the Auditing and Assurance Standards Board (AUASB).
This compilation is not a separate Auditing Standard made by the AUASB. Instead, it is a representation of ASA 505 (October 2009) as amended by other Auditing Standards which are listed in the Table below.
Table of Standards Table of Standards
Table of Standards
Standard
Date made
Operative Date
ASA 505 [A]
27 October 2009
Financial reporting periods commencing on or after 1 January 2010.
ASA 2018-1 [B]
5 December 2018
Financial reporting periods commencing on or after 15 December 2019, with early adoption permitted[*].
ASA 2020-1 [C]
3 March 2020
Financial reporting periods commencing on or after 15 December 2021[#]
[A] Federal Register of Legislation – registration number F2009L04088, 12 November 2009
[B] Federal Register of Legislation – registration number F2019L00016, 3 January 2019
[C] Federal Register of Legislation – registration number F2020L00252, 13 March 2020
Table of Amendments Table of Amendments
Table of Amendments
Paragraph affected
How affected
By … [paragraph]
2Footnote 4
Amended
ASA 2018-1 [50]
2Footnote 5
Amended
ASA 2018-1 [51]
3Footnote 11
Amended
ASA 2018-1 [52]
A9Footnote 14
Amended
ASA 2020-1 [130]
A17Footnote 18
Amended
ASA 2020-1 [131]
A19Footnote 20
Amended
ASA 2020-1 [132]
AUTHORITY STATEMENT
Auditing Standard ASA 505 External Confirmations (as amended to 3 March 2020) is set out in paragraphs Aus 0.1 to A25.
This Auditing Standard is to be read in conjunction with ASA 101 Preamble to AUASB Standards, which sets out how AUASB Standards are to be understood, interpreted and applied. This Auditing Standard is to be read also in conjunction with ASA 200 Overall Objectives of the Independent Auditor and the Conduct of an Audit in Accordance with Australian Auditing Standards.
Conformity with International Standards on Auditing
This Auditing Standard conforms with International Standard on Auditing ISA 505 External Confirmations, issued by the International Auditing and Assurance Standards Board (IAASB), an independent standard‑setting board of the International Federation of Accountants (IFAC).
Paragraphs that have been added to this Auditing Standard (and do not appear in the text of the equivalent ISA) are identified with the prefix “Aus”.
Compliance with this Auditing Standard enables compliance with ISA 505.
AUTHORITY STATEMENT AUTHORITY STATEMENT
AUTHORITY STATEMENT
Auditing Standard ASA 505 External Confirmations (as amended to 3 March 2020) is set out in paragraphs Aus 0.1 to A25.
This Auditing Standard is to be read in conjunction with ASA 101 Preamble to AUASB Standards, which sets out how AUASB Standards are to be understood, interpreted and applied. This Auditing Standard is to be read also in conjunction with ASA 200 Overall Objectives of the Independent Auditor and the Conduct of an Audit in Accordance with Australian Auditing Standards.
Conformity with International Standards Conformity with Interna
This is an opening excerpt, not the complete document.