QuickBooks Online and Orderful integration
QuickBooks Online runs accounting and vendor management for small-to-mid-market businesses. Orderful translates and routes EDI documents to trading partners. Connecting them keeps purchase orders synchronized with supplier EDI acknowledgments and ensures incoming invoices from partners land in QuickBooks Online as bills without manual re-entry. ml-connector manages the different authentication methods and handles EDI schema mapping on both sides.
What moves between them
Purchase orders flow from QuickBooks Online to Orderful as EDI 850 documents, routed to the correct trading partner by ISA identifier. Incoming EDI 855 purchase order acknowledgments and 810 invoices from Orderful are mapped back into QuickBooks Online as bills and purchase order changes, keyed by vendor reference and PO number. The sync runs on a configurable schedule, typically daily or on-demand when new EDI documents arrive via webhook.
How ml-connector handles it
ml-connector stores the OAuth refresh token encrypted and refreshes the access token when calls return 401, capturing the realm_id from the initial QuickBooks Online authorization. It stores the Orderful API key encrypted and presents it on every request in the orderful-api-key header. On the QuickBooks Online side, it fetches full purchase order details after each webhook event, extracts line items and vendor information, and maps them to X12 850 format with the correct sender and receiver ISA identifiers. Incoming Orderful webhooks containing EDI 855 or 810 documents are parsed, validated against the original PO, and posted as bills or purchase order adjustments in QuickBooks Online, matching the correct account and department. QuickBooks Online webhook payloads can arrive out of order or duplicated, so ml-connector deduplicates by entity ID and operation; Orderful transactions are keyed by document instance ID. All records carry full audit trails and can be replayed if a downstream call fails. Refresh token rotation every 24-26 hours is tracked so a revoked token surfaces immediately.
A real-world example
A small-to-mid-market distributor uses QuickBooks Online for accounting and manages relationships with 30-50 suppliers who send EDI documents. Previously, order acknowledgments and invoices arrived as EDI to their translation service, which the operations team had to manually re-enter into QuickBooks Online, creating duplicate entry work and frequent reconciliation gaps between what the EDI said and what accounting recorded. With QuickBooks Online and Orderful connected, outbound purchase orders flow automatically to suppliers who support EDI 850, and incoming acknowledgments and invoices are translated from EDI 855 and 810 formats and posted directly as bills in QuickBooks Online, matched to the original PO and vendor. The team eliminates manual data entry, reduces invoice-matching errors, and can see supply chain events in real time without leaving QuickBooks Online.
What you can do
- Map QuickBooks Online purchase orders to Orderful EDI 850 format and send to the correct trading partner by ISA identifier.
- Translate incoming Orderful EDI 855 and 810 documents into QuickBooks Online bills and purchase order acknowledgments, keyed to the original PO.
- Authenticate QuickBooks Online via OAuth 2.0 with automatic token refresh and Orderful via static API key, both stored encrypted.
- Deduplicate and order QuickBooks Online webhooks and Orderful transactions by entity ID and document instance to ensure exactly-once delivery.
- Audit every record mapped, sent, or received, with full error replay and transaction state visibility.
Questions
- How does ml-connector handle the different authentication methods between QuickBooks Online and Orderful?
- ml-connector stores the QuickBooks Online OAuth refresh token encrypted and automatically refreshes the access token when it expires (1 hour) or when QuickBooks Online returns 401. For Orderful, it stores the static API key encrypted and includes it in the orderful-api-key header on every request. Both credentials are validated at connection setup and tracked for expiry or rotation.
- What EDI documents can flow between QuickBooks Online and Orderful?
- Purchase orders in QuickBooks Online map to X12 850 format for Orderful. Incoming EDI 855 purchase order acknowledgments and 810 invoices are translated back into QuickBooks Online as bills or purchase order changes, matched to the original PO by vendor reference and PO number. Other EDI document types (856 ship notices, 846 inventory inquiries) can be received by Orderful but are not yet mapped into QuickBooks Online.
- How often does data sync between the two systems?
- ml-connector syncs on a configurable schedule, typically daily or on-demand when new EDI documents arrive via Orderful webhook. QuickBooks Online webhook events for purchase orders trigger an immediate fetch of the full PO record, and Orderful webhooks for incoming EDI are processed as they arrive or polled every 5-10 minutes if webhooks are not enabled.
Related integrations
More QuickBooks Online integrations
Other systems that connect to Orderful
Connect QuickBooks Online and Orderful
Free to use. Add your credentials, ping your real systems, and see if we fit.
Get started