SAP S/4HANA EDI integration
Weredi connects X12 EDI to SAP S/4HANA through SAP’s own APIs, on Cloud Public Edition, Private Cloud or on-premise. A retailer’s 850 becomes a sales order, a supplier’s 810 a supplier invoice against your purchase order, an 820 a payment advice SAP clears against the incoming payment, and the 810s you send are billing documents created from the order. No IDoc mapping project.
The trial includes the SAP connector. No credit card.
What syncs with SAP S/4HANA
Four flows, following SAP’s own document chain. Payments you make to suppliers come from SAP’s payment run, so outbound 820s are generated from SAP, not pushed into it.
| EDI document | From | Becomes in SAP | What happens |
|---|---|---|---|
| 850 Purchase Order | Your trading partner | Sales order | Created through the Sales Order API with the customer’s PO number and date. An order already in SAP for the same PO and sold-to party is reused, not doubled. |
| 810 Invoice | Your trading partner | Supplier invoice | Posted against your purchase order lines, with the tax code per line. |
| 820 Payment Order/Remittance Advice | Your trading partner | Payment advice | Tells SAP which invoices the incoming money pays; SAP clears them when the deposit arrives on the bank statement you import. |
| 810 Invoice | You | Billing document | Created from the sales order, so SAP prices and posts it; Weredi compares SAP’s total with the 810 you sent and flags a gap. |
You turn each flow on separately, per partner. Each push is logged as its own delivery with SAP’s answer, and a refused one can be sent again from the same screen.
A new connector, set up with you
The SAP S/4HANA connector shipped in November 2026 and is built on SAP’s published APIs and communication scenarios. Every SAP system is configured differently, so your first partner goes live after we run its documents with you in your sandbox or quality system.
Beyond the 850, 810 and 820
Any EDI document, mapped to any SAP field
The 4 flows above work out of the box. Every other document your partners exchange can reach SAP too: map its fields to the ones you need, and Weredi posts the result to SAP’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-03PurchaseOrderByCustomerPOC-03to_Item.RequestedQuantityDeliver 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 SAP S/4HANA
Connect SAP
Enter your S/4HANA API host and the communication user of a communication arrangement. Weredi only talks to SAP over HTTPS, through SAP’s own APIs.
Match your partners
Link each trading partner to its customer and vendor in SAP, 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 SAP; translate item numbers with lookup tables.
Turn on the flows
From then on, each document is pushed to SAP the moment it arrives or is sent. Errors come back in SAP’s own words.
What is specific to SAP S/4HANA
SAP is an ERP with its own document chain. The connector follows it instead of turning everything into an invoice.
SAP’s document chain, not shortcuts
Purchase orders become sales orders, your invoices are billing documents created from those orders, and supplier invoices reference your purchase orders. SAP keeps doing the pricing, tax and posting.
SAP prices the invoice, Weredi checks it
When you send an 810, Weredi creates the billing document from the order and compares SAP’s gross total with the invoice you sent, so a price gap is flagged before the retailer sees it.
Remittances as payment advices
An 820 becomes a payment advice listing the invoices paid. SAP clears them when the deposit shows up on your imported bank statement, the way SAP expects cash to be applied.
No double orders
Before creating a sales order or a supplier invoice, Weredi checks SAP for the same customer PO or supplier reference and reuses what is already there.
What you need
- A Weredi Plus plan or the 14-day trial: integrations are part of Plus.
- SAP S/4HANA Cloud Public Edition, Private Cloud or on-premise (not SAP ECC or Business One).
- A communication user and arrangements for the sales order (SAP_COM_0109), billing document (SAP_COM_0120) and supplier invoice (SAP_COM_0057) APIs.
- An HTTPS API endpoint Weredi can reach: on-premise systems publish one through a reverse proxy or API Management.
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 SAP: what was sent, what SAP answered, and a retry button.
Weredi Plus
The SAP S/4HANA 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.
SAP S/4HANA EDI questions
Does SAP S/4HANA support X12 EDI?
SAP’s own EDI is built on IDocs, so X12 documents need translating before SAP can use them. Weredi translates the X12 and writes it through SAP’s OData APIs instead, with no IDoc mapping.
How do I automate EDI into SAP S/4HANA?
Give Weredi your API host and a communication user, match each retailer to its sold-to party, and turn on the flows. Each 850 then becomes an SAP sales order when it arrives. We run the first documents with you in your sandbox before go-live.
Do I need SAP Integration Suite, PI/PO or the Cloud Connector?
No. Weredi calls SAP’s published APIs over HTTPS. An on-premise system needs one HTTPS endpoint reachable from the internet, through a reverse proxy or API Management.
Does it work with SAP ECC or SAP Business One?
No, the connector is for SAP S/4HANA: Cloud Public Edition, Private Cloud and on-premise. Other systems can receive any EDI document, mapped field by field, through mapped webhooks and the Weredi REST API.
How much does the SAP S/4HANA 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, and we run your first documents with you.
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 →
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.