Epicor Customer Portal: Self-Service Orders, Invoices & Payments

How Epicor customer self-service can simplify order, invoice, and payment visibility—and where AR automation takes the process further.

Table of Content
  1. No sections available

Search

Why Customers Keep Asking Your Team for Information Epicor Already Has

The shared inbox fills up with the same messages every week. "Where is my order?" "Can you resend invoice 40117?" "How much do we owe you?" "Has the shipment gone out?" "Can I pay this by card?"

None of these questions is difficult, and the answers are already in Epicor. Each one still pulls someone in sales, customer service or finance away from other work to look it up and reply. Across hundreds of customers, that adds up to a steady load of repetitive work.

Customer self-service is the obvious fix. Epicor offers customer-facing products that let buyers look up orders, shipments, invoices and account information themselves, and in some cases pay online, without emailing anyone.

That solves the information problem, but it doesn't settle what happens next. A customer who can see an overdue invoice might pay it, question it, dispute it, promise to pay later, or ignore it. Everything from that point on is receivables work, the stretch of the Epicor Kinetic order-to-cash process where visibility has to become collected, correctly applied cash.

This guide follows that journey in order: order visibility, invoice visibility, payment, collections and cash application.

What Is an Epicor Customer Portal?

An Epicor customer portal is a customer-facing layer that gives buyers controlled, logged-in access to selected information from your Epicor environment.

It helps to separate three layers:

  • Epicor ERP (Kinetic) holds the underlying transactions: sales orders, shipments, AR invoices, cash receipts and customer balances.

  • The customer portal exposes a permissioned slice of that data to each customer.

  • The customer retrieves what they need without contacting your team.

There is no single product called "the Epicor customer portal." Customer self-service comes from several Epicor offerings, each with a different focus.

Epicor Commerce (formerly Epicor Commerce Connect) is Epicor's B2B and B2C eCommerce platform. Besides online ordering, Epicor says buyers can view shipping, billing and account information and reach their full account history, including orders, quotes, invoices and shipments. Features vary by tier.

Epicor Cash Collect is a cloud-based credit and collections product that Epicor integrates with Kinetic, Prophet 21 and Eclipse. Its self-service side is receivables-focused: customers can access and pay invoices and manage disputes and promises to pay online.

Epicor WebDocs is a cloud application that stores customer invoices, credits and A/R statements and can be configured so customers log in and retrieve their own documents. Epicor presents WebDocs within its automotive aftermarket resources, so Kinetic users should confirm with Epicor whether it applies to their environment.

Some Kinetic users also add payment portals from Epicor partners, or build their own customer portal on Kinetic's REST API. What your customers can actually do therefore depends on which product you license, its tier and how it is configured.

What Can Customers Do Through an Epicor Customer Portal?

The practical question is: what can my customers do without contacting my team? Here is what Epicor documents, product by product.

View Orders, Order History and Order Status

Epicor Commerce gives buyers access to their account history, including orders and quotes, and lets them reorder from past orders. For most manufacturers and distributors, this is what takes "where is my order?" off the inbox.

Check Shipment Information

Shipments are also part of the account history Epicor describes for Commerce, alongside shipping information on the account. Customers can confirm what went out without asking customer service.

Access Invoices and Transaction History

This capability appears in more than one product:

  • Epicor Commerce: invoices appear in the buyer's account history.

  • Epicor Cash Collect: customers can access invoices online. Supporting documents such as proof of delivery and purchase orders can be stored against individual invoices, with contracts and credit reports stored at the account level.

  • Epicor WebDocs: customers can retrieve invoices, credit memos and billing statements, and staff can search by customer PO number.

See Account Information and Open Balances

Epicor Commerce shows billing and account information, and its Base tier includes an Open AR view in the buyer's account. Cash Collect offers online account access and an automated phone attendant that lets customers call in to check their balance, review open invoices or check on payments.

Pay Invoices

Payment is where the products differ most. In the Epicor Commerce Base tier, on-account buyers can pay open invoices by credit card from their account's Open AR view. Cash Collect supports ACH, EFT and credit card payments. Partner payment portals add other options. Availability depends on product, tier and payment setup.

Raise Disputes and Promises to Pay

Of the products above, Cash Collect is the one Epicor documents as letting customers manage disputes and promises to pay through self-service.

The pattern is clear. Epicor Commerce is built around buying and account history, Cash Collect around receivables, and WebDocs around document retrieval. Most businesses need to decide which of those problems they are actually trying to solve.


From Order Visibility to Invoice Visibility

