Xero EDI integration
Weredi connects EDI to Xero through Xero’s own API. A retailer’s 850 purchase order becomes a sales invoice, a supplier’s 810 becomes a bill, an 820 remittance becomes a payment on the invoices it names, and the invoices and payments you send by EDI are recorded too. You sign in with Xero; if you run several organisations, you pick which one.
The trial includes the Xero connector. No credit card.
What syncs with Xero
Five flows, each one a Xero invoice or payment created through the Xero API, on the contact you matched to the partner.
| EDI document | From | Becomes in Xero | What happens |
|---|---|---|---|
| 850 Purchase Order | Your trading partner | Sales invoice (ACCREC) | The retailer’s order becomes a sales invoice with the PO number as its reference, and each line’s item, quantity, price, account and tax rate. |
| 810 Invoice | Your trading partner | Bill (ACCPAY) | A supplier’s EDI invoice becomes a bill on that contact, coded to your expense accounts. |
| 820 Payment Order/Remittance Advice | Your trading partner | Payment | A customer’s remittance becomes payments on the invoices it lists, and its PDF is attached to each invoice paid. |
| 810 Invoice | You | Sales invoice (ACCREC) | The EDI invoice you send is recorded as a Xero sales invoice, so receivables match what the retailer received. |
| 820 Payment Order/Remittance Advice | You | Payment on a bill | A payment you send by EDI is recorded on the supplier bills it pays. |
You turn each flow on separately, per partner. Each push is logged as its own delivery with Xero’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 Xero field
The 5 flows above work out of the box. Every other document your partners exchange can reach Xero too: map its fields to the ones you need, and Weredi posts the result to Xero’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.
BCH-03ReferencePOC-03LineItems.QuantityDeliver 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 Xero
Connect Xero
Click Connect to Xero in Weredi, sign in and allow access. If your login sees several organisations, choose one; you can switch later.
Match your partners
Link each trading partner to its customer and vendor in Xero, 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 Xero; translate item numbers with lookup tables.
Turn on the flows
From then on, each document is pushed to Xero the moment it arrives or is sent. Errors come back in Xero’s own words.
What is specific to Xero
Xero has its own way of doing invoices, payments and attachments. The connector follows it rather than forcing a generic shape.
Several Xero organisations
Accountants and groups often reach several organisations with one login. Weredi shows an organisation switcher and pushes to the one you picked.
The source EDI, attached
A PDF of each EDI document is attached to the Xero record it created. Xero payments cannot carry files, so a remittance’s PDF goes on the invoice it pays.
Your tax rates, per line
Each line carries a Xero tax rate picked from your organisation’s own list, so GST/HST, QST or no-tax lines land exactly as your accountant set them up.
Account codes and item codes in lists
Account codes, item codes and tax types are read live from Xero and offered as lists in the mapping editor; no codes to look up by hand.
What you need
- A Weredi Plus plan or the 14-day trial: integrations are part of Plus.
- A Xero organisation and a user allowed to connect apps to it.
- Your revenue and expense account codes, and items in Xero if you track them.
- Tax rates set up in Xero for what you sell (GST/HST, QST, exempt).
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 Xero: what was sent, what Xero answered, and a retry button.
Weredi Plus
The Xero 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.
Xero EDI questions
Does Xero support EDI?
Not on its own. Xero has no X12 translator, so a retailer’s 850 or 810 cannot go into it directly. Weredi translates each document, posts it through the Xero API and exchanges the files with your trading partners.
How do I get EDI orders into Xero?
Connect Xero in Weredi, match the retailer to its contact, and turn on the 850 flow. Each purchase order becomes a Xero sales invoice with the PO number as its reference, the moment it arrives.
Can I use it with several Xero organisations?
Yes. When your Xero login reaches several organisations, Weredi shows a switcher and pushes documents to the one you pick.
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 can be mapped field by field and sent to Xero or any other system through mapped webhooks and the Weredi REST API.
How much does the Xero 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.
QuickBooks Online
Purchase orders become invoices, supplier EDI becomes bills, remittances become payments.
QuickBooks Online integration →
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 →
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.