Study guide

5.3 IT General Controls (ITGC) & Automated Application Controls

EPSO Auditors Open Competition AD7, Field of Audit

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Competition Structure & Reasoning Tests

1.1 Competition Format, Eligibility & Selection Rules 1.2 Verbal Reasoning: Text Analysis & Deductive Logic 1.3 Numerical Reasoning: Ratios, Percentages & Data Interpretation 1.4 Abstract Reasoning: Pattern Recognition & Matrix Sequences

2 Chapter 2: Auditing Frameworks, Standards & Professional Ethics

2.1 International Standards on Auditing (ISA) & IAASB Framework 2.2 Public Sector Auditing: INTOSAI & ISSAI Architecture 2.3 The IIA Global Internal Audit Standards (IPPF) 2.4 Professional Ethics, Independence & Professional Skepticism

3 Chapter 3: Audit Risk Assessment & Materiality

3.1 Strategic & Annual Audit Planning 3.2 Understanding the Entity, Environment & Inherent Risk (ISA 315) 3.3 The Audit Risk Model: Inherent, Control & Detection Risk 3.4 Materiality, Performance Materiality & Tolerable Misstatement (ISA 320)

4 Chapter 4: Audit Evidence, Procedures & Sampling

4.1 Sufficient Appropriate Audit Evidence & Financial Assertions (ISA 500) 4.2 Substantive Testing & Substantive Analytical Procedures (ISA 520) 4.3 Audit Sampling: Statistical, Monetary Unit Sampling & Sampling Risk (ISA 530) 4.4 Audit Documentation, Working Papers & Audit Trails (ISA 230)

5 Chapter 5: Internal Control Systems & IT Audit

5.1 COSO Framework: The Five Components & Seventeen Principles 5.2 Tests of Controls, Walkthroughs & Evaluating Deficiencies (ISA 265) 5.3 IT General Controls (ITGC) & Automated Application Controls 5.4 CAATs, Data Analytics & Continuous Auditing 5.5 Audit Methodology, Tools & Knowledge Management

6 Chapter 6: Performance Auditing & The Three Es

6.1 Principles & Mandates of Performance Auditing (ISSAI 300/3000) 6.2 The Three Es: Economy, Efficiency & Effectiveness 6.3 Audit Findings (Condition, Criteria, Cause, Effect) & SMART Recommendations 6.4 Following Up Findings & Recommendations 6.5 Leading & Coordinating Audit Assignments

7 Chapter 7: Fraud Risk, Compliance & Investigative Bodies

7.1 Fraud Risk Assessment, Fraud Triangle & ISA 240 7.2 Compliance Auditing: Legality, Regularity & ISSAI 400/4000 7.3 EU Anti-Fraud Architecture: OLAF, EPPO & Irregularity Reporting

8 Chapter 8: Audit Reporting & Opinions

8.1 Audit Opinions: Unmodified, Qualified, Adverse & Disclaimer (ISA 700/705) 8.2 Key Audit Matters (KAM), Emphasis of Matter & Other Matter Paragraphs 8.3 ECA Annual Reports, DAS & Special Reports 8.4 Quality Assurance & Peer Review

9 Chapter 9: EU Financial Governance & Budget Architecture

9.1 The EU Budget, Multiannual Financial Framework & Own Resources 9.2 The EU Financial Regulation: Budgetary & Financial Principles 9.3 Budget Implementation Modes: Direct, Shared & Indirect Management 9.4 The Annual Discharge Procedure & Parliamentary Oversight (CONT)

10 Chapter 10: EU Written Test (EUFTE) & Reserve List Strategy

10.1 EUFTE: Official Format & Written-Communication Anchors 10.2 Source-Based Drafting Under Time Pressure 10.3 Reserve List & Institution-Led Recruitment

5.3 IT General Controls (ITGC) & Automated Application Controls

Key Takeaways Explain This Topic AI

ITGCs support reliable operation of systems and automated controls across access, change, development and computer-operations processes.

Application controls address transaction input, processing, interfaces and output; their audit relevance depends on the financial assertions and system dependencies.

