Matched to the receipts
Each invoice line is lined up against the receipt it bills, in the unit the receipt was taken in.
- The vendor behind the purchase order
- Each line against what was received
- Quantity and price differences on the line
Every supplier invoice vouched in Prophet 21
Supplier invoices arrive as PDFs, scans and email. Fluent reads each one, finds the purchase order and the receipts it bills, and drafts the voucher in the window your AP team would use: Convert PO to Voucher against receipts, Voucher Entry By Amount for expenses, and a debit memo for a vendor credit.
How it works
Match the invoice to what was received
The vendor, the purchase order and its receipts resolved against live P21 data, and every difference shown on the line it belongs to.
Checked before it drafts
Fluent catches what would make a voucher fail or post twice, before anyone presses save.
- An invoice number already vouched for the vendor
- Receipts already vouched
- Tax and freight against the invoice total
Ready for AP to release
Whatever could not be settled is named on the draft, and the voucher lands unapproved so AP releases it in P21.
- Unresolved lines named
- G/L accounts suggested from the vendor's history
- Every decision on the record
Comparison
No templates, no field mapping, no model training
Legacy document capture is configured per layout: a template for each vendor, a coordinate for each field, a model retrained when the paperwork changes. Fluent is configured in written instructions, and rewriting them changes what it does.
Legacy OCRAgentic automation
Templates
A template for every vendor, layout and document type
Reads each document the way a person does, whatever the layout
Field mapping
Fields found by position, so a moved column breaks extraction
No coordinates. It consults live Prophet 21 data before it writes
Model training
Models retrained on samples whenever a design changes
Corrections become instructions, so it improves without retraining
Exceptions
Exceptions fall out to a queue for manual keying
Reasons through variations and exceptions instead of failing
Changing behavior
Behavior changes through a configuration project
Behavior is set in written instructions you control
Governance
Autonomy you can hand to an auditor
Every agent operates inside boundaries you define. Every action it takes is recorded, explainable, and reversible before it posts.
Approval thresholds
A document over an amount or outside a price tolerance goes to the approvers who own it.
Audit logs
Every field the agent read, every decision it made, on the record.
Data retention
Your documents and data stay under retention policies you control.
Prophet 21 validation
Transactions are validated by Prophet 21 before they post.
Human review
Exceptions escalate to your team with the agent's reasoning attached.
Permissions
Agents only touch the documents and companies you allow.
Guides
Compare the options
How to Automate Voucher Entry in Epicor Prophet 21
The ways distributors take supplier invoices into Prophet 21 today, what each one leaves to AP, and how to automate vouchering against PO receipts.
Best AP Automation for Epicor Prophet 21 in 2026
The AP automation options that work with Prophet 21 as of November 2026, how each gets a supplier invoice into P21, and how to choose between them.
Three-Way Matching in Accounts Payable: How It Works and How to Automate It
Three-way matching compares invoice, purchase order and receipt before payment. Tolerances, manufacturing exceptions, and how each exception reaches the person who approves it.
Procure to Pay Process: Steps, Documents and How to Automate It
The procure to pay process for manufacturers and distributors: each step, the document that arrives, where it lands in Epicor Kinetic, and how approvals keep exceptions moving.
Prophet 21
Automate more of Prophet 21
Epicor Prophet 21
Order Entry
Customer purchase orders drafted as P21 orders, from the ship-to down to the contract price.
Frequently Asked Questions
Yes. The agent finds the purchase order the supplier invoice refers to, lines it up against what was received, and drafts the voucher in Convert PO to Voucher. Quantity and price differences are shown on the line they belong to, so an AP clerk sees exactly which item disagrees. Anything the agent could not resolve is named on the draft for a person to settle before it is saved.
The invoice waits. Prophet 21 can only voucher receipts that exist, so Fluent holds the invoice until the receipt is entered, up to the window you set, and then drafts the voucher. Nothing has to be sent again.
Not by default. Vouchers are created unapproved, so your AP team releases each one in Prophet 21 before it can reach a check run. A saved voucher can be reversed but not edited, so the default keeps that decision with AP. You can change it per agent.
They are drafted in Voucher Entry By Amount, one line per G/L account, with accounts suggested from how the vendor has been coded before. Tax and freight become their own lines. A vendor credit is drafted as a debit memo.
Ready to stop keying vouchers?
Send us a batch of the supplier invoices your AP team keys into Prophet 21. We will show you what an agent can match and voucher, and what still needs your judgment.
