All customer storiesProduction system
Four European markets, run as one commercial operation.
Bredent Medical ran four European markets on separate Dynamics 365 and legacy systems, and every order, delivery and payment was typed in more than once. One integration layer now moves the data between the systems. AI reads supplier invoices, matches purchase orders and bank payments, and a person confirms each step. Manual entry fell 60% and the group got its first real-time view across all four markets.
- Client
- Bredent Medical
- Sector
- Healthcare, commercial operations
- Engagement
- Production system
- Measured result
- 60%less manual entry
Open the workspaceSample data. No live systems connected.
REC-402Delivery 02, implant kitsSample data
- On supplier invoice INV-402
- 260 units
- On purchase order PO-402
- 300 units
- Scanned at the dock
- 260 units
60%less manual entry
We ran four markets on systems that did not talk to each other. SIEL connected them without replacing anything, and for the first time we see all four in one view. The retyping went with it.
The full account
01The requirement: keep every local system
Each market ran its own ERP: Dynamics 365 in some, older local systems in others. Orders were keyed in twice, and group figures came from four separate extracts. The brief was to keep every system and run the four markets as one operation.
02One integration layer, AI at the handoffs
An integration layer links the Dynamics 365 standard API and each legacy system's own interface, with product codes mapped across them. AI reads supplier invoice PDFs into goods-receipt lines with lot numbers and expiry dates, and checks them against the purchase order. It matches bank payments to open invoices and drafts purchase orders when stock runs low. Clinic orders are picked by scan, invoiced and filed with the tax authority without a second entry.
03What the group has now
Manual entry is down 60%, and orders, stock and payments across the four markets are visible in real time. Every AI proposal waits for a person to confirm or change it. That decision is recorded, and every message through the layer is logged with its source and result. A new market joins by connecting its existing systems, with no move to a common ERP.