Payables orchestration for finance, procurement and shared services

In an enterprise, a supplier invoice does not belong to one team. It is received and processed by accounts payable, matched against a purchase order that procurement owns, approved against a budget that finance controls, checked against a contract, validated for tax, and paid on a schedule treasury sets. Three functions touch the same document, and each is measured on a different result.

That shared ownership is where the cost hides. The Hackett Group’s 2025 Working Capital Survey found USD 1.7 trillion tied up in excess working capital across the top 1,000 US public companies, and named working capital optimisation the top finance priority for the year.

The AFP Payments Fraud and Control Survey reported that 76% of organisations experienced attempted or actual payments fraud in 2025. And Ardent Partners’ State of ePayables 2025 put the average all-inclusive cost to process a single invoice at USD 9.84, with an average processing time of 8.2 days.

These numbers land on three different functions. This article takes each function in turn, finance, procurement, and shared services, then looks at the single layer that serves all three, and what it means for compliance.

It helps to be precise about the word before applying it to each function. Integration connects systems so data can move between them. Orchestration coordinates the decisions made across those systems through one control layer that captures every invoice, validates it against the relevant rules, enforces policy consistently, and gives every team the same view of the same transaction.

Connecting systems does not, on its own, govern what happens once they are connected. Middleware can pass an invoice from a capture tool to an ERP without checking it against a contract, a budget, and a fraud rule in one pass. An orchestration layer is where those checks happen together, and where finance, procurement, and shared services rules are applied to the same invoice instead of in three separate places.

This matters because few enterprises run payables on one system. APQC benchmarking reported by CFO.com found the median enterprise runs two ERPs across its finance shared services organisation, and organisations at the 75th percentile run four or more.

Each system carries its own supplier master, its own matching configuration, and its own controls. A layer that sits above all of them, ingests from each, and posts back to each is what lets one set of rules govern invoices no matter where they entered. With that defined, the rest of this article is what the layer does for each function that depends on it.

Finance reads payables as a cash and risk position, and it owns the downside when either goes wrong. The headline metric is days payable outstanding, where a higher number means the organisation holds its cash longer.

The Hackett Group reported average DPO recovering to 59 days in 2025, with the improvement in payables the main driver of working capital gains across the companies surveyed. Finance also carries the cost of every duplicate payment, every fraudulent one, and every invoice that clears without the right approval.

A duplicate-payment check only works on the invoices it can see, and when the same supplier submits one invoice by email to one entity and a second through a portal to another, neither system’s check sees both. The payment goes out twice.

An AFP survey found checks the payment type most exposed to fraud, hit at 58% of organisations, and names business email compromise, a fraudster impersonating a known supplier, one of the most common attack methods. Both failures exploit the same blind spot: no single point where every payment is checked before it leaves.

An orchestration layer closes that spot by capturing every invoice into one place before payment, so duplicate detection and fraud controls run against the complete picture instead of one system’s slice of it. It also gives finance direct control over payment timing.

With contract terms and the cash position visible together, the layer can hold a payment to the end of the agreed terms to protect DPO, then release it earlier when capturing a discount is the better outcome.

Real-time dashboards replace the month-end scramble to assemble a cash position from several systems, and every transaction carries a complete audit trail from receipt to payment.

For finance, the value is fewer bad payments, tighter control of when cash leaves, and a per-invoice cost of $5 on average.

Procurement teams read the same invoice through the supplier and the contract. The team negotiates a price, a payment term, and often a rebate or early-payment discount, and its performance depends on those terms being honoured when the invoice is actually paid.

There is a gap between what was negotiated and what gets paid: World Commerce & Contracting research estimates the average organisation loses almost 9% of annual value to poor contract management.

Much of that gap is invoices paid at a price the contract never agreed to. An invoice priced above the negotiated rate clears because the person approving it cannot see the contract, and the difference is gone. A negotiated early-payment discount is lost because the invoice sat in an exception queue past the discount window.

A supplier is set up twice — once by procurement with the negotiated terms, once by finance to clear an urgent payment, with default terms and a different bank record — so there are two payment schedules and no single view of total exposure. None of these is a procurement failure on its own. Each happens because the contract terms live somewhere the payment process cannot reach.

An orchestration layer puts the contract into the transaction. Each invoice is validated against the agreed price and terms at the point it is processed, so an overcharge is flagged before payment instead of recovered afterwards. One supplier master across the group means a vendor is onboarded once, with one set of terms and bank details.

Multichannel intake also widens supplier inclusion: Ardent found that on average 57% of suppliers can submit invoices electronically, while best-in-class organisations have 1.4 times more of their suppliers enabled to do so, which is what makes touchless processing possible at volume.

The clean, structured spend data that results feeds the category and supplier analysis procurement teams need to negotiate the next contract from evidence instead of estimate.

Shared services is different from the other two, because it is an operating model more than a function with its own scorecard. A shared service centre is the team asked to run finance’s controls and procurement’s contract rules identically across every entity in the group, at the lowest cost per invoice it can reach.

That is harder than running them once. A centre handling AP for multiple subsidiaries inherits multiple versions of the supplier master, multiple matching configurations, and invoices arriving in several languages and formats through different channels.

Each additional ERP needs its own specialists, and the standardisation the centre depends on for its cost advantage erodes with every system it has to support. Intercompany invoices add another layer, reconciling on both sides of a transaction between two entities in the same group, work that a multi-system centre does by hand. Consolidated reporting becomes a monthly aggregation exercise, pulling group-wide AP metrics out of several systems and assembling them manually.

An orchestration layer is what makes one process possible across all of it. The same capture, matching, and payment logic applies to every entity regardless of the ERP underneath, so the centre runs one process instead of multiple.

