A medical-device group operating several legal entities
Connecting the working system to the financial system
A group that chose Priority for finance did not have to abandon the working system it already ran on — a bidirectional synchronisation layer turned double entry into single entry.
- Integrations
- Priority ERP
- Multi-company
- Procurement
This customer is described by organisation type, as agreed with them.
Illustration of an integration monitoring dashboard connected to Priority ERP.
- Sector
- Medical devices
- Status
- Running in production.
The challenge
Procurement and budgets were managed in a spreadsheet-based working system. The group decided to implement an ERP for finance, but to keep working where decisions are actually made. In practice that meant recording everything twice — once where the decision is made, and once where the accounting record lives.
Why a standard implementation was not enough
Double entry is not merely wasted time. It creates two versions of the truth that drift apart slowly: an order approved in one place and never recorded in the other, an invoice approved but not updated. The standard answer — move all the work into the ERP and close the working system — is correct on paper and fails in practice, because the approval processes the organization built are the processes the work actually runs on.
Architectural approach
The architectural decision went the other way: leave the workflow where it already happens, make the ERP the financial source of truth, and connect them. Each service was defined in the same structure — trigger, input, action, output — and written for every entity in the group rather than for a single company.
What was delivered
- Bidirectional interface services between the working system and the ERP
- Vendor creation after quality approval, checking for an existing record before creating one
- Budget transfers between lines as a controlled operation
- Purchase-order creation, returning the order number to the working system
- An invoice approval round spanning both systems
- Guarded cancellation: the operation is refused and returns an error when the order is already closed or carries an invoice