SYSPRO and Tradeshift integration

What moves between them

The main flow is from Tradeshift into SYSPRO. After suppliers submit invoices and despatch notices through Tradeshift, ml-connector polls the Tradeshift documents endpoint on a schedule you define, parses the UBL XML, and posts the invoices into SYSPRO's ApInvoice and ApPosting tables, mapping supplier and GL account identifiers. Shipment receipts from Tradeshift update SYSPRO inventory records. In the reverse direction, purchase orders created in SYSPRO can be transmitted to suppliers via Tradeshift, allowing two-way procurement flow. Reference data such as supplier master records and GL accounts are aligned in both directions.

How ml-connector handles it

ml-connector stores both OAuth credential sets encrypted and refreshes the Tradeshift OAuth tokens according to their expiry time on each API call. On the SYSPRO side, it logs in to the e.net Utilities.Logon endpoint, caches the returned UserId session token, and passes that token on all subsequent business object calls; the token is re-obtained when it expires due to timeout. UBL documents from Tradeshift are parsed and mapped to SYSPRO's business object structure, with supplier codes and GL accounts normalized to match SYSPRO's configuration. Because both systems are pull-only, ml-connector polls Tradeshift on a schedule tied to your AP cycle, and independently checks SYSPRO for outbound purchase orders when needed. Tradeshift rate limits are respected with backoff and retry, and every record carries a full audit trail so documents can be replayed if a posting fails downstream.

A real-world example

A mid-sized electronics distributor runs SYSPRO for inventory and AP, and participates in Tradeshift's supplier network to receive invoices and shipment notices from their top 50 suppliers. Before the integration, the AP team downloaded UBL documents from Tradeshift each morning and manually entered invoice details into SYSPRO, with frequent mismatches in supplier codes and GL allocations causing downstream reconciliation pain. With SYSPRO and Tradeshift connected, each supplier invoice flows into SYSPRO automatically on the schedule they define, mapped to the correct GL accounts and cost centers, and shipment receipts update inventory without manual steps. AP processing is now 80% faster, and supplier exceptions are caught immediately.

What you can do

• •Post invoices and credit notes from Tradeshift into SYSPRO's AP module, mapped to the correct supplier and GL accounts.
• •Receive and process shipment advice and despatch notices from Tradeshift, updating SYSPRO inventory records.
• •Authenticate Tradeshift with OAuth 1.0a credentials and SYSPRO with e.net session tokens, managing token expiry and renewal.
• •Translate UBL 2.0 and 2.2 XML documents from Tradeshift to SYSPRO's e.net business object structure.
• •Poll on your AP cycle with retries, full audit trail, and document replay if posting fails.

Questions

Which direction does data move between SYSPRO and Tradeshift?

Invoices, credit notes, and shipment advice flow from Tradeshift into SYSPRO, where they are posted to AP and inventory. In the reverse direction, purchase orders created in SYSPRO can be transmitted to suppliers through the Tradeshift network. Reference data such as supplier master records are aligned in both directions.

How does ml-connector handle SYSPRO's session token and token expiry?

ml-connector logs in to SYSPRO's e.net Utilities.Logon endpoint once and caches the returned UserId token for all subsequent calls. When the token expires due to timeout, ml-connector obtains a fresh token automatically before the next batch of calls, so no manual re-authentication is required.

What happens when UBL documents from Tradeshift do not match SYSPRO's supplier codes or GL structure?

ml-connector validates supplier codes and GL accounts against SYSPRO's master records before posting, and raises an audit alert if a match is not found. You can then correct the mapping configuration, and ml-connector will replay the document on the next polling cycle without requiring manual re-entry.