Match every supplier invoice to the order and the receipt.
Three-way matching automation checks each supplier invoice against the purchase order and the goods receipt before it is posted, without a person comparing the three documents by hand. It is the heart of accounts payable automation: Elentaria reads invoices as they arrive in the accounts payable inbox, matches every line to the PO and the receipt in the ERP your team already runs, posts the ones that agree, and sends the differences to the person who decides.
Reads
Supplier invoices arriving as PDF attachments or email text in the accounts payable inbox, including invoice number, supplier details, line items, quantities, unit prices, tax and the purchase order reference.
Checks
Each invoice line against the purchase order and the goods receipt in the ERP: price, quantity, unit of measure, tax, supplier name and bank details, and whether the same invoice has been received before.
Writes
Matched invoices posted in the ERP, or prepared for posting where your rules require a final sign-off, with the invoice, the purchase order and the goods receipt linked on the record.
To a person
Invoices with a price or quantity difference, no goods receipt, an unknown supplier or a possible duplicate, sent to the named approver with the differing lines and values listed.
From invoice received to invoice posted.
Elentaria connects invoice intake, purchase order and receipt matching, exception handling, posting and supplier communication so an invoice is read once and every later step works from the same record.
Capture the invoice wherever it arrives.
Elentaria watches the accounts payable inbox and turns each supplier invoice into a structured case: which supplier, which purchase order, which lines, and what is being charged.
PDF attachments, scanned invoices, email text, credit notes and invoices forwarded by colleagues, including invoice number, date, due date, line items, quantities, unit prices, tax and totals.
Supplier matching against the vendor master in the ERP, VAT or tax numbers, bank details compared with the record on file, and invoices from suppliers not yet set up.
Purchase order number read from the invoice or found from the supplier, amount and dates, and invoices with no order reference set aside for a person.
- Invoice received
- Document read
- Supplier identified
- PO found
- Case created
Compare every line with the order and the receipt.
Before anything is posted, Elentaria matches each invoice line to the purchase order line and the goods receipt line in the ERP, within the tolerances your finance team has set.
Unit price against the PO price, invoiced quantity against the received quantity, unit of measure, currency, discounts and freight or surcharge lines.
Tax rate and amount per line, invoice total against the matched lines, rounding differences and partial invoices against partial receipts.
Same invoice number, amount or date from the same supplier, and differences inside or outside the tolerance your rules allow.
- PO lines matched
- Receipt lines matched
- Tax checked
- Duplicates checked
- Result recorded
Route every difference to the person who decides.
Invoices that do not match are not posted on a guess. Elentaria holds them, puts the order, the receipt and the invoice side by side, and asks the responsible person with the differences listed.
Price above the PO, quantity above the receipt, missing goods receipt, unknown supplier, changed bank details and possible duplicates, each shown with the invoice line, the PO line and the receipt line.
Approve, reject, ask the supplier for a credit note or wait for the receipt, recorded against the case and applied in the ERP once made.
Questions to the buyer or the warehouse when the receipt is missing or the quantity differs, sent from the case so the answer stays with the invoice.
- Difference identified
- Documents gathered
- Approver asked
- Decision applied
- Case updated
Post the invoice in the ERP, once, with the documents linked.
Elentaria posts matched and approved invoices in the ERP you already run, or prepares them for posting where your rules require a final sign-off, and keeps the payment run informed.
Supplier invoice posted against the purchase order and the receipt, with cost centres, tax codes and payment terms taken from the order and the vendor master.
The invoice PDF, the purchase order and the goods receipt attached to the posted record so an auditor can see all three from one place.
Due date and early payment discount recorded, invoices on hold marked as such, and the payment run given only what has been matched or approved.
- Invoice approved
- Posted in ERP
- Documents linked
- Due date recorded
- Ready for payment
Tell the supplier what happened to the invoice.
Elentaria answers supplier queries and sends the requests that follow from a match result, from the same case, so accounts payable is not reconstructing the history from an inbox.
Replies to suppliers asking whether an invoice has been received, approved or scheduled for payment, with the invoice reference and the expected date.
Requests for a credit note, a corrected invoice or a missing purchase order reference, sent once the approver has decided.
Remittance details sent when payment is made, and the full history of the invoice, the match and the messages kept on one record.
- Query received
- Status found
- Reply sent
- Correction requested
- History kept
Automate the matching. Keep the payment decisions.
Elentaria does the reading, matching and posting of invoices that agree with the order and the receipt; rules, approvals and exceptions decide how work moves, and paying a difference stays with the person you have named.
Price and quantity differences outside tolerance, invoices without a purchase order and new suppliers wait for the named approver.
Missing receipts, unknown suppliers, changed bank details and possible duplicates are held and routed, never posted on a guess.
Every invoice shows where it came from, which PO and receipt it was matched to, what differed, who decided and whether it is posted or waiting.
Common questions
What is three-way matching automation?
It is the work of checking a supplier invoice against the purchase order and the goods receipt before it is posted or paid, without a person comparing the three documents by hand. Elentaria reads the invoice, matches every line to the order and the receipt in the ERP a company already runs, posts the invoices that agree, and sends the differences to the person who decides, with the company's tolerances and approval rules applied.
Which invoice formats can Elentaria read?
PDF attachments, scanned invoices, invoices typed into the email body, credit notes and invoices forwarded by colleagues. Supplier details are matched against the vendor master in the ERP, purchase order references are read from the invoice or found from the supplier and amount, and invoices that cannot be matched with confidence go to a person.
Does Elentaria replace our ERP?
No. The ERP stays the system of record. Elentaria reads purchase orders, goods receipts and the vendor master from it, posts or prepares matched invoices in it, and links the three documents on the record, so nothing about your stack changes.
Which tools do teams compare for this work?
Teams looking at invoice and order document automation usually compare Esker, Conexiom and Parseur. Our sourced comparisons are at https://elentaria.ai/compare/conexiom-vs-esker, https://elentaria.ai/compare/best-esker-alternatives and https://elentaria.ai/compare/parseur-vs-conexiom.
How do we get started?
Bring ten recent supplier invoices with their purchase orders and receipts to the demo. Elentaria is set up on your tolerances, vendor master and approval rules for that flow, scoped on a live demo, and extended from there.
See how Elentaria would run your invoice matching.
Bring ten recent supplier invoices with their purchase orders and receipts to the demo. See them matched line by line, posted where they agree and routed to your approver where they do not.