QuickBooks Online EDI integration
Weredi connects EDI to QuickBooks Online (QBO) directly, with no middleware and no CSV import. A retailer’s 850 purchase order becomes a QuickBooks invoice, a supplier’s 810 becomes a bill, an 820 remittance becomes a payment applied to its invoices, and the 810 invoices and 820 payments you send are recorded too.
The trial includes the QuickBooks connector. No credit card.
What syncs with QuickBooks Online
Five flows, each one a native QuickBooks Online transaction created through Intuit’s API, under the customer or vendor you matched to the partner.
| EDI document | From | Becomes in QuickBooks | What happens |
|---|---|---|---|
| 850 Purchase Order | Your trading partner | Invoice | The retailer’s order becomes an invoice for that customer, line by line: dates, items, quantities, prices and tax codes. |
| 810 Invoice | Your trading partner | Bill | A supplier’s EDI invoice becomes a bill under that vendor, ready to approve and pay. |
| 820 Payment Order/Remittance Advice | Your trading partner | Payment | A customer’s remittance becomes a payment applied to the invoices it lists, by invoice number. |
| 810 Invoice | You | Invoice | The EDI invoice you send is recorded as a QuickBooks invoice, so receivables match what the retailer received. |
| 820 Payment Order/Remittance Advice | You | Bill payment | A payment you send by EDI is recorded against that vendor’s bills. |
You turn each flow on separately, per partner. Each push is logged as its own delivery with QuickBooks’s answer, and a refused one can be sent again from the same screen.
Beyond the 850, 810 and 820
Any EDI document, mapped to any QuickBooks field
The 5 flows above work out of the box. Every other document your partners exchange can reach QuickBooks too: map its fields to the ones you need, and Weredi posts the result to QuickBooks’s API, or to any system around it, the moment the document arrives.
Prefer not to build it? Our team sets up the mapping and the webhook for you.
Pick the documents
An automation listens for any transaction set, from any partner or only the ones you choose, inbound or outbound.
Map element to field
The mapping editor turns X12 elements into the exact JSON your target expects, with lookup tables for codes and item numbers.
TD5-05ShipMethodRefREF-02TrackingNumDeliver by webhook or API
A webhook posts it as JSON, XML or a form, signed with a bearer token, basic auth, an API key, HMAC or OAuth, and retried if the endpoint is down. Going the other way, your system sends documents out through the Weredi REST API.
How to connect EDI to QuickBooks Online
Connect QuickBooks
Click Connect to QuickBooks in Weredi, sign in with Intuit and choose the company. There are no keys to copy.
Match your partners
Link each trading partner to its customer and vendor in QuickBooks, once. Every document from that partner then lands on the right account.
Review the mapping
Each document starts from a reference mapping. Pick accounts, taxes and items from lists read live from QuickBooks; translate item numbers with lookup tables.
Turn on the flows
From then on, each document is pushed to QuickBooks the moment it arrives or is sent. Errors come back in QuickBooks’s own words.
What is specific to QuickBooks Online
QuickBooks Online is the connector every other Weredi connector was modelled on. These are the details it handles for you.
The original EDI travels with the transaction
A PDF of the source EDI document is attached to the QuickBooks transaction, so whoever opens the invoice or bill sees exactly what the partner sent.
Canadian sales tax, the QuickBooks way
QuickBooks Online Canada refuses an invoice without a GST/HST code on every line. The mapping sets the tax code per line and lets QuickBooks compute the tax, including zero-rated lines for exports.
Your accounts, items and classes in lists
Accounts, products and services, tax codes, classes and locations are read live from your company and offered as lists, with accounts filtered to the right type for each field.
Errors you can act on
When QuickBooks refuses a document, its own message shows on the delivery, for example a missing GST/HST rate. Fix the mapping and send it again; nothing is retyped.
What you need
- A Weredi Plus plan or the 14-day trial: integrations are part of Plus.
- A QuickBooks Online company and a user allowed to connect apps to it.
- Your products and services in QuickBooks, or a lookup table from the retailer’s item numbers to yours.
- Your sales tax codes set up in QuickBooks (GST/HST, QST, zero-rated).
What Weredi handles on the EDI side
- The connection to each trading partner: AS2, SFTP or FTPS (with PGP), or a VAN mailbox.
- 997 functional acknowledgments, sent and reconciled.
- Validation of every document against the partner’s own guide before it leaves.
- The 855, 856 (with SSCC labels) and 810 built from the partner’s 850, ready to send.
- A record of every push to QuickBooks: what was sent, what QuickBooks answered, and a retry button.
Weredi Plus
The QuickBooks Online integration is in Weredi Plus
One flat price: unlimited trading partners and transactions, all six ERP connectors, mappings, lookup tables, automations and the REST API. Try it free for 14 days with your own partners.
QuickBooks Online EDI questions
Does QuickBooks Online support EDI?
Not on its own. QuickBooks Online cannot read or send X12 documents such as the 850 or 810. An EDI provider has to translate them and post them through Intuit’s API; Weredi does both, and also exchanges the files with your trading partners.
How do I import EDI purchase orders into QuickBooks Online?
Connect QuickBooks in Weredi, match the retailer to its customer in QuickBooks, and turn on the 850 flow. Each purchase order then becomes a QuickBooks invoice when it arrives, with no CSV and no retyping.
Does it work with QuickBooks Desktop or Enterprise?
No. The connector is for QuickBooks Online only. Desktop and Enterprise can exchange data with Weredi through its REST API, which our team can set up for you.
Which EDI documents does it cover?
Out of the box: purchase orders (850) in, invoices (810) in and out, and payments (820) in and out. Any other EDI document, such as an 856, 860 or 846, can be mapped field by field and sent to QuickBooks or any other system through mapped webhooks and the Weredi REST API. Weredi also builds your 855, 856 and 810 replies from the 850 and handles the 997 acknowledgments.
How much does the QuickBooks Online integration cost?
It is part of Weredi Plus, $999 CAD a month at a flat price with unlimited trading partners and transactions. The 14-day free trial includes it, with no credit card.
Other ERP integrations
The same EDI side, connected to a different system.
Oracle NetSuite
Invoices, vendor bills and payments through SuiteTalk REST, with no duplicates on re-send.
Oracle NetSuite integration →
SAP S/4HANANew
Sales orders, supplier invoices, billing documents and payment advices through SAP’s APIs.
SAP S/4HANA integration →
Xero
Sales invoices, bills and payments from EDI, in the Xero organisation you choose.
Xero integration →
Sage Accounting
Sales and purchase invoices, receipts and payments from EDI, with Canadian tax regions.
Sage Accounting integration →
OdooNew
Confirmed sales orders, vendor bills and registered payments, on Odoo 17 to 20.
Odoo integration →Running something else?
Every other system connects through the Weredi REST API and webhooks. If you would rather not build it, our team will.
See all integrations →
Speak to an EDI expert today
Connect with one of our experienced EDI experts to learn how Weredi’s Modern EDI Platform can handle your company’s EDI needs.