Skip to content

Purchase order matching

Supplier invoice in, goods receipt out. Nothing retyped.

The model reads the supplier's PDF into goods-receipt lines with lot numbers and expiry dates, checks them against the purchase order, and flags every difference. The warehouse confirms with a scan. Nothing enters stock and nothing is paid until the documents agree or a person has explained why.

Discuss your invoice matchingWhere it slows down

Running in production at Bredent Medical, across four European markets.

Proven in production60%less manual entry at Bredent Medical, across four marketsTested on real deliveries, not a demo file. ↗

Where it slows down

Every delivery is typed in twice.

  • PDF to receipt by hand

    Supplier invoices retyped line by line into the goods receipt.

  • Lots and expiry dates

    Copied from paper, where one wrong digit breaks traceability weeks later.

  • Invoice and order disagree

    Quantities, prices and terms that differ, found late or not at all.

  • Back-orders nobody tracks

    Short deliveries that leave the purchase order open without anyone noticing.

  • Double or wrong payments

    Money paid twice or at the wrong amount, then chased back.

  • The exceptions eat the day

    The one delivery in ten that does not fit takes most of the time.

Proven in production

Tested on real deliveries, not a demo file.

less manual entry at Bredent Medical, across four markets
60%less manual entry at Bredent Medical, across four markets
of supplier invoices matched automatically at a beverage manufacturer
94%of supplier invoices matched automatically at a beverage manufacturer
from invoice to payment instead of three days, at that same manufacturer
15 minfrom invoice to payment instead of three days, at that same manufacturer
invoices a month through a running finance workflow
2,500+invoices a month through a running finance workflow

Bredent Medical is named with permission. The other figures come from production systems for clients we do not name.

Read the Bredent Medical case

How we start

One supplier group, real invoices. Then the rest.

  1. 01

    Pick the flow

    One supplier group or one warehouse with volume and a person who owns it.

  2. 02

    Run it on your invoices

    The model reads last month's real supplier PDFs, so you see what it gets right before anything goes live.

  3. 03

    Connect it

    To your ERP, purchase orders and scanners. Approval steps stay where your policy puts them.

  4. 04

    Add suppliers and sites

    The next flow goes faster than the first. Your team owns every rule.

Works with what your team already runs

  • Dynamics 365
  • SAP
  • NetSuite
  • Legacy and local ERPs
  • Supplier PDFs by email
  • Barcode scanners
  • Excel and CSV

Why SIEL

We spent years automating finance with rules. We know where rules stop.

Your systems stay
We connect the ERPs you run instead of replacing them.
AI reads, code checks
The model reads messy PDFs. Deterministic code compares quantities, prices and lots.
People confirm
Anything outside tolerance or policy goes to a named person with the reason.
Fixed fee
Agreed before we start. We tell you when AI is not the right answer.

Start the conversation

Which deliveries take the longest to book in?

Tell us the suppliers, the ERP and the monthly volume. A senior engineer reads it and replies within two business days.

  • No generic sales sequence.
  • Fixed fee, agreed before we start.
  • We tell you when AI is not the right answer.