QuickBooks Desktop and TrueCommerce integration

What moves between them

Purchase orders created in QuickBooks Desktop are read via QBWC polling and forwarded to TrueCommerce for EDI transmission to suppliers. Purchase order acknowledgments and advance ship notices arrive at TrueCommerce from trading partners, are retrieved from its SFTP folder, parsed into EDI format, and written back into QuickBooks Desktop as items received and vendor invoices. The flow is primarily from QuickBooks Desktop outbound to suppliers via TrueCommerce, and from TrueCommerce inbound to QuickBooks Desktop. The cadence is tied to your polling interval and QuickBooks Desktop availability.

How ml-connector handles it

ml-connector maintains a persistent SOAP session with QuickBooks Desktop via the QBWC polling model, requesting modified vendors, purchase orders, and bills on each poll. Before writing changes back, it retrieves the current EditSequence version counter to prevent concurrent-edit conflicts. Outbound purchase orders are formatted into TrueCommerce-compatible file layouts and written to the SFTP folder at integrationftp.truecommerce.com. Inbound EDI documents such as purchase order acknowledgments (855) and advance ship notices (856) are retrieved from TrueCommerce SFTP, parsed to extract line-item detail and ASN dates, and written into QuickBooks Desktop as item receipts and vendor invoice records. QBXML has a 60-second request timeout, so large purchase order or receipt batches are paginated. EditSequence counters prevent stale updates; each write re-fetches the current version. Every transaction is logged with full direction, field mappings, and error details for audit and replay.

A real-world example

A regional distributor uses QuickBooks Desktop to manage accounts payable and inventory, and connects to suppliers via TrueCommerce EDI. Before the integration, the procurement team manually re-keyed purchase orders from QuickBooks Desktop into TrueCommerce portal forms, and transcribed incoming EDI acknowledgments and receipts back into QuickBooks Desktop. With QuickBooks Desktop and TrueCommerce connected, each new purchase order in QuickBooks Desktop automatically flows to suppliers via EDI, and receipt and invoice documents from suppliers come back through TrueCommerce and post into QuickBooks Desktop. The manual re-entry step is eliminated, supplier acknowledgments appear in the accounts payable register on time, and the distributor avoids duplicate orders and missed receipts.

What you can do

• •Sync purchase orders from QuickBooks Desktop to TrueCommerce for EDI transmission to suppliers, with automatic order numbering and line-item detail.
• •Retrieve purchase order acknowledgments and advance ship notices from TrueCommerce EDI documents and write them into QuickBooks Desktop as item receipts.
• •Manage QBWC session authentication via credential handshake and maintain EditSequence version counters on every update to prevent conflicts.
• •Handle QBXML pagination for large batches and respect the 60-second timeout by splitting requests into manageable queries.
• •Provide a complete audit trail on every purchase order, receipt, and vendor record with timestamps, field mappings, and error replay capability.

Questions

How does ml-connector handle the QBWC polling model if QuickBooks Desktop must remain open and running?

ml-connector acts as the remote SOAP endpoint that QBWC polls on your specified interval. Your customer's QBWC agent, configured with your ml-connector endpoint URL, runs on the Windows machine alongside QuickBooks Desktop and calls your service periodically to request changes. ml-connector returns QBXML queries for the agent to execute against the open QuickBooks file. The customer remains responsible for keeping QuickBooks Desktop open and logged into the company file.

What happens if a purchase order is edited in QuickBooks Desktop after ml-connector has already sent it to TrueCommerce?

ml-connector retrieves the current EditSequence version counter before writing any update back into QuickBooks Desktop. If the record has been modified since the last sync, the EditSequence will not match, and the write is rejected. ml-connector logs this conflict, flags it in the audit trail, and requires manual review or a re-fetch and re-apply of the change. This prevents stale data from overwriting newer changes.

How are vendor and line-item details preserved when a purchase order moves from QuickBooks Desktop through TrueCommerce EDI to a supplier?

ml-connector reads the full purchase order structure from QuickBooks Desktop, including vendor name, items, quantities, unit prices, and delivery dates. It maps those fields to the TrueCommerce file format (typically X12 850 purchase order EDI structure), preserving vendor references and line-item detail. When acknowledgments and receipts return from suppliers via TrueCommerce EDI, ml-connector parses them and maps them back to QuickBooks Desktop item IDs and quantity received fields.