AP invoice automation
Supplier invoices matched two-way or three-way against the order and the receipt, with every difference shown on the line.
AP automation for Epicor Prophet 21 and every customer order into Order Entry
Distributors on Prophet 21 key supplier invoices and customer purchase orders from inboxes full of PDFs. Fluent reads each one and drafts it where a clerk would: supplier invoices in Voucher Entry, matched to the purchase order and its receipts, and customer orders in Order Entry. A person reviews every draft before it is saved.
Agents
Automate Voucher Entry and Order Entry
Two agents for Prophet 21, built and available today: supplier invoices for accounts payable, and customer purchase orders for inside sales.
Sales order automation
Customer purchase orders drafted as sales orders, checked for duplicates before anything is written.
Validation
Check every document against Prophet 21 before it is saved
Each agent resolves what the document says against your live P21 data and drafts it in the window your team already uses, with every difference shown on the draft.
Supplier invoices in Voucher Entry
The invoice is tied to the purchase order it bills and to what was received against it.
- The supplier and the purchase order behind the invoice
- Each line against what was received
- Quantity and price differences on the line
Customer orders in Order Entry
The customer's purchase order becomes a draft order, checked before anything is written.
- Customers and ship-tos resolved
- Items, including the customer's own part numbers
- Existing orders on the same customer PO flagged
Ready to review
Whatever could not be settled is named on the draft, so a reviewer sees the open questions and nothing else.
- Unresolved items named per line
- Nothing saved until a person approves it
- 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 Epicor 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.
Epicor Prophet 21 validation
Transactions are validated by Epicor 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.
ERPs
Automate documents in other ERPs
- Epicor Kinetic
- SAP Business One
- SAP S/4HANA
- Oracle NetSuite
- Acumatica
- Dynamics 365 Business Central
- Dynamics 365 Finance and Supply Chain
- Odoo
- Infor SyteLine
- Infor M3
- Infor LN
- Infor VISUAL
- Plex
- QAD
- IFS Cloud
- SYSPRO
- Sage Intacct
- Sage X3
- Sage 100
- Sage 300
- Oracle Fusion Cloud ERP
- JD Edwards
- Global Shop Solutions
- JobBOSS²
Frequently Asked Questions
Yes. The agent finds the purchase order the supplier invoice refers to, lines it up against what was received in Receipts, and drafts the voucher in Voucher Entry. 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, such as an unknown supplier item number, is named on the draft for a person to settle before it is saved.
The agent reads the customer's purchase order, resolves the customer, their ship-to and each item against your live P21 data, including the customer's own part numbers, and checks for an existing order with the same customer PO before drafting. The draft order appears in Order Entry with every unresolved item called out. Your inside sales team reviews it and saves it, so nothing reaches the order book without a person approving it.
Our engineers connect Fluent to your Epicor Prophet 21 company during onboarding and run each agent against test documents before it writes to production. The agents read your own vendors, customers, parts and open orders from Epicor Prophet 21, and only touch the companies and documents you allow.
Not unless you choose that. By default every agent drafts the transaction and waits for review. An approval workflow routes each document to the people who sign off on it, with thresholds such as an amount or a price variance deciding who reviews what, and every decision the agent made is recorded on the document.
PDFs, scans, photographs, spreadsheets, email bodies, XML and EDI, forwarded by your team or emailed straight to the agent. There are no templates to build per vendor or customer: each document is read the way a person reads it, whatever the layout.
What would you hand an agent in Epicor Prophet 21 first?
Send us a batch of the documents your team keys into Epicor Prophet 21 today. We will show you what an agent can match and post, and what still needs your judgment.
