Approval thresholds
Low-risk orders post automatically; high-value or unusual ones wait for a person.
Invoices, orders, packing slips, quotes and payments, read and posted into the Kinetic screen they belong in. Ten screens today, covering quote to cash and purchase to pay end to end.
Workflows
Automating one screen saves one person an afternoon. Automating the cycle it sits in is what changes the month end. Each of these posts through the same business object the Kinetic screen uses.
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.
Vendor 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.APInvoiceEntrySupplier invoices matched two-way or three-way against the order and the receipt.
How it works
Forwarded by email, sent straight to the agent's own address, or dropped in. PDFs, scans, photographs, spreadsheets and EDI.
Header, lines and charges, in whatever layout the sender used. No template, no field coordinates, nothing to maintain per vendor.
Customers, vendors, parts, units and open balances resolved against live data through the same business objects the screen uses.
Every run ends in a draft carrying what it could not settle. Nothing posts unattended, and anything unresolved is named on the document.
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.”
Send us a batch of sample documents. Our Epicor specialists will show you what an agent can automate, and what still needs your judgment.