ERP health check

Independent ERP health check

An ERP health check is an independent review of the system you already run: how much of it is used, where processes have leaked into spreadsheets, what the licences and support really cost, how far behind the vendor you are, and what to fix first.

19 yrssenior systems delivery
7finance platforms delivered
39 daysearly on an Oracle to Dynamics migration
22m+assets in the National Grid separation

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

An ERP audit of the system you already run

A readiness assessment happens before a programme and asks whether you can carry one. An ERP health check happens afterwards, often years afterwards, and asks what the live system is actually doing for you. The two are easily confused and the confusion is expensive, because the answer to a poorly performing ERP is not always a new ERP. Our ERP readiness assessment covers the former; this page covers the latter.

The triggers are familiar. Finance has rebuilt the management accounts in spreadsheets. The warehouse runs a parallel paper system. A renewal or a vendor deadline is approaching and nobody can say which modules are used. The implementation partner proposes an upgrade, a reimplementation or a move to the cloud edition, and you would like a view from someone who does not earn from the answer. A merger has left two systems where one was promised. Or the board simply asks what it got for the money.

What you get is an ERP audit in the plain sense of the word: evidence gathered from the system, its logs and its users, judged against what the business needs now rather than what it specified five years ago. We look at nine areas, set out below, and we end with a prioritised improvement plan with costs, owners and sequence. Support arrangements are part of the review, and our article on ERP support explains what good looks like once the partner has left.

Utilisation, process fit, data, integrations and customisation

Five of the nine areas concern how the system is used and how it has been built.

  • Utilisation. Active users against licences, modules paid for and never switched on, functions configured and abandoned. System logs answer most of this in a day.
  • Process fit. Where the designed process and the real one diverge: approvals by email, orders keyed twice, month end journals posted from spreadsheets. We walk the processes with the people who run them.
  • Data quality. Duplicate customers and suppliers, stale open items, items with no cost, master data with no owner. Poor data is usually the real reason reports are not trusted.
  • Integrations. How many interfaces exist, how many are documented, what happens when one fails, and how much rekeying has grown up around the gaps.
  • Customisation debt. Custom code and configuration that blocks upgrades and that nobody dares remove. On SAP systems the Custom Code Migration app classifies custom objects as Used, Referenced or Not Used, and the Not Used category is the decommissioning list; on other platforms we build the inventory from the code repository and the change log.

Each finding is tied to a consequence the business recognises: hours per month, days added to the close, orders delayed, audit points raised. That is what makes the plan at the end persuasive to a finance director rather than merely interesting to an IT team. Where the integration findings are serious we bring in our ERP integration practice, and where data is the problem our data migration consultancy takes the cleansing on.

Licences, support costs, upgrade position, security and reporting

The remaining four areas are where an independent reviewer earns the fee, because each is usually explained to you by somebody with a stake in the answer.

  • Licence and support costs. The licence mix against actual use, the support percentage and what it buys, and exposure you may not know about. SAP's Digital Access model charges indirect access by the number of documents created across nine document types while human users stay licensed per user, and SAP offers a free evaluation service to estimate the count. Microsoft's Dynamics 365 Team Members licence is for light use through designated apps and does not cover custom applications, so a Team Members user doing a full user's job is an audit finding in waiting.
  • Upgrade position and vendor roadmap. Where you sit against the vendor's cadence and deadlines. Oracle Fusion Cloud updates are quarterly and cannot be skipped, with test environments updated on the first Friday of the update month and production two weeks later. Dynamics 365 finance and operations customers can postpone one consecutive service update and no more. NetSuite offers a Release Preview account built from a copy of production so workflows can be tested before the upgrade lands. SAP ECC mainstream maintenance ends at the close of 2027, and S/4HANA now moves on a two year release cycle with seven years of mainstream maintenance per release. Each changes what doing nothing costs.
  • Security. Role design and segregation of duties, dormant and shared accounts, who holds administrator rights, and whether patches and updates are current.
  • Reporting. How long the close takes, how many reports exist and how many are used, and how much of the board pack is assembled by hand.

