Oracle NetSuite and TrueCommerce integration

What moves between them

Purchase orders created or updated in Oracle NetSuite are polled by ml-connector and converted from NetSuite record format to X12 850 (Purchase Order) documents. These are delivered to TrueCommerce SFTP for distribution to your trading partners. Return documents (856 Advance Ship Notice and 810 Invoice) are pulled from TrueCommerce SFTP, parsed, and created as Vendor Bills and receipt records in NetSuite. The schedule is configurable: pull from NetSuite on a cadence that matches your ordering frequency, and poll TrueCommerce SFTP hourly or daily depending on your supply chain needs.

How ml-connector handles it

ml-connector stores both credential sets encrypted: NetSuite account ID and OAuth client certificate for M2M auth, and TrueCommerce SFTP username and password. On the NetSuite side, ml-connector uses OAuth 2.0 Client Credentials flow to obtain bearer tokens (refreshing every 60 minutes) and polls SuiteQL to fetch new or changed purchase orders. On the TrueCommerce side, ml-connector connects via SFTP to integrationftp.truecommerce.com port 22 and pulls documents from customer-specific integration paths (established during account setup). Purchase order data is mapped: NetSuite vendor records to X12 segments, line items and quantities to PO1 loops, and ship-to locations to delivery address segments. Incoming EDI 856 and 810 documents are parsed for vendor ID, invoice number, and line-item quantities, then created in NetSuite as Vendor Bills and receipt records, mapped back to the originating purchase orders. ml-connector tracks NetSuite account ID and OAuth token expiry, retries SFTP connections with backoff on connection failures, and deduplicates inbound documents using EDI ISA control numbers and NetSuite record IDs.

A real-world example

A mid-market wholesale distributor runs Oracle NetSuite for procurement and accounting, and uses TrueCommerce to exchange orders and invoices with 40 trading partners via EDI. Before the integration, buyers created purchase orders in NetSuite, then manually exported and translated them into X12 format, uploaded to TrueCommerce, and re-entered incoming invoices from trading partners back into NetSuite for matching and payment. With Oracle NetSuite and TrueCommerce connected, purchase orders flow automatically to TrueCommerce and onward to trading partners, and return invoices from TrueCommerce are posted directly into NetSuite for three-way matching. The manual translation and re-entry steps are gone, order cycle time drops, and month-end invoice reconciliation is automated.

What you can do

• •Convert Oracle NetSuite purchase orders to X12 850 format and deliver them to TrueCommerce SFTP for trading partner distribution.
• •Poll TrueCommerce SFTP for incoming Advance Ship Notices (856) and invoices (810), parse them, and create Vendor Bills in Oracle NetSuite.
• •Authenticate NetSuite with OAuth 2.0 Client Credentials using a customer certificate, and manage SFTP credentials encrypted for TrueCommerce.
• •Map purchase order data bidirectionally: NetSuite vendors and line items to X12 segments, and incoming EDI documents back to NetSuite Vendor Bills and purchase order receipts.
• •Maintain a full audit trail on every record converted and track document deduplication via EDI ISA control numbers and NetSuite record IDs.

Questions

How does ml-connector handle the format conversion between Oracle NetSuite and TrueCommerce EDI documents?

ml-connector maps NetSuite purchase order records (vendor, items, quantities, delivery addresses) into X12 850 segment structure for outbound documents, and parses inbound X12 856 and 810 documents back into NetSuite Vendor Bill and receipt records. The mapping is based on documented conventions: vendor ID maps to X12 vendor loop, line-item quantities to PO1 loops, and locations to delivery address segments. Parsing and mapping are deterministic and logged in the audit trail.

What if TrueCommerce SFTP is temporarily unavailable or a file transfer fails?

ml-connector retries SFTP connections with exponential backoff and jitter. If a pull fails, it resumes on the next scheduled interval. If a delivery to SFTP fails, the document remains in the work queue and is retried until it succeeds or the retry limit is reached. Every attempt is logged so you can see exactly when a transfer failed and why.

Do I need a local Windows Integration Service or agent to run this integration?

No. Because Oracle NetSuite is a cloud ERP, ml-connector uses TrueCommerce's Exchange API or SFTP directly without a local Windows agent. You provision SFTP credentials and integration paths with TrueCommerce during account setup, and ml-connector polls those paths on the schedule you define.