Supplier confirmation matching

Match every supplier confirmation to the purchase order it answers.

Supplier order confirmation matching automation is the work of reading each order confirmation a supplier sends back and checking it, line by line, against the open purchase order in the ERP. Elentaria reads confirmations from the procurement inbox, compares price, quantity, part number, unit and delivery date with the PO, writes confirmed lines and new dates back to the ERP, and brings every change to the buyer with the confirmation and the PO side by side.

A desk with a monitor showing a technical drawing, a wall planner behind it and pens in a wooden holder

Reads

Supplier order confirmations arriving as PDF attachments or email text in the procurement inbox, including the supplier's reference, the PO number, line items, quantities, unit prices, units and confirmed delivery dates.

Checks

Every confirmed line against the open purchase order in the ERP: price, quantity, part number, unit of measure and delivery date, with partial and split confirmations matched to the PO lines they cover.

Writes

Confirmed lines, confirmed dates and the supplier's reference to the purchase order in the ERP, and a flag on each customer order that depends on a line whose date or quantity changed.

To a person

Lines with a price change, a split or late delivery, or a part number the PO does not carry, handed to the buyer with the confirmation and the PO side by side and the exact values that differ.

The confirmation matching workflow

From confirmation received to purchase order updated.

Elentaria connects confirmation intake, line matching, change detection, the buyer's decision and the PO update so each confirmation is read once and the purchase order, the ERP and the dependent customer orders all reflect it.

01 — Confirmation intake

Find the confirmation and the order it answers.

Elentaria watches the procurement inbox, recognises which messages are order confirmations, and pairs each one with the open purchase order it refers to before any line is compared.

Read the document

PDF attachments, confirmations typed in the email body, scanned copies and supplier portal exports, including the supplier's order number, the PO number, line items, quantities, prices, units and dates.

Find the purchase order

PO number matched to the open orders in the ERP, supplier identified from the sender and the document, and confirmations that quote no PO number matched on supplier, items and quantities.

Handle the rest

Duplicate confirmations, a second confirmation that replaces a first, confirmations for a PO already closed, and messages that are not confirmations at all, each recorded or routed without slowing the queue.

  1. Email received
  2. Confirmation recognised
  3. Document read
  4. PO found in ERP
  5. Case opened
02 — Line matching

Compare every line with the PO.

Elentaria places each confirmed line against the purchase order line it answers and compares the five fields that decide whether the order is confirmed as placed: part number, quantity, unit, price and delivery date.

Pair the lines

Supplier part numbers mapped to your part numbers, PO line references, descriptions and quantities used to pair lines when the supplier renumbers or reorders them.

Compare the fields

Unit price, extended price, quantity, unit of measure and confirmed delivery date compared with the PO values, with currency, pack size and tolerance rules applied the way your buyers apply them.

Record the match

Lines that match within tolerance marked confirmed, lines with a difference marked with the field and the two values, and lines missing from the confirmation listed as unconfirmed.

  1. Lines paired
  2. Part numbers checked
  3. Price and quantity compared
  4. Dates compared
  5. Match recorded
03 — Change detection

Separate a clean confirmation from a changed one.

Elentaria sorts each difference by what it means for the order: a rounding difference inside tolerance is not the same as a later date on a line a customer order is waiting for.

Classify the difference

Price increases and decreases, short and over-confirmed quantities, split deliveries, later or earlier dates, substituted or unknown part numbers and changed units, each measured against the tolerances your rules set.

Trace the impact

Customer orders, production orders and stock reservations in the ERP that depend on the affected PO line, and the delivery promise each of them carries.

Prepare the question

The PO line, the confirmed line, the difference, the downstream impact and the supplier's own note, assembled so the buyer can decide from one screen.

  1. Differences classified
  2. Tolerances applied
  3. Dependent orders traced
  4. Impact recorded
  5. Question prepared
04 — Buyer decisions

Route each change to the buyer who decides it.

