EDI Specifications Reference

EDI Specifications: Complete Reference

Article Type: Reference Audience: Solution Architects, EDI Analysts, Integration Specialists, Partners Module: EDI Processing & EDINation Connector Applies to Versions: Fuuz 2026.2+

1. Overview

Fuuz provides native EDI processing through the EDINation connector and the EdiFabric specification library — one of the most comprehensive EDI reference platforms available. This reference catalogs every EDI standard, version, transaction set, and message type supported by the library, along with industry context and integration guidance.

EDI documents are exchanged through Fuuz's FTP connector (for AS2/SFTP/FTP file transport), HTTP connector (for REST-based EDI APIs and web EDI), or gateway Local File driver (for VAN file drops). The EDINation connector then parses, validates, transforms, and generates EDI documents within Fuuz data flows. This architecture means Fuuz handles the complete EDI lifecycle — transport, parsing, transformation, validation, acknowledgment, and generation — without third-party EDI middleware.

2. Native EDI Connector and Bindings

Fuuz provides a Named Application Connector for EDINation (EdiFabric) that includes four dedicated JSONata bindings for EDI processing within Fuuz data flows:

Fuuz Binding	Function	Description
$readEDI(format, file, options)	Parse	Reads an EDI document (X12 or EDIFACT) and returns structured JSON. Supports options for charset, error handling, EANCOM S3 syntax, and custom model definitions.
$writeEDI(format, data, options)	Generate	Converts JSON data into a properly formatted EDI string. Supports whitespace preservation, charset encoding, and EANCOM S3 syntax.
$ackEDI(format, data, options)	Acknowledge	Generates functional acknowledgment documents (997/999 for X12, CONTRL for EDIFACT) from received EDI data.
$validateEDI(format, data, options)	Validate	Validates EDI documents against specification rules and returns validation results.

Supported format parameters: 'x12' and 'edifact'

3. ANSI ASC X12 (North American Standard)

The dominant EDI standard in North America for all commercial transactions. Fuuz's EdiFabric library supports all X12 versions from 2040 through 8060 and 300+ transaction sets.

X12 Version Support

Version	Release Year	Status	Common Usage
2040	1987	Legacy	Rarely encountered. Oldest supported version.
3010 – 3070	1988 – 1991	Legacy	Declining use. Some legacy government/defense, automotive, and retail systems.
4010	1992	Active — Most Common	Dominant version in retail, distribution, manufacturing. Walmart, Amazon, Target, most major retailers mandate 4010.
4020 – 4060	1993 – 1995	Active	Some retail and manufacturing. 4050 growing as 4010 replacement.
5010	1996	Active — Mandatory for Healthcare	HIPAA mandated version. All US healthcare EDI uses 5010.
5020 – 6050	1997 – 2001	Active	Moderate use in newer implementations.
7030	2003	Active — Next HIPAA Version	Proposed next HIPAA mandate. Adoption growing.
7010 – 8060	2002 – 2012	Active	Latest versions. Limited adoption.

X12 Transaction Sets — Retail and Supply Chain

