TCP Logo

Fluent automates the documents you key into Epicor

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.

How it works

Every run ends in a draft you approve

  1. 01

    It arrives

    Forwarded by email, sent straight to the agent's own address, or dropped in. PDFs, scans, photographs, spreadsheets and EDI.

  2. 02

    It gets read

    Header, lines and charges, in whatever layout the sender used. No template, no field coordinates, nothing to maintain per vendor.

  3. 03

    It is checked against Epicor

    Customers, vendors, parts, units and open balances resolved against live data through the same business objects the screen uses.

  4. 04

    A person decides

    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

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.

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 Fabrication
5agents 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.”
Richard GardnerGroup IT Director, Luceco
“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.”
Will BoltonSenior IT Technician, ILIV Interior Textiles
Read more on EpiUsers.help

Ready to Save Hours Every Week?

Send us a batch of sample documents. Our Epicor specialists will show you what an agent can automate, and what still needs your judgment.