Epicor Kinetic and Tradeshift integration

What moves between them

The primary flow moves from Tradeshift into Epicor. Invoices and credit notes that arrive in Tradeshift are polled and transformed into Epicor AP invoices, mapped to Epicor vendors and GL accounts based on supplier name and line-item commodity codes. Purchase order status is read from Tradeshift and synced back to Epicor so order fulfillment remains visible in the ERP. Both systems are queried on a configurable schedule, typically daily or per business event, and invoice reconciliation happens in Epicor after the GL postings land.

How ml-connector handles it

ml-connector stores both Epicor and Tradeshift credentials encrypted and refreshes OAuth tokens before they expire on both sides. On the Epicor side it queries the full OData v2 path scoped to your company and instance, using $filter on UpdatedOn to retrieve only changed records since the last poll. On the Tradeshift side it polls the documents API with a changedAfter timestamp filter to pull new and updated invoices and POs. Each invoice is mapped to an Epicor vendor by matching Tradeshift supplier name against Epicor vendor records, and line items are mapped to GL accounts and cost centers using the commodity or line description as a key. Epicor AP invoice creation uses the two-step pattern required by the API: GetNewAPInvoice followed by UpdateMaster to finalize the record. ml-connector retries failed postings with exponential backoff, and every record carries a full audit trail so disputes can be replayed if needed. UBL document amounts are converted to Epicor's native numeric format, and any GL account that does not exist in Epicor is flagged for manual review.

A real-world example

A mid-sized manufacturing company in discrete parts uses Epicor Kinetic for ERP and general ledger, and sources raw materials and components from a network of 40-50 suppliers who submit invoices through Tradeshift. Before the integration, the AP team received invoices in Tradeshift, manually checked them against purchase orders, exported invoice data, and re-entered it into Epicor by hand, a process that consumed 15-20 hours per pay cycle and introduced transcription errors. The general ledger reconciliation in month-end close took days because invoice totals did not match PO commitments. With Epicor Kinetic and Tradeshift connected, invoices flow automatically into Epicor AP the day they arrive in Tradeshift, matched to the correct vendors and GL accounts, and the month-end ledger reconciliation is complete before manual close begins.

What you can do

• •Poll Tradeshift for invoices and credit notes and post them into Epicor AP transactions, mapped to the correct vendors and GL accounts.
• •Sync purchase order status from Tradeshift back into Epicor so order fulfillment remains visible in the ERP.
• •Authenticate Tradeshift with OAuth 1.0a and Epicor with OAuth2 or Basic Auth, refreshing tokens before expiry.
• •Transform UBL 2.0/2.2 invoice line items from Tradeshift into Epicor line items using commodity or description matching for GL account mapping.
• •Carry a full audit trail on every invoice and PO record, replay failed postings, and flag unmapped vendors or GL accounts for manual review.

Questions

Which direction does data move between Epicor Kinetic and Tradeshift?

The primary flow is Tradeshift into Epicor Kinetic. Invoices and credit notes from Tradeshift are posted into Epicor as AP transactions, while purchase order status flows from Tradeshift back into Epicor. General ledger postings are read-only from Epicor side, so ml-connector does not write GL entries back into Tradeshift.

How does ml-connector handle the UBL XML format and GL account mapping?

Tradeshift delivers invoices as UBL 2.0/2.2 XML documents with supplier name, line description, and amount in the structure. ml-connector parses the UBL, matches the supplier name to an Epicor vendor record, maps each line item to an Epicor GL account using commodity code or line description, and converts amounts to Epicor's native numeric format. Unmapped vendors or accounts are flagged for manual review before posting.

What happens if an invoice posting fails in Epicor after it arrives from Tradeshift?

ml-connector retries failed postings with exponential backoff and carries a full audit trail showing when and why each posting failed. If the failure is transient, the retry succeeds. If the failure is permanent, the invoice is flagged in the audit log so your team can investigate and manually correct the issue or replay the posting after the root cause is fixed.