Shared Services Procure-to-Pay: One Process, Six Countries, Zero Standard

Coretexly Customer Team· 7 min read· September 2, 2026

Shared services centers and BPO operations are where end-to-end finance processes such as Procure-to-Pay, Order-to-Cash, and Record-to-Report are meant to be standardized. They are also where the most variation hides, because the work is distributed across countries, teams, and tools, and most of it happens outside the ERP.

This is the story of a global shared services center that discovered it was running six versions of Procure-to-Pay under one name.

The situation

A shared services center processing invoices for operating companies in six countries, with roughly 220 staff in accounts payable
A single ERP, plus an invoice capture tool, a vendor portal, country-specific tax and compliance tools, a large volume of email with vendors and approvers, and the spreadsheets each team had built to manage exceptions
Invoice cycle times that ranged from four days in the best-performing country to nineteen in the slowest, with no accepted explanation for the gap
A global process owner whose documented standard was followed, according to every team, and clearly was not
A transformation program that wanted to deploy agents into invoice processing and could not decide where to start

Why the standard did not exist

The global process was documented in detail. Each country team had signed off on it. And each country team had adapted it to local tax rules, local approver behavior, and local vendor habits until the documented standard described none of them.

The ERP logs showed when an invoice was received and when it was paid. They did not show the email chase for a missing purchase order, the manual VAT check in a country tool, the spreadsheet that one team used to batch approvals, or the vendor portal lookup that another team performed for every invoice and a third team never performed at all.

The process owner had a standard. The center had six processes.

What Coretexly found

Coretexly's capture ran on the accounts payable desktops across all six country teams, observing the work across the ERP, the capture tool, the portal, the country tools, and email. No integration with the ERP was needed. Within weeks the live model showed each team's real process side by side:

Six distinct end-to-end paths, differing in step order, number of touches, and which systems were involved
The fastest team had eliminated a manual purchase order matching step by using a portal lookup the other five did not know existed
The slowest team performed a duplicate approval routing through email that added an average of six days and served no control purpose the policy required
Exception handling for missing purchase orders was the largest single source of delay in every country, and was handled six different ways
Roughly a fifth of all invoices touched a spreadsheet at some point, invisible to the ERP and to the process owner

What changed

For the first time the process owner could see all six processes, measured, rather than argue with six teams about which one was following the standard.

The center standardized around the fastest team's path, adopting the portal lookup globally and removing the duplicate email approval. Missing purchase order handling, the largest exception path, was redesigned as a single defined flow with a clear routing rule, replacing six informal ones.

That exception flow became the first agent deployment. It was high volume, its variants were now known, its exception logic was defined, and its baseline was measured. The agent handles the purchase order chase with vendors and approvers from the captured process context, escalating only the cases that fall outside the rule.

The result

Invoice cycle time converged across the six countries, with the slowest team closing most of the gap to the fastest within one quarter
Manual touches per invoice fell measurably once the duplicate routing and redundant checks were removed
The process owner gained a continuously updated view of the global process, so the next divergence is caught early rather than discovered in a cycle time report
The transformation program had an evidence-based roadmap for agent deployment across Procure-to-Pay, ranked by measured friction

We thought we had a standard process. What we had was a standard document. Now we have both. Head of Global Business Services