How Long Does It Take to Implement AP Automation with Epicor Kinetic?
A phase-by-phase timeline for AP automation on Epicor Kinetic, from the first call to go-live, and the decisions on your side that take longer than the software.
Gonzalo Nuñez
Chief Technology Officer

With Fluent, AP automation on Epicor Kinetic starts on the first call: technical setup is one 30-minute session that leaves Fluent connected to your instance, a second session trains the people who approve invoices, and a 30-day trial on your own invoices follows. What takes longer is rarely the software. It is the work around it on your side: duplicate vendor records, deciding who approves what, agreeing how large a price difference AP will accept, and, on an on-premise instance, your own IT change process for allowing Fluent's IP addresses. A project-led route such as Epicor ECM AP Automation takes longer to stand up, and fits better when you also want Epicor's own document archive and approval workflows.
The short answer
- Connected: one 30-minute technical session with your Epicor administrator and IT.
- First invoices drafted: in that opening session, on your own documents.
- Approvers trained: a second session, functional onboarding, on the invoices they already handle.
- Proven on your own invoices: a 30-day trial on one agent, against your own Epicor instance.
- Live: when the agent has earned its place, and you add the next workflow when your team is ready.
Why the software part is short
Most of what makes an AP automation project long is configuration per vendor: a template for each layout, a coordinate for each field, a model retrained when the paperwork changes. Fluent has none of that. The agent reads each invoice the way a person does, whatever the layout, and behavior is set in written instructions. When a reviewer corrects a draft, the correction becomes an instruction.
Nothing is installed inside Epicor either: no customization, no BPM, no staging table and no import file. Fluent calls Epicor's own REST API from outside, so there is nothing to deploy, test through an upgrade or uninstall later. Deploying Fluent is not a consulting engagement, and there is no separate services agreement to scope or sign.
Phase by phase
| Phase | Who takes part | What happens | How long |
|---|---|---|---|
| Demo | Your AP lead, and Fluent's Epicor specialists | You send a batch of your own invoices. We run them and show what the agent drafts, and what it hands back for a person to decide. | One meeting |
| Before setup | Your Epicor administrator and IT | Create a dedicated integration account and an API key, and confirm the Epicor endpoint is reachable. On-premise, allow Fluent's fixed IP addresses. | Set by your own change process |
| Technical onboarding | Your Epicor administrator and IT, with Fluent | Create your Fluent team, import the agent's access scope in Security Management, test the connection together and pick the agent for the trial. | One 30-minute call |
| Functional onboarding | AP staff and approvers | Train the people who will approve the drafts, on the documents they already handle. | One session |
| Trial | Your AP team, with a dedicated customer success manager | One agent against your own Epicor instance, with a credit balance included. Regular sessions tailor the agent's instructions to the way your team works. | 30 days |
| Go live | Your AP team | Keep the agent if it earned its place. You only start paying when the trial converts. | When the trial converts |
What takes longer, and how to shorten it
None of the items below has to be finished before you start. Each one is a reason an invoice waits for a person, so each one you settle early makes the trial look more like the months that follow.
Vendor master clean-up
Fluent matches the vendor on each invoice by name and tax ID against your vendor master. Duplicate vendor records and vendors with no tax ID leave room for doubt, and when no vendor matches, the agent drafts the invoice with a note of what it searched for and waits for a person to choose. Merging the duplicates you already know about, and filling in missing tax IDs for your biggest suppliers, removes the most common question before the trial starts.
Receipts entered on time
Three-way matching compares the invoice with the purchase order and the receipts behind it in Epicor. If receiving falls behind, invoices arrive before their receipts and wait. Fluent offers only the quantity still left to bill, so an invoice for goods nobody has received yet shows the gap on the line. If receiving is the bottleneck, Receipt Entry automation drafts packing slips against the purchase order line by line.
Approval routing
Deciding who signs which invoice is a policy decision inside your company, and it usually involves people outside AP: controllers, buyers, plant managers. Fluent's approval stages pick each approver by name, by workload, from a shared queue, or by having the AI find the right person, such as the buyer on the purchase order. Conditions are written in plain language, such as "invoices with no purchase order", and out-of-office approvers are routed to a delegate. Writing the rules takes minutes once they are agreed, so agree them before the trial.
Price and quantity differences
Fluent compares quantity against what is left to bill and unit price against the order, and records every difference on the line rather than absorbing it. What your team does with a difference is yours to decide: which differences AP clears, and which go to a buyer. A document over an amount or outside a price tolerance goes to the approvers who own it, so write that threshold down as an approval condition.
Training
Functional onboarding is one session, because reviewing a Fluent draft means checking the flagged lines rather than keying the invoice again:
Network changes for on-premise Epicor
An Epicor-hosted instance usually needs no network change at all. An on-premise instance needs Fluent's fixed IP addresses allowed on the Epicor endpoint and nothing else opened. That change is small, but if firewall changes go through a change board, raise the request when you book onboarding so it does not hold up the first call. Self-signed certificates work, though a valid certificate is better. The guide to how AI agents connect to Epicor Kinetic covers each hosting option.
What customers saw
Metalworks, an Epicor Kinetic manufacturer in Ludington, Michigan, handed its AP invoices to Fluent's agents. It connected in a day, and reviewers rarely had to change what it read. Read the Metalworks story.
On order entry, Luceco saw the same pattern on its first call:
We started our implementation call at 4:30 yesterday. First sales orders processing by 4:50. Minimal mistakes out the box.
Richard Gardner · Group IT Director, Luceco
How other routes compare
Routes that need a build, such as an integration on the Kinetic REST API or Service Connect and Automation Studio workflows, take longer to stand up, and they fit when your invoices already arrive as structured data and a developer will own the code. Epicor ECM AP Automation is usually a project run by Epicor or a partner, and fits when you want Epicor's own archive and workflows; Fluent can do the reading inside it. The guide to automating Epicor AP Invoice Entry compares seven routes on setup effort, and the best AP automation for Epicor Kinetic compares the vendors.
How to plan your first 30 days
- Before the demo, collect a batch of real invoices, including the awkward ones: a partial shipment, a freight line, a supplier's own part numbers and an invoice with no purchase order.
- Before technical onboarding, have your Epicor administrator create the integration account and API key, and on-premise, have IT allow Fluent's IP addresses.
- Write your approval rules as plain sentences: who approves what, above which amount, and who covers when someone is away.
- Merge the duplicate vendors you already know about.
- During the trial, correct drafts in review rather than in Epicor, so each correction becomes an instruction.
- At the end, set the review time against the minutes your team spends keying an invoice today, with the ROI calculator.
Customer results
Metalworks, a family-owned manufacturer in Michigan on Epicor since 2010, runs its AP invoices through Fluent. Fluent connected to Epicor in a day, and reviewers rarely change a field it read. Keying an invoice took seven to eight minutes; reviewing the draft now takes under a minute, and an approval that took five minutes now takes seconds, from an email. “It’s like a breath of fresh air,” says Jill Schoedel, IT Manager.
Where to start
Read about Fluent AP automation and how Fluent connects to Epicor. Paid plans start at $600/month, after a 30-day trial. To see an agent draft your own supplier invoices and set dates for onboarding, book a demo.
Frequently Asked Questions
With Fluent, technical setup is one 30-minute call that leaves Fluent connected to your Epicor instance, a second session trains the people who approve invoices, and a 30-day trial on one agent follows on your own invoices. What takes longer is usually on your side: cleaning up duplicate vendors, agreeing approval rules, and allowing Fluent's IP addresses on an on-premise instance.
No. Deploying Fluent is not a consulting engagement, and there is nothing to scope, staff or sign alongside the subscription. Onboarding is two meetings, and a dedicated customer success manager holds regular sessions to tailor the agent's instructions to the way your team works.
Create a dedicated integration account and an API key in Epicor, and confirm the Epicor endpoint is reachable. On-premise, allow Fluent's fixed IP addresses on that endpoint; an Epicor-hosted instance usually needs no network change. On the setup call, your administrator imports the agent's access scope in Security Management.
No, but it helps. Fluent matches each vendor by name and tax ID, so duplicate records and missing tax IDs leave room for doubt. When no vendor matches, the invoice is drafted with a note of what was searched and waits for a person to choose. Merging the duplicates you already know about removes the most common question.
Yes. The 30-day trial runs one agent against your own Epicor instance, with a credit balance included, and you only start paying when the trial converts. A person approves every invoice in Fluent before anything is written to Epicor.
One session, functional onboarding, on the invoices your team already handles. Reviewing a draft means checking the flagged lines: the median review time in production was 55 seconds per document, across 25,359 documents reviewed in the 90 days to 1 September 2026.


