QuickBooks Desktop and IBM Sterling integration

What moves between them

Vendor and bill data flows from QuickBooks Desktop into IBM Sterling. ml-connector polls QuickBooks via the Web Connector for new and modified vendors and bills, translates vendor master records into EDI 997 setup transactions, and converts bills into EDI 810 invoices. The integration then posts those documents into IBM Sterling's mailbox API, where they are routed to the appropriate trading partners over AS2 or SFTP according to Sterling's trading partner profiles. Purchase orders and advanced ship notices from Sterling flow inbound through the mailbox API and are converted into QuickBooks purchase order and bill records. Reference data such as item codes and cost centers are synchronized bidirectionally.

How ml-connector handles it

ml-connector implements the SOAP Web Connector interface that QuickBooks expects, handling the session-token authenticate() handshake on each poll cycle and retrieving the EditSequence (version counter) before modifying any records to prevent concurrent-edit conflicts. On the QuickBooks side, it manages QBXML request timeouts (approximately 60 seconds) by paginating large queries and querying only changed records within a modified-date window. On the IBM Sterling side, it stores the customer's B2Bi hostname, port, and credentials encrypted, authenticates with HTTP Basic Auth or OAuth 2.0 (retrieving tokens from the customer's local token endpoint), and posts EDI documents into the mailbox API with idempotency keys to prevent duplicate submissions. EDI translation uses industry-standard X12 850/810/997 segments, mapping QuickBooks vendor/item/account codes to EDI identifier types. The integration tracks message delivery status in Sterling's mailbox, implements exponential backoff on API 429 responses, and maintains a full audit trail of every QBXML query, EDI translation, and Sterling API call.

A real-world example

A mid-market electronics distributor runs QuickBooks Desktop for accounting and inventory management, and uses IBM Sterling to exchange EDI 850 purchase orders and 810 invoices with 30 manufacturing suppliers across AS2 and SFTP. Before the integration, the procurement team exported bills and purchase orders from QuickBooks as CSV, manually mapped them to EDI 810 and 850 formats in a spreadsheet, and uploaded them to the Sterling gateway. Inbound supplier invoices arrived as EDI 810s, were converted to text by the EDI gateway, and then manually entered back into QuickBooks by the accounting team. With QuickBooks Desktop and IBM Sterling connected, each bill created in QuickBooks is automatically translated to EDI 810 and routed to the supplier, inbound supplier invoices are converted to QuickBooks bills ready for approval, and the manual translation step is eliminated. Purchase orders flow the opposite direction, reducing order-entry time and invoice reconciliation errors.

What you can do

• •Translate QuickBooks Desktop vendors and bills into EDI 810 invoices and route them to trading partners via IBM Sterling's AS2 and SFTP gateways.
• •Receive inbound EDI 850 purchase orders and 810 invoices from Sterling and convert them into QuickBooks purchase orders and bills.
• •Manage the QBXML session-token handshake and authenticate to IBM Sterling with HTTP Basic Auth or OAuth 2.0 (local instance).
• •Prevent duplicate EDI submissions and concurrent edits in QuickBooks by tracking EditSequence values and using idempotency keys.
• •Maintain a complete audit log of every QBXML request, EDI translation, and Sterling API call, with the ability to replay failed transactions.

Questions

How does ml-connector act as the Web Connector for QuickBooks Desktop?

ml-connector implements the SOAP Web Connector interface that QuickBooks expects. The customer configures their QuickBooks Web Connector to call ml-connector's SOAP endpoint at a schedule you set (typically 5-15 minutes). ml-connector authenticates the Web Connector via session token, queries QuickBooks for changed records using ModifiedDateRangeFilter, and retrieves them in QBXML format. The Web Connector then feeds that data into QuickBooks, keeping both sides synchronized.

Which direction does data move, and what EDI standards are supported?

Vendors and bills flow from QuickBooks Desktop to IBM Sterling as EDI 810 invoices and 997 setup transactions. Purchase orders and invoices flow inbound from Sterling to QuickBooks as EDI 850 and 810, converted back into QuickBooks purchase order and bill records. The integration supports ANSI X12 EDI standards (850, 810, 997) and routes documents via Sterling's AS2 and SFTP adapters according to trading partner profiles.

Does this work with on-premises IBM Sterling, and how are credentials managed?

Yes, IBM Sterling B2B Integrator is deployed on-premises or in a hybrid-cloud environment, so ml-connector connects directly to the customer's B2Bi instance using the hostname and port they provide. Credentials for both QuickBooks and Sterling are stored encrypted. For Sterling, ml-connector can authenticate with HTTP Basic Auth or OAuth 2.0 (Client Credentials), retrieving tokens from the customer's local token endpoint, and tracking certificate and token expiry so renewals do not cause outages.