Nobody loses a distributor’s margin in one place. A rebate tier gets crossed and never claimed. A price file stops following the contract. A line is keyed at the wrong unit of measure. Each miss is trivial on its own, and across a year and every branch they are the difference between a good year and a flat one.
We know this one from the inside. Kelsan, a multi-state distributor in our own group, runs a tool we built inside its Epicor P21 that checks those things every morning before anyone opens the branch.
Margin and rebate checks that run every morning inside Epicor P21.
01
Somebody has to compare what was agreed against what was actually billed, at distribution volume.
Rebates, contract pricing, freight terms, and invoice accuracy all need the same thing: somebody comparing what was agreed against what actually happened, line by line. Done by hand that is impossible at volume, so it becomes a sample check, done late, by whoever has an afternoon.
None of it surfaces on a dashboard either, because the system that would have to notice is the same system the detail is buried in. The result is a business that knows its margin is leaking without being able to point at where.
02
The ERP is the system of record, so that is where the checking belongs.
We build inside Epicor P21 rather than beside it. The tool reads the same orders, invoices, and contracts your people read, and puts what it finds where those people already look. No second database, no sync to mind, and nothing anyone has to remember to run.
It reads and it flags. Anything that would change a record waits for a person, and the write is narrow and logged. A distributor cannot afford a tool that quietly edits an order, and neither can we.
03
A purchasing manager opens a short exception list instead of a report nobody had time to build: these lines missed a rebate term, this customer was billed on the wrong basis, this order arrived as an email and is drafted and waiting for confirmation. A few minutes of judgment, in place of a quarterly scramble or a check that was not happening at all.
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 checks every invoice line against the rebate terms in Kelsan’s contracts each morning and surfaces the margin the manual check was missing.
Scope
Vendor and customer terms read from the contracts and checked daily.
Lines priced off contract or billed on the wrong basis, flagged next morning.
Emailed and PDF orders drafted into the ERP for a person to confirm.
Invoices checked against purchase orders line by line.
Checks that used to wait for month-end, run every morning instead.
The recurring reports produced without anyone assembling them.
FAQ
Software that does the checking a distributor cannot staff: reading contracts and comparing them against every order and invoice, drafting entries, and flagging exceptions. It lives inside the ERP and hands its findings to a person.
No, though it is where we have the most miles. The tool we run every day is a Prophet 21 build, and the same approach fits other distribution ERPs that expose their data.
No. Pricing, credits, and order changes stay with your people. The tool puts the exception in front of the purchasing or branch manager who owns that account, with the contract language beside it, and waits. When they approve an entry, the write is logged under their name.
The read-only part earns its place first, because an exception list is worth something before a single record changes. The fixed-fee audit tells you what is realistic on your data before anyone commits to a build.
One fixed fee. A build-or-don’t-build verdict in writing.