Does Epicor Have an Email Integration System? Explained

Yes, but mostly in one direction. Epicor Kinetic sends email well: BPM alerts, emailed reports, and routed documents through Advanced Print Routing, all over SMTP or Microsoft 365. What standard Kinetic does not do is read an inbox and turn the attachments into ERP records. 

For finance teams, that missing direction is the expensive one. In IOFM's Future of Accounts Payable Survey, 31% of supplier invoices arrived as email attachments, usually PDFs, and many were still processed as if they were paper. 

This article covers what Kinetic's native email tools do, where they stop, and how the Epicor Kinetic REST API lets capture tools carry an emailed invoice into AP. It narrows the methods in our Epicor integration guide to REST API, Service Connect and EDI down to one entry point: the inbox. 

Two Directions of Email Integration in an ERP 

An ERP email integration can mean outbound mail, inbound capture, or both. The two need different tools, so it helps to separate them before judging what Epicor offers. 

Outbound is mostly configuration. Inbound is an integration project, because a PDF has to become a validated transaction before Kinetic will accept it. 

What Epicor Kinetic Does With Email Out of the Box 

Kinetic's native email features are all outbound. They share one mail configuration and differ in what triggers the message. 

APR is the closest thing Kinetic has to a document distribution system. It handles breaking and routing, for example splitting one AR invoice run into a separate email per customer, and it powers most Epicor report email setups. 

Users do find the toolset fragmented. A widely followed EpiUsers thread asks Epicor to re-engineer Kinetic's email components, noting that BPMs, alerts, custom code, an add-on and APR all overlap. 

Where Native Email Stops: Invoices Sitting in the AP Inbox 

Standard Kinetic has no built-in mailbox reader that turns an emailed invoice into an AP invoice. Without an added capture layer, the work looks like this: 

1. An AP clerk opens the shared mailbox and downloads the PDF. 

   
   

2. They look up the supplier, PO and receipt in Kinetic. 

   
   

3. They key the header and lines into AP Invoice Entry and code any non-PO lines to GL. 

   
   

4. They chase approvals by forwarding the email, then file the PDF somewhere it can be found at audit. 

Epicor addresses inbound capture with a separate product. Epicor ECM, formerly DocStar, captures and stores documents and offers AP automation with two- and three-way matching. Its Intelligent Data Capture (IDC) uses AI to classify documents and extract data, and Epicor's DocStar AP material says it processes invoices from multiple inbound sources. Even so, ECM AP invoice capture is the document-input stage, and matching, coding and posting rules still have to be configured around it. 

Email approvals hit the same wall. On EpiUsers, one customer noted that approving POs by email needed middleware to carry the reply into the REST API, and an Epicor staff member pointed to Automation Studio, a paid option, for that pattern. 

The Epicor Kinetic REST API: The Bridge From Inbox to Ledger 

Any tool that brings emailed invoices into Kinetic ends up writing through the Epicor Kinetic REST API. That makes the API the real answer to the email question: Kinetic does not read mail, but it accepts validated transactions from anything that does. 

What the Epicor Kinetic API exposes 

Kinetic publishes its business objects, such as suppliers, purchase orders, receipts and AP invoices, as REST services with OData support. Saved queries (BAQs) and Epicor Functions are exposed the same way. Because writes call the same business object methods as Kinetic's screens, Epicor's own validations still run when an outside tool posts an invoice. 

How to access the Epicor REST API 

1. Confirm your version. REST v2, with API keys and access scopes, arrived in Epicor ERP 10.2.400; earlier v1 builds lack both. 

   
   

2. Create an API key. Search the Kinetic menu for API Key Maintenance, generate a key, and attach an access scope. Each key can be limited down to specific methods. 

   
   

3. Set up a dedicated integration user. v2 calls need the API key on every request plus a user identity, such as basic credentials or a bearer token. 

   
   

4. Open the REST help page. Each instance serves an interactive Swagger page under https://<server>/<instance>/api/help/. Cloud tenants reach it without a VPN, using the same URL pattern on their Epicor SaaS host. 

   
   

5. Test reads before writes. Run a BAQ or a supplier lookup first, then try a write in a test company. 

Where to find Epicor API documentation 

Epicor's API documentation is instance-specific rather than one public reference site, so most Epicor API help starts on your own server. The Epicor Kinetic REST API documentation lives in four places:

• The REST help (Swagger) page on your own instance, listing every service and method your version exposes. 

  
  

• Kinetic Application Help, which covers API keys, access scopes and mail settings. 

  
  

• EpicCare, Epicor's support portal, with knowledge base articles for licensed customers. 

  
  

• The EpiUsers community, where developers and Epicor staff share working examples. 

Scope the key to the job. An Epicor API integration for invoice capture needs read access to suppliers, POs and receipts, and write access to AP invoices, not the whole service catalog. 

The email-to-ERP pattern 

Whatever tool you choose, an emailed invoice reaches Kinetic in the same five steps: 

1. Ingest: watch the AP mailbox and pull each attachment, keeping the original email as evidence. 

   
   

2. Extract: read supplier, invoice number, dates, lines, tax and totals from the PDF. 

   
   

3. Validate: check the data against suppliers, POs and receipts read from Kinetic through OData or BAQs. 

   
   

4. Write: create the AP invoice through Kinetic's business objects, with the PDF attached. 

   
   

5. Confirm: read the record back and return posting status, or route the exception to a person. 

Ways to Automate Email-to-ERP for Epicor Kinetic 

Five routes can move emailed documents into Kinetic. They differ mainly in who builds the extraction and matching logic, and who maintains it after each Kinetic update. 

