TCP Logo

Every customer payment applied in Cash Receipts Entry

Payment orders, single checks and bank exports arrive as PDFs, images or spreadsheets. Fluent resolves the payer and the invoices against live Epicor data, then drafts the receipt into Epicor Kinetic Cash Receipts Entry, in the currency the document states.

How it works

Tie every payment to the invoice it settles

The payer resolved from the document, and every invoice it cites checked against what Epicor still shows open.

Resolved against Epicor

The payer is resolved from the tax identifier on the document, and every invoice it references is looked up for that customer.

  • Customers, by tax identifier
  • Invoices, by their legal number
  • Only invoices Epicor still shows open

Balances checked against Epicor

Applications accumulate across the invoices a payment covers, and no invoice takes more than the balance Epicor holds for it.

  • The balance Epicor still shows open
  • What the document asks to apply
  • What is left of the payment

Ready to review

An invoice Epicor cannot confirm is applied at zero and named as unverified, rather than having cash applied to it.

  • Unverified invoices named on the draft
  • Overpayments left on account
  • The receipt group is created unposted

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

Stop keying cash receipts into Epicor

Send a real payment order and a real bank export, and see what Fluent drafts into Cash Receipts Entry.