In an audit firm, certifying the accounts no longer rests only on invoices, confirmations and inventory counts: it relies on information systems that produce, transform and store most of the accounting data. Someone has to make sure those systems deserve the trust placed in them. That is the role of the information systems auditor, who works alongside the financial audit team without being the same job. This article explains why the profession exists, what it tests, how an engagement unfolds, which profiles firms recruit, where it leads, and what a recruiter reads on a CV.
Why financial audit needs IT auditors
A statutory auditor must obtain assurance that the accounts contain no material misstatement. To get there, they assess risks first, then choose between two approaches: test the entity’s controls and rely on them, or check balances and transactions directly. Yet at most clients, a control is no longer performed on paper. The bank reconciliation, the approval of an invoice, the calculation of depreciation or the valuation of inventory all go through an ERP, a payroll package or a consolidation tool.
Professional auditing standards also require the auditor to understand the entity’s IT environment as part of the risk assessment. That is what the texts published by the Compagnie nationale des commissaires aux comptes 🔗 and the profession’s standards aim at. But understanding an IT environment requires knowledge the financial auditor does not always have: reading a permissions matrix in an ERP, judging whether a release procedure is reliable, understanding how an interface moves data from one system to another.
Hence the split of roles:
- the financial auditor decides which accounting risks are at stake and which automated or manual controls they wish to use;
- the IT auditor examines whether the IT environment can be relied upon, and concludes on its reliability;
- the engagement manager builds those conclusions into the audit strategy: reliance on the client’s controls, or wider substantive testing.
If the IT auditor finds weaknesses, the financial team cannot rely on the computerised controls and must compensate with more direct work on the accounts. Their work therefore has a concrete effect on the volume and nature of the tests.
General IT controls and application controls
The vocabulary of IT audit rests on a distinction every candidate should master.
General IT controls (ITGC) concern the environment in which applications run. They usually cover four areas:
- access management: creation, change and removal of accounts, periodic review of rights, privileged accounts, segregation of duties;
- change management: who requests, develops, tests, approves and releases a change to the system;
- operations: backups, scheduled jobs, incident management;
- development and acquisition: project management framework, data migrations, acceptance testing.
A simple example: if the same user can create a supplier, enter an invoice and approve the payment, the segregation-of-duties control fails, however good the software is.
Application controls are built into a specific application. Examples are the three-way match between order, receipt and invoice, the blocking of a payment above a threshold, the automatic calculation of a provision, or a format check on an interface. The IT auditor tests them on a sample of cases, or by examining the configuration.
The link between the two is essential: an automated application control is reliable only if the general controls protect it. A calculation that is correct today can be altered tomorrow by an unauthorised change. This is why the IT auditor almost always starts with the general controls.
Interfaces deserve a separate mention. Data flows between the billing system and the ledger, between payroll and social security filings, between an operational tool and consolidation. Each interface is a point where data can be lost, duplicated or altered. The auditor checks that transfers are complete and accurate, that rejections are followed up, and that manual corrections are traced.
A typical engagement alongside the financial team
An IT audit engagement fits into the financial audit calendar rather than following it. Here is a common sequence.
- Scoping with the engagement manager. The financial team presents the applications that feed the accounts and the controls it plans to rely on. The IT auditor derives the scope: which applications, which databases, which operating systems.
- Understanding the environment. Interviews with the IT department, review of the application map and of the access and change procedures. This is the time to spot the year’s changes: a new ERP, a migration, outsourcing to a service provider.
- Testing the controls. Extracting the user list, comparing it with the leavers list supplied by human resources, checking sensitive rights, selecting changes released to production to verify their authorisation and testing.
- Data analysis. Rights conflicts or entries posted by unusual users can be searched across the whole population. Our article on data analytics in audit details these uses.
- Reporting. Weaknesses are ranked by their possible effect on the accounts, discussed with the client, then passed to the financial team, which decides the effect on its procedures. A recommendation goes to the client’s management.
When the client outsources part of its processing to a provider, for example payroll or hosting, the auditor often relies on an assurance report issued by another auditor on that provider. They then read the scope covered, the exceptions noted and the controls the client must perform itself in addition.
Timing matters. Engagements concentrate early in the cycle, to test controls before the year-end, then again close to the closing to cover recent changes. An IT auditor often works on several clients in parallel, with less permanent presence at each than a financial assistant. On the workload specific to the closing period, read our article on the busy season in audit.
Profiles recruited and useful certifications
Firms recruit their IT teams from three broad families of profiles.
Engineering schools and technical universities. A degree in computer science, information systems or cybersecurity provides the technical base: networks, databases, operating systems, development. The candidate often has no accounting training, which the firm supplements with internal courses on assertions, cycles and risk-based reasoning.
Master’s degrees in information systems or in audit and control. Some master’s programmes combine management, accounting and information systems. They suit candidates who want to stay close to financial audit while specialising. Our article on choosing a master’s in audit or management control helps compare these routes.
Career changers from audit. A financial auditor who has worked on ERPs, extractions and rights testing can ask to join the IT team, provided they show a technical foundation: SQL, an understanding of a database, first training courses. It is a common route, because they already know the accounting stakes. The reverse path exists too, more rarely: an IT auditor who wants to move into financial audit.
The certifications that count most are those that validate the method of information systems auditing and security:
- the CISA (Certified Information Systems Auditor), awarded by ISACA 🔗, the reference for information systems audit; it requires professional experience in addition to the exam, which makes it a medium-term goal rather than a prerequisite for hiring;
- security management certifications, such as those tied to the ISO/IEC 27001 standard (auditor or lead auditor);
- vendor training on the most widespread ERPs, which makes access rights easier to read.
The firm often funds CISA preparation once experience is gained. It is therefore better to list it as “in progress” than to leave it out.
Pathways to cybersecurity or consulting
IT audit in a firm is a broad starting point. The skills acquired transfer in several directions.
Cybersecurity. Auditing access rights, configurations and security processes prepares for governance, risk and compliance roles, and for technical security audit. In France, the security audit of certain sensitive systems is entrusted to providers qualified under an ANSSI 🔗 framework, which structures a market of more technical roles. The move generally requires strengthening technical testing skills.
IT consulting. IT internal control, compliance preparation, support for transformation projects: consulting firms look for profiles who know control logic as well as technology.
Internal control and internal audit at a client. An internal audit department seeking to cover IT risks willingly recruits former IT auditors. Our article on the internal controller’s job describes this function.
Transformation and data. The data analyses performed on engagements provide a base for analysis and steering roles.
Leaving the firm is a choice that needs preparation: our article on reasons and moments to leave audit helps set the criteria.
What the recruiter looks for on the CV
An IT audit manager reads a CV with two questions: does this candidate understand the technology, and can they connect it to the accounts? Here is what answers both.
- Named environments. Cite the ERPs, databases and systems you actually tested, rather than a general “mastery of information systems”.
- Control areas. Access, changes, operations, interfaces: one line per area worked shows that you speak the firm’s language.
- The link with financial audit. Say that your conclusions served an audit team, for example to decide whether to rely on automated controls.
- Analysis tools. SQL, advanced spreadsheets, data preparation tools. Our article on audit software to list on a CV details how to present this section.
- A readable technical degree, with the track, and the certification aimed for or obtained.
An example line: “Tested sensitive access in the ERP of 5 industrial clients (comparison of active accounts with the leavers list, review of payment approval rights), reported to the financial team before the interim visit.” It names a scope, a method and a recipient, without inflating results.
To build this page, the CV editor handles the layout for you and produces a PDF that applicant tracking software reads correctly, whereas poorly structured documents are discarded before any human review. The IT auditor CV example shows how to organise these elements on one page.
Frequently asked questions
Do I need an accounting background to become an IT auditor in a firm?
No, it is not essential. Firms recruit engineers and technical profiles and teach them audit concepts. Showing curiosity about accounting and about the risks of misstatement in the accounts is nonetheless a real asset in interviews.
Does the IT auditor do cybersecurity?
Not exactly. They assess the controls that protect the reliability of financial data, which overlaps with security without exhausting it. A penetration test or an in-depth technical audit belongs to other teams, even if IT audit is a good entry point to those careers.
Do IT auditors have the same grades as financial auditors?
Firms generally use a comparable ladder, from assistant to manager then partner, with titles that may vary. Our article on grades in an audit firm details this ladder.
Is the CISA mandatory?
No, it is rarely required at entry. It becomes useful after a few years of experience, to attest to a recognised method. Firms often support it with training.
Can you do IT audit outside the big networks?
Yes, but the organisation differs: in a mid-sized firm, the IT auditor is sometimes alone for several teams and handles more varied topics. Our overview of audit firms outside the Big Four presents these differences.