Phase one deliberately had no integration at all. That was the point.
An education technology group operating across five countries needed procurement and invoicing under control.
A group growing that fast across that many markets has a sequencing problem. Integrate first and you are wiring together processes that are still changing. Wait for the processes to settle and you never start.
Phase one delivered procurement and invoicing with no integration at all. That was deliberate: get the process live, get people using it, and find out what the rules actually are in each market before committing them to interfaces.
Phase two then built the integration onto a process that had stopped moving — invoice, payment, supplier information management, supplier and accounts data flowing between the platform and the finance system.
A platform administration service ran alongside, with change requests handled as the rollout extended, and application managed services covering the group's own users and its suppliers. The engagement has run since 2021.
Valtatech is software vendor agnostic. The technology named here is what this client selected; we start from requirements, operating model and existing systems. See how we approach integration →
Sequencing is the decision most implementations get wrong by default, because integrating everything at once looks like efficiency. It is usually the opposite: interfaces built against a process still in flux get rebuilt, and the rebuild is rarely budgeted.
Talk to us about what this would look like in your business.
Start a conversation