X12
All Business Units
19segments
6loops
5mandatory
Schema Reference
19 segments · X12 855 Purchase Order Acknowledgment
ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
ISA02 Authorization Information
ISA03 Security Information Qualifier
ISA04 Security Information
ISA05 Interchange ID Qualifier
ISA06 Interchange Sender ID
ISA07 Interchange ID Qualifier
ISA08 Interchange Receiver ID
ISA09 Interchange Date
ISA10 Interchange Time
ISA11 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 Interchange Control Version Number
ISA13 Interchange Control Number
ISA14 Acknowledgment Requested
ISA15 Interchange Usage Indicator
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
GS02 Application Sender's Code
GS03 Application Receiver's Code
GS04 Date
GS05 Time
GS06 Group Control Number
GS07 Responsible Agency Code
GS08 Version / Release / Industry Identifier Code
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
ST02 Transaction Set Control Number
BAK Beginning Segment for Purchase Order Acknowledgment
Mandatory Max: 1
BAK01 Transaction Set Purpose Code
BAK02 Acknowledgment Type
BAK03 Purchase Order Number
BAK04 Date
REF Reference Information
REF01 Reference Identification Qualifier
REF02 Reference Identification
PER Administrative Communications Contact
Optional Max: 3
PER01 Contact Function Code
PER02 Name
PER03 Communication Number Qualifier
PER04 Communication Number
PER05 Communication Number Qualifier
PER06 Communication Number
N1 Party Identification
Optional Max: 1
N101 Entity Identifier Code
N102 Name
N103 Identification Code Qualifier
N104 Identification Code
N2 Additional Name Information
Optional Max: 2
N201 Name
N202 Name
N3 Party Location
Optional Max: 2
N301 Address Information
N302 Address Information
N4 Geographic Location
Optional Max: 1
N401 City Name
N402 State or Province Code
N403 Postal Code
N404 Country Code
PO1 Baseline Item Data
Optional Max: 1
PO101 Assigned Identification
PO102 Quantity
PO103 Unit or Basis for Measurement Code
PO106 Product/Service ID Qualifier
PO107 Product/Service ID
PO108 Product/Service ID Qualifier
PO109 Product/Service ID
PID Product/Item Description
Optional Max: 1
PID01 Item Description Type
PID05 Description
ACK Line Item Acknowledgment
Optional Max: 1
ACK01 Line Item Status Code
ACK02 Quantity
ACK03 Unit or Basis for Measurement Code
ACK04 Date/Time Qualifier
ACK05 Date
N1 Party Identification
Optional Max: 1
N101 Entity Identifier Code
N102 Name
N103 Identification Code Qualifier
N104 Identification Code
N2 Additional Name Information
Optional Max: 2
N201 Name
N202 Name
N3 Party Location
Optional Max: 2
N301 Address Information
N302 Address Information
N4 Geographic Location
Optional Max: 1
N401 City Name
N402 State or Province Code
N403 Postal Code
N404 Country Code
CTT Transaction Totals
Optional Max: 1
CTT01 Number of Line Items
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
SE02 Transaction Set Control Number
How It Works
Automating Rivian Automotive, Inc EDI 855
Stacksync validates, transforms, and delivers your 855 transactions automatically — so your team can focus on operations, not EDI compliance.
Validate
Transform
Route
Monitor
Stacksync generates and sends 855 Purchase Order Acknowledgments automatically when your system confirms an order. Accept, reject, or modify line items through your ERP — Stacksync handles the EDI formatting and transmission.
Rivian Automotive, Inc EDI 855 FAQ
Common questions about 855 Purchase Order Acknowledgment transactions with Rivian Automotive, Inc.
How long does it take to set up Rivian Automotive, Inc EDI with Stacksync?
Most suppliers are fully connected and processing live Rivian Automotive, Inc EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.
POC from integration engineers
No-code EDI setup
Real-time compliance monitoring
White-glove onboarding