Epicor positions Automation Studio, powered by Workato, as running in the cloud while connecting to both cloud and on-premises Epicor. It is also the stated successor to Service Connect, which no longer receives new development. Standard Automation Studio email automation is built around sending messages from Kinetic events; reading invoices out of a mailbox is a custom recipe. 

Whichever route you pick becomes part of your ERP integration layer. Judge it on how it handles duplicates, failed writes and Kinetic upgrades, not only on how fast the first invoice posts. 

How Hyperbots Connects the AP Inbox to Epicor Kinetic (With Persimmon Case Study) 

Hyperbots is an agentic AI layer for finance and accounting that sits alongside Kinetic rather than replacing it. Kinetic stays the system of record; Hyperbots HyperAGENTS handle the document and decision work around it, the pattern described in how AI complements ERP systems. 

How the integration works 

The Invoice Processing HyperAGENT reads invoices from the AP mailbox, extracts header and line data, and validates it against Kinetic before anything is written. The Hyperbots Epicor connector then follows the REST pattern described above:

• Native transport. A Kinetic token plus the tenant's API key; OData for reads and change tracking, business object methods for writes. 

  
  

• Invoices built Epicor's way. It creates the AP invoice group, header and lines, attaches the source PDF, codes non-PO lines to GL, and matches PO lines to receipts through AI three-way matching. 

  
  

• No duplicates. Group IDs derive from supplier and invoice number, so a resent email updates rather than duplicates, backed by duplicate invoice checks. If any step fails, the connector removes what it created. 

  
  

• Posted means posted. Posting runs Epicor's own pre-post checks, and success is reported only when Epicor confirms it. 

  
  

• Visible errors. Epicor's error text appears in Hyperbots, with alerts in Slack or Teams and human-in-the-loop review for anything outside tolerance. 

The same capture flow feeds the wider procure-to-pay process in Kinetic, from POs and receipts through accruals. 

Case study: Persimmon Technology 

In Hyperbots' Epicor ERP integration interview, Dave Sackett, VP of Finance at Persimmon Technology, describes the rollout on on-premises Epicor: 

Persimmon's timeline was faster than usual. Hyperbots integrations on ERPs with an existing API connector, including Epicor, typically take 6 to 8 weeks. 

Epicor Email Integration Comes Down to the Kinetic REST API 

Epicor does have an email system, and for outbound work it is capable. Email Settings Maintenance, BPM alerts and Advanced Print Routing cover notifications, emailed reports and per-customer document delivery. 

Inbound email is a different job. Turning an invoice in the AP inbox into a posted Kinetic record takes capture, validation and a write through the Epicor Kinetic REST API, whether that comes from Epicor ECM, Automation Studio, your own code or a finance automation platform. 

Start with the API basics: confirm REST v2, scope an API key, and explore your instance's REST help page. Then pick the route whose maintenance burden your team can carry. 

See how Hyperbots HyperAGENTS take invoices from your AP inbox to posted Epicor records. Request a demo. 

Frequently Asked Questions About Epicor Email Integration 

Q1. Can Epicor Kinetic automatically read invoices from an email inbox? 

Not on its own. Kinetic's standard email tools send mail; they do not watch a mailbox or extract data from attachments. Inbound capture comes from Epicor ECM with Intelligent Data Capture, an Automation Studio recipe, custom code, or a third-party AP platform that writes to Kinetic through the REST API. 

Q2. Does Epicor Kinetic work with Microsoft 365 and Outlook? 

Yes, for outbound mail. Email Settings Maintenance supports legacy SMTP or a Microsoft 365 app registration, which avoids basic-auth SMTP that Microsoft discourages. Epicor cloud customers can also have Epicor send mail through its managed SendGrid service. Reading an Outlook inbox still needs a separate tool or integration. 

Q3. Do I need Advanced Print Routing to email invoices and POs from Epicor?

Not for one-off sends, since any report can be emailed from the print dialog. APR, a licensed module, becomes worthwhile when you need automation at scale: splitting one invoice run into an email per customer, pulling addresses from contact records, or delivering by FTP. Community users note that breaking and routing requires the APR license. 

Q4. How do I access the Epicor REST API? 

Confirm you are on REST v2, available from Epicor ERP 10.2.400 onward. Create a key in API Key Maintenance with a narrow access scope, then call the API with that key plus a user identity such as basic auth or a bearer token. Your instance's REST help page lets you test calls before writing any code. 

Q5. Where is the Epicor Kinetic REST API documentation? 

The main reference is the interactive REST help (Swagger) page on your own instance, because it reflects your exact version and customizations. Kinetic Application Help covers API keys and scopes, EpicCare holds knowledge base articles for licensed customers, and the EpiUsers forum shares working examples from developers and Epicor staff. 

Q6. Can suppliers' emailed invoices post to Epicor without manual entry? 

Yes, with a capture and validation layer in front of Kinetic. The tool must match each invoice to the supplier, PO and receipt, handle duplicates and exceptions, and confirm posting. Persimmon Technology reports about 80% of invoices flowing from its Outlook AP mailbox to posted Epicor invoices with Hyperbots. 

Q7. Can managers approve Epicor POs or invoices by replying to an email? 

Kinetic can email an approval request, but turning the reply into an approval needs middleware that calls the REST API. Epicor points customers to Automation Studio, a paid add-on, for this. A simpler alternative is an email containing a link to the approval screen, or approvals routed through Teams. 

Q8. Does email-to-ERP automation work with on-premises Epicor? 

Yes. On-premises Kinetic exposes the same REST services; the challenge is network access for cloud tools. Common answers are a secure gateway or a lightweight agent on the Epicor app server that opens an outbound tunnel, the approach Persimmon used without inbound firewall changes.