Non-PO Invoice Automation for Epicor Prophet 21 (P21)
Non-PO invoice automation for Prophet 21 handles the expense invoices that have no purchase order to match. An AI vision agentic system reads the invoice, GL accounts are proposed, the invoice is approved by rule, and the expense voucher is posted in P21.
What Counts as a Non-PO Invoice in P21
A non-PO invoice is a vendor invoice with no purchase order behind it: utilities, rent, freight carriers, professional services, subscriptions and other expenses. There is nothing to match it against, so the work is different from a PO invoice. Someone has to decide which GL accounts it belongs to and who must approve it.
ESS Fusion AI runs these invoices through their own pipeline, separate from PO invoices, because they need different checks.
GL Coding for Non-PO Invoices
After the invoice is read, GL accounts are proposed for each line. The vendor's own purchase accounts in Prophet 21 are tried first, then the chart of accounts. A reviewer confirms or changes the proposal, so the coding decision stays with your team.
- Accounts proposed from the vendor's purchase accounts, then the chart of accounts
- The distribution can be split by account and department, by amount or by percent
- The split must total the invoice before it can post
- Vendor, invoice number, date, terms and totals are read from any layout, with no template
Approval Routing by Rule
Approval workflows are set up on screen. A rule selects the workflow for an invoice, and the workflow defines who approves and in what order.
- Rules on invoice amount, vendor, department, freight and document type
- Sequential or parallel steps, with a required number of approvals per step
- Approvers named as a user, a role or an email address
- Approvers can decide from an emailed link, and can adjust the GL distribution first
- Reminders when a step is overdue
- An audit trail of who was notified and who decided
Posting the Expense Voucher in Prophet 21
Once approved, the invoice is posted in Prophet 21 as an expense voucher with its GL distribution, through ESS's API layer. Prophet 21 checks the invoice number for the vendor when the voucher is created, so a duplicate is stopped at posting. The voucher number is recorded against the invoice.
Intercompany and Multi-Company Invoices
Some expenses belong to more than one company. An intercompany expense voucher can be posted, and one invoice can be split across companies. The split can use percentages saved for that vendor, or a reviewer can enter the amounts, which must add up to the invoice total.
AP automation for Epicor Prophet 21FAQ
Non-PO Invoice Automation for Prophet 21 — FAQ
Non-PO invoice automation reads the expense invoice with AI vision, proposes GL accounts from the vendor's purchase accounts and the chart of accounts, routes the invoice for approval by rule, and posts an expense voucher in Prophet 21. A reviewer confirms the GL coding before the invoice posts.
Your team does. The system proposes accounts for each line, and a reviewer or approver confirms or changes them. The distribution can be split by account and department, by amount or percent, and it must total the invoice.
Yes. Approval workflows are selected by rules on invoice amount, vendor, department, freight and document type. Each workflow can have sequential or parallel steps, a required number of approvals, and reminders when a step is overdue.
Yes. An intercompany expense voucher can be posted in Prophet 21, and a single invoice can be split across companies using saved percentages for the vendor or amounts entered by a reviewer.
In two places. The file is checked when it arrives, so the same document is not processed twice. Prophet 21 then checks the invoice number for the vendor when the voucher is created.
No. ESS provides its own simplified API layer for Prophet 21, with 150+ endpoints, so expense vouchers post without licensing the Epicor API module separately.
See a Non-PO Invoice Coded and Posted in P21
Send us an expense invoice. We will read it, propose the GL coding and post the expense voucher in a P21 test environment.
