ERP automation guide
Prophet 21 Invoice and AP Automation
By Airdev. We build custom AI order entry for distributors running Prophet 21: built to match your exact process, owned by you, with no per-order fees. This guide is what we've learned doing it.
AP in Prophet 21 can be automated, and unlike sales order capture, this side has a verified Epicor answer: ECM's AP workflows genuinely work with P21, reading vendor invoices with intelligent data capture and matching them against PO data. Without a layer like that, the AP side mirrors manual order entry, with vendor invoices arriving as PDFs and someone keying them into Convert PO to Voucher by hand.
Whether ECM, Conexiom, or a custom extraction layer fits you comes down to how consistent your vendor invoices are and how you feel about per-document pricing. All three end the retyping, and in all three a person still approves the voucher.
How AP entry works in P21 today
The native workflow is Convert PO to Voucher. You enter the vendor ID on the voucher information tab, and the receipt screen lists that vendor's purchase orders in a grid; if one invoice covers several receipts, you select multiple lines and they populate the voucher together. Then you key the invoice date, the invoice amount including freight, the invoice number, the total freight, and the period and year. Freight can be prorated by weight or by quantity only. The vouch-all checkbox comes checked by default, and there are tabs to attach the invoice document, set AP accounts, and confirm vendor terms and discounts.
One gotcha deserves bold text in your AP team's runbook: once you convert a PO to a voucher, you can no longer do a reverse PO receipt on it, even if you only paid for one item on that receipt. Clearing unvouchered receipts against POs is a known admin headache on the P21 forums, and basic receiving questions there sometimes get zero replies.
What Epicor ECM actually does for P21 AP
This is the part of the ECM story that verifies cleanly for P21. Epicor publishes P21-specific training for two AP workflows. IDC, intelligent data capture, uses AI-based document capture to read and classify vendor invoices, including supplier-specific date formats, and it covers both PO-backed and non-PO invoices. PNP, pull and present, matches incoming invoices against PO data. The integration handles real distribution wrinkles, like drop-ship scenarios and branch IDs on non-PO invoices. Epicor's marketing claims up to 90 percent AP processing-time reduction, which we'd treat as directional rather than a promise, but the product itself is real and P21-supported.
If your invoice formats are reasonably consistent and you want a single-vendor answer, evaluate ECM first. The sales order side is the opposite story: Epicor sells an ECM order capture product too, but the deployments we can find documented are on its other ERPs, not P21, so ask that question separately if you're evaluating both.
The other routes: Conexiom and custom
Conexiom handles AP invoices against P21 with published validation logic for field matching and tolerances, and its July 2026 Epicor partnership explicitly covers AP invoices alongside orders. Expect per-document or subscription pricing.
A custom extraction layer earns its keep in the situations template-based capture struggles with: vendor invoices that vary wildly in format, tolerance and matching logic specific to your business, or the wish to run order intake and AP intake through one system you own rather than two subscriptions. The mechanics mirror our order entry approach. The system reads the invoice, matches it against the PO and receipts, flags anything off tolerance, and stages the voucher for a person to approve. Nothing posts without that sign-off.
Budget for one P21-specific wrinkle on the custom route. The Transaction API posts transactions without interactive prompts, but in practice it throws UI-shaped errors that automation has to handle, and Convert PO to Voucher is a documented offender: its receipts-matching browse has a blank tab page name that breaks the API's addressing convention, and the community thread reporting it (February 2026) is still unanswered. The API is also licensed separately from P21. None of this is a blocker, but it rewards teams who have built against P21 before.
A note on three-way matching
P21's voucher conversion matches the invoice against PO receipts through the receipt screen, which is the heart of a three-way match. What we could not find documented natively is tolerance-based automatic matching, the kind that approves an invoice within half a percent of the PO without a person looking at it. That logic shows up in the layers on top: ECM's matching workflows and Conexiom's price, freight, and total tolerance validations. If tolerance-based auto-approval is what you're after, plan on one of those layers rather than a native P21 setting.
Frequently asked questions
Want this for your Prophet 21?
Built around your exact process and your Prophet 21. You own it, with no per-seat or per-order fees.