How to Test AP Automation on Your Own Epicor Kinetic System: A Pilot Checklist
Which supplier invoices to send in a 30-day trial, what to compare against your baseline, a pass/fail scorecard, who signs off, and what a trial cannot show.
Gonzalo Nuñez
Chief Technology Officer

To test AP automation on Epicor Kinetic, run Fluent's 30-day trial on its AP Invoice Entry agent, against your own Epicor instance, with the supplier invoices your team finds hardest today. A trial run that way answers the questions a demo cannot: whether the drafts match your purchase orders and receipts, how often a reviewer has to change a field, and whether the exceptions reach the right person before anything is written to Epicor. If you also want supplier payments run from the AP tool, test a payments product alongside it, because Fluent leaves payment in your ERP and bank process.
This checklist covers what to set up before the trial, which invoices to send, what to measure, a pass/fail scorecard, who signs off, and what 30 days cannot show you.
What the trial includes
- One agent, on your Epicor. The AP Invoice Entry agent runs against your own Kinetic instance, cloud or on-premise, with a credit balance included. You only start paying when the trial converts.
- Two onboarding sessions. A 30-minute technical call connects Epicor, and a functional session trains the people who will approve the drafts.
- A customer success manager. Regular sessions during the trial turn your team's corrections into written instructions for the agent.
- Nothing installed in Epicor. Fluent connects through Kinetic's REST API from outside, with a dedicated integration account and an access scope your Epicor administrator imports.
- A person approves every invoice. Drafts wait in Fluent's review queue, and nothing is written to Epicor until someone approves the draft.
Before the trial starts
- Create the integration account and API key in Epicor, and import the agent's access scope in Security Management. On-premise, allow Fluent's fixed IP addresses.
- Decide how invoices arrive. Forward them from the AP mailbox, or have suppliers email the agent directly.
- Write the approval rules in plain language: invoices with no purchase order go to the requester, invoices priced above the order go to the buyer, anything over an amount you choose goes to the controller.
- Record your baseline. Minutes to key one invoice today, how long an approval takes, and how many exceptions AP clears in a typical week. Without a baseline, the trial produces impressions instead of a comparison.
- Keep receipts current. A three-way match is only as good as the receiving record, so make sure Receipt Entry is up to date for the purchase orders in your test set.
Which invoices to send
Send the invoices that cost your team time today. A clean, single-line invoice from your best supplier proves little.
| Invoice | Why it belongs in the set | What a pass looks like |
|---|---|---|
| Your hardest suppliers | Scans, photos, multi-page invoices, unusual layouts | Supplier, invoice number, dates and lines read correctly, with no template set up |
| Purchase order invoice for received goods | The everyday three-way match | Each line tied to the receipt it bills, quantity and price agreeing with the purchase order |
| Invoice with no purchase order | Services, utilities, one-off purchases | Drafted without a purchase order, saying so, and routed by your rule for invoices with no purchase order |
| Partial receipt | The order shipped in pieces | Only the quantity received and not yet billed is drafted, with the difference shown on the line |
| Price above the purchase order | Surcharges, annual increases, errors | The line shows the difference in amount and percentage, and your rule sends it to the buyer |
| Freight and miscellaneous charges | Freight, fuel surcharges, setup fees | Shown as separate charges on the draft, kept out of the line prices |
| Credit memo | Returns, rebates, price corrections | Drafted as a debit memo, without waiting for a receipt |
| Duplicate | An invoice your team already entered, sent again | A possible duplicate warning on the invoice number before anything is written |
| Invoice before receipt | The supplier billed faster than the dock received | The invoice waits for the receipt and drafts once it is entered, or a person continues without waiting |
| Different unit of measure | Billed by the box, received by the each | The unit difference is stated on the line, with no false quantity difference |
Twenty to forty invoices across these rows is enough for a first week. Add volume once the hard cases pass.
What to measure
- Fields changed at review. How often a reviewer had to change something Fluent read. Fluent's document analytics show it per document.
- Review time per invoice, set against your baseline keying time.
- Exceptions caught. Duplicates, price differences and quantities billed but not received that would otherwise have reached the payment run.
- Three-way match outcomes. Share of lines tied to a receipt on the first pass, and the reason for each one that was not.
- Routing. Whether every exception reached the person who owns it, with a note on what to check.
- Approval time. From the invoice arriving to the draft being approved, including approvals by email.
- Administration. What your Epicor administrator had to grant, change or maintain during the trial.
Pass/fail scorecard
| Check | Pass | Fail |
|---|---|---|
| Reading | Reviewers rarely change a field on your hardest suppliers | Reviewers rekey the same fields invoice after invoice |
| Matching | Lines tied to the right receipts, including partial and split receipts | Lines matched to the order quantity instead of the received quantity |
| Exceptions | Every difference stated on the line it belongs to | Differences absorbed into a total, or missing |
| Duplicates | Caught before anything is written to Epicor | Found later in the payment run |
| Routing | Price differences reach the buyer and invoices with no purchase order reach the requester, by your written rules | Everything lands on one person |
| Review time | Clearly below your baseline keying time | No faster than keying |
| Control | Nothing reaches AP Invoice Entry without an approval, and the audit log shows who approved what | Drafts written to Epicor before review |
| Administration | Nothing installed in Epicor, and access limited to the scope your administrator imported | Customizations or broad access required |
Who signs off
- AP lead: the drafts, the review time and the exception queue.
- Controller: the approval rules, the tolerances written into them and the audit log.
- Buyer: that price differences arrive with the right purchase order and enough context to decide.
- Epicor administrator and IT: the access scope, the integration account and that nothing was installed.
At day 30, keep the agent if it earned its place. If it did not, cancel and pay nothing.
What a 30-day trial cannot show
- Seasonal peaks. Year-end, quarter-end and annual price increases may fall outside the trial window.
- Rare suppliers. A supplier who invoices twice a year may not appear at all. Send an old invoice from them instead.
- Annual savings. Thirty days gives you a measured review time and approval time; the annual figure is a projection from those, and should be presented as one.
- An audit cycle. The audit log is there from the first invoice, but your auditors will judge it at year-end.
- Receipt timing you have not fixed. If receipts are entered days late, invoices wait. That is a receiving process to fix, and automating Receipt Entry from packing slips is the usual next step.
Customer results
Metalworks, a Michigan manufacturer on Epicor since 2010, ran this kind of test on its own AP invoices. Fluent connected to Epicor in a day. Reviewers rarely had to change a field Fluent read, entering an invoice went from seven or eight minutes of keying to under a minute of review, and an approval that took about five minutes on paper now takes seconds from an email. Read the Metalworks story.
Start the trial
The AP automation page covers the AP Invoice Entry agent, three-way matching works through the exceptions above, and how long AP automation takes lays out the onboarding phase by phase. Plans and credits are on the pricing page. To plan a trial on your own invoices, book a demo.
Frequently Asked Questions
Run Fluent's 30-day trial on its AP Invoice Entry agent against your own Epicor instance, with the supplier invoices your team finds hardest: partial receipts, price differences, freight, credit memos, duplicates and invoices with no purchase order. Record your baseline keying and approval times first, then compare fields changed at review, review time and exceptions caught.
Only after a person approves them. Every invoice waits as a draft in Fluent's review queue, and nothing is written to AP Invoice Entry until someone approves the draft.
Nothing. The 30-day trial includes a credit balance, and you only start paying when the trial converts. Paid plans start at $600/month.
The ones that cost your team time: your hardest suppliers' layouts, partial receipts, prices above the purchase order, freight and miscellaneous charges, credit memos, an invoice already entered, invoices that arrive before the receipt, and invoices billed in a different unit of measure.
Create a dedicated integration account and API key, import the agent's access scope in Security Management, and on-premise allow Fluent's fixed IP addresses. Nothing is installed inside Epicor, and the technical setup is one 30-minute call.
Seasonal peaks such as year-end, suppliers who invoice rarely, a full audit cycle and annual savings. Thirty days gives you measured review and approval times; the annual figure is a projection from them. Send old invoices from rare suppliers to cover what the window misses.