Deadlines turn a health check into a decision. If your platform is approaching the end of its supported life, the review doubles as the first step in deciding whether to upgrade, reimplement or move, which is where our ERP vendor selection work begins if it is needed.

A prioritised improvement plan, not a sales pitch

The output is a prioritised improvement plan, not a proposal for a programme. Findings are scored for business impact and effort, then grouped into quick wins the in house team can take, defined projects with a cost and a benefit, and strategic questions for the board, such as whether the platform should be kept at all. Each item has an owner, a sequence and a dependency on the vendor's dates. We present it to the sponsor and the finance director first, then to the implementation partner, in that order.

Independence shapes the result. PEF has no reseller, referral or alliance deal with any vendor and earns nothing from your licences or your partner's services, so the plan can say that the system is fine and the process is the problem, or that a cheaper edition would do, or that the upgrade the partner is proposing should wait a year. Our consultants have led and analysed the decisions that come before, during and after system migrations, which is the experience a review like this draws on: knowing what a healthy system looks like two years in, and recognising the early signs of one that is not.

Where the review finds a programme still in flight that is not landing, we switch to ERP programme recovery. Where it finds savings in licences, support or process, the follow through sits with our cost optimisation and benefits realisation practice. Either way, you choose the work; the review does not come with a programme attached. Fees for the health check are published on the pricing page, so you know the cost before we start.

What we have delivered

  • Ran the procurement of every software provider on the National Grid separation, more than 22 million assets, through to implementation including Oracle to SAP S/4HANA.
  • Delivered the Oracle to Microsoft Dynamics migration at BP Pulse 39 days ahead of forecast, with a £25m saving, the largest on a programme where PEF held the main contract.
  • Delivered the £9bn Energy Bills Support Scheme for Ofgem, BEIS and HMRC.
  • Implemented and delivered most major finance systems over 19 years: Oracle, Microsoft Dynamics, NetSuite, Sage, SAP S/4HANA, Unit4 and Access.
  • A suite of consultants who have led and analysed pre, mid and post migration decisions and implementations across ERP and CRM platforms, independent of every vendor.

Questions we are asked

What is an ERP health check?

An ERP health check is an independent review of a live ERP system covering utilisation, process fit, data quality, integrations, customisation debt, licence and support costs, upgrade position against the vendor's roadmap, security and reporting. It gathers evidence from the system, its logs and its users rather than opinion, and produces a prioritised improvement plan with costs, owners and sequence. It is done by a reviewer who sells no software and earns nothing from the recommendation.

What is the difference between an ERP health check and an ERP readiness assessment?

Timing and question. A readiness assessment happens before a programme and asks whether your data, processes, people and governance can carry an implementation. A health check happens after go live, often years later, and asks what the live system is doing for the business and what should change. One prevents a bad start; the other decides whether to fix, upgrade, reimplement or replace a system you already own.

What does an ERP audit look at?

Who actually uses the system and which licences and modules sit idle; where real processes diverge from the designed ones; the state of master and transaction data; the number and reliability of interfaces; the volume of custom code and whether it is used; what licences and support cost against what they deliver; how far behind the vendor's releases you are; role design and access control; and how much reporting is still done by hand in spreadsheets.

How often should we review our ERP system?

Every two to three years as a matter of routine, and always before a contract renewal, a major upgrade decision, a merger or a proposal from your partner to reimplement or move platform. Vendor cadences also set the rhythm: mandatory quarterly updates on Oracle Fusion Cloud, April and October major releases for Dynamics 365 finance and operations apps, NetSuite upgrades you can preview in advance, and fixed maintenance deadlines on SAP all make a periodic independent look worthwhile.

Should we fix our ERP or replace it?

Usually fix first. Most complaints about a live ERP trace back to data quality, process discipline, missing training or customisation that blocks upgrades, none of which a new system solves on its own. Replacement makes sense when the vendor's roadmap no longer fits your business, when support is ending, or when the cost of carrying customisation exceeds the cost of change. A health check gives you the evidence to make that call rather than the partner's instinct.

Is your ERP paying its way?

Tell us what you run and what frustrates you about it, and we will scope an independent review with no product at the end.

Book a conversation