Transaction Set	Name	Direction	Common Usage	Concerns / Limitations
850	Purchase Order	Buyer → Seller	Universal. Walmart, Amazon, Target, Home Depot, Costco all require.	Most-used transaction. Complex mapping with line-item detail, allowances, and special instructions.
855	PO Acknowledgment	Seller → Buyer	Response to 850. Confirms acceptance, rejection, or changes.	Must reference original 850 PO number. Line-item level acceptance/rejection.
856	ASN / Ship Notice	Seller → Buyer	Advance Shipment Notice with carton/pallet detail.	Most complex common transaction. Hierarchical loop structure. GS1-128 compliance. Chargebacks for ASN errors are common (especially Walmart).
810	Invoice	Seller → Buyer	Billing document. Maps to 850 PO and 856 ASN.	Three-way match (PO/ASN/Invoice) failures cause payment delays. Tax calculation complexity.
846	Inventory Inquiry/Advice	Either direction	Inventory availability or status reporting.	Used for VMI (Vendor Managed Inventory) programs. Location-level detail.
832	Price/Sales Catalog	Seller → Buyer	Product catalog with pricing, descriptions, UPCs.	Can be very large (thousands of items). UPC/GTIN validation.
830	Planning Schedule	Buyer → Seller	Demand forecast and delivery schedule.	Critical for manufacturing planning. Automotive and industrial supply chains. Firm vs. forecast zones.
860	PO Change Request	Buyer → Seller	Modifications to existing 850 PO.	Must reference original PO. Version control complexity.
862	Shipping Schedule	Buyer → Seller	Specific delivery dates and quantities.	Automotive JIT/JIS critical. Sequence-level delivery requirements. Dock code precision.
997	Functional Acknowledgment	Receiver → Sender	Confirms receipt and syntax validation.	Required for every X12 interchange. Fuuz $ackEDI() generates automatically.

X12 Transaction Sets — Transportation and Logistics

Transaction Set	Name	Direction	Common Usage	Concerns / Limitations
204	Motor Carrier Load Tender	Shipper → Carrier	Requests carrier to transport shipment.	Origin/destination, weight, pickup/delivery dates. Carrier response via 990.
210	Motor Carrier Freight Details	Carrier → Shipper	Freight invoice/bill.	Rating and billing detail. Accessorial charges.
214	Shipment Status	Carrier → Shipper	In-transit tracking status updates.	Real-time tracking events. Status code standardization varies by carrier.
990	Response to Load Tender	Carrier → Shipper	Acceptance/rejection of 204.	Time-sensitive — carriers expect fast response.
301 / 315 / 322	Ocean Booking / Status / Intermodal	Carrier ↔ Shipper	International ocean freight and intermodal operations.	Container details, port-level status, customs clearance milestones.

X12 Transaction Sets — Warehouse

Transaction Set	Name	Direction	Concerns / Limitations
940	Warehouse Shipping Order	Depositor → Warehouse	3PL operations. Order-level and item-level shipping instructions.
943 / 944	Stock Transfer (Shipment / Receipt)	Either direction	Transfer between warehouse locations. Quantity discrepancy handling.
945	Warehouse Shipping Advice	Warehouse → Depositor	ASN equivalent for warehouse operations.
947	Inventory Adjustment Advice	Warehouse → Depositor	Inventory count discrepancies, damage. Reconciliation triggers.

X12 Transaction Sets — Finance

Transaction Set	Name	Common Usage	Concerns / Limitations
820	Payment Order / Remittance Advice	Electronic payment with remittance detail.	Bank routing, payment method. ACH/wire integration. Also used for healthcare premium payments.
824	Application Advice	Error notification for previously sent transactions.	Used when a transaction fails business validation (not syntax). Exception handling workflow.
812	Credit/Debit Adjustment	Price adjustments, chargebacks, allowances.	Chargeback processing. Deduction management.

4. X12 HIPAA (US Healthcare — Federally Mandated)

Version 005010 is currently mandated by CMS for all HIPAA-covered transactions. Version 007030 is proposed for future mandate. Non-compliance results in federal penalties.

HIPAA Compliance: Fuuz EDI processing of HIPAA transactions must comply with HIPAA Privacy and Security Rules. PHI (Protected Health Information) in EDI documents requires encryption in transit and at rest. Fuuz platform security controls (TLS, encryption, access controls) cover these requirements, but trading partner agreements and BAAs (Business Associate Agreements) must be in place.

