External Audit and Assurance
How external assurance differs from internal audit: a defined scope, an outside reader, and a report whose wording and limits need to be read as carefully as its conclusion.
The short answer
External audit and assurance is checking performed by a party outside the firm, for a reader outside the firm, within a scope that has been agreed in advance. The outside party examines evidence, tests controls or arrangements as agreed, and reports a conclusion whose strength depends entirely on that scope. The discipline for the firm is to understand, before the work starts, what question is being answered, what evidence will be examined, and what the resulting report can and cannot claim.
External assurance is valuable precisely because it is independent, but that independence comes with limits. An external reviewer does not know the firm as its own staff do, works within a timetable, and relies on the evidence the firm produces and the access the firm grants. A clean external report is therefore a meaningful signal, but it is not a general certificate of resilience, and reading it as one is one of the most common mistakes a board or a supervisor can make.
Why does scope come first?
Scope decides what the conclusion means. An engagement that examines one service, one control area, or one period can only support a conclusion about that service, area, or period, however confidently the report is worded. The firm should be able to state, in plain terms, which services were in scope, which were not, what kind of testing was performed, and what standard the work was judged against, and it should be able to explain those limits to anyone who reads the report.
How should a firm prepare?
Preparation for external assurance is largely the same work as building a good evidence trail, done in advance rather than under pressure. The firm should be able to produce, for each service in scope, its map, its tolerance, its recent test records, and its incident reviews, with consistent naming and visible links between them. Gaps found during preparation are a gift, because they can be fixed or honestly acknowledged before the reviewer finds them, and an acknowledged gap is far less damaging than a gap discovered during fieldwork.
Preparation should not become rehearsal. Coaching the people who will be interviewed to give polished answers, tidying records to remove awkward findings, or steering the reviewer away from difficult services all undermine the very independence the firm is paying for, and they usually fail, because an experienced reviewer recognises a prepared performance. The better preparation is to make sure the people who run the service understand it well enough to answer honestly, including about its weaknesses, and to have the evidence ready for them to point to.
What happens during the work?
During the work, the reviewer will typically ask for evidence, interview staff, and test selected controls or arrangements, following the trail for the services in scope. Requests may seem repetitive, because the reviewer is checking the same point from several angles: the plan, the test record, and the recollection of the person who would act. That repetition is not inefficiency; it is how the reviewer distinguishes a control that operates from a control that is merely described.
How should the report be read?
Read the report from its scope and limitations inward, not from its headline conclusion outward. Note which services and periods were covered, what testing was performed, and what the reviewer did not examine. Note the exact wording of the conclusion, because assurance reports use careful language, and the difference between one form of wording and another can be the difference between a strong and a limited conclusion. Note also any findings, recommendations, or matters raised, even when the overall conclusion is positive, because those details often contain the most useful actions.
What should happen afterwards?
After the report, the work is follow-up. Each finding should be assigned an owner and a date, and its fix should be evidenced in the service trail, not merely asserted in a management response. The board or committee that receives the report should be able to see which findings are closed on evidence, which remain open, and which have been accepted as a risk, with the reasoning for acceptance recorded. A report that is filed without follow-up has bought assurance at the price of learning nothing.
External assurance should also be used to improve the internal trail. If the reviewer struggled to find a record, that record was not in a producible form, whatever the firm believed. If the reviewer misread a tolerance, the tolerance may need clearer wording. Treating the engagement as a test of the evidence system, rather than as a hurdle to clear, turns a periodic cost into a lasting improvement, and it makes the next engagement easier, because the trail will already be in the shape an outside reader needs.
Primary sources on the record
- Financial Conduct Authority, operational resilience: the UK regime, labelled separately from DORA.
- Regulation (EU) 2022/2554 on digital operational resilience for the financial sector, Official Journal text on EUR-Lex.
Legal status: Regime-dependent and labelled in the guide. DORA applies from 17 January 2025. The UK regime has its own policy statements and dates, stated separately where the guide compares regimes. Application position for this topic: DORA: from 17 January 2025. UK: see the UK line for its own dates.