EDI X12

Sage Accounting EDI integration

Weredi connects EDI to Sage Accounting (Sage Business Cloud Accounting) through Sage’s API. A retailer’s 850 purchase order becomes a sales invoice, a supplier’s 810 becomes a purchase invoice, an 820 becomes a customer receipt allocated to its invoices, and the invoices and payments you send by EDI are recorded too. All five flows are tested end to end.

Live connectorSign in with SageIncluded in Weredi Plus

Start 14-day free trial

The trial includes the Sage connector. No credit card.

Example · 850 purchase order → Sage sales invoiceMapping

ISA*00*…*ZZ*RETAILER*ZZ*SUPPLIER*…~

ST*850*0001~

BEG*00*SA*4500123456**20261104~

PO1*1*24*CA*18.50**IN*CT-88214*UP*062345000127~

PID*F****Cedar planter, large~

ISA-06contact_idmatched once

BEG-03contact_reference4500123456

BEG-05date2026-11-04

PO1-02invoice_lines.quantity24

PO1-04invoice_lines.unit_price18.50

The customer comes from the partner, matched once. Every other field is editable in the mapping editor.

Any document

5 ready flows, the rest by mapping

0 CSV files

Pushed through the Sage API

Unlimited

Trading partners and transactions

FR · EN

Built and supported in Montréal

What syncs with Sage Accounting

Five flows, each one a Sage Accounting artefact created through the Sage API, on the contact you matched to the partner.

EDI document	From	Becomes in Sage	What happens
850 Purchase Order	Your trading partner	Sales invoice	The retailer’s order becomes a sales invoice with the PO number as the customer reference, the lines, and the tax region you sell from.
810 Invoice	Your trading partner	Purchase invoice	A supplier’s EDI invoice becomes a purchase invoice on that contact, coded to your ledger accounts.
820 Payment Order/Remittance Advice	Your trading partner	Customer receipt	A customer’s remittance becomes a receipt allocated to the invoices it lists, found by invoice number.
810 Invoice	You	Sales invoice	The EDI invoice you send is recorded as a Sage sales invoice, freight lines included.
820 Payment Order/Remittance Advice	You	Supplier payment	A payment you send by EDI is recorded against the supplier’s purchase invoices.

850 → Sales invoice · from your partner

The retailer’s order becomes a sales invoice with the PO number as the customer reference, the lines, and the tax region you sell from.

810 → Purchase invoice · from your partner

A supplier’s EDI invoice becomes a purchase invoice on that contact, coded to your ledger accounts.

820 → Customer receipt · from your partner

A customer’s remittance becomes a receipt allocated to the invoices it lists, found by invoice number.

810 → Sales invoice · from you

The EDI invoice you send is recorded as a Sage sales invoice, freight lines included.

820 → Supplier payment · from you

A payment you send by EDI is recorded against the supplier’s purchase invoices.

You turn each flow on separately, per partner. Each push is logged as its own delivery with Sage’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 Sage field

The 5 flows above work out of the box. Every other document your partners exchange can reach Sage too: map its fields to the ones you need, and Weredi posts the result to Sage’s API, or to any system around it, the moment the document arrives.

855856860846852812824214EDIFACTand the rest

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-03contact_referencePOC-03invoice_lines.quantity
Deliver 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 Sage Accounting

Connect Sage
Click Connect to Sage in Weredi, sign in with your Sage account and choose the business.
Match your partners
Link each trading partner to its customer and vendor in Sage, 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 Sage; translate item numbers with lookup tables.
Turn on the flows
From then on, each document is pushed to Sage the moment it arrives or is sent. Errors come back in Sage’s own words.

What is specific to Sage Accounting

Sage Accounting has firm rules about quantities, numbering and allocations. These are the ones the connector takes care of.

Canadian tax regions

Sage needs to know which province a sale is taxed in. The mapping sets the tax region (Québec, Ontario…) and a tax rate per line, including zero-rated goods such as fresh produce.

Quantities that stay quantities

Sage keeps a per-unit quantity only on lines tied to a product or service. Map lines to your Sage products and 24 cases stay 24 cases; without one, Weredi keeps the line total right.

Invoice numbers Sage accepts

Sage numbers invoices as a prefix plus a number. Weredi splits an EDI invoice number such as INV17930 into both parts, so your numbering is kept.

Payments that never overpay

Each allocation is capped at what is still outstanding on the invoice, so a remittance never leaves Sage with an overpaid invoice.

What you need

A Weredi Plus plan or the 14-day trial: integrations are part of Plus.
A Sage Accounting business (the cloud product, not Sage 50, 300 or Intacct) and a user allowed to connect apps.
Products or services in Sage for the items you sell, so quantities are kept.
Your tax rates in Sage, and the province you sell from.

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 Sage: what was sent, what Sage answered, and a retry button.

Weredi Plus

The Sage Accounting 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.

$999 CAD / month

Start 14-day free trial Compare plans

No credit card · Cancel anytime

Sage Accounting EDI questions

Which Sage product does it connect to?

Sage Accounting, the cloud product also called Sage Business Cloud Accounting. Sage 50, Sage 300 and Sage Intacct are different products and are not connected; they can exchange data with Weredi through its REST API.

How do I import EDI purchase orders into Sage Accounting?

Connect Sage in Weredi, match the retailer to its contact, and turn on the 850 flow. Each purchase order becomes a Sage sales invoice when it arrives, with the PO number as the customer reference.

Does it handle Canadian sales tax?

Yes. Each invoice carries the tax region you sell from (Québec, Ontario…) and a Sage tax rate per line, including zero-rated goods.

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, all five tested end to end. Any other EDI document can be mapped field by field and sent to Sage or any other system through mapped webhooks and the Weredi REST API.

How much does the Sage 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.