Resolved against Epicor
Epicor addresses job material by assembly and material sequence, which no document carries, so Fluent matches against the job's own rows.
- Material rows on that job
- Units active for that part
- Accepted only on a single match
Issue material to the job without looking up the sequence
A PDF, a photo, an email or a dictated line arrives naming a job, a material and a quantity. Fluent posts it through Epicor Kinetic's Issue Material Entry screen, against the job material sequence it resolved and in the unit the source actually stated.
How it works
Issue material to the job without looking up the sequence
The material sequence resolved from the job itself, the unit confirmed for that part, and the transaction previewed in Epicor.
Previewed before it posts
Fluent runs the real Epicor issue transaction without committing, so the draft carries Epicor's own warehouse, bin and quantity answers.
- Warehouse, bin and date defaults
- Quantity on hand and job requirement
- Lot and serial rules from Epicor
Ready to review
Ambiguity holds the document instead of guessing, and one warning is enough to stop it posting automatically.
- Ambiguous lines held, never guessed
- Wording it cannot ground is an error
- One warning stops automatic posting
The difference
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 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
Low-risk orders post automatically; high-value or unusual ones wait for a person.
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 validation
Transactions are validated by Epicor’s own business logic before they post.
Human review
Exceptions escalate to your team with the agent’s reasoning attached.
Permissions
Agents only touch the business objects and companies you allow.
Customers
What customers are saying
“My dreams have been answered. … Check out Fluent. 10/10 customer service & ease of use!”
Bonnie KlassenPresident, Klassen Custom Metal Fabrication5agents in production
64 secaverage review time
98.6%extraction accuracy
“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
Automate other workflows
Erp.UI.QuoteEntry
See all agentsQuote Entry
Requests for quote drafted as Kinetic quotes, with customer part numbers resolved three ways.
Erp.UI.SalesOrderEntryOrder Entry
Customer purchase orders posted as sales orders, checked for duplicates before drafting.
Erp.UI.CustShipEntryCustomer Shipment
Shipping instructions become packs, every line resolved to its order release.
Erp.UI.ARInvoiceEntryAR Invoice Entry
Customer invoices and credit memos posted so billing stops waiting on a person.
Erp.UI.CashRecEntryCash Receipts Entry
Payments applied to the open invoices they settle.
Erp.UI.POEntryPO Entry
Vendor quotes and requisitions become purchase orders, priced in the vendor's own currency.
Erp.UI.ReceiptEntryReceipt Entry
Packing slips received against the purchase order line by line, in the unit the supplier shipped.
Erp.UI.APInvoiceEntryAP Invoice Entry
Supplier invoices matched two-way or three-way against the order and the receipt.
Erp.UI.TimeEntryTime Entry
Timesheets and shop paperwork posted against the right job and operation.
Frequently Asked Questions
Stop keying material issues
See Fluent draft one against your own job, your parts and your units of measure.
