855

EDI 855 — Purchase Order Acknowledgement

Supplier → Flxpoint · PO acknowledgement

EDI 855 — Purchase Order Acknowledgement

Purpose

Confirm receipt of a Purchase Order (850) and communicate your intent to fulfill it — line by line. Originates with the Supplier, sent to Flxpoint.

In Plain English

The 855 is the supplier's commitment back to the retailer: "I got your PO and here is exactly what I plan to ship." Unlike the 997 — which only confirms the file envelope arrived — the 855 confirms business intent, line by line. For each item on the original 850 the supplier responds with an acknowledgement code: accept as-is, accept with a changed quantity, backorder, or reject. Flxpoint uses the 855 to update the order status in the channel before the shipment actually moves, so the end customer sees accurate expectations. A missing or partial 855 is a common source of support tickets because the retailer cannot tell what will ship until the ASN arrives hours or days later.

Frequency

Send within 24 hours of receiving the 850. Required for every PO received.

Business Rules

  • The 855 must reference the original 850 PO number
  • You must respond to every line item from the 850
  • Accepted quantity must be ≤ the original PO quantity
  • Unit of measure must be EA (Each)
  • Send one 855 per 850 — do not combine multiple POs in one 855

Status Codes

BAK02 — Transaction Purpose

CodeMeaning
ADAccepted — PO is accepted as-is
ACAccepted with Changes — some lines modified
RDRejected

ACK01 — Line Item Status

CodeMeaningWhen to Use
IAItem Accepted, No ChangeYou will ship exact quantity at exact price
IQItem Accepted, Quantity ChangedYou can only partially fulfill this line
IRItem Rejected — No Reason GivenItem cannot be fulfilled
R2Item Rejected — Out of StockItem is not available
R4Item Rejected — Item DiscontinuedItem is no longer carried

Segment Hierarchy

code
ISA  Interchange Header
 GS  Group Header (GS01 = "PR")
  ST   Transaction Set Header (ST01 = "855")
  BAK  Beginning Acknowledgement for PO
  ┌─ PO1 Loop (repeats per line item)
  │  PO1  Line Item Detail
  │  ACK  Line Item Acknowledgement
  └─
  CTT  Transaction Totals (optional)
  SE   Transaction Set Trailer
 GE  Group Trailer
IEA  Interchange Trailer

Segment Overview

SegmentNameFLX StatusNotes
STTransaction Set HeaderRequiredST01 = 855
BAKBeginning AcknowledgementRequiredPurpose 00, ack type, PO#, date
N1 / N3 / N4Ship-To LoopSituationalShip-to address — mirror from 850
PO1Line Item LoopRequiredOne per line item from original 850
ACKLine Item AcknowledgementRequiredStatus code per PO1
CTTTransaction TotalsSituationalCount of PO1 segments
SETransaction Set TrailerRequired

Segment Specifications

ST — Transaction Set Header

ElementNameLengthM/OValue/Notes
ST01Transaction Set ID Code3 IDRequired855
ST02Transaction Set Control Number9 NRequiredUnique, must match SE02

BAK — Beginning Acknowledgement

ElementNameLengthM/OValue/Notes
BAK01Transaction Set Purpose Code2 IDRequired00 (Original)
BAK02Acknowledgement Type2 IDRequiredAD (Accepted), AC (Accepted with Changes), RD (Rejected)
BAK03Purchase Order Number22 ANRequiredMust match BEG03 from the original 850
BAK04Date8 DTRequiredDate of acknowledgement (CCYYMMDD)

N1 Loop — Ship-To Address (Situational)

When included, the N1 loop mirrors the Ship-To address from the original 850.

ElementNameLengthStatusValue/Notes
N101Entity Identifier Code3 IDRequiredST (Ship To)
N102Name60 ANRequiredCustomer name
N103Identification Code Qualifier2 IDSituationalZZ (Mutually Defined)
N104Identification Code80 ANSituationalFacility or location identifier

N3 and N4 follow (address line, city/state/zip) — same structure as 850.

PO1 — Line Item Detail

PO1 in the 855 echoes back the line items from the original 850. Include the same product identifiers that were in the 850 PO1. Multiple ID pairs (positions 6–17) are supported.

ElementNameLengthStatusValue/Notes
PO101Assigned Identification20 ANRequiredLine item number from the 850
PO102Quantity Ordered15 NRequiredOriginal quantity from the 850
PO103Unit of Measure2 IDRequiredEA (Each)
PO104Unit Price17 RSituationalUnit price from the 850
PO106Prod/Serv ID Qualifier2 IDRequiredPrimary ID type: SK, UP, EN, BP, MG, or VP
PO107Prod/Serv ID48 ANRequiredPrimary identifier — must match the 850
PO108Prod/Serv ID Qualifier2 IDSituationalAdditional type (e.g., BP Buyer Part #, EN EAN, MG Manufacturer)
PO109Prod/Serv ID48 ANSituationalValue for PO108 qualifier
PO110–PO117Additional ID PairsSituationalUp to 4 more pairs matching the 850

Tip: Include all product ID pairs that were in the original 850 PO1. This ensures Flxpoint can match the acknowledgement to the correct line item even if the primary ID is ambiguous.

ACK — Line Item Acknowledgement

ElementNameLengthM/OValue/Notes
ACK01Line Item Status Code2 IDRequiredIA, IQ, IR, R2, or R4 (see Status Codes above)
ACK02Quantity15 NRequiredAccepted quantity. Must be ≤ PO102
ACK03Unit of Measure2 IDRequiredEA (Each)

SE — Transaction Set Trailer

ElementNameLengthM/OValue/Notes
SE01Number of Included Segments6 NRequiredCount of all segments including ST and SE
SE02Transaction Set Control Number9 NRequiredMust match ST02

Example File

EDI · 004010VICS
ISA*00* *00* *ZZ*SUPPLIER *ZZ*FLXPOINT *240115*1200*U*00401*000000010*0*P*>~
GS*PR*SUPPLIER*FLXPOINT*20240115*1200*10*X*004010VICS~
ST*855*0010~
BAK*00*AD*PO-12345678*20240115~
PO1*1*2*EA*29.99**SK*SKU-ABC123~
ACK*IA*2*EA~
PO1*2*1*EA*49.99**SK*SKU-DEF456~
ACK*IA*1*EA~
PO1*3*4*EA*15.00**SK*SKU-GHI789~
ACK*IQ*2*EA~
SE*9*0010~
GE*1*10~
IEA*1*000000010~

Scenario: 3-line PO response

  • Line 1 (SKU-ABC123): 2 units — Fully accepted (IA)
  • Line 2 (SKU-DEF456): 1 unit — Fully accepted (IA)
  • Line 3 (SKU-GHI789): Only 2 of 4 units available — Partial acceptance (IQ, qty=2)

Common Mistakes

⚠️ ACK02 must always be ≤ PO102. You cannot accept more than was ordered. Sending a higher quantity will cause a validation error.

⚠️ BAK03 must exactly match the PO number from BEG03 of the 850. A mismatch means Flxpoint cannot link the acknowledgement to the original order.

⚠️ One 855 per 850. Never combine acknowledgements for multiple POs in a single transaction set.

Something unclear?

Ask our AI assistant — it knows this spec and can explain any segment, error, or rule in plain English.