What are written representations?
ISA 580.9 requires the auditor to request written representations from management with appropriate responsibilities for the financial statements. In practice, the engagement team drafts a letter and management reviews it before a signatory with sufficient authority signs. The letter goes out before the auditor's report date.
The letter covers two categories. ISA 580.10 and 580.11 set out the mandatory representations: that management has fulfilled its responsibility for preparing the financial statements in accordance with the applicable framework, and that it has provided the auditor with all relevant information and access. Beyond those, ISA 580.13 requires the auditor to request any additional representations necessary to support other audit evidence obtained during the engagement. These additional representations are where the letter earns its value. A boilerplate letter with only the mandatory items fails the intent of paragraph 13.
ISA 580.14 requires the letter to be dated as near as practicable to, but not after, the date of the auditor's report. This date alignment matters because the representations cover management's assertions through to the opinion date, not just the balance sheet date.
Key Points
- The auditor must obtain written representations on every engagement; omitting them triggers a scope limitation.
- Representations confirm management's responsibility for the financial statements and completeness of information provided.
- A refusal to sign the representation letter requires the auditor to consider the effect on the opinion.
- Representations supplement other audit evidence but never replace substantive testing or external confirmations.
Why it matters in practice
The FRC has repeatedly flagged representation letters that use generic template language without engagement-specific tailoring in its annual Audit Quality Inspection reports. ISA 580.13 requires representations that support other audit evidence obtained during the engagement. A letter that does not reference the specific estimates and risk areas identified on that engagement fails this requirement.
Teams frequently date the representation letter days or weeks before the auditor's report date. ISA 580.14 requires the letter to be dated as near as practicable to, but not after, the date of the auditor's report. A two-week gap between the letter date and report date creates a coverage hole that reviewers catch immediately.
Worked example: Schreiber Maschinenbau GmbH
Client: German manufacturing subsidiary, FY2024, revenue €28M, HGB statutory accounts with IFRS consolidation package. The engagement team prepares the letter using ISA 580.10 and 580.11 as the starting point. Because Schreiber is a subsidiary reporting under both HGB and IFRS, the letter addresses the Geschäftsführer and covers both sets of financial statements.
During fieldwork, the team identified a €1.2M provision for a product liability claim and a related party loan of €3.5M to the parent company. The team adds representations confirming the completeness of legal claims disclosed and the completeness of related party transactions (per ISA 550.26). Each additional representation is cross-referenced to the underlying working paper.
The Geschäftsführer confirms authority to sign. The letter is dated 14 March 2025, matching the auditor's report date per ISA 580.14. The signed original is scanned and filed, and the engagement partner reviews the letter against the list of matters identified during the audit that required additional representations.
Written representations vs external confirmation
Written representations come from management inside the entity. External confirmations come from independent third parties outside it. The evidential weight differs accordingly. ISA 580.4 is clear that written representations are necessary audit evidence but do not, on their own, provide sufficient appropriate evidence for any matter they address. External confirmations (governed by ISA 505) carry higher evidential value because the respondent is independent of the entity.
On engagements where the auditor relies on a management representation for a balance that could be confirmed externally (bank balances, receivables, legal claims, inventory held by third parties), the question is straightforward: why wasn't external confirmation performed? If the answer is convenience rather than impracticability, the file has a gap.
Key standard references
- ISA 580.9: Requires the auditor to request written representations from management with appropriate responsibilities.
- ISA 580.10–11: Mandatory representations on management's responsibility for the financial statements and completeness of information provided.
- ISA 580.13: Requires additional representations necessary to support other audit evidence obtained during the engagement.
- ISA 580.14: Requires the letter to be dated as near as practicable to, but not after, the date of the auditor's report.
- ISA 580.4: Written representations are necessary but do not on their own provide sufficient appropriate evidence.
Related terms
Related reading
Frequently asked questions
When are written representations required?
Written representations are required on every audit engagement. ISA 580.9 requires the auditor to request representations from management with appropriate responsibilities for the financial statements. The letter must cover the mandatory representations under ISA 580.10 and 580.11 (management's responsibility for the financial statements and completeness of information provided) plus any additional representations necessary under ISA 580.13 to support other audit evidence obtained. Omitting the letter triggers a scope limitation.
How should the representation letter be dated?
ISA 580.14 requires the letter to be dated as near as practicable to, but not after, the date of the auditor's report. This means the representations cover management's assertions through to the opinion date, not just the balance sheet date. A gap of days or weeks between the letter date and the report date creates a coverage hole that reviewers will flag.