Covered
E9 Service Connect
Supported
Use Cases
Timeline
Why manufacturers on ERP 9 and ERP 10 add Payment Hub, and why now rather than after the upgrade
The most common objection we hear from an E10 shop is reasonable: we are moving to Kinetic in eighteen months, so why touch payments now? The answer is that the integration does not change when you upgrade, and the eighteen months of manual cash application do not come back.
Manufacturers on ERP 9 or ERP 10 run a familiar process. Sales orders with deposits get a card number keyed into a virtual terminal. Invoices go out with remit-to instructions. Customers mail checks or set up their own ACH, and a few call in cards. The AR team gets a processor report and creates cash receipts by hand, matching amounts to ARInvoice records. When an order ships in releases, the deposit and the balance captures rarely line up without someone reconciling them.
Payment Hub replaces that with one flow that posts to your Epicor AR. A customer pays a deposit from a link, pays an invoice from the portal, or the AR team takes a card by phone, and the result lands in Epicor as a CashHead and CashDtl applied to the invoice, in the right company and site. On E10 that happens through Epicor's REST services. On E9 it happens through Service Connect. Either way the AR clerk reviews rather than keys.
The upgrade argument runs the other way from how most people expect. Kinetic is ERP 10 continued: same OrderHed, same ARInvoice, same CashHead, same REST services with newer versions. An integration built against E10 today is the integration you will run on Kinetic. Doing it now means the upgrade project inherits a working payment process instead of adding one to its scope.
What stays in Epicor
Epicor remains the system of record for customers, sales orders, releases, jobs, invoices and cash, on whichever release you run. Payment Hub does not keep a parallel ledger. It reads what it needs, takes the payment on a PCI-compliant surface, and writes cash receipts in the same shape your AR team creates by hand.
Your Epicor configuration does not change. Companies, sites, BPM directives, customizations and any Service Connect workflows you already run stay as they are. Payment Hub adds a payment link to the invoice form you already send and a portal beside Epicor, not inside it.
Who is still on ERP 9 and ERP 10, and what Payment Hub does for each
The E9 and E10 installed base is mostly discrete and mixed-mode manufacturing, the same verticals Epicor built Kinetic for. Payment Hub covers all of them, and the payment pattern that matters most changes with how the shop sells.
Machinery
Metals
& Electrical
& Transportation
Plastics
& Defense
Devices
Fixtures
& Multi-Company
Job shops and make-to-order manufacturers get the most from deposits on sales orders and captures per shipment release, because that is how their cash actually moves. Repeat-order manufacturers in electronics and automotive carry the largest open AR and use the portal and consolidated invoice payment. Aerospace and medical device shops care about the audit trail, and every Payment Hub transaction exists in Epicor as a normal cash receipt with a gateway reference. Multi-company and multi-site shops need the routing from day one.
Most E9 and E10 customers span two of these, which is why the full feature set is installed and you enable what your AR team uses.
Payment Hub vs native Epicor payment on E9/E10, honest side-by-side
ERP 9 and ERP 10 include credit card processing through a small set of partnered gateways, and it handles a card on an order. Payment Hub is the gateway-agnostic option for manufacturers who need more than that, and the differences are worth being clear about.
| Capability | Native E9/E10 Payment | Payment Hub on E9/E10 |
|---|---|---|
| Gateway / processor choice | ✗ Limited to Epicor's partnered gateways for that release | ✓ 19+ gateways: Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree, Authorize.Net and more, on your merchant account |
| Customer self-service portal | ✗ Not included | ✓ Branded portal reading live ARInvoice data, with pay-many, pay-on-account and saved methods |
| Click-to-pay links on invoices | ✗ Requires customization | ✓ Payment link on every invoice form, tokenized, no card data in email |
| Deposits and per-release captures | ✗ Manual reauthorization per release | ✓ Deposit at order entry, automatic reauthorization and capture as each OrderRel ships |
| Level III line-item data | ✗ Not sent | ✓ Level III built from OrderDtl on every eligible card transaction |
| Multi-company / multi-site routing | ✓ Per-company processing supported | ✓ Routing by company, site, merchant account and GL cash account from one configuration |
| Carry-over to Kinetic | ✗ Native processing must be re-implemented against Kinetic's supported gateways | ✓ The E10 integration moves to Kinetic as part of the upgrade, with tokens and configuration intact |
| ACH / eCheck | ✓ Available through select partners | ✓ ACH, eCheck and card on the same portal and the same cash receipt posting |
Native processing is a reasonable answer for a single-company shop with modest card volume and no portal ambitions. Manufacturers move to Payment Hub when they want to stop re-keying cash receipts, when customers ask to pay online, when release-based captures become a monthly reconciliation problem, or when they realize the Kinetic upgrade will otherwise mean rebuilding payments. The last one is the reason this page exists.
The Missing LinkBetween Paymentsand Your ERP
Clarity Payment Hub closes that gap, connecting your orders, invoices, and payment channels into one flow.
Speak to a Platform ArchitectHow Clarity Connect integrates Payment Hub with ERP 9 and ERP 10
On ERP 10 the integration runs on Epicor's REST services and OData, the same surface Kinetic exposes. On ERP 9 it runs on Epicor Service Connect and the business-object services. Eight capabilities make up the integration, and none of them are installed as BPM directives or customizations in your database.
REST services on E10, Service Connect on E9
On ERP 10 (10.1.500 and later) Payment Hub reads and writes through the REST services for Customer, Sales Order (OrderHed / OrderDtl / OrderRel), AR Invoice and Cash Receipt (CashHead / CashDtl). On ERP 9 the same operations run through Service Connect workflows against the business objects. Same integration, different transport.
Real-time cash application
A payment taken in the portal, on an invoice link or by phone posts to Epicor as a CashHead / CashDtl applied to the ARInvoice it settles, in the company and site that own it. Unapplied and on-account payments post with the customer set so AR can apply them without guesswork.
Manufacturing-aware order-to-cash
Deposit at order entry, reauthorization and capture as each OrderRel ships, final capture on the last invoice. The pattern follows how your orders actually ship, not a generic checkout.
Level III auto-enrichment
Line detail from OrderDtl, including part, quantity, unit price, tax and ship-to, is attached to eligible card transactions so commercial and purchasing cards qualify for Level III interchange. Nobody types it in.
Multi-company and multi-site routing
Each transaction is routed to the merchant account, bank and GL cash account for the Epicor company and site on the order or invoice. Multi-company shops get the same routing across companies from one configuration.
Tokenized method vault
Cards and bank accounts are tokenized at the gateway and stored against the Epicor customer. The tokens survive your Kinetic upgrade, so customers do not re-enter payment methods after you move.
Recurring and scheduled payments
Customers on a payment schedule, statement autopay or a fixed monthly draw run on the scheduler, with dunning for failed attempts and every run posting as a normal cash receipt.
Upgrade-safe by design
Because Kinetic shares E10's data model and REST surface, the integration, the portal, the tokens and the configuration carry over as part of your upgrade. Payment Hub customers who move from E10 to Kinetic do not re-implement payments.
The integration workflow, deposit at order entry to posted CashHead, across an upgrade
A concrete walk-through. A custom packaging manufacturer with two sites on Epicor ERP 10.2, with a Kinetic upgrade scheduled for next year, takes a $64,000 order for tooling plus a first production run, with a 40 percent deposit and two shipment releases. Payment Hub handles the deposit, the release captures and the cash application, and the process survives the upgrade untouched.
Sales enters the order in ERP 10
The account manager creates sales order 71880 for Brightline Foods: $64,000 covering custom tooling and an initial production run, shipping from the Dayton site in two releases. Terms call for a 40 percent deposit at order entry. OrderHed and OrderDtl post, and two OrderRel records carry the release schedule.
E10 Order EntrySite DAY-012 ReleasesDeposit captured through Payment Hub
The account manager sends a click-to-pay link for the $25,600 deposit. Brightline's AP pays it on a purchasing card. Payment Hub tokenizes the card, attaches Level III detail from OrderDtl, and authorizes and captures on the Dayton site merchant account.
Click-to-PayLevel IIITokenizedEpicor records the deposit
Payment Hub writes a CashHead / CashDtl to ERP 10 through the REST services, applied as a customer deposit on order 71880 and posted to the Dayton cash GL. AR sees the deposit on the order at once. No settlement report, no re-keying.
REST ServicesCashHead / CashDtlRelease 1 ships: tooling
Six weeks later the tooling ships on release 1. ERP 10 invoices $22,000 as ARInvoice 40311 with part of the deposit applied. Payment Hub captures the balance on the saved card automatically, reauthorizing since the original authorization has aged out.
OrderRel 1Auto-CaptureRelease 2 ships: first production run
Four weeks on, the production run ships on release 2. ARInvoice 40358 posts for $42,000 net of the remaining deposit. The invoice form carries the payment link, so Brightline gets a payment-ready invoice without the AR team doing anything extra.
OrderRel 2Invoice LinkCustomer pays the final invoice in the portal
Brightline's AP contact logs into the portal, sees invoice 40358 with the deposit applied, and pays the balance on the saved purchasing card. Payment Hub posts the CashHead / CashDtl against 40358 in real time.
Customer PortalSaved MethodAuto-AppliedKinetic upgrade, eight months later
The manufacturer upgrades ERP 10.2 to Kinetic. The REST services are the same surface with a newer version, the tables are the same, and Payment Hub's configuration, portal and stored tokens carry over as part of the cutover. Brightline's saved card still works the morning after.
Kinetic UpgradeZero RebuildMonth-end is routine on both releases
Before and after the upgrade, every payment exists in Epicor as a cash receipt applied to the right invoice, in the right company and site, on the right GL account. The processor statement matches the cash GL, and the upgrade project never had payments on its scope.
Month-EndReconciledThe detail worth noticing is step seven. Most manufacturers assume payments are something to sort out after the upgrade. Building on E10's REST services now means the upgrade inherits the integration instead of scheduling it.
Payment Hub use cases on ERP 9 and ERP 10
All 11 Payment Hub use cases run on E9 and E10. The ones manufacturers deploy first are highlighted here, and each links to the full use-case page.
Deposits at order entry, capture per OrderRel as releases ship, final capture on the last invoice.
Most deployedB2B Invoice PaymentsA payment link on every invoice form, tokenized, with the CashHead posted on payment.
Customer-facingSelf-Service Payment PortalA branded portal reading live ARInvoice data, with saved methods that survive the Kinetic upgrade.
Unit economicsLevel III Interchange OptimizationOrderDtl detail on every eligible card, so purchasing and commercial cards settle at Level III rates.
Multi-siteMulti-Location PaymentsRouting by company, site, merchant account and GL cash account across every Epicor location.
ARERP Payment ReconciliationEvery payment lands as a cash receipt with GL set, so bank reconciliation matches the processor.
Technical details, for Epicor admins and partners on E9/E10
The engineering reality of the integration, for IT teams, Epicor system administrators, BPM and Service Connect developers, and Epicor partners evaluating Payment Hub for a customer on ERP 9 or ERP 10.
- API layer, ERP 10. Epicor REST services (v1 from 10.1.500, v2 with OData from 10.2.300) for Customer, Sales Order (OrderHed / OrderDtl / OrderRel), AR Invoice (ARInvoice / ARInvoiceDtl), Cash Receipt (CashHead / CashDtl), Company and Site. Kinetic exposes the same services with newer versions, which is why the integration carries over.
- API layer, ERP 9. Epicor Service Connect workflows against the business-object services (SalesOrder, ARInvoice, CashRec, Customer). Same operations as the E10 path, delivered through Service Connect rather than REST. Most E9 sites already run Service Connect for EDI or shop-floor integration.
- Authentication. ERP 10: an Epicor user with an API key or token scoped to the services above. ERP 9: a Service Connect service account with access limited to the business objects used. Credentials are stored encrypted on Payment Hub's side and rotated on your schedule.
- Data direction. Reads: customers, contacts, open orders and releases, open invoices, company and site configuration. Writes: cash receipts, deposit applications and payment-method tokens stored as customer attributes. Payment Hub never writes pricing, inventory, jobs, order lines or GL entries directly.
- Card data. No cardholder data reaches Epicor, your network or Payment Hub's application tier. Entry happens on a PCI DSS Level 1 hosted surface at the gateway, and Epicor receives a token and a reference. Your PCI scope shrinks.
- Company and site routing. A configuration map from Epicor company and site to merchant account, bank account and GL cash account. Adding a site is a configuration change.
- Customizations. No BPM directives, customizations, UD fields or schema changes are installed in your Epicor database. Existing BPMs, customizations, Service Connect workflows and third-party integrations continue unchanged, and your upgrade path to Kinetic is not affected.
- Deployment. Works with E9 and E10 on-premise and with Epicor-hosted E10. The Payment Hub service reaches the REST services or Service Connect over TLS through your firewall or Epicor's hosted endpoint.
- Timeline. Standard go-live is 48 hours from API or Service Connect access: connect, map companies and sites, add the payment link to your invoice forms, test in your Epicor test company, cut over. Portal branding, gateway migration and recurring setup are added when you want them. The Kinetic carry-over is part of your upgrade cutover, not a separate project.
- Support. Clarity supports the integration and the payment side, on the release you have and through the upgrade. Your Epicor partner keeps supporting Epicor exactly as they do today.
Epicor ERP 9 / ERP 10 + Payment Hub FAQ
The questions Epicor administrators, AR managers, IT teams and Epicor partners ask before adding Payment Hub to an ERP 9 or ERP 10 deployment.
Does Clarity Payment Hub integrate with Epicor ERP 9 and ERP 10?
Yes, both. On ERP 10 the integration uses Epicor's REST services and OData. On ERP 9 it uses Epicor Service Connect and the business-object services. Deposits, invoice payments, portal payments, refunds and on-account payments all post to Epicor in real time as CashHead / CashDtl records applied to the right invoice.
Customers, orders, releases, invoices and cash stay in Epicor as the single source of truth on either release.
We are upgrading to Kinetic next year. Should we wait?
No, and this is the most common question we get on E10. Kinetic is the continuation of ERP 10 with the same tables and the same REST services. The integration you build on E10 today is the integration you run on Kinetic, and your configuration, portal and stored tokens carry over as part of the upgrade cutover. Waiting only postpones the benefit and adds payments to the upgrade's scope.
Which ERP 10 versions support the REST path?
REST services v1 arrived in 10.1.500 and v2 with OData in 10.2.300. Sites on 10.1.500 or later use REST. Sites on 10.0 or earlier 10.1 releases, and all ERP 9 sites, use the Service Connect path. Either way the integration behaves the same from your side.
What does the ERP 9 integration require?
Epicor Service Connect, which most E9 sites already run for EDI, shop-floor or other integrations, plus a service account scoped to the business objects used. Payment Hub supplies the workflows. If you do not run Service Connect today, we scope that before quoting.
How is this different from the payment processing built into Epicor?
Native processing on E9 and E10 takes a card on an order through a small set of partnered gateways. It does not include a customer portal, click-to-pay invoice links, automatic per-release captures or Level III enrichment, and it does not carry over to Kinetic. Payment Hub adds all of that on whichever gateway you prefer.
Does Payment Hub handle multi-company and multi-site?
Yes. Each payment routes to the merchant account, bank and GL cash account for the Epicor company and site on the order or invoice. Multi-company shops get the same routing across companies from one configuration.
How do deposits and shipment releases work?
Payment Hub takes the deposit at order entry and posts it as a customer deposit on the order. As each OrderRel ships and invoices, it captures the release balance on the saved method, reauthorizing when an authorization ages out. The customer sees charges that match shipments, and AR sees cash receipts applied to each invoice.
Will Level III interchange savings apply to a manufacturer?
If a meaningful share of your card volume is commercial or purchasing cards, which is typical for B2B manufacturers, then yes. Payment Hub attaches OrderDtl detail to each eligible transaction so it qualifies for Level III rates. The saving is generally 0.5 to 1.0 percent on that volume, applied automatically once enabled.
Do we have to install BPM directives or customizations?
No. The integration lives outside your Epicor database and uses only the REST services or Service Connect. Your existing BPMs, customizations and workflows stay as they are, and nothing about the integration complicates your Kinetic upgrade.
Can we keep our current gateway and merchant account?
Almost always. Payment Hub connects to 19+ gateways including Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree and Authorize.Net. If your processor is on the list you keep your rates and your relationship.
What is the implementation timeline?
Forty-eight hours from REST or Service Connect access is the standard go-live for the core integration: connection, company and site mapping, invoice link on your forms, testing in your Epicor test company and cutover. Portal branding, gateway migration and recurring setup are added on top. The Kinetic carry-over happens inside your upgrade cutover rather than as a separate project.
Who supports the integration, Clarity or our Epicor partner?
Clarity supports the integration and the payment side, on E9 or E10 today and through your move to Kinetic. Your Epicor partner keeps supporting Epicor exactly as they do today.