The auditor identifies relevant technologies, evaluates control design and implementation, and tests operating effectiveness only where the audit approach requires reliance.

A relevant ITGC deficiency can undermine dependent controls, but it does not automatically invalidate unrelated controls or require 100% transaction testing.

Developer and privileged access should be authorised, restricted, logged and reviewed; exceptional access is evaluated in context rather than prohibited by an invented universal rule.

Last updated: October 2026

5.3 IT General Controls & Automated Application Controls

Financial systems can initiate, process, record and report transactions with little visible manual intervention. The audit therefore identifies the technologies relevant to financial reporting, understands the related IT processes and determines how controls and data depend on them.

IT general controls

IT general controls support the continued operation of applications, data and automated controls. A common audit structure covers four connected domains:

Access to programs and data

Access controls include authorised provisioning and removal, role design, authentication, privileged-access management, periodic review, logging and monitoring. The auditor tests whether rights match job responsibilities and whether elevated users can bypass normal application controls.

Privileged access is not assessed through a slogan that developers may “never” enter production. Routine development and deployment powers should be separated from production operation. Where emergency or exceptional access is permitted, it should have a documented purpose, prior or prompt approval as policy allows, time limitation, logging and independent review.

Program changes

Change management covers request, risk assessment, approval, development, testing, migration and post-implementation review. The auditor identifies who can change code or configuration, whether development and production are appropriately separated, and whether emergency changes follow a controlled path. The governing policy sets time limits; there is no universal 24- or 48-hour rule for every system.

Program development

Development controls govern new systems and major releases: requirements, security and control design, testing, data conversion, acceptance, cutover and post-implementation review. For a migration, reconciliation should address record counts, control totals, mapping, rejected items and opening balances. “100% of rows loaded” is not enough if fields were mapped incorrectly or the source population was incomplete.

Computer operations

Operations controls include job scheduling, interfaces, incident and problem management, backups, restoration testing, availability, monitoring and disaster recovery. A successful backup job is not evidence that restoration will work; auditors examine restore tests and whether recovery objectives match business needs.

Application controls

Application controls operate within a business process:

  • input controls validate required fields, formats, ranges, authorised master data and duplicates;
  • processing controls perform calculations, three-way matches, sequence checks and workflow approvals;
  • interface controls reconcile records and totals transferred between systems; and

output controls restrict and review reports, exception lists and reconciliations.

The auditor maps each control to an assertion. A three-way match can support occurrence, accuracy and authorisation of a payment, but it does not prove that master data, purchase orders or receipts were genuine. An automated range check proves only that configured values met the programmed rule.

Testing controls and dependencies

Start by evaluating design and implementation : could the control address the risk, and is it in use? If reliance is planned, test operating effectiveness over the relevant period. Evidence may include configuration inspection, controlled reperformance, change logs, exception handling and the ITGCs that keep the configuration stable.

For a fully automated control with unchanged code and configuration, testing one or a small number of executions may sometimes be combined with evidence over relevant ITGCs. This is a methodology decision, not a universal “sample of one” rule. Changes, multiple configurations, manual intervention or unreliable logs require different work.

Responding to deficiencies

When an ITGC fails, identify the affected applications, controls, reports, interfaces, users and periods. Evaluate compensating controls and whether alternative evidence exists. Without support, do not rely on the affected automated controls; revise the nature, timing and extent of other procedures. Unaffected controls remain available if their independence is demonstrated.

Constructed scenario

Assume developers held unreviewed production administrator rights during year-end and several financial-rule changes lacked approval and testing. The auditor would identify which automated validations and reports could have changed, inspect logs and configuration histories, test compensating review, extend transaction or data procedures where necessary and communicate the deficiency at the level required by ISA 265. The response depends on impact and evidence; it is not automatically a full-population manual retest.

Document scope precisely: application version, configuration, interfaces, infrastructure, relevant reports and period. A control that worked in one environment or business unit may not support another. When service organisations or cloud providers operate part of the stack, evaluate the applicable assurance report, complementary user controls, subservice arrangements and exceptions rather than assuming outsourced technology is outside the audit. Retain evidence of every dependency conclusion.

Loading diagram... Technology Dependencies in the Audit Plan