Italy
FatturaPA through the Sistema di Interscambio (SDI)
EDI · E-invoicing · Peppol
EDI and e-invoicing. Partners ready on day one.
Trading partners still need purchase orders, ship notices and invoices to move without a project on either side. SAIL onboards them over EDI, API, files, portal or email, and delivers the same invoice data to every e-invoicing mandate your customers and suppliers require.
What this page covers
Everything related to EDI and e-invoicing, in one place.
Buyers ask for EDI. Governments ask for e-invoices. Carriers ask for ASNs. SAIL is the business network platform that treats those as onboarding plans, not integration projects, so you stay findable when people search for EDI, Peppol, AS2 or country mandates, and ready when they need to connect.
EDI
Electronic data interchange that partners can actually join
X12 and EDIFACT documents, AS2 and SFTP connections, acknowledgements and partner guides. Partners with B2B systems connect directly. Partners without IT join by portal, spreadsheet, email or PDF, and you still receive clean EDI-shaped data.
E-invoicing
One invoice model. Every country network.
Peppol, SDI, KSeF, XRechnung, Factur-X, CFDI and more. Your ERP keeps one invoice. SAIL maps it to the format and clearance network each country requires, and keeps the archive and evidence with the transaction.
EDI documents
The documents partners exchange every day
Order to cash is still the core of most trading partner networks. SAIL maps the documents you need, and the acknowledgements that prove they arrived.
| Document | Common codes | Direction |
|---|---|---|
| Purchase order | 850 / ORDERS | Buyer to supplier |
| Order acknowledgement | 855 / ORDRSP | Supplier to buyer |
| Advance ship notice | 856 / DESADV | Supplier to buyer |
| Invoice | 810 / INVOIC | Supplier to buyer |
| Payment advice | 820 / REMADV | Buyer to supplier |
| Functional acknowledgement | 997 / CONTRL | Automatic |
E-invoicing mandates
Country rules change. Your invoice data should not.
Mandatory e-invoicing is rolling out across Europe, LatAm and beyond. Each market has its own format, network and clearance step. SAIL keeps one canonical invoice and configures the mandate on top.
Germany
XRechnung and ZUGFeRD for B2G and B2B
France
Factur-X and the national e-invoicing rollout
Belgium and EU
Peppol BIS Billing and Access Point exchange
Poland
KSeF national e-invoicing
Mexico
CFDI 4.0 fiscal invoices
How partners connect
Plan A, B, C or D. Whatever they already run
Plan A
EDI or API
Partners with B2B systems connect directly. Many are already on the SAIL network.
Plan B
AS2, SFTP or files
Partners who exchange files send them as they are. SAIL maps the format.
Plan C
Web portal & forms
Partners with no IT work in a browser. You receive clean data.
Plan D
Email & PDF
Partners who only email keep emailing. SAIL reads it and turns it into data.
Built in
Standards and networks SAIL already knows
Native coverage across EDI, e-invoicing, healthcare and payments standards, kept current so a new mandate is a configuration change, not a rebuild.
EDI X12EDIFACTTRADACOMSEANCOMODETTEVDAAS2AS4SFTPAPIPeppol BISUBLcXMLFatturaPA / SDIXRechnungZUGFeRDFactur-XKSeFCFDI 4.0HL7FHIRISO 20022and hundreds more
Why teams search for this
When “we need EDI” really means “we need partners live”
A major customer asks for EDI. A government sets an e-invoicing deadline. A 3PL needs ASNs on AS2. The project plan used to stretch 8 to 22 weeks per partner. With SAIL you describe the outcome, review the onboarding plan, invite one partner or thousands, and trade the same day.
- No IT project on your side. Describe what you need in plain words. Approve the plan.
- No IT on their side either. They connect the way they already work.
- Always connected. If one route fails, the next plan takes over and trading continues.
Bring us your partners
Ready for EDI and e-invoicing on day one.
One trading partner or your whole network. Logistics, supply chain, SMB or a regulated industry. The same platform.