Transaction Set	Name	Direction	Concerns / Limitations
837P / 837I / 837D	Healthcare Claims (Professional / Institutional / Dental)	Provider → Payer	Complex claim attachment requirements. Diagnosis/procedure code combinations. NPI validation. Revenue codes and DRG grouping for institutional claims.
835	Payment / Remittance Advice	Payer → Provider	Adjustment reason codes (CARCs/RARCs). Secondary/tertiary payer coordination. Complex reconciliation with 837.
270 / 271	Eligibility Inquiry / Response	Provider ↔ Payer	Real-time or batch. Complex benefit detail (deductibles, copays, coinsurance, maximums).
276 / 277	Claim Status Request / Response	Provider ↔ Payer	Status category codes. Detailed error information.
278	Prior Authorization	Provider ↔ Payer	Real-time certification requirement growing. CMS mandate for electronic PA expanding 2026+.
834	Benefit Enrollment	Sponsor → Payer	Open enrollment processing. Dependent add/drop. COBRA continuations. Retroactive effective dates.
999	Implementation Acknowledgment	Receiver → Sender	Required for all HIPAA transactions. Fuuz $ackEDI() generates. Implementation guide compliance level reporting.

5. UN/EDIFACT (International Standard)

The dominant EDI standard outside North America. Over 200 message types across 46+ directory versions (D.93A through D.22A).

EDIFACT Directory Version Support

Version Range	Years	Status	Common Usage
D.93A – D.96A	1993 – 1996	Legacy	Some legacy European implementations.
D.96B – D.01B	1996 – 2001	Active — Most Common	Dominant versions in global trade. Most European trading partners.
D.02A – D.22A	2002 – 2022	Active	Newer implementations. Growing adoption in specific industries.

Key EDIFACT Message Types

Message	Name	Common Usage	Concerns / Limitations
ORDERS	Purchase Order	International equivalent of X12 850.	Multi-currency support. UN/LOCODE for locations. INCOTERMS for trade terms.
INVOIC	Invoice	Billing document. Equivalent of X12 810.	VAT/tax handling for international trade. Multi-currency. Self-billing support.
DESADV	Despatch Advice (ASN)	Shipment notice. Equivalent of X12 856.	SSCC/GS1-128 barcode data. Package hierarchy. Customs documentation reference.
DELFOR / DELJIT	Delivery Forecast / JIT Delivery	Equivalents of X12 830/862.	Automotive production sequencing. Window-level delivery precision.
CUSCAR / CUSDEC	Customs Cargo / Declaration	Mandatory for many countries. Border control filing.	HS codes. Country of origin. Duty calculation. AES/ICS filing.
CONTRL	Syntax Acknowledgment	Receipt confirmation. Equivalent of X12 997.	Required for every EDIFACT interchange. Fuuz $ackEDI('edifact') generates automatically.
MSCONS / UTILMD	Metered Services / Utility Master Data	Energy/gas/water consumption and master data.	Smart meter data. European energy market deregulation.
BAPLIE / COPARN	Bayplan / Container Announcement	Maritime/container vessel operations.	SMDG standard. Container position, weight, hazmat status.

6. EANCOM / GS1 (Global Retail Standard)

EANCOM is a subset of EDIFACT that uses GS1 identifiers (GTINs, GLNs, SSCCs) for global retail supply chains. Supported by the EdiFabric library as an EDIFACT variant.

EANCOM Syntax 3: The Fuuz $readEDI() and $writeEDI() bindings include an eancomS3 option specifically for EANCOM Syntax 3 handling. Ensure this option is set correctly based on trading partner requirements.

Key EANCOM messages include: ORDERS (retail POs with GTIN), INVOIC (invoices with EAN/UPC codes), DESADV (ASN with SSCC barcodes and GS1-128 labels), PRICAT (product catalog with GTIN and GDSN alignment), SLSRPT (point-of-sale reporting), INVRPT (inventory with GLN locations), and RECADV (receiving advice with SSCC-level confirmation).

7. VDA (German Automotive)

Fixed-length EDI format used by German automotive OEMs (VW, BMW, Daimler/Mercedes, Porsche, Audi) and their tier suppliers. Supported through the EdiFabric library.