Intercompany relationships are identified and reconciled automatically, then posted back to each entity’s ERP. Group-wide reporting comes from a single layer without the manual assembly. Onboarding a new entity becomes a repeatable configuration instead of a fresh integration project, which matters most for groups that grow by acquisition.

The payoff at scale: Deloitte’s 2025 Global Business Services Survey found around half of responding organisations achieving more than 20% in savings from their shared services operations, with effective governance and digital technology named as the elements that drive that value.

(For the technical detail of running payables across a multi-ERP enterprise, see payables orchestration for multi-ERP enterprises.)

Each team wants different things from the same invoice. Finance teams want it paid on the last day the terms allow, to protect cash. Procurement teams want it paid on the contracted day to capture the discount and keep the supplier whole. Shared services teams want it cleared with no manual handling at all. All three are correct from where each team sits, and none of them sees the whole transaction.

When payables runs across separate systems, those priorities are reconciled by email, by exception queue, and by whoever escalates hardest. The cost is spread thin enough that no single team carries it on their books, which is why it survives.

It shows up in the exception rate: Ardent puts the average invoice exception rate at 18.4%, and exceptions are the single biggest reason invoices are slow and expensive to process.

A control layer resolves the conflict by holding all three sets of rules in one place and applying them to each invoice at the point it is processed. Finance’s approval thresholds and fraud controls, procurement’s contract prices and payment terms, and shared services’ matching tolerances are encoded once and checked together.

The payment-timing example shows how the goals become compatible instead of competitive: because the layer can see both the contract term and the cash position, it can protect DPO and still release a payment inside the discount window when the maths favours it.

Government e-invoicing mandates require structured, machine-readable invoices delivered and reported on fixed deadlines, and manual workarounds do not survive a structured pipeline.

In the UAE, the Ministry of Finance’s phased rollout opens with a pilot on 1 July 2026 and makes structured e-invoicing mandatory for large businesses above AED 50 million in revenue from 1 January 2027, with smaller businesses required to implement from 1 July 2027 and government entities from 1 October 2027.

The same shift is happening across much of an enterprise’s footprint at once. The EU formally adopted its VAT in the Digital Age (ViDA) package on 11 March 2025, with mandatory intra-EU B2B e-invoicing and digital reporting from 1 July 2030.

Several member states are moving ahead of that deadline: Belgium’s domestic B2B mandate began on 1 January 2026, with France, Germany and Poland phasing in their own requirements, and outside the EU, Saudi Arabia and Malaysia continue staged rollouts.

A structured pipeline serves all three functions at once: it gives finance validated, auditable data for compliance and fraud control, gives procurement clean contract and supplier data on every transaction, and gives shared services the touchless processing that only structured data makes possible. Compliance has become the practical entry point for orchestration because it forces the data quality the layer depends on.

SpendConsole is a payables orchestration platform that sits above existing ERPs and applies one set of rules to every invoice, whichever system or entity it came from. It does not replace SAP, Oracle, Dynamics 365, Workday, NetSuite, or Ariba. It ingests from each, processes the transaction once, and posts the result back.

The platform maps to the three functions described here.

For finance teams, it captures every invoice into one place before payment, runs duplicate detection and fraud controls against the full picture, and routes payments across multiple rails with reconciliation tied back to the originating invoice, purchase order, and contract.

For procurement teams, it validates each invoice against contract pricing and tax rules, holds one supplier master across the group, and ingests invoices through eight channels read with AI extraction across more than 20 languages, including handwritten Arabic.

For shared services, it applies the same capture, matching, and payment logic to every entity, identifies and reconciles intercompany invoices, and assembles group-wide reporting from a single layer.

Oli, the platform’s embedded AI agent, answers questions about that data in plain language, and a single Peppol-certified compliance engine handles e-invoicing validation across jurisdictions, with the UAE configuration built for the FTA’s accredited service provider model.

What is the difference between payables automation and payables orchestration?

Automation speeds up individual steps, such as reading an invoice or generating a payment file. Orchestration coordinates the decisions across those steps through one control layer, applying finance, procurement, and shared services rules to the same invoice and posting the result back to the relevant ERP. Automation makes a step faster; orchestration makes the whole process consistent.

What does payables orchestration change for a finance team specifically?

It captures every invoice into one place before payment, so duplicate detection and fraud controls work against the complete picture instead of one system’s slice. It gives finance control of payment timing to protect days payable outstanding while still capturing discounts when they are worth more, real-time cash visibility, and a complete audit trail on every transaction.

How does it help procurement when procurement does not run accounts payable?

Procurement owns the contracts and supplier relationships, and orchestration is where those terms are enforced in practice. Each invoice is validated against the agreed contract price before payment, suppliers are onboarded once into a single master, and the structured spend data produced feeds category and supplier analysis.

Does a business need a shared services centre to benefit from orchestration?

No. Finance and procurement gain from one control layer even in a single-entity company. The shared services benefit is specific to running AP across multiple entities and ERPs, where one process replaces a separate one per system. For organisations without a centre, the same capability is what a centralised AP operation would look like.

How does e-invoicing compliance connect to orchestration?

E-invoicing mandates require structured, machine-readable invoices on fixed deadlines, which removes the manual slack that let teams paper over process gaps. That structured data is also what an orchestration layer needs to validate, match, and pay invoices without human handling. Compliance has become the practical entry point for orchestration because it forces the data quality the layer depends on.

How does orchestration work when an enterprise runs several ERPs?

A control layer sits above the ERPs, ingests invoices from each, applies one set of rules, and posts results back to the correct system, which avoids the multi-year migration a full ERP consolidation would require.