How long does invoice automation take to implement?

It depends on invoice volume, ERP, and exception complexity. We do not quote timelines before the audit, because the honest answer requires seeing your data. What we can commit to before the audit is the audit's scope and price ($7,500, fixed).

Can this work with Epicor P21 specifically?

Yes. We have built and run production AI systems inside P21 at Kelsan, including the rebate-and-margin tool. AP invoice automation uses the same integration surface: read PO and receipt tables, write to AP voucher tables through approved entries. If you run P21, the path is well-mapped. Distribution operators can see more in our [AI for distributors](https://throughlinebuilt.com/distribution/) page.

Do we still need our AP clerks?

Yes, in a different shape. The clerks stop re-keying invoices and start approving exceptions, managing vendor relationships, and catching the judgment calls a system should never make alone. Headcount conversations vary by shop. What changes for certain is what the AP team spends their day doing.

Is this the same as billing automated on the receivables side?

No. AP invoice automation is about invoices you receive from vendors. Billing automated on the AR side is invoices you send to customers. The mechanics rhyme (documents, matching, posting) but the systems and risks are different. Both are candidates for [back office automation](https://throughlinebuilt.com/services/ai-automation/back-office-automation/), and both belong on the same operator's roadmap.

How to Automate Invoice Processing Without Replacing AP

How to automate invoice processing without ripping out your AP function is the question most mid-market finance leads are actually asking. The honest answer: a system reads the invoices you already receive, matches them against records in the ERP you already run, and surfaces entries for a person to approve before anything posts. You do not need a second AP platform sitting next to the one you have. You need software that reads documents and writes to the system of record you already trust.

Key takeaways

Invoice automation is a pipeline of five stages: capture, extraction, matching, approval, and posting. Skipping any one of them is where projects fail.
A person should approve anything that changes a live record. Full autonomy over money-touching systems is not a feature, it is a liability.
Buying an AP SaaS product means running a second system of record next to your ERP. Building into the ERP means fewer integrations and one source of truth.
Throughline's fixed-fee AI Capability Audit is $7,500. The build is a separate fixed fee, agreed in writing before anyone touches code.
Inside Kelsan, a multi-state distributor running Epicor P21, a rebate-and-margin system built by Throughline has recovered over $100,000 in margin a person approved before it posted.

What the actual workflow looks like

Five stages. In order:

Capture. Invoices arrive as PDFs in an inbox, EDI feeds, portal downloads, or paper that gets scanned. The system pulls them from wherever they land and normalizes the file.
Extraction. The tool reads the document and pulls structured fields: vendor, invoice number, PO reference, line items, quantities, unit prices, tax, totals. This is where intelligent document automation lives, and it is the stage that used to require an army of clerks.
Matching. The extracted invoice gets matched against the PO and the receipt inside the ERP. Three-way match, line by line. Discrepancies flag for review.
Approval. A person on your team reviews the flagged items and the routine posts alike. The system presents the invoice, the match result, and the proposed GL coding side by side.
Posting. Once approved, the entry writes to the ERP as an AP voucher, coded and ready for the payment run.

That is the whole loop. Anything a vendor sells you as "invoice automation" that does not touch all five stages is a partial solution, and the gaps become the operator's problem.

Where the human belongs, and where they do not

The human belongs on the approval step. Always. Anything that writes to a live record, an AP voucher, a GL entry, a payment file, goes through a person who can see what is about to change and stop it.

The human does not need to belong on capture, extraction, or the first-pass match. Those are mechanical tasks. A well-built system handles clean invoices without a person touching them until the approval queue. The point is not to remove judgment. The point is to remove re-keying, so judgment is the only thing the AP team is being paid for.

Buy an AP SaaS, or build into the ERP you already run

The buy path is faster to a demo. You sign with an AP automation vendor, they stand up an instance, and you have a shiny dashboard in weeks. The catch: you now run two systems of record. Invoices live in the SaaS. Vouchers eventually sync to the ERP. Reconciliation between them becomes its own chore. If the sync breaks, your month-end breaks.

The build path takes longer up front. A system built into your ERP reads invoices, matches against live PO and receipt data, and writes vouchers directly. There is one system of record. There is no sync layer to babysit. And the logic is yours: how you code GL, how you handle short-shipments, how you treat freight, all encoded in software that fits your operation instead of the vendor's average customer.

For most mid-market distributors and manufacturers running Epicor P21, NetSuite, or Dynamics, the build path wins on total cost of ownership over three years, assuming you have a partner who can actually do ERP automation without breaking the ERP.

What ERP integration actually requires

Three things, honestly. Read access to the tables you need (POs, receipts, vendor master, GL structure). Write access, gated by approval, to the AP voucher tables. And a place to run the extraction and matching logic that can call the ERP's API or its database directly.

That is it. You do not need to replace anything. You do not need a middleware suite. You need a small piece of software that speaks your ERP's language and a builder who has done this before. This is what generative AI integration is when it is done for a real operator instead of demoed on a slide.

What we built inside our own group

Throughline is a small team of builders inside Keller Group. We build AI systems into our own operating companies first. The clearest example: Kelsan, a multi-state distributor running Epicor P21. We built a rebate-and-margin recovery system that reads supplier rebate documents, matches them against invoices in P21, and surfaces entries for a person on the Kelsan team to approve before anything posts. It has recovered over $100,000 in margin that would otherwise have been lost.

The mechanism is the same one that applies to AP invoice automation. Read the documents you already receive. Match them against records already in the ERP. Present a person with what is about to change. Post only what they approve. You can read more about the rebate-and-margin tool we built inside Kelsan if you want the fuller version.

The messy cases

Three-way match works cleanly maybe 70% of the time in a real distribution shop. The other 30% is where the system earns its keep or fails. A short-shipped line. A vendor who invoiced before the receipt hit. Freight billed separately. A price that changed and nobody updated the PO. Tax on the invoice that does not match your tax logic.

A good system does not try to solve these with a rule engine that becomes unmaintainable. It presents the exception with all the context: the PO, the receipt, prior invoices from this vendor, the GL history. The person makes the call in seconds instead of minutes, and the decision is captured so patterns become visible. That visibility is where the next round of automation comes from, once you know which exceptions are actually recurring.

What this costs, honestly

Every engagement with Throughline starts with a fixed-fee AI Capability Audit at $7,500. The audit gets us into your invoice flow, your ERP, your exception patterns, and produces a written scope with a fixed price for the build. The build itself is quoted separately, in writing, before anyone starts. Running costs are metered like any cloud service, and we quote them before the build so there are no surprises.

We do not promise a specific savings figure. Anyone who does, on a first call, before they have seen your data, is guessing. What we will tell you honestly, during the audit, is whether the invoice volume and exception rate in your shop justify a build, or whether you would be better served buying an off-the-shelf AP tool and living with the sync overhead. Sometimes the answer is not to build.

Ready to look at your invoice flow

If you run a mid-market distribution or manufacturing operation and you are trying to figure out whether invoice automation software or a build into your ERP is the right call, the audit is designed for exactly that decision. Book a call with Throughline, or start with a fixed-fee AI Capability Audit ($7,500). The call is free. Call 865-417-3554.

About the author

Throughline is a small team of builders inside Keller Group. We build AI systems into our own operating companies first, then into yours.