VDA Message	Name	Common Usage	Concerns / Limitations
VDA 4905	Delivery Schedule	Supplier delivery forecast from OEM. Equivalent of DELFOR/830.	Fixed-length records. Critical for German automotive supply chains.
VDA 4913	Advance Shipping Notification	ASN from supplier to OEM. Equivalent of DESADV/856.	Packaging unit detail. VDA 4902 label standard. Batch/lot tracking.
VDA 4915	JIT Call-Off	Just-in-time delivery schedule. Equivalent of DELJIT/862.	Sequence-level production call-off. Sub-hourly delivery windows.
VDA 4984 / 4987	EDIFACT-based Successors	Newer EDIFACT-based delivery schedule and ASN formats.	Gradual migration from fixed-length. VDA 4902 label compliance still required.

VDA Transport: Fixed-length VDA formats require exact field positioning — no delimiters. Transport typically uses OFTP2 (Odette File Transfer Protocol), which is not natively supported by Fuuz connectors. Use a VAN or OFTP2 gateway (SEEBURGER, OpenText, Data Interchange) that deposits files via FTP/SFTP for Fuuz FTP connector pickup.

8. HL7 (Healthcare Messaging)

HL7 Version 2.x (Pipe-Delimited)

Used by 95%+ of US healthcare systems. Pipe-delimited segment format. HL7 v3 (XML-based) is also supported through the EdiFabric library.

Message Type	Name	Common Usage	Concerns / Limitations
ADT	Admit/Discharge/Transfer	Patient registration and movement events.	A01 (Admit), A02 (Transfer), A03 (Discharge), A04 (Register), A08 (Update). Foundation of hospital workflow.
ORM / ORU	Order / Observation Result	Clinical orders (lab, radiology, pharmacy) and results.	Complex order detail. Result hierarchies. LOINC test codes.
SIU	Scheduling	Appointment scheduling.	S12 (New), S14 (Modification), S15 (Cancel). Resource scheduling.
RDE	Pharmacy Encoded Order	Medication orders.	Drug codes (NDC, RxNorm). Dosing instructions. Allergy checking.
VXU	Vaccination Update	Immunization administration record.	State immunization registry reporting. CDC requirements.

HL7 FHIR (REST-Based — Modern)

FHIR (Fast Healthcare Interoperability Resources) is the modern REST-based healthcare standard. R4 is the current normative version. FHIR is accessed via standard REST APIs — the Fuuz HTTP connector handles this natively without EDINation. The 21st Century Cures Act mandates FHIR-based patient access APIs for US healthcare organizations.

9. NCPDP (Pharmacy Standards)

NCPDP SCRIPT (e-Prescribing)

Current mandated version: 2017071. Version 2023011 emerging.

Message	Name	Direction	Concerns / Limitations
NEWRX	New Prescription	Prescriber → Pharmacy	NDC drug database required. Controlled substance handling (EPCS). State PDMP reporting.
REFREQ / REFRES	Refill Request / Response	Pharmacy ↔ Prescriber	Refill count tracking. Prior authorization integration.
CANRX	Cancel Prescription	Either direction	Regulatory requirements for controlled substances.

NCPDP Telecom (Pharmacy Claims)

Real-time point-of-sale pharmacy claim adjudication. Current version: D.0. Version F6 mandated by 2028. Transactions include B1 (Billing), B2 (Reversal), and B3 (Rebill) with sub-second response requirements.

10. Industry-Specific Standards

IATA (Aviation)

Aviation industry messaging standards including PADIS (Passenger Data: PNRGOV, PAXLST) and Cargo-IMP (FWB, FHL, FFM). Mandatory for border control and air cargo operations in many countries.

EDIGAS (European Gas Industry)

EDIFACT-based messages for European gas market operations (NOMINT, NOMRES, ALOCAT, DELORD, INVOIC). Current version up to 6.1, governed by ENTSOG.

SMDG (Maritime/Shipping)

