Skip to content
X12 EDI

Dow Inc. X12 855 Purchase Order Acknowledgment

Plan X12 855 Purchase Order Acknowledgment for Dow Inc. / Dow. Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
12
Loops
2
X12 855
Partner references ↗

Implementation guide

Dow Inc. / Dow: 855 mapping and validation

X12 855 Purchase Order Acknowledgment is used when a seller responds to an order. Preserve original purchase order, response revision and order line so the purchase-order response in your business system stays connected to the original document.

This document is listed for Dow Inc. / Dow. Confirm the version, required fields and responses that apply to your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record purchase-order response

original purchase order, response revision and order line

  • Define which combination of original purchase order, response revision and order line identifies one business record, its lines and any later revision.
Update the receiving system Processing the purchase-order response

ID assigned by the receiving system and processing result

  • Test a partially accepted order with a backordered line and retain both outcomes.
  • Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates.
Check the processing result Processing status for the purchase-order response

Original document reference and matching response

  • Reconcile the purchase-order response with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

The document reference includes 12 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when a seller responds to an order. Name the operational owner of the purchase-order response and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map original purchase order, response revision and order line. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Dow Inc. guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic purchase-order response data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful purchase-order response processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 855 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic purchase-order response data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out purchase-order response without processing it twice.

Transaction context

Where 855 Purchase Order Acknowledgment fits on Dow

On Dow, the X12 855 Purchase Order Acknowledgment can follow the 850 Purchase Order in an example Order-to-cash cycle. Confirm the required sequence for your trading agreement.

Dow Inc. channels
1 of 1

1 of Dow Inc.'s 1 channel list 855

Trading partners
269

partner references list 855

Channels
328

channel entries list 855

Document structure

X12 855 Purchase Order Acknowledgment at the element level

The X12 855 reference contains 54 segment entries and 204 data elements; 72 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
54
Data elements
204
Mandatory elements
72
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
BAK 6 4
CUR 2 2
REF 3 1
FOB 3 1
SAC 10 1
DTM 4 1
TXI 7 1
N9 3 1
MSG 2 1
N1 4 1
N2 2 1
Key identifiers in 855
  • Transaction Set Purpose Code
  • Acknowledgment Type
  • Purchase Order Number
  • Date
  • Entity Identifier Code
  • Currency Code
  • Reference Identification Qualifier
  • Shipment Method of Payment
Segment reference — 12 segments 2 loops · X12 855 Purchase Order Acknowledgment
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

BAK Beginning Segment for Purchase Order Acknowledgment 4 elements

To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates

REF Reference Identification 2 elements

To specify identifying information

LIN Item Identification 3 elements

To specify basic item identification data

MEA Measurements 3 elements

To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001)

N9 Loop Repeat: 1,000
N9 Reference Identification 2 elements

To transmit identifying information as specified by the Reference Identification Qualifier

MSG Message Text 1 element

To provide a free-form format that allows the transmission of text information

PO1 Loop Repeat: 100,000
PO1 Baseline Item Data 9 elements

To specify basic and most frequently used line item data

DTM Date/Time Reference 2 elements

To specify pertinent dates and times

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Dow Inc. / Dow EDI 855 questions

Common questions about 855 Purchase Order Acknowledgment on the Dow channel.

What is X12 855 Purchase Order Acknowledgment used for?

855 is used when a seller responds to an order. It carries information for the purchase-order response. Match it to your business system using original purchase order, response revision and order line.

Is 855 required for Dow Inc. / Dow?

855 is listed for Dow Inc. / Dow. Confirm the required version and direction for your business unit and account with the partner.

What should I map for X12 855?

Start with original purchase order, response revision and order line and the target purchase-order response. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 855 error handling?

Test a partially accepted order with a backordered line and retain both outcomes. Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 855 relate to other EDI messages?

X12 850 Purchase Order is a related document also listed on Dow. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 855 and 850?

855 is used when a seller responds to an order. 850 is used when a buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect Dow Inc. EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.