SA 580 requires the auditor to obtain written representations from management, and where relevant those charged with governance, confirming matters relevant to the audit — most importantly, that management has fulfilled its responsibility for the financial statements and has provided the auditor with all relevant information and access it agreed to in the engagement letter. The letter is dated as close as practical to, but not after, the date of the auditor's report, and it comes at the end of the process specifically because it is a confirmation of representations already made throughout the audit, never a source of new evidence that substitutes for a procedure that should have been performed.
What the letter has to cover, at minimum
- Management's acknowledgment of its responsibility for the preparation of the financial statements in accordance with the applicable framework.
- A statement that management has provided the auditor with all information agreed in the terms of the engagement, and allowed unrestricted access as agreed.
- That all transactions have been recorded and reflected in the financial statements.
- Any matters specific to the engagement that SA 580 or other Standards on Auditing specifically require — for example, representations on related party disclosures, litigation and claims, or the going-concern assessment where those are relevant.
Regulatory requirement
A written representation is required audit evidence, but SA 580 is explicit that it does not, by itself, provide sufficient appropriate evidence about any of the matters it addresses — it supplements other evidence, and where no other evidence can reasonably be expected to exist (management's own intent regarding a plan, for instance), the representation is the best evidence available, not a replacement for evidence that could have been obtained elsewhere.
Why this often gets treated as a formality, and why that's a mistake
Because the letter is signed near the very end of the engagement, after most fieldwork is already done, it's easy to treat as paperwork rather than as a real audit step. The actual discipline SA 580 requires is reading the letter critically before it's signed: does every representation in it actually match what was found during fieldwork? A representation that "no fraud has been identified by management" sitting in the same file as a fraud risk the audit team itself flagged earlier is a contradiction that has to be resolved before the letter is accepted, not signed over.
What happens if management refuses to sign, or representations are inconsistent with other evidence
| Situation | What SA 580 requires |
|---|---|
| Management refuses to provide a required written representation | Raises doubt about management's integrity broadly, and about the reliability of other representations and evidence obtained during the audit — may result in a disclaimer of opinion |
| A specific representation is inconsistent with other audit evidence obtained | The inconsistency has to be investigated and resolved; if it can't be, it casts doubt on the reliability of other representations, with the same consequence as an outright refusal |
How we think about this
The representation letter is the last checkpoint, not the first line of defence. If a representation is the only evidence standing behind a material balance that could reasonably have been corroborated independently, the problem is the missing independent evidence, not the letter — adding a stronger representation doesn't fix an evidence gap that shouldn't exist.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Audit documentationSA 230: what actually has to be in the fileThe experienced-auditor test explained in plain terms, what documentation has to demonstrate, when the file has to be assembled, and the gaps that most often draw comment on review.
- Audit workflow & automationSA 570: going concern, and when it actually changes the audit reportMost going-concern evaluations end exactly where they should: no material uncertainty, no change to the report. The standard is about the minority of cases where that's not true.
- Audit documentationEngagement letters: what SA 210 requiresWhat an engagement letter must establish, when it needs renewing, and the gaps most often found on file inspection — undated letters and stale scope.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.