Epicor projects usually turn into a middle layer. A platform pulls Prophet 21 data somewhere else, does the clever part there, and pushes an answer back. Now there are two systems of record and a sync to mind, and the first time they disagree, nobody trusts either one.
We build the other way around. The tool works against P21 itself, on the records your team already works on, and puts its output where those people already look. We have done this in a live P21 every morning for a distributor in our own group.
Margin and rebate checks that run every morning inside Epicor P21.
01
The integration that survives is the one nobody has to open a second window for.
Your ERP is where the orders, the invoices, the contracts, and the pricing actually live. An automation that copies all of that somewhere else inherits every problem of a second copy: staleness, drift, and an argument about which number is real.
Building against P21 avoids the argument. There is nothing new for your people to learn, nothing extra for IT to secure, and no second version of the truth to reconcile at month-end.
02
A tool can read everything in P21 and still be trusted to write almost nothing.
Reads come through supported paths and stay read-only by default, which is how a tool starts being useful without anyone gambling on a live ERP. From that the tool builds its picture: what was ordered, what was invoiced, what the contract said it should have been.
Writes are deliberately small. The tool proposes a specific entry or update, a person approves it, and it goes through the route your Epicor partner would sanction, with a record of who approved what. If a job cannot be written back safely, it stays a flag and a person does the entry.
03
The rebate-and-margin tool we built inside Kelsan, a multi-state distributor in our own group, runs every morning in its Epicor P21. It reads the rebate terms out of the contracts, checks each invoice line against them, and hands the finance team a short exception list with the contract language beside every item. It moves no money on its own, and it has surfaced the margin the manual check was missing since the day it went live.
Proof
Margin and rebate checks that run every morning inside Epicor P21.
Runs daily inside Kelsan, a multi-state distributor in our own group.
It reads contract terms and checks invoice lines inside a live Prophet 21 every morning, and it writes nothing a person has not approved.
Scope
Read access through supported paths, in your tenant, against your data.
Emailed and PDF orders drafted as entries for a person to confirm.
Contract terms compared against what was actually invoiced.
Narrow, logged writes that happen only after a person says yes.
A short morning list in place of a quarterly reconciliation.
Your Epicor partner kept in the loop on anything touching the ERP.
FAQ
Connecting automation or other tools to Epicor so they work with its live records rather than copies of them. In our builds the tool reads P21 directly, drafts the work, and writes back only what a person approves.
Yes. The rebate-and-margin tool we run inside Kelsan is a P21 build in daily production. Other Epicor products and other ERPs follow the same pattern wherever they expose their data.
It should not. We build alongside what you have instead of customizing the core, use supported access routes, and keep your partner informed. Nothing we add should make an upgrade harder.
Most P21 data is messy. The fixed-fee audit looks at the real tables and the real process and says which jobs are clean enough to automate. Sometimes the honest verdict is to fix the data first.
AI Integration
ERP automation built inside the system you already run, Epicor P21 or otherwise: order entry, daily checks, and reports that run on their own.
generative ai integration servicesGenerative AI integration services: we wire AI into the software you already run so it reads and writes real records, not a chat window off to the side.
One fixed fee. A build-or-don’t-build verdict in writing.