Skip to content

X12 transaction code

X12 861 Receiving Advice Acceptance Certificate

X12 861 Receiving Advice Acceptance Certificate: explore its business purpose, mapping identifiers, validation tests and 6 partner references across 15 listed channels.

Standard
X12
Code
861
Partner references
6

Implementation guide

X12 861 mapping and validation

X12 861 Receiving Advice Acceptance Certificate is used when received goods are counted or accepted. Preserve receipt, shipment, order and inspected item so the goods receipt or acceptance record in your business system stays connected to the original document.

Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record goods receipt or acceptance record

receipt, shipment, order and inspected item

  • Define which combination of receipt, shipment, order and inspected item identifies one business record, its lines and any later revision.
Update the receiving system Processing the goods receipt or acceptance record

ID assigned by the receiving system and processing result

  • Separate received quantity from accepted quantity when damaged goods are reported.
  • Reconcile two partial receipts against one shipment without closing the order early.
Check the processing result Processing status for the goods receipt or acceptance record

Original document reference and matching response

  • Reconcile the goods receipt or acceptance record with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

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.

  • X12 856 Ship Notice Manifest

    shipment notice (ASN): shipment contents are known before the agreed notification deadline.

  • X12 810 Invoice

    accounts-receivable or accounts-payable invoice: a bill is ready for the buyer to process.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when received goods are counted or accepted. Name the operational owner of the goods receipt or acceptance record and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map receipt, shipment, order and inspected item. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner 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 goods receipt or acceptance record 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 goods receipt or acceptance record processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 861 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic goods receipt or acceptance record 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 goods receipt or acceptance record without processing it twice.

Document structure

X12 861 Receiving Advice Acceptance Certificate at the element level

The X12 861 reference contains 21 segment entries and 95 data elements; 42 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
21
Data elements
95
Mandatory elements
42
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
BRA 5 4
REF 3 1
DTM 4 1
PRF 4 1
N1 4 1
N2 2 1
N3 2 1
PER 8 1
LIN 11 2
CTT 1 1
Key identifiers in 861
  • Reference Identification
  • Date
  • Transaction Set Purpose Code
  • Receiving Advice or Acceptance Certificate Type Code
  • Reference Identification Qualifier
  • Date/Time Qualifier
  • Purchase Order Number
  • Entity Identifier Code

Catalog breakdown

Where X12 861 Receiving Advice Acceptance Certificate appears in this catalog

The largest groups of classified 861 catalog entries are in agriculture, manufacturing & industrial and electronics & technology.

By industry

  • agriculture 10 channels
  • manufacturing & industrial 2 channels
  • electronics & technology 1 channel
  • logistics & transport 1 channel
  • healthcare & pharma 1 channel

By network

  • Saicits 1 channel
Partner entries with the most listed channels

FAQ

X12 861 questions

What is X12 861 Receiving Advice Acceptance Certificate used for?

861 is used when received goods are counted or accepted. It carries information for the goods receipt or acceptance record. Match it to your business system using receipt, shipment, order and inspected item.

Which partners list X12 861?

The directory on this page links 6 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

What should I map for X12 861?

Start with receipt, shipment, order and inspected item and the target goods receipt or acceptance record. 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 861 error handling?

Separate received quantity from accepted quantity when damaged goods are reported. Reconcile two partial receipts against one shipment without closing the order early. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 861 relate to other EDI messages?

X12 856 Ship Notice Manifest; X12 810 Invoice are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 861 and 856?

861 is used when received goods are counted or accepted. 856 is used when shipment contents are known before the agreed notification deadline. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect 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.