QuickBooks Online and IBM Sterling integration

What moves between them

Incoming EDI invoices and purchase orders arrive in Sterling's mailbox from trading partners. ml-connector polls Sterling every 2-5 minutes, extracts each new EDI document, parses the vendor and line-item data, looks up the matching QuickBooks vendor and account, and writes a bill record into QuickBooks. Vendors and departments are mapped bidirectionally so QB line items land on valid GL accounts in Sterling configurations. The flow is primarily one-way inbound (Sterling to QB) for document creation.

How ml-connector handles it

ml-connector stores QuickBooks OAuth credentials and Sterling HTTP Basic or OAuth credentials encrypted. On the QB side it refreshes the OAuth bearer token when a call returns 401 (access tokens expire in 1 hour) and captures the realm_id from the initial OAuth callback to construct the correct API base URL. On the Sterling side it polls GET /B2BAPIs/svc/mailboxMessages/ on your schedule and extracts each arrived document payload. Because QB requires exact object representation with SyncToken for updates and additions, ml-connector fetches any existing bill for the EDI invoice number before writing, merges the payload with the SyncToken, then writes or updates atomically. Sterling EDI documents often contain vendor names and codes that must be normalized against QB's vendor list - ml-connector matches on vendor code first, then fuzzy-matches on name if needed. If a QB vendor does not exist yet, ml-connector can optionally create a new one. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-market distributor receives purchase orders and invoices from five key suppliers via EDI 850 and 810 standards through IBM Sterling. Before integration, the procurement team received EDI files in Sterling's mailbox, manually extracted invoice data, and entered bills into QuickBooks by hand - a process that took two days per week and introduced re-keying errors. With Sterling and QuickBooks Online connected, each incoming EDI invoice flows into QB as a bill assigned to the correct supplier and GL account within minutes. The procurement team now reviews only bills that fail to match (missing vendors, invalid accounts) and approves the rest in QB's bill review workflow. Month-end close starts with 95 percent of payables already recorded.

What you can do

• •Translate EDI invoices and purchase orders from Sterling into QuickBooks bill records, assigned to the correct vendor and GL account.
• •Keep QuickBooks vendors and departments in sync with Sterling trading partner configurations through bidirectional mapping.
• •Poll Sterling's mailbox on a schedule you control and extract full EDI payloads without waiting for a push.
• •Handle OAuth 2.0 token refresh on QuickBooks and HTTP Basic or OAuth 2.0 authentication on Sterling with a full audit trail.
• •Replay bills if a downstream write to QB fails, with no duplicate invoices or orphaned records.

Questions

Which direction does EDI data flow between Sterling and QuickBooks?

The primary flow is Sterling inbound to QuickBooks. EDI invoices, purchase orders, and remittances that arrive in Sterling's mailbox are translated and written to QB as bills. Vendors and departments can be synced bidirectionally so QB accounts accept the incoming line items on valid GL dimensions. QB vendor and bill updates do not flow back to Sterling - the connector is primarily inbound.

Does ml-connector need direct network access to the Sterling instance?

Yes. IBM Sterling B2B Integrator runs on customer infrastructure (on-premises or customer-managed cloud), so ml-connector must reach it over your network - typically VPN, DMZ exposure, or private cloud link. Sterling REST API base URL, host, and port are customer-configured and must be provided during setup. QB Online is cloud-hosted, so no special network access is needed on that side.

What happens when an EDI vendor is not found in QuickBooks?

ml-connector matches EDI vendor codes against QB vendor records first, then falls back to fuzzy name matching. If no match is found, the bill record is flagged in the audit log and halted until you either create the vendor in QB or map it manually in ml-connector. Optionally, ml-connector can auto-create new QB vendors from EDI data if your process approves it, but the default is to flag and wait.