EDIFACT-based messages for container shipping: BAPLIE (bayplan/stowage), COPARN (container announcement), CODECO (gate-in/out), VERMAS (verified gross mass — SOLAS VGM mandatory since 2016), and MOVINS (stowage instruction).

EDIFACT ACE (US Customs — CBP)

CUSCAR (advance manifest filing — 24-hour rule for ocean, 4-hour for air) and CUSDEC (import/export entry filing) for ACE (Automated Commercial Environment) system and ISF/10+2 compliance.

11. EDI Transport Protocols

EDI documents are standard-agnostic — they can be transmitted via multiple transport protocols. Fuuz supports the most common methods:

Transport Protocol	Fuuz Support	Common Usage	Concerns / Limitations
SFTP	✓ FTP connector	File-based EDI exchange. VAN file drops.	Natively supported. Most VANs support SFTP. Simple, reliable, widely supported.
FTP/FTPS	✓ FTP connector	Legacy file-based exchange.	Natively supported. Declining use in favor of SFTP.
HTTP/REST (Web EDI)	✓ HTTP connector	Modern API-based EDI. Trading partner portals.	JSON/XML payloads. OAuth2 authentication. Growing adoption.
VAN (Value Added Network)	✓ via FTP connector	Traditional EDI mailbox (SPS Commerce, TrueCommerce, OpenText, IBM Sterling).	VAN provides mailbox — Fuuz FTP connector retrieves/deposits files. Per-KC pricing.
AS2 (HTTPS)	Via HTTP connector	Most common modern EDI transport. Encrypted HTTPS with digital certificates.	May require custom data flow logic for AS2 envelope/signature. Consider AS2 gateway for complex requirements.
OFTP2 (Odette)	✗ Not natively supported	German/European automotive (VDA). Odette standard.	Requires OFTP2 gateway that bridges to SFTP for Fuuz FTP connector.
Direct SMTP	✓ SMTP connector	Legacy email-based EDI transport.	Declining use. Not recommended for new implementations.

12. EDI Implementation Concerns and Best Practices

Challenge	Description	Fuuz Mitigation
Trading partner variability	Each partner has unique implementation guides, field requirements, and validation rules.	Fuuz data flows allow per-partner transformation logic. EDINation model parameter supports custom specification overrides.
Version mismatches	Partners may use different X12 versions (e.g., one requires 4010, another 5010).	EdiFabric supports all versions simultaneously. Data flows route by version.
Acknowledgment management	997/999 (X12) and CONTRL (EDIFACT) must be generated for every interchange.	Fuuz $ackEDI() auto-generates acknowledgments. Data flows track status.
Large document handling	Catalog (832/PRICAT) and forecast (830/DELFOR) documents can be 10,000+ line items.	Data flow pagination and chunking. EDINation streaming parser for memory efficiency.
Chargeback compliance	Major retailers (Walmart, Amazon, Target) impose financial penalties for EDI errors.	Fuuz $validateEDI() validates before sending. Pre-submission compliance checking.
HIPAA compliance	PHI in healthcare EDI requires encryption, access controls, and audit logging.	Fuuz platform security (TLS, encryption at rest, RBAC, audit logs). BAA required.
Testing and certification	Many partners require EDI testing/certification before production.	Fuuz development environments (Build/QA) for EDI testing. EDINation validation against implementation guides.

13. Legend

Symbol	Meaning
✓ Named connector/binding	Fuuz has native EDI processing capability through the EDINation connector and $readEDI(), $writeEDI(), $ackEDI(), $validateEDI() bindings.
Via Connector	EDI transport or related functionality handled by another Fuuz connector (HTTP, FTP, SMTP).
✗	Transport protocol not natively supported — requires third-party gateway.

See Also

• Cloud-Connectors-Complete-Reference-Guide
• Edge-Connections-Complete-Industrial-Integration-Reference
• Integration-Nodes
• Data-Flow-Nodes-Reference
• Debugging-and-Context-Nodes
• Platform website: fuuz.com

---

Source: support.fuuz.com