Epicor Kinetic and JAGGAER integration

What moves between them

The main flow is from JAGGAER into Epicor Kinetic. Invoices received in JAGGAER are polled and matched to the corresponding purchase order in Epicor Kinetic, then posted to AP invoices with GL account and cost center lines intact. Vendor master records and contract terms flow bidirectionally so both systems reference the same supplier set. Purchase requisitions created in Epicor Kinetic can be pushed to JAGGAER to initiate sourcing workflows. AP GL postings from invoices are reconciled automatically so the accounts payable and general ledger remain aligned.

How ml-connector handles it

ml-connector manages both OAuth2 token lifecycles: J1P client credentials on the JAGGAER side with automatic token refresh when expired, and Epicor Kinetic bearer token refresh via its OAuth2 endpoint or Token Resource Service for on-premises instances. Because both systems are pull-only, ml-connector polls both on a schedule tied to your invoice receipt and payment cycles. Invoices are matched to purchase orders by PO number and vendor ID; if a match is found, the invoice is automatically imported into Epicor Kinetic's AP module with GL account and cost center lines copied from the originating PO. Vendor records are mapped bidirectionally to keep master data synchronized. For on-premises Epicor Kinetic instances, ml-connector accepts the full server URL and instance name. All writes to Epicor Kinetic follow the GetNewXxx and UpdateMaster pattern required by the platform. Every record carries a full audit trail, and failed imports are retried with exponential backoff.

A real-world example

A mid-market discrete manufacturer runs Epicor Kinetic ERP for manufacturing, supply chain, and finance, and uses JAGGAER for procurement, sourcing, and supplier management across three plants. Before the integration, the procurement team received invoices in JAGGAER, exported them to CSV, and manually matched and re-entered them into Epicor Kinetic's AP module weekly, a process that often missed invoice deadlines and created reconciliation issues during month-end close. With Epicor Kinetic and JAGGAER connected, invoices flow automatically from JAGGAER to AP the moment they arrive, matched to the PO and posted to the correct GL accounts and cost centers. Vendor master data is kept synchronized automatically, so procurement can manage suppliers in JAGGAER without asking finance to update Epicor Kinetic. Month-end close is faster because AP and GL are already reconciled.

What you can do

• •Automatically import invoices from JAGGAER into Epicor Kinetic AP module, matched to originating purchase orders and posted to GL accounts.
• •Keep vendor master records synchronized bidirectionally so both systems reference the same supplier set and terms.
• •Post invoice GL lines to the correct cost centers and GL accounts based on the originating PO.
• •Authenticate Epicor Kinetic via OAuth2 bearer token or on-premises Token Resource Service, and JAGGAER via J1P OAuth2 client credentials.
• •Poll both systems on a schedule tied to your invoice receipt cycle, with automatic token refresh, retries, and a full audit trail.

Questions

How does the integration match invoices in JAGGAER to purchase orders in Epicor Kinetic?

Invoices are matched by PO number and vendor ID. Once a match is found, the invoice is imported into Epicor Kinetic's AP module with GL account and cost center lines inherited from the originating PO. If a match cannot be found, the invoice is flagged for manual review and logged in the audit trail.

Does JAGGAER's push/event feature eliminate the need for polling?

JAGGAER supports event-driven configuration, but it requires JAGGAER professional services to set up and is not available self-serve. By default, ml-connector polls both systems on a schedule tied to your procurement cycle. If you enable JAGGAER event configuration with professional services, ml-connector can also listen for invoice notifications.

How does the integration handle Epicor Kinetic's two-step write pattern for invoices?

ml-connector follows the GetNewXxx and UpdateMaster pattern required by Epicor Kinetic. It first retrieves a new invoice object, populates the header and line details, then commits the record with UpdateMaster. This ensures compliance with the platform's business object lifecycle and prevents data integrity issues.