Digital transformation in a finance function rarely fails because the software was wrong. It fails because the controls that existed on paper were never rebuilt in the system, and nobody noticed until something went missing.

Automation moves the control, it does not remove it

When a payment required two signatures, the control was visible. When it requires two approvals in a system, the control is a configuration setting — one that can be changed by whoever holds administrator rights, often without anyone else knowing.

So the first question in any system implementation is not what it can do. It is who can change what it does.

Four things to settle before go-live

Access design. Decide which roles exist and which combinations are prohibited before users are created. Rights granted in the rush of implementation are rarely revoked afterwards, and the combination of creating a supplier and approving its payment is the classic exposure.

Audit logging. Confirm it is switched on, that it captures changes to master data, and that somebody is accountable for reviewing it. A log nobody reads is not a control.

Data migration. Balances carried into a new system must be reconciled to the old one and signed off. This is the moment errors become permanent, because the opening balance quickly stops being questioned.

Change management. There must be a documented route from request to testing to deployment. Changes applied directly to a live system are how correct data becomes incorrect overnight.

The spreadsheet problem does not go away

Even in well-implemented systems, the most material calculations often live in a spreadsheet outside it — depreciation, impairment, consolidation, the tax computation. These sit outside change control and frequently outside review. They are part of the financial system and should be treated that way.

Start small and prove it

The transformations that succeed tend to automate one painful, well-understood process first, prove the controls hold, and expand. The ones that struggle attempt everything at once and discover the control gaps only when the auditors arrive.

This article is general guidance and not advice on any particular set of facts. If you are planning a systems change, our advisory team in Blantyre will be glad to help you think it through.