TCP Logo

Every packing slip received against the purchase order line

Packing slips arrive as PDFs, scans and photographs, often photographed on the dock. Fluent reads them, matches every line to an open release on the purchase order in the unit the supplier shipped, and drafts the receipt in Epicor Kinetic Receipt Entry.

How it works

Receive the packing slip against the purchase order

Every line matched to an open release on the order, in the unit the supplier actually shipped.

Resolved against Epicor

The supplier, the parts and the open releases on the purchase order, confirmed against live data.

  • Suppliers and their purchase points
  • Parts and their lot tracking
  • Open, unvoided order releases

Quantities and units compared

Each line is matched on the balance still unreceived, and a printed unit that differs from the order's is restated using that order's own ratio.

  • Quantity against the balance still open
  • The unit the supplier shipped
  • A slip already received is flagged

Ready to review

The draft names every line Epicor could not confirm, so receiving is a check rather than a re-entry.

  • Unmatched parts and units named per line
  • Lot numbers checked against the part
  • 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

Ready to Simplify Your Receiving Process?

Send us a batch of supplier packing slips, however they arrive. Our Epicor specialists will show you what an agent can receive against the purchase order, and what still needs your judgment.