Resolved against Epicor
The supplier, the parts and the open releases on the purchase order, confirmed against live data.
- Suppliers and their purchase points
- Parts and their lot tracking
- Open, unvoided order releases
Packing slips arrive as PDFs, scans and photographs, often photographed on the dock. Fluent reads them, matches every line to an open release on the purchase order in the unit the supplier shipped, and drafts the receipt in Epicor Kinetic Receipt Entry.
How it works
Every line matched to an open release on the order, in the unit the supplier actually shipped.
The supplier, the parts and the open releases on the purchase order, confirmed against live data.
Each line is matched on the balance still unreceived, and a printed unit that differs from the order's is restated using that order's own ratio.
The draft names every line Epicor could not confirm, so receiving is a check 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.APInvoiceEntrySupplier invoices matched two-way or three-way against the order and the receipt.
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 packing slips, however they arrive. Our Epicor specialists will show you what an agent can receive against the purchase order, and what still needs your judgment.