TCP Logo

Every supplier invoice posted into AP Invoice Entry

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

Match every supplier invoice before it posts

Two-way and three-way matching against the purchase order and the receipts behind it, with every difference shown on the line.

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

Quantities and prices compared

Each line is tied to the receipt it bills, and what the invoice claims is checked against what Epicor holds.

  • Quantity against what is left to bill
  • Unit price against the order
  • Freight never billed twice

Ready to review

The draft shows what matched, what did not, and every difference, so approving it is a decision rather than a re-entry.

  • Every difference shown on the line
  • Unmatched values named, never guessed
  • Nothing posts until a person processes it

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

Frequently Asked Questions

What would you hand an AP agent first?

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.