Three-Way Match for Epicor Prophet 21 (P21)
Three-way match in Prophet 21 means every vendor invoice line is checked against the purchase order and the receipt before a voucher posts. ESS Fusion AI automates that 3-way match for P21: an AI vision agentic system reads the invoice, compares it with the open PO under your tolerances, and vouchers only what was received.
How the 3-Way Match Works in P21
The 3-way match in P21 compares three things for every vendor invoice line: what the invoice bills, what the purchase order agreed, and what the warehouse received. ESS Fusion AI runs that check in two steps, and both use live Prophet 21 data.
First, the invoice is compared with the purchase order. Each invoice line is paired with its PO line by item, then quantity, unit price and unit of measure are compared under the tolerances you set. Second, the voucher is created from the PO receipts through Prophet 21's own Convert PO to Voucher process, so the invoiced quantity on a line can never exceed the quantity received. An invoice that bills for more than was received does not post.
- Invoice to purchase order: item, quantity, unit price and unit of measure, line by line
- Invoice to receipt: each voucher line is capped at the received quantity in P21
- Header checks: vendor, PO number, invoice total and freight
- A full match can post with no one touching it; anything else goes to a reviewer
Two-Way and Three-Way Invoice Matching in Epicor
Two-way and three-way invoice matching in Epicor Prophet 21 answer different questions. Two-way matching checks the invoice against the purchase order only. It suits services, drop shipments and other purchases where no receipt is recorded. Three-way matching adds the receipt, and it is the right control for stocked goods.
In ESS Fusion AI the choice is configuration. Each document type runs through its own pipeline, so PO invoices for stock can require the receipt while service invoices are matched to the PO alone. You do not have to pick one rule for every vendor.
Invoice, PO and Receipt Matching for Distributors
Invoice, PO and receipt matching for distributors is harder than the textbook version, because the three documents rarely line up one to one. ESS Fusion AI is built for the cases a distribution AP team sees every day in Prophet 21.
- Partial shipments: the voucher covers what was received, and the rest of the PO stays open
- Unit of measure differences: an invoice in cases against a PO in eaches is vouchered in the invoice's unit of measure
- Price changes: the invoice cost is carried to the voucher line, and the variance is checked against your price tolerance
- One invoice across several purchase orders: the voucher can be created for a vendor and a list of PO numbers
- Freight on the invoice: entered on the voucher and prorated across the lines by quantity
- Lines that repeat the same item: paired by a reviewer when the system cannot tell them apart
Match Tolerances You Control
A match is only useful if you decide what counts as close enough. Tolerances in ESS Fusion AI are set per field on a configuration screen, not buried in code.
- Exact match, an absolute amount, a percentage, or a date window of plus or minus a number of days
- A severity for each field, so a price variance can stop an invoice while a date variance only warns
- Auto-approve when every field matches, with the option to post automatically after approval
- A per-vendor block, so chosen vendors always get a human review
When a Line Does Not Match
Every line gets a status: full match, variance, exception, a new line that is on the invoice but not the PO, or a missing line that is on the PO but not the invoice. The reviewer sees the invoice PDF beside the Prophet 21 values, field by field, with the difference shown.
From there the reviewer can pair lines by hand and re-run the match, correct a value, approve, reject, or send the invoice into an approval workflow. Approval rules can route on invoice amount, vendor, department or freight, with sequential or parallel approvers and reminders when a step is overdue. Every step is recorded on the document's timeline.
When the Invoice Arrives Before the Receipt
Vendors often invoice on shipment, so the invoice reaches AP before the goods reach the dock. With no received quantity in P21, there is nothing to voucher against, and the three-way match cannot pass.
ESS Fusion AI can park the invoice instead of failing it. The pipeline re-checks Prophet 21 on a schedule, resumes by itself once the receipt is posted, and notifies AP if the invoice is still waiting when the deadline passes. Nobody has to remember to try again.
Packing slip and receiving automation for Prophet 21Three-Way Match Reporting for AP
Matching is also a reporting question. The AP workspace in ESS Fusion AI reports on three-way match results, price variance, freight, and receipts that have been received but not invoiced, so the controller can see where invoices stall and which vendors cause the exceptions.
See the full Prophet 21 AP automation flowFAQ
Three-Way Match in Prophet 21 — FAQ
A three-way match in Prophet 21 checks each vendor invoice line against the purchase order and the receipt before a voucher is created. The invoice says what the vendor billed, the PO says what was agreed, and the receipt says what arrived. ESS Fusion AI automates all three checks against live P21 data and only sends an invoice to a person when something does not agree within your tolerances.
In two steps. It compares the invoice with the purchase order line by line, on item, quantity, unit price and unit of measure. Then it creates the voucher from the PO receipts through Prophet 21's own Convert PO to Voucher process, which caps every line at the quantity received. If the invoice bills for more than was received, the voucher is not posted and the invoice is routed for review with the reason.
Two-way matching compares the invoice with the purchase order. Three-way matching also compares it with the receipt. Use two-way matching where no receipt exists, such as services or drop shipments, and three-way matching for stocked goods. ESS Fusion AI lets you set this per document type, so both run side by side in Epicor Prophet 21.
In ESS Fusion AI. Tolerances are configured per field as an exact match, an absolute amount, a percentage or a date window, each with its own severity. An administrator changes them on a configuration screen, and every change is logged.
The invoice cannot be vouchered until Prophet 21 has a received quantity for the PO line. ESS Fusion AI can park the invoice, re-check P21 on a schedule and resume automatically once the receipt is posted. If the receipt has not appeared by the deadline you set, AP is notified.
Yes. When a vendor bills several purchase orders on one invoice, the voucher can be created for that vendor against a list of PO numbers, and each line is still capped at what was received on its PO.
No. ESS provides its own simplified API layer for Prophet 21, with 150+ endpoints, so the match and the voucher posting work without licensing the Epicor API module separately.
See a Three-Way Match Run on Your Own Invoice
Send us a vendor invoice and its PO number. We will match it against the PO and the receipt and post the voucher in a P21 test environment.
