QuickBooks Desktop and Tradeshift integration

What moves between them

The main flow runs from Tradeshift into QuickBooks Desktop. Invoices and credit notes received from suppliers through the Tradeshift network are polled periodically, mapped to QuickBooks vendors, and posted as bills and bill adjustments in the QuickBooks company file through the customer's on-site Web Connector agent. Purchase orders can also flow from Tradeshift into QuickBooks if the customer's procurement process relies on the network for order confirmation. All records carry the Tradeshift document ID in a custom field so rematch on re-query is idempotent.

How ml-connector handles it

ml-connector maintains OAuth 1.0a credentials for Tradeshift and polls the documents/v2/ endpoint at a schedule tied to your procurement cycle. For each invoice or credit note found, it looks up or creates the matching vendor in QuickBooks by querying vendors via SOAP through your Web Connector endpoint, then constructs a QBXML Bill or BillAdjustment request with line items mapped from the UBL document. Before posting, it fetches the current EditSequence token on the Bill or Account to prevent concurrent edit collisions, a requirement of QuickBooks SOAP. If the QBWC session times out (typical 60 seconds on large queries), ml-connector retries the request with pagination. Every bill post is logged with its Tradeshift document ID, so a failed downstream integration can replay the same bill without duplication.

A real-world example

A mid-sized manufacturer sources materials from suppliers worldwide and uses Tradeshift to receive invoices electronically. Before the integration, the AP team downloaded invoices from Tradeshift daily and manually entered them into QuickBooks Desktop, matching line items to purchase order numbers and cost centers. This process was error-prone and consumed 4 to 6 hours per week. With Tradeshift and QuickBooks Desktop connected, invoices flow automatically from the supplier network into the accounting ledger on a schedule set to the company's typical invoice receipt pattern. The AP team now spends that time on exception handling and reconciliation instead of data entry.

What you can do

• •Pull invoices and credit notes from Tradeshift and post them as bills and bill adjustments in QuickBooks Desktop, mapped to the correct vendor and cost center.
• •Validate EditSequence tokens before each bill modification to prevent concurrent edits and duplicate posts.
• •Handle SOAP session authentication and QBWC polling intervals configured to your procurement cycle, with automatic retries on timeout.
• •Track Tradeshift document IDs in QuickBooks bills so re-queried invoices are matched idempotently without creating duplicates.
• •Maintain a complete audit trail of every invoice post, with the ability to replay a failed bill into QuickBooks if a downstream system call fails.

Questions

How does ml-connector handle QuickBooks Desktop's requirement for EditSequence tokens?

Every bill modification in QuickBooks requires the current EditSequence version token to prevent concurrent edits. ml-connector queries the existing bill or account to fetch the current EditSequence before posting an update, ensuring the customer's Web Connector agent can commit the change without conflict.

Does the integration require QuickBooks to be running on the customer's machine?

Yes. QuickBooks Desktop is installed locally on Windows, and the Web Connector agent must be able to communicate with it. QuickBooks must be open and logged into the company file for the QBWC polling to succeed. ml-connector does not bypass this requirement; it simply operates your remote SOAP endpoint that the customer's agent calls.

What happens if an invoice appears in Tradeshift before the matching purchase order reaches QuickBooks?

ml-connector polls Tradeshift on a configurable schedule. If an invoice arrives before the PO, the integration can defer posting the bill until the PO is created, or post the bill with a reference to the Tradeshift document and allow the AP team to match it during reconciliation. The audit trail shows the complete history of each invoice so no details are lost.