Resolved against Epicor
The vendor, the parts and the order behind the invoice, confirmed against live data before anything is written.
- Vendors, by name and tax ID
- Parts, including the supplier's own numbers
- Purchase order lines and their receipts
Supplier invoices arrive as PDFs, scans, photographs, spreadsheets, XML or EDI, forwarded by your team or emailed straight to the agent. Fluent reads them, matches every line against the purchase order and the receipts behind it, and drafts the invoice in Epicor Kinetic AP Invoice Entry for a person to review.
How it works
Two-way and three-way matching against the purchase order and the receipts behind it, with every difference shown on the line.
The vendor, the parts and the order behind the invoice, confirmed against live data before anything is written.
Each line is tied to the receipt it bills, and what the invoice claims is checked against what Epicor holds.
The draft shows what matched, what did not, and every difference, so approving it is a decision rather than a re-entry.
The difference
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.
A template for every vendor, layout and document type
Reads each document the way a person does, whatever the layout
Fields found by position, so a moved column breaks extraction
No coordinates. It consults live Epicor data before it writes
Models retrained on samples whenever a design changes
Corrections become instructions, so it improves without retraining
Exceptions fall out to a queue for manual keying
Reasons through variations and exceptions instead of failing
Behavior changes through a configuration project
Behavior is set in written instructions you control
Governance
Every agent operates inside boundaries you define. Every action it takes is recorded, explainable, and reversible before it posts.
Low-risk orders post automatically; high-value or unusual ones wait for a person.
Every field the agent read, every decision it made, on the record.
Your documents and data stay under retention policies you control.
Transactions are validated by Epicor’s own business logic before they post.
Exceptions escalate to your team with the agent’s reasoning attached.
Agents only touch the business objects and companies you allow.
Customers
“My dreams have been answered. … Check out Fluent. 10/10 customer service & ease of use!”
Bonnie KlassenPresident, Klassen Custom Metal Fabrication“We started our implementation call at 4:30 yesterday. First sales orders processing by 4:50. Minimal mistakes out the box.”
“The Fluent team got connected very quickly and orders are flowing well. Some mistakes, but easy to resolve with some agent tweaks. Really impressive platform.”
Workflows
Requests for quote drafted as Kinetic quotes, with customer part numbers resolved three ways.
Erp.UI.SalesOrderEntryCustomer purchase orders posted as sales orders, checked for duplicates before drafting.
Erp.UI.CustShipEntryShipping instructions become packs, every line resolved to its order release.
Erp.UI.ARInvoiceEntryCustomer invoices and credit memos posted so billing stops waiting on a person.
Erp.UI.CashRecEntryPayments applied to the open invoices they settle.
Erp.UI.POEntryVendor quotes and requisitions become purchase orders, priced in the vendor's own currency.
Erp.UI.ReceiptEntryPacking slips received against the purchase order line by line, in the unit the supplier shipped.
Erp.UI.TimeEntryTimesheets and shop paperwork posted against the right job and operation.
Erp.UI.IssueMaterialEntryMaterial issued to the job without looking up the sequence by hand.
Send us a batch of supplier invoices, however they arrive. Our Epicor specialists will show you what an agent can match and post, and what still needs your judgment.