A price change, a split or late delivery or an unknown part number is not accepted on the supplier's word. Elentaria brings it to the buyer with the confirmation and the PO side by side and applies the answer.

Decide

Accept the change, reject it, or reply to the supplier with a question or a counter, recorded against the case with who decided and when.

Reply to the supplier

Acceptance, rejection or a request for a corrected confirmation sent to the supplier from the case with the PO reference and the lines in question.

Escalate

Changes that break a customer promise or pass a spend threshold routed to the person your rules name, and open questions to the supplier chased until they are answered.

  1. Change presented
  2. Buyer decides
  3. Supplier answered
  4. Decision recorded
  5. Follow-up scheduled
05 — PO update and downstream

Write the result to the ERP and warn whoever depends on it.

Once the lines are confirmed or the buyer has decided, Elentaria updates the purchase order in the ERP and flags the customer orders and schedules that the confirmed dates and quantities affect.

Update the PO

Confirmed quantities, prices, dates and the supplier's reference written to the purchase order lines in the ERP, with the confirmation document attached to the order.

Flag downstream

Customer orders, production orders and stock reservations that depend on a changed line flagged in the ERP, and the responsible sales or planning person informed of the new date or quantity.

Close and learn

Case closed with the full history of the match, and supplier performance on confirmation time, price changes and date changes recorded for the next order.

  1. PO lines updated
  2. Confirmation attached
  3. Customer orders flagged
  4. Owners informed
  5. Case closed
Your team stays in control

Automate the matching. Keep the supplier decisions.

Elentaria reads, pairs and compares; your rules, approvals and exceptions decide how work moves. Accepting a higher price, agreeing a later date or taking a substitute part stays with the buyer.

Approvals

Price changes, quantity changes, split or late deliveries and substitutions wait for the buyer or the person you have named, with thresholds set per supplier or per spend.

Exceptions

Unreadable confirmations, confirmations with no matching PO, unknown part numbers and a second confirmation that contradicts the first are held and routed, never matched on a guess.

Visibility

Every purchase order shows whether its confirmation arrived, which lines matched, which differ, who is deciding and what has been written to the ERP.

Common questions

What is supplier order confirmation matching automation?

It is the work of reading each order confirmation a supplier sends back, usually as a PDF or an email, and checking it line by line against the open purchase order in the ERP: price, quantity, part number, unit and delivery date. Matched lines are recorded in the ERP, and any difference is sent to the buyer with the confirmation and the PO side by side. Elentaria runs this from the procurement inbox and the ERP the company already uses, with its own tolerances and approval rules applied.

Which confirmation formats can Elentaria read?

PDF attachments, confirmations written in the body of an email, scanned copies and exports from supplier portals, in the supplier's own layout and numbering. Supplier part numbers are mapped to yours, and confirmations that quote no PO number are matched on supplier, items and quantities. A confirmation that cannot be paired with confidence goes to the buyer instead of being matched on a guess.

Does Elentaria replace our ERP?

No. The ERP stays the system of record for the purchase order. Elentaria reads the open PO from the ERP the company already runs, writes the confirmed lines, dates and references back to it, and attaches the confirmation document. Nothing about the procurement system changes.

Which tools do teams compare for this work?

Order confirmation matching is usually evaluated alongside order entry tools, because the same document reading sits under both. The comparisons at https://elentaria.ai/compare/conexiom-vs-esker, https://elentaria.ai/compare/esker-vs-workist and https://elentaria.ai/compare/workist-vs-conexiom cover the tools most procurement teams shortlist and where each is the better choice.

How do we get started?

Bring five real supplier confirmations and the purchase orders they answer to the demo. Elentaria is set up on your suppliers, tolerances and approval rules for that flow, scoped on a live demo, and extended from there.

See how Elentaria would match your supplier confirmations.

Bring five real supplier confirmations and the purchase orders they answer to the demo. You will see each one read, matched line by line and written back to the PO, with the differences routed to your buyers.