A European mid-market company that is not listed in the United States has no obligation to build a SOX programme. Yet its CFO answers the same questions as peers who are subject to the law: who can change a supplier’s bank details? Who approves a manual month-end journal? What happens if a user enters and approves their own purchase order? Sooner or later, the external auditor, the lender, the insurer or a prospective acquirer will ask.
The ERP is where these risks materialise, and it is also the best place to treat them. This guide is written for CFOs, internal controllers and internal auditors in mid-market companies. It sets out a pragmatic approach built on the COSO framework and the IIA Three Lines Model, one that needs neither a consulting firm nor a dedicated GRC tool to get started.
If your company is consolidated by a US-listed group, read our analysis of ERP and SOX compliance for European subsidiaries instead. Here we cover the general case: useful, proportionate internal control, without the formalism of a SOX 404 audit.
Internal Control: What the ERP Changes
A Reference Framework, Not a Formal Obligation
The most widely used reference remains the COSO Internal Control, Integrated Framework, published in 1992 and updated in 2013. It describes five components: control environment, risk assessment, control activities, information and communication, and monitoring. You do not need to be “certified” against it. It works as a checklist to make sure no component has been forgotten: many mid-market companies invest in control activities (the approvals inside the ERP) without ever formalising risk assessment or monitoring.
Manual, Automated, Preventive, Detective
In an ERP, the same risk can be covered in four different ways. Choosing between these control types is the first design decision.
| Type | Principle | ERP example | Reliability |
|---|---|---|---|
| Automated preventive | The system blocks the action | An invoice outside the matching tolerance is blocked | High, testable once |
| Automated detective | The system flags it afterwards | Daily duplicate-invoice report | High, depends on alert follow-up |
| Manual preventive | A person approves before the action | Dual approval of a bank detail change | Medium, depends on vigilance |
| Manual detective | A person reviews afterwards | Monthly review of manual journals | Medium to low, depends on rigour |
The rule of thumb: automate preventive controls first on high-volume or high-stakes processes (purchasing, treasury, payroll), and keep manual controls for situations that call for judgement. A well-configured automated control runs on every transaction, with no fatigue and no holidays. It also leaves a usable trail, which makes proving the control to the auditor much easier.
One caution: an automated control is only as reliable as the protection around its configuration. If any administrator can change a tolerance without a trace, the control no longer exists in practice. Access to configuration is therefore in scope, just like transactions.
The Three Lines Model Applied to the ERP
The IIA Three Lines Model, updated in 2020, clarifies who does what in managing risk. For a mid-market company its main value is to dispel a common misunderstanding: internal control is not “the accounting team’s job”. Everyone has a distinct role.
First Line: Operations and Process Owners
Buyers, accounts payable clerks, inventory managers and payroll managers own the risks and run the day-to-day controls. In the ERP, they are the ones who enter, approve and reconcile. The process owner (for example the head of purchasing for the procure-to-pay cycle) is responsible for designing the control and making sure it is performed properly.
Second Line: Control and Support Functions
Management control, internal control, compliance, risk management and the CISO define the framework, challenge the first line and monitor indicators. In a mid-market company, these functions can be one or two people, or even the CFO alone. That is not a problem as long as roles are written down and the controller is not the person performing the transaction being controlled.
Third Line: Internal Audit
Internal audit provides independent assurance to the audit committee or to management. Many mid-market companies have no dedicated department and outsource or share the function. What matters is independence: internal audit does not audit what it designed.
Roles and Deliverables
| Line | Who | Role on the ERP | Expected deliverables |
|---|---|---|---|
| 1st | Process owners, users | Run the controls, handle alerts | Evidence of execution, signed reconciliations, exceptions resolved |
| 2nd | Internal control, management control, IT/CISO | Design the framework, review access rights, monitor indicators | Risk-control matrix, periodic access review, exceptions dashboard |
| 3rd | Internal audit (in-house or outsourced) | Test effectiveness independently | Audit plan, reports, follow-up of recommendations |
In practice, IT holds a special position: it administers the ERP and therefore holds powerful rights. It belongs to the first line for its own operations (access management, changes) and must be audited like everyone else. See our guide on operational risk management, DORA and NIS2 in the ERP for resilience and cyber compliance.
10 Controls to Configure First
These ten controls cover the most frequent fraud and error risks in a financial ERP. Parameter names vary by vendor (SAP, Dynamics 365, Odoo, Sage, NetSuite), but the principle is the same.
1. Three-way match tolerances. Purchase order, receipt, invoice: set price and quantity tolerances by purchasing category, in percentage and absolute value. Tolerances that are too wide let drift through; too narrow and accounts payable drowns in blocked invoices. Review them every year and protect who can change them.
2. Approval thresholds. Define approval tiers for orders and invoices by amount and type of spend. The workflow must refuse to let a requester approve their own request. Thresholds must reflect the delegation of authority that has actually been signed.
3. Accounting period locking. Once the close is validated, the period is closed to everyone, except for a traced and approved exception. Locking by module (purchasing, sales, inventory, general ledger) prevents a backdated invoice from changing a result that has already been published.
4. Automatic blocking of modified supplier accounts. After a change of bank details or address, the supplier is blocked for payment until a second person has validated the change. This is the basic control against payment redirection fraud.
5. Dual approval of bank details. One person enters the change, another validates it, with a call-back to the supplier on a number already on file (never the one given in the request). The ERP must record who entered and who validated, with the old and new values.
6. Manual journal controls. Manual entries are the classic channel for manipulating results. Require a mandatory reason, third-party approval above a threshold, a ban on posting to certain sensitive accounts, and a monthly report of all entries made outside automated flows, particularly at period end.
7. Inventory adjustments. Stock adjustments must follow an approval path, with value thresholds, segregation between the person who counts and the person who adjusts, and analysis of recurring variances by item and location.
8. Delegations. When an approver is absent, the temporary delegation must be configured with a start and end date and be visible in a report. Forgotten “permanent” delegations are a classic way of bypassing thresholds.
9. Privileged access. Administrator profiles, direct database access and technical accounts must be inventoried, restricted, logged and reviewed at least once a year. For incompatible duties, our guide on segregation of duties controls to implement before the annual audit details the method.
10. Reconciliations. Bank, third parties, intercompany, inventory and general ledger: automate reconciliations with matching rules, and require any unresolved difference beyond a defined deadline to be escalated to the owner. Reconciliation is both a first-line control and an indicator for the second line.
These ten controls do not need a heavy programme. A two-to-three-day workshop with the CFO, the head of purchasing, the payroll manager and IT is enough to take stock of each one: does it exist, is it automated, who owns it, how is it evidenced?
Continuous Audit Testing: Queries, Data Analytics, Process Mining
A control configured today can be bypassed tomorrow by a settings change, an added account or a disabled workflow. Continuous testing means checking routinely that controls work, instead of waiting for the annual audit.
ERP Queries and Reports
The first step needs no additional tool. Most ERPs can produce scheduled reports or queries on:
- duplicate supplier invoices (same supplier, same amount, same date or similar number);
- payments to suppliers whose bank details were changed in the preceding days;
- manual journals posted at weekends, at period end or by unusual users;
- purchase orders created after the invoice (“after-the-fact” purchasing);
- users holding incompatible rights;
- approvals made by the creator of the transaction.
Schedule these reports, send them to the control owner, and require a record of how exceptions were handled.
Data Analytics
An analytics tool (Power BI, Tableau, Python or dedicated audit software) lets you go further: analysing every transaction rather than a sample, detecting statistical anomalies, and cross-checking the ERP against external files. For the internal auditor, the benefit is moving from sampling to full-population testing on certain cycles.
Process Mining
Process mining reconstructs the actual paths of transactions from ERP logs. It shows, for example, what share of orders really follow the intended workflow, or how many invoices are entered before the purchase order. It reveals workarounds that conventional reports miss. The tool is most useful on high-volume processes such as procure-to-pay and order-to-cash, and assumes clean event logs. For a mid-market company, the sensible approach is to master scheduled queries first, then evaluate process mining on a single pilot cycle.
Documenting for the Auditor: The Risk-Control Matrix
A control that is not documented does not exist in the auditor’s eyes. The central document is the risk and control matrix (RCM). It links what can go wrong to what you do to prevent it.
What the Matrix Should Contain
Each row describes a risk and its associated control. Useful columns: control ID, process, risk covered, control description, type (preventive or detective, manual or automated), frequency, owner, system and parameter concerned, evidence retained, and date and result of the last test.
Example
| ID | Process | Risk | Control | Type | Frequency | Owner | Evidence |
|---|---|---|---|---|---|---|---|
| PUR-04 | Purchasing | Fraudulent payment after a bank detail change | Payment block until a second user validates | Preventive, automated | Each change | Head of accounts payable | Change and approval log |
| CLO-02 | Close | Change to an already closed period | Period locking, reopening subject to CFO approval | Preventive, automated | Each close | CFO | Period settings, reopening log |
| GL-06 | General ledger | Unjustified manual journal | Monthly review of all manual journals above a threshold | Detective, manual | Monthly | Financial controller | Signed report, comments |
| IT-01 | Access | Unjustified privileged account | Annual review of administrator profiles | Detective, manual | Annual | CISO, CIO | Reviewed and approved list |
Testing the Controls
Each control is tested. For an automated control, checking the configuration and running one test case is generally enough as long as the configuration is unchanged. For a manual control, you check on a sample that the evidence exists and that the exception was handled. The underlying audit trail is subject to retention rules, detailed in our article on the ERP audit trail and legal retention obligations (in French).
Common Mistakes
Super-users who bypass everything. An “all rights” profile created to troubleshoot during the project stays active for years. It can enter, approve and pay. Inventory these profiles, remove them from daily use, and manage their use through a traced, reviewed emergency account.
Shared accounts. An “accounting” login used by three people destroys traceability: you cannot tell who did what. Without individual identity, no segregation of duties can be demonstrated. Require named accounts, including for interns and temps.
Controls designed but never tested. A tolerance set five years ago and never reviewed no longer fits current volumes or prices. Schedule an annual test of each key control.
Rights not removed on departure or transfer. Rights accumulate: the accountant who became a controller keeps their entry rights. Link access management to HR movements.
Controls without an owner. An exceptions report nobody reads has no value. Every control needs a name, a frequency and a handling deadline.
Configuration that can be changed without a trace. If admin rights allow thresholds to be changed with no log, the whole framework rests on trust.
Trying to cover everything at once. An exhaustive framework nobody maintains is less useful than a short list of living controls. Start with the major risks.
90-Day Action Plan
Days 1 to 30: scope and map.
- Appoint a sponsor (the CFO) and a lead (internal control or management control).
- List the priority cycles (purchasing, sales, treasury, payroll, close) and their major risks.
- Extract the list of users, profiles and admin rights from the ERP.
- Assess the ten controls from the previous chapter: present, partial, absent.
Days 31 to 60: fix the high-stakes gaps.
- Configure or correct the critical preventive controls: bank details, thresholds, period locking, tolerances.
- Remove shared accounts and reduce privileged profiles.
- Set up three to five scheduled exception reports, each with a named recipient.
- Draft the first version of the risk-control matrix on the priority cycles.
Days 61 to 90: test, steer, present.
- Test the key controls and record the results.
- Address the gaps found and set deadlines.
- Present a summary to the executive committee, or to the audit committee if there is one: controls in place, exceptions, improvement plan.
- Schedule the annual access review and the testing calendar for the following year.
After these 90 days you have a simple but demonstrable framework: a matrix, configured controls, evidence and follow-up. That is what an auditor, a banker or an acquirer will expect, long before a full SOX programme.
Download our ERP evaluation scorecard to assess your ERP against 30 criteria and measure your maturity level before your next audit. To go further, also read our guide on SoD controls to implement before the annual audit.