All case studiesProduction 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

Growth goal

Grow volume across four European markets without replacing the systems each market runs.

Operating constraint

The systems did not exchange data, so orders, goods receipts, invoices and payments were re-keyed by hand.

Measured result

60% less manual entry and one real-time view of orders, stock and payments across the four markets.

Summary

Challenge: A supplier invoice was typed into the goods receipt by hand, lot by lot. Bank statements were matched to invoices line by line. Orders were entered a second time before a warehouse could ship, and group figures were compiled from four separate extracts.
What SIEL built: An integration layer on the Dynamics 365 standard API and each legacy system's own interface, with product codes mapped across them. On top of it, AI reads supplier invoice PDFs into goods-receipt lines with lot numbers and expiry dates and checks them against the purchase order, matches bank statement lines to open invoices, and drafts purchase orders when stock falls below its threshold.
Controls: Every message through the layer is logged with its source and result. Every AI proposal, a goods receipt, a payment match, a reorder, waits for a person to confirm or change it, and the decision is recorded next to it.
Impact: A new market joins by connecting its existing systems to the layer, without migrating to a common ERP.

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.

Florian Obadan, Regional Director, Bredent Medical

The full account

01The requirement: keep every local system

Each market's team worked in its own ERP, Dynamics 365 in some markets and older local systems in others, and knew those tools well. The requirement was to keep every local system and make them behave as one operation. That set the design. Data would move between the existing systems rather than into a new one, and every movement had to be traceable back to the transaction that caused it.

02Where AI bridges the gap

Four places where a person used to retype what another system already knew. A supplier delivery arrives with a PDF invoice: the model reads it into goods-receipt lines, with lot numbers and expiry dates, and checks them against the purchase order; the warehouse confirms by scanning the boxes. A clinic orders: the order is built from live stock and the customer's prices, picked by scan, invoiced and filed with the tax authority without a second entry. The bank statement comes in: the model proposes which open invoice each payment settles, and accounting confirms the matches instead of searching for them. Stock runs low: the system drafts the purchase order per supplier for a buyer to approve.

03What the group has now

Manual data entry in commercial operations is down 60%. Orders, stock and payments across the four markets are visible in real time instead of being assembled from reports. When a figure looks wrong, operations or IT follow the layer's log to the transaction that produced it. Where people correct a proposal, the correction shows what the model still gets wrong.

Discuss Your Operation With Our Engineers.

Describe one workflow and the systems it relies on. A senior engineer responds within two business days with an initial assessment: what we would build, what we would not, and why.