TCP Logo

Turn any Epicor ECM document type into a working agent

Fluent reads the document types you already run in Epicor ECM: their custom fields, their repeating groups, their folders and their workflows. Pick one, and you have an agent that reads the incoming document, fills those fields and files it in ECM.

Book a demo

How it works

An agent for every document type you already run

Fluent builds agents from your ECM configuration, not from a fixed catalog. The document types, custom fields and workflows you have already defined are the specification.

Built from your ECM configuration

Fluent reads your instance and lists what is there: document types, their custom fields, the repeating groups that hold line tables, the folder tree, and the workflows a document can be routed into.

  • Document types and custom fields read live from your instance
  • Repeating custom-field groups become the agent's line tables
  • Filing folder and workflow set per agent, or left to the content type

The template defines the document, not the layout

An ECM document type says what a document is and which index values it carries. It does not say where those values sit on the page. Fluent reads each incoming document the way a person does, whatever the supplier and whatever the layout.

  • No per-vendor template, no field coordinates, no model retraining
  • PDFs, scans, photos, spreadsheets and email attachments read the same way
  • Corrections your reviewers make become instructions the agent follows

Filed in ECM with the index values already populated

The reviewed document is uploaded and created against the document type you chose, with header fields and line rows typed the way ECM expects. Mapping is deterministic: what a reviewer approves is what ECM stores.

  • Header values and line rows written as ECM custom field values
  • Each value typed to its field definition, read-only fields left alone
  • The document lands in its folder and starts its workflow on create

Coverage

Your ECM configuration is the specification

Fluent reads what your instance already has rather than asking you to describe it again.

Document types
Every content type configured on your instance, listed so you can pick the one an agent is built around.
Custom fields
The index fields on that document type, with their definitions, so values are written typed the way ECM expects.
Repeating groups
The groups that hold line tables become the agent's line rows.
Folders and workflows
The filing folder and the workflow a created document enters, set per agent or left to the content type.

Connectivity

Keep the keys to your own instance

Epicor-hosted or on your own servers, Fluent connects the same way: from outside, with credentials your team creates and can take back.

Cloud or on-premise
An Epicor-hosted instance usually needs no network change at all. A restricted network needs a short outbound allowlist, and nothing has to be opened inward.
Credentials you create
A dedicated integration account and an API key, both generated in Epicor by your team and held wherever you keep secrets. Revoke either and Fluent stops, without a call to us.
An access scope you assign
Each agent declares the services and methods it needs. You assign that scope to the account, and Epicor refuses anything outside it.
Encrypted before storage
Connection details are encrypted before they are stored. Nothing is kept in plaintext, including on our side.

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

An order over an amount or outside a price tolerance goes to the approvers who own it.

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.

Frequently Asked Questions

Any of them. Fluent lists the document types configured on your instance, along with their custom fields and repeating groups, and builds the agent around the one you select. A document type your team defined last month is as available as one that shipped with ECM.

No, and the distinction matters. An ECM document type is a schema: the class of document and the index fields it carries. A capture template is a layout: which field sits at which coordinate on which vendor's paperwork. Fluent uses the first and never builds the second, so a supplier redesigning their invoice changes nothing.

Feeding it. ECM remains the repository, the workflow engine and the system of record. Fluent does the reading and indexing a person would otherwise do at the capture step, then creates the document under your content type, security class and workflow. Destination is set per agent, so the same platform can post into Epicor Kinetic for one document type and file into ECM for another.

With the address your users already open in the browser, and either an ECM login or an Epicor IDP token. Fluent discovers the API server from that address, and outbound traffic leaves from a fixed IP your network team can allow through the firewall. Sessions are released after each call so concurrent-user licences are not held open.

Point Fluent at your ECM templates

Bring a document type you already run and the documents that arrive against it. We build the agent on your instance and show you the first one filing into ECM.

Book a demo