Order visibility answers operational questions. Once the order ships and is invoiced, the customer's questions change:

  • "What do I owe?"

  • "When is payment due?"

  • "Can I get a copy of the invoice?"

  • "How do I pay?"

The progression looks like this:

Order → Fulfillment → Shipment → Invoice → Amount due → Payment

In Kinetic, shipped lines are pulled into AR Invoice Entry, and a posted invoice becomes an open receivable with a due date driven by the payment terms. From that moment, the invoice a customer sees in a portal is no longer just a document. It is an open receivable that AR is responsible for turning into cash.

This handoff sits at the center of the order-to-cash process. Self-service helps here too. Customers who can retrieve invoices themselves stop asking for copies, can check charges against their own records before paying, and have fewer grounds for "we never received it."

Visibility is only the first step, though. The more important question is what the customer does next.

What Happens After a Customer Sees an Outstanding Invoice?

Seeing an invoice doesn't guarantee payment. A customer looking at an open balance usually does one of five things.

Pay

The customer pays through the portal or by another channel, such as ACH, wire or check. The receivable now moves toward cash application: the payment has to be matched to the right invoices and applied in Epicor.

Ask a Question

"Why is freight on this invoice?" "Which PO does this relate to?" Someone in finance or customer service needs to answer before the customer will pay. Until then, the invoice keeps aging.

Raise a Dispute

The customer challenges a price, quantity, tax amount or PO reference. Finance has to investigate, route the issue to whoever can fix it (billing, sales or operations), and resolve it. Reminders won't collect a disputed invoice.

Promise to Pay Later

The customer commits to a payment date. That commitment needs to be recorded, tracked and followed up if the date passes without payment.

Do Nothing

The invoice goes past due and nothing happens. Collections has to follow up.

Only the first outcome ends with cash, and even that one leaves application work to do. Customer self-service solves information access. It doesn't remove the work that follows when customers don't pay right away.

Where Customer Self-Service Stops

A customer portal answers the customer's questions:

  • "What invoices do I have?"

  • "What is the amount due?"

  • "What is my order status?"

Finance still has to answer its own questions:

  • "Why hasn't this invoice been paid?"

  • "What should we do next on this account?"

  • "Does this customer have an open dispute?"

  • "When did they promise to pay, and did they?"

  • "Which overdue accounts should we work first today?"

  • "Where did the payment go once it arrived?"

This isn't a shortcoming of any portal. Self-service and finance automation handle different parts of the customer-to-cash journey. Epicor's own Cash Collect reflects the same split: it pairs customer self-service with a separate set of collector tools for sequencing, activity management and dispute resolution. Customers need access to information, and finance needs a way to act on it.

From Customer Self-Service to Automated Collections

Collections automation picks up where visibility leaves off. A typical automated workflow looks like this:

Invoice becomes due → Customer receives a reminder → Customer pays, responds, disputes or promises to pay → Collection activity adjusts to that response → Exceptions are escalated → The ERP is updated

Within that flow, collections automation helps finance teams:

  • Prioritize overdue accounts by risk and value, not only by age

  • Use customer and payment-behavior context to decide the next action

  • Send pre-due and post-due reminders

  • Run follow-ups and record the outcome

  • Track responses and promises to pay, and flag broken promises

  • Detect and route disputes to the right owner

  • Escalate exceptions to a person

  • Keep collection activity connected to the ERP

Epicor offers this category of capability itself. Epicor describes Cash Collect as using a configurable, rule-based engine to trigger customer communications and assign collector activities, with automatic reminders, promise-to-pay and broken-promise tracking, dispute management and escalation, and multichannel communications.

So collections automation is a category, not a single product. Epicor's own tool and third-party AR automation software both sit in it. When evaluating options, look at how prioritization is decided, how customer responses are captured, how outcomes are written back to Kinetic, and whether cash application is covered too.

That last point matters, because collections ends when the customer pays, and that is where the next piece of work starts.

What Happens When the Customer Pays?

Payment closes the collections loop and starts cash application:

Customer pays → Payment arrives → Remittance and payment information is interpreted → Payment is matched to invoices → Cash is applied → AR position is updated

A card payment made against specific invoices in a portal already carries its invoice references. Many B2B payments don't come through the portal, though. They arrive as ACH, wires, checks or lockbox deposits, with remittance information sent separately, incompletely or not at all. That is why remittance advice is central to Epicor cash application. In Kinetic, the allocation itself happens in Cash Receipt Entry.

When a payment can't be matched confidently, it sits as unapplied cash. This connects back to the portal. A customer who has paid but whose payment hasn't been applied still sees an open balance and may get a reminder they don't deserve. Accurate self-service depends on prompt cash application.

What Customer Self-Service Solves vs. What Finance Automation Solves

The table below summarizes the division of labor. "Self-service" refers to the Epicor product that documents the capability. Availability depends on product, tier and configuration.

Customer need

Self-service addresses

Finance automation addresses

View order and order history

Yes (Epicor Commerce)

—

View shipment information

Yes (Epicor Commerce)

—

View or retrieve invoice

Yes (Epicor Commerce, Cash Collect, WebDocs)

—

View amount due

Yes (Commerce Open AR view; Cash Collect account access)

Uses the same balance to prioritize follow-up

Pay online

Depends on product (Commerce Base: card; Cash Collect: ACH, EFT, card)

Cash application for all payment channels

Overdue invoice

Visibility

Collections follow-up

Payment reminder

Cash Collect

Collections: prioritized, behavior-based reminders

Dispute

Customer can raise it (Cash Collect)

Detection, routing, resolution, ERP update

Promise to pay

Customer can submit it (Cash Collect)

Tracking, reminders, escalation when broken

Incoming payment

—

Matching, application, exception handling

How Hyperbots Extends the Customer-to-Cash Workflow

With the full journey mapped, the role of an automation layer becomes clearer. Epicor provides the transaction and customer data. Customer-facing tools make that information accessible. Hyperbots automates the finance work around overdue receivables and incoming payments.

The idea behind AI agents that extend Epicor's finance and accounting capabilities is straightforward: Epicor keeps the records, and the agents handle the repetitive work around them. In a customer-to-cash flow, that looks like this:

  1. Customer views invoices, account information and payment options in an Epicor customer-facing experience.

  2. Invoice becomes due.

  3. Collections HyperAGENT prioritizes, reminds, follows up and tracks responses.

  4. Customer pays, disputes or promises to pay.

  5. Cash Application HyperAGENT matches the payment, applies it and handles exceptions.

  6. Epicor Kinetic remains the system of record, with AR updated.


Collections HyperAGENT: Working the Overdue Receivables

The Hyperbots Collections HyperAGENT handles the work that begins when an invoice isn't paid:

  • Dynamic prioritization. It continuously reprioritizes collection actions using payment behavior, invoice risk, dispute likelihood, customer value and the aging impact on DSO.

  • Reminders and follow-ups. It automates pre-due and post-due reminders based on customer behavior, risk and dispute context, and sends personalized email and portal follow-ups.

  • Disputes. It picks up dispute signals before the due date, such as price, quantity, tax or PO mismatches, and routes each one to billing, sales, tax or operations.

  • Promises to pay. It captures and tracks commitments, sends reminders and escalates when a promise is broken.

  • ERP write-back. It records collection actions, notes, dispute status, promises to pay and outcomes in the ERP.

Hyperbots also provides its own customer portal, where customers can view invoices, pay, raise disputes, submit promises to pay and track resolution. That gives teams without a receivables-focused customer layer a way to capture disputes and commitments directly in the collections workflow. It is an option, not a replacement for the Epicor customer-facing tools you already use.

Escalation management stays with people. Hyperbots reports up to 80% improvement in collections productivity, with more than 70% of collection tasks automated.

Teams already using Epicor Cash Collect will see overlap in reminders, promises to pay and dispute handling. The things to compare are how each tool decides what to do next and whether cash application is part of the same workflow.

Cash Application HyperAGENT: Applying the Payment

When the customer pays, the Hyperbots Cash Application HyperAGENT takes over:

  • It ingests payments and remittances from bank feeds, lockboxes, ACH, wires, checks, portals and email.

  • It matches payments to invoices using invoice numbers, PO references, amounts, dates, customer behavior and historical patterns, including when remittance data is incomplete.

  • It detects short payments, overpayments, deductions and unidentified cash, classifies the likely cause and routes each exception.

  • It posts validated cash applications, adjustments, write-offs and credits back to the ERP.

Hyperbots reports that it typically reaches 60% to 90% straight-through processing and brings unapplied cash below 10%. Anything outside confidence thresholds goes to a reviewer through its human-in-the-loop workflow, with the context already assembled.

Epicor Stays the System of Record

Hyperbots connects to Epicor through a pre-built connector. In a detailed conversation about Hyperbots' Epicor integration, Dave Sackett of Persimmon Technology explains that the connector uses Epicor's REST v2 endpoints, or Service Connect on older builds, and that Epicor remains the system of record.

Hyperbots has an Epicor Kinetic customer in production: a Boston-based semiconductor robotics manufacturer processing more than 30,000 invoices a year. It achieved 50% human bandwidth optimization and cut invoice processing time from one week to one day. That deployment covers P2P, not O2C, so it demonstrates Epicor integration experience rather than collections or cash application results. O2C write-back scope for a given Kinetic environment is confirmed during implementation scoping.

For ERPs where Hyperbots already has an API connector, including Epicor, integration typically takes six to eight weeks. Persimmon's rollout, at three to five weeks, was faster than usual.

When Should Businesses Consider Automating the Workflow?

Not every organization needs to automate collections and cash application. A business with a few dozen customers and clean payment habits may do well with a customer portal and Kinetic's standard AR tools. The case for automation grows with transaction and customer volume. Common signals include:

  • A high volume of customer questions about invoices and orders, even with a portal in place

  • AR staff spending much of their day on repetitive reminders and follow-ups

  • A large or growing number of overdue invoices

  • Frequent disputes that surface late, after the due date has passed

  • Promises to pay tracked in spreadsheets or notes

  • High or persistent unapplied cash

  • Payments matched to invoices by hand

  • Customer communication spread across email, phone and portals

  • A collections backlog that grows faster than the team

If several of these apply, it's worth putting numbers on the opportunity. The collections ROI calculator is a practical place to start.

Frequently Asked Questions

What is an Epicor customer portal?

It is a customer-facing layer that gives your customers logged-in access to selected information from your Epicor environment, such as orders, shipments, invoices and balances. Epicor doesn't sell a single product by that name. Customer self-service comes from products such as Epicor Commerce, Epicor Cash Collect and, in some Epicor environments, WebDocs, as well as partner and custom-built portals.

Can customers view orders through Epicor?

Yes, with a customer-facing product. Epicor Commerce gives buyers access to their account history, including orders, quotes, invoices and shipments, and lets them reorder from past orders. Core Kinetic records the sales order, but customers need a customer-facing layer to see it themselves.

Can customers access invoices through an Epicor customer portal?

Yes. Epicor Commerce includes invoices in the buyer's account history. Epicor Cash Collect lets customers access invoices along with supporting documents stored against each invoice, such as proof of delivery. WebDocs stores invoices, credits and A/R statements for customer retrieval. Which applies to you depends on the product you license.

Can customers make payments through an Epicor customer portal?

In some products, yes. The Epicor Commerce Base tier lets on-account buyers pay open invoices by credit card. Epicor Cash Collect supports ACH, EFT and credit card payments. Partner payment portals are another option. Payment methods depend on the product, tier and payment processing setup.

Can customers see their outstanding balance?

Yes, in products that expose AR data. Epicor Commerce includes an Open AR view in the buyer's account, and Cash Collect offers online account access plus an automated phone attendant for balance checks. The balance is only as accurate as your cash application. A payment that has arrived but hasn't been applied will still appear as open.

How does Epicor customer self-service help accounts receivable?

It cuts routine requests for invoice copies, balances and order status, and makes it easier for customers to pay. Where Cash Collect is used, it also lets customers raise disputes and submit promises to pay. It doesn't decide which overdue accounts to pursue or match incoming payments to invoices. Those remain collections and cash application tasks.

What is the difference between customer self-service and collections automation?

Self-service is customer-initiated: the customer comes to the portal to find information or pay. Collections automation is finance-initiated: it decides which accounts need attention, sends reminders, tracks disputes and promises, escalates exceptions and records outcomes in the ERP. One gives customers access to their receivables. The other acts on those receivables.

Can Hyperbots work alongside Epicor Kinetic?

Yes. Hyperbots uses a pre-built Epicor connector built on Epicor's APIs, and Epicor remains the system of record. Hyperbots has an Epicor Kinetic customer in production on P2P workflows. Integrations with ERPs where it already has a connector typically take six to eight weeks, and O2C write-back scope is confirmed during scoping.

Epicor Customer Portals and AR Automation: Two Halves of Customer-to-Cash

An Epicor customer portal reduces routine information requests by putting orders, invoices and account information in front of the customer. That is valuable, and for many teams it is the right first step.

When invoices go overdue, get disputed or are paid with exceptions, finance still has to act. A portal answers "What do I owe?" Collections and cash application answer "What happens next?"

Hyperbots automates that second half, working overdue receivables and applying incoming payments while Epicor Kinetic remains your system of record.

See how prioritized collections, dispute and promise-to-pay tracking, and automated cash application fit alongside your Epicor environment, with your finance team in control of every decision that needs judgment.

Book a Demo

Search

Table of Content
  1. No sections available