Every shared services programme reaches the same meeting. The target operating model is on the screen, the standard process is agreed in principle, and then a country controller explains why it cannot apply to their entity. They are usually right, and the programme stalls there for a quarter.

What stalls it is rarely the ERP. It's that standardisation was presented as a single process when the thing that can actually be shared is a single policy, applied differently where the law says so.

Why the last programme stalled

The previous attempt probably tried to make twelve entities look identical to the system. That fails because the differences aren't preferences, but obligations, and the person who signs is personally accountable.

The organisational structures underneath make the point on their own. Dynamics 365 models the entity that owns the books as a legal entity, an organisation with a registered legal structure. Workday's equivalent is the Company, the level at which you hold a balanced set of books; legal entities are normally set up as companies, though a company can sit below legal-entity level if you need it to. Either way, somebody signs a statutory account at the bottom of that structure, and a programme that treats the boundary as an inconvenience is arguing with the accounting.

One policy, one set of instructions per country

The workable shape is narrower than it sounds. The policy is shared and says what has to be true before an invoice is released for payment: the supplier is known, the amounts agree with the order and the receipt within an agreed limit, the tax treatment has been checked, and the approval sits with someone who has the authority.

The instructions that satisfy that policy are written once per country, because that's where the variation genuinely lives. Poland has run mandatory KSeF receipt for all businesses since February 2026, so a Polish invoice arrives through a national platform with a number attached. Italy has worked through the Sistema di Interscambio for years. Germany runs on different rules again. Instead of abandoning the standard, stop pretending one instruction fits twelve statutes.

The ERP stays where it is

The instinct to consolidate ledgers first is what turns a two-quarter programme into a three-year ordeal and burnt-out teams. The ERP remains master at posting, and that's a feature rather than a constraint to route around: whatever your agents or your people decide upstream, the system of record applies its own controls when the document posts.

Design for that on purpose. Reconcile the limits your process uses with the limits the ERP enforces, once per company code, and write down which one governs when they disagree. It's the narrower of the two, every time.

What the countries keep

This is the part that unblocks the meeting. Say it out loud before you ask anyone to adopt anything:

• The statutory sign-off. The named person on the local accounts stays the named person.
• The tax treatment. Local rules are applied locally, by whoever answers for them.
• The archive obligation. Retention and format follow the country, not the programme.
• The supplier relationship. Disputes, dunning and payment terms stay where the relationship lives.
• The right to be stricter. A country can tighten a limit. It cannot loosen the shared one.

Everything not on that list is a candidate for the shared standard. The list is short on purpose, and it's the reason the standard gets accepted.

One queue, one set of numbers, twelve sign-offs

What genuinely improves when this works is not the ERP landscape. It's that exceptions from every entity land in one queue with the same reason codes, so for the first time the programme can see that four countries share a supplier-master problem and one country has a genuine legal difference.

Before that, every entity had its own explanation for the same delay.

How Hypatos runs one policy across many ledgers

Hypatos was built for this shape rather than adapted to it. The invoice processing workforce carries the shared policy, the country instructions sit alongside it in plain language, and the e-invoicing validation skill handles the national formats and networks each entity is obliged to use.

The agents propose, a named person decides, and the record shows what was checked. That last part is what lets a group standard coexist with twelve local sign-offs, because the controller in Warsaw can see exactly what was applied to their invoice and why.

Hypatos fits when one policy has to run over several ERPs and several statutes without moving the accountability away from the person who signs the local accounts.

Which process goes first

Start with the country that has the most exceptions and the least legal difference. It gives you the shared instruction set fastest, and it gives the sceptical controller in the room something to look at that isn't a slide.

‍