Ask a CPO at a global enterprise how many ERP systems their company runs, and the honest answer is rarely “one.” A decade of mergers, regional rollouts, and divisional autonomy means most large organizations are running SAP in one business unit, Oracle in another, and a handful of legacy or acquired systems somewhere in between.

‍

Procurement technology that assumes a single, clean ERP environment is solving for a reality that doesn’t exist in most enterprises — which is exactly why ERP-agnostic platforms are gaining ground.

‍

‍

The Single-ERP Assumption Is the Problem

A lot of procurement software is architected around a single deep integration — built natively for SAP, or built natively for Oracle, with everything else treated as an afterthought. That works fine for a company that genuinely runs one ERP everywhere. It breaks down fast for anyone else, and “anyone else” describes most enterprises above a certain size.

‍

When procurement technology is tied to one ERP, multi-entity organizations end up with one of two bad outcomes: they either run different procurement tools in different business units (which recreates exactly the fragmentation problem procurement technology was supposed to solve), or they force every entity onto the ERP the procurement platform happens to support, regardless of whether that’s the right system for that part of the business.

‍

‍

What “ERP-Agnostic” Actually Has to Mean

ERP-agnostic isn’t just a checkbox that says “we have an SAP connector and an Oracle connector.” A platform is genuinely ERP-agnostic when:

‍

Supplier and spend data stays unified regardless of which ERP a transaction originated in. If finance wants a consolidated view of total spend with a supplier across three business units running three different ERPs, that view needs to exist without a manual reconciliation exercise.

‍

Workflows are consistent for the people using them, even when backend systems aren’t. A procurement analyst submitting a sourcing event or processing an invoice shouldn’t need to learn three different interfaces depending on which entity they’re supporting that week.

‍

New entities, acquisitions, and ERP migrations don’t require rebuilding the procurement layer. This is where ERP-agnostic architecture pays for itself most directly — when a company acquires a business running a different ERP, or migrates a division from one ERP to another, the procurement platform should absorb that change rather than becoming the reason the integration project takes another six months.

‍

‍

The Compliance Angle Most Vendors Don’t Talk About

Multi-ERP environments don’t just create integration headaches — they create real compliance risk, because the same supplier can exist as different vendor master records in different systems, with different tax statuses, different banking details, and no single source of truth for whether that supplier is actually in good standing.

‍

This is the structural version of the fragmented-data problem HFS Research points to when it describes the gap between where enterprises want to be (AI-driven orchestration) and where the underlying data readiness actually is. You cannot orchestrate spend decisions across an enterprise if “the supplier” means three different, slightly inconsistent records depending on which system you’re looking at.

‍

An ERP-agnostic platform that centralizes supplier data and compliance status above the ERP layer — rather than inside any single one of them — solves this at the root rather than patching it system by system.

‍

‍

Why This Matters More as AI Enters Procurement

There’s a second, less obvious reason ERP-agnosticism is becoming more important rather than less: AI-driven procurement orchestration depends on having a complete, unified dataset to reason over. A spend analytics or supplier risk model that can only see the transactions flowing through one ERP is working with a partial picture — and a partial picture produces partial (or wrong) recommendations.

‍

If the next wave of procurement value genuinely comes from intelligence layered on top of transactional data, as HFS Research’s S2P analysis argues, then that intelligence layer needs visibility across every system spend actually flows through, not just the one a platform happened to be built for first.

‍

‍

The Practical Test

When evaluating whether a platform’s ERP-agnosticism is real rather than marketing language, a useful test is to ask what happens during a migration or acquisition. Does spend visibility, supplier compliance status, and sourcing history carry over cleanly when an entity moves from one ERP to another — or does that transition mean rebuilding reporting and re-onboarding suppliers from scratch?

‍

Platforms genuinely designed to work across multiple ERP systems treat that scenario as routine. Platforms built around one ERP and retrofitted to “support” others tend to treat it as a project.

‍

For enterprises that already operate — or expect to operate, through growth or acquisition — across more than one ERP environment, that distinction isn’t a technical nicety. It’s the difference between procurement technology that scales with the business and procurement technology that becomes the next system the business has to work around.

‍

‍

‍

Source: HFS Research, “CPOs Must Unite Enterprise Processes, Platforms, and People for AI-Enabled Outcomes,” 2026.

‍