Epicor IDC Alternative: Fluent with Epicor ECM, from capture to approval

Fluent is an alternative to Epicor Intelligent Data Capture (IDC), the capture layer of Epicor ECM AP Automation, and it works alongside Epicor ECM. Keep ECM for the document archive, its workflows and retention, and let Fluent do the reading in place of IDC: it reads each invoice, matches it against the purchase order and receipts in Kinetic, drafts it in AP Invoice Entry, and files the document into ECM with the index values populated. Before anything reaches Epicor, Fluent adds an approval workflow in which an approval agent checks the invoice for each approver before they open it. Teams without ECM can use Fluent on its own.

What each product does

Epicor ECM AP Automation is Epicor's own AP product, built on Epicor ECM (formerly DocStar). It combines three things that are worth separating, because they are separate decisions:

• Capture. Reading the invoice and pulling out its fields. In Epicor's stack this is Intelligent Data Capture (IDC).
• Document management. Storing, indexing and retrieving the invoice and everything attached to it, with retention. This is ECM itself.
• Workflow. Routing the document for review and approval. ECM workflows handle this.

Fluent takes on the first of those jobs, goes further into Kinetic than a capture layer usually does, and adds its own approval step before the document reaches Epicor. Fluent's AP agent reads the invoice, resolves the vendor, parts, purchase order and receipts against live Kinetic data, drafts the invoice in AP Invoice Entry, and routes it to the people who sign off, with an approval agent checking it for each of them first. For the archive it files into ECM: Fluent's ECM document agent builds an agent from any ECM document type you already run, fills that type's custom fields and line rows, and files the document with the index values populated.

Fluent vs IDC at the capture layer

This is the real comparison. ECM stays in both columns.

"Ask Epicor" means we could not confirm the answer from Epicor's public positioning. Ask for a demo on your own invoices.

How the two work together

Fluent's Epicor ECM integration turns ECM document types into agents. A typical AP flow looks like this:

1. Invoices are emailed or forwarded to the Fluent agent.
2. The agent reads the invoice and finds the vendor by name and tax ID.
3. It matches each line against the purchase order and the receipts behind it: quantity against what is left to bill, unit price against the order, and freight never billed twice. On partial shipments it offers only the quantity still left to bill.
4. It prepares the invoice draft for AP Invoice Entry, with every difference shown on the line.
5. It files the document into ECM with the index values populated, and can send it to an ECM workflow, so ECM keeps the archive, workflows and retention it already handles.
6. It routes the invoice through Fluent's approval stages. Conditions are written in plain language, such as "invoices with no purchase order", and an approval agent reviews the invoice for each approver with read-only lookups in Epicor, marking it "nothing flagged" or "needs review" with a note on what to look at. Nothing is written to Epicor while an approval is pending.
7. Approvers decide in Fluent or by replying to the approval email: approve, reject, or return the invoice to AP with a reason. Out-of-office approvers are routed to a delegate, and every decision is in the audit log. A person processes the draft, and nothing posts before that.

If no vendor matches, the invoice is drafted with a note of what was searched and waits for a person. Fluent also validates invoices with fiscal authorities such as SAT (Mexico), DIAN (Colombia) and SEFAZ (Brazil).

Fluent's approval step sits before the document reaches Epicor. The approval agent has already read the invoice against Kinetic and tells each approver what to look at. Where an approver allows it, the agent approves on their behalf when nothing is flagged, and if its review fails the invoice goes to a person, so nothing is approved silently. Once approved, the invoice is created in AP Invoice Entry through Kinetic's own business logic, and ECM's workflows carry on from there.

Metalworks runs its AP invoices through Fluent's agents in Epicor Kinetic. Read the Metalworks story.

What gets installed

Epicor ECM is a document management system, so it is infrastructure you run or have hosted, with its own administration. That is part of its value: it is a system of record for documents.

Fluent installs nothing inside Epicor. It calls Epicor Kinetic's REST API from outside, with no customization, no BPM, no staging table and no import file. It works on premise or Epicor-hosted; restricted networks allowlist Fluent's fixed egress IPs. Each agent generates an Epicor access scope listing exactly the services it calls, which you import so Epicor enforces least privilege. Setup is about thirty minutes of accounts and onboarding, and most teams review documents the same day.

The archive is a real reason to keep ECM

ECM is more than AP. It stores and indexes documents across the business: invoices, packing slips, contracts, quality records, whatever your team files. If auditors, customers or your own staff pull documents out of ECM today, that is a reason to keep it, and Fluent is built to work with it.

Fluent keeps an audit log of every field it read, every decision it made and every approval, including who signed on whose behalf. That answers "why did the agent draft this line this way, and who approved it?" It is not a company-wide document repository; keep ECM for that.

Beyond AP

ECM document types are not limited to invoices, and neither are Fluent agents. Fluent has agents for ten Epicor Kinetic screens: Quote Entry, Order Entry, Customer Shipment, AR Invoice Entry, Cash Receipts Entry, PO Entry, Receipt Entry (packing slips), AP Invoice Entry, Time Entry and Issue Material. A customer purchase order or a packing slip stored in ECM can be read and drafted into Kinetic the same way.

Which option to choose

• You run ECM and IDC, and neither capture, matching nor approvals slow you down: stay where you are.
• You run ECM, and the slow part is correcting capture, keying lines, matching to receipts or checking invoices before sign-off: keep ECM for the archive, and use Fluent in place of IDC for capture, matching and approvals.
• You do not run ECM, and you need a company-wide document archive: add ECM for the archive, and use Fluent for capture, matching and approvals from the start.
• You do not run ECM, and you only need AP entry and matching in Kinetic: Fluent on its own is enough. It runs the approval workflow and keeps the audit log, and your original documents stay wherever you keep them today.
• You want one vendor for everything: Epicor's own stack keeps it to one vendor. TCP, the company behind Fluent, is an Epicor Platinum Partner, but Fluent is a separate product with its own contract.

In a demo on your own invoices, test the step after capture as hard as capture itself:

• Route an invoice to two approvers by a rule written in plain words, such as "invoices with no purchase order".
• Set an approver out of office and see where the invoice goes.
• Approve by replying to the approval email.
• See what was flagged for each approver before they open the invoice.

Try it with your ECM setup

The ECM integration is described on Fluent for Epicor ECM, the AP agent on AP automation, and the Kinetic connection on Epicor integration. Paid plans start at $600/month, with usage metered in credits (pricing). To see Fluent on your own invoices and ECM document types, book a demo.