ERP can go live. Finance never does.

Most ERP programmes pass every technical test and still leave finance unable to trust the numbers. Enterprise Finance Architect Marinda van Harskamp explains why, and what to design before the system is built.

The Actuals teamActuals · 3 min read

The new ERP passed every test. Integrations run, the project team celebrates, the steering committee signs off. And in finance, someone keeps the old spreadsheet open next to the new system, just to be sure the numbers are right.

That moment is where this episode of High Volume Accounting Live starts. Peter Engel talks with Marinda van Harskamp, CFO advisor and Enterprise Finance Architect. She has spent thirty-three years in finance. She started by keying in shoeboxes of invoices and bank statements at a small accountancy office, and later standardised finance worldwide at IKEA. Today she designs the financial backbone of organisations that implement systems like NetSuite and Microsoft Dynamics.

Finance is behind on day one

The episode title is her line, and she uses it on purpose.

"Your ERP can go live, but finance never does. And I do that also to rock the boat."

What she sees on her assignments is a finance team that reviews the project but does not lead it. "In almost every assignment I see that finance is behind. They don’t trust the system." Often finance brings its current chart of accounts and reports to the project. Then it asks for exactly the same setup again.

Think in events, not transactions

Her core point is a change of perspective. "Finance is still thinking in transactions." Its world is incoming and outgoing invoices and bank statements. The business runs on events: a contract signed, a purchase order, goods received.

Take goods received. In Marinda’s way of working, that one event is designed from five perspectives at once: accounting, management reporting, tax, ESG and KPIs. Decide upfront what the event means for each, register it once, and the reports downstream follow from it.

Regulation is moving the same way. IFRS 15 ties revenue recognition to events. IFRS 18 asks you to bridge statutory and management results. And VAT is expected to move from the invoice to the moment of delivery from 2030 onwards. Yet, she says, nobody teaches it: "We were not trained to think event based."

A long close is a design symptom

Why does the close take so long in a company with high volumes? Her answer: the events were never designed and nobody took explicit decisions about them. After go-live, everyone hopes the books will be fine. Design from the full end-to-end process instead, from the first lead to the final report. Then you know what is coming into your month-end. Reconciliation gets easier, because the work was done upstream.

A company that still needs 10 days to close, she says, should read that as a signal.

The ERP is not the goal

She often hears that the new ERP will fix everything. Her reply is short: "ERP is not the goal, it’s the tool." A new system only works when leadership treats it as an organisational change. Leadership has to stand behind the move from silos to processes.

She also has a clear view of what belongs in the standard. Finance should be as standard as possible, because no company wins its market with its bookkeeping. The core business is another matter. That is where you differ from competitors, and she would rather not force it into a standard model.

It is a finance question

When the month-end runs on workarounds in Excel and Google Sheets, the reflex is to call IT. Marinda disagrees: "It’s not an IT question, it’s a finance question." Finance has to decide upstream what each event means. It also decides where unique identifiers belong, so the spreadsheets are no longer needed. Only then does it become a question of storing data.

The same applies to AI. Tools are coming at finance from the software side. She thinks the direction should be reversed: "We need to bring finance to the innovation".

What to take from it

Peter asked her what a CFO who is considering an ERP should do on Monday. Her advice: "Find somebody who can translate finance to ERP language with a finance background and an IT understanding."

Before that call, one check is useful. List the five events that drive most of your volume. For each one, ask whether anyone decided its meaning for the books and for tax before the system was configured. If nobody did, the go-live date is not the date finance goes live.

The Actuals scan takes 15 minutes and shows where your source data first stops matching your books.

In practiceMoving to a new ERP? What goes into it on day one?

Written by

The Actuals teamActuals