EDI 861 Receiving Advice: Complete Guide

The EDI 861 Receiving Advice is the X12 transaction set a buyer sends after physically receiving a shipment to report what actually arrived at the dock versus what the 856 ASN said was coming. Every discrepancy on an 861 is a potential chargeback or invoice deduction, so vendors need to monitor these closely.

What is an EDI 861?

An EDI 861 Receiving Advice is a structured post-receipt notification defined by the ASC X12 standards body that documents the outcome of a receiving inspection, line by line, comparing actual received quantities against what the ASN and purchase order specified.

Authoritative sources for 861 implementation:

The X12.org Transaction Sets reference defines the BRA, RCD, and LIN segment structure for all 861 implementations
GS1 US governs the SSCC-18 and UPC identifiers used in LIN segments to match received cartons to ASN data

The 861 documents the results of a receiving inspection. It answers one question: did the shipment match expectations?

The buyer compares three data points:

What was ordered (from the 850 Purchase Order)
What was announced as shipped (from the 856 ASN)
What actually arrived at the receiving dock

If everything lines up, the 861 confirms receipt. If there are differences, the 861 spells out exactly what went wrong: short shipments, overages, damage, wrong items, or labeling problems.

Why the 861 Matters

The 861 is directly tied to chargebacks and payment adjustments. When a retailer finds discrepancies, the 861 creates the data trail that triggers:

Deduction from payment on the corresponding invoice
Chargeback fees for non-compliance (especially at major retailers)
Vendor scorecard penalties that affect future business

If you ship to retailers like Walmart, Target, or Amazon, receiving discrepancies flagged on 861s can cost you real money. Reviewing your 861s is not optional. For a full breakdown of retailer-specific requirements, see the Walmart EDI requirements guide.

Key Segments Explained

BRA - Beginning Segment for Receiving Advice

BRA*RCV20260305*20260305*RR**AC

BRA01: Reference Identification (receiving document number)
BRA02: Date (receiving date)
BRA03: Transaction Type Code
- RR = Receiving Report
- RD = Receiving Discrepancy
BRA04: Not used (reserved)
BRA05: Receiving Advice Status Code
- AC = Accepted (receipt matches expectations)
- RJ = Rejected (receipt has discrepancies)

N1 - Party Identification

The N1 loop identifies the parties involved:

N1*ST*WAREHOUSE 42*92*WH042
N1*SF*ACME SUPPLY CO*92*VEND001

N101: Entity Identifier Code
- ST = Ship To (receiving location)
- SF = Ship From (vendor/shipper)
- BY = Buying Party
N102: Name
N103: Identification Code Qualifier (92 = Assigned by buyer)
N104: Identification Code

RCD - Receiving Conditions

This is the core of the 861. The RCD segment reports actual quantities received and any discrepancies:

RCD*OK*48*EA***48*EA

For a discrepancy:

RCD*OS*52*EA***48*EA

RCD01: Receiving Condition Code
- OK = No discrepancy
- OS = Over-shipment
- US = Under-shipment
- DM = Damaged
- WI = Wrong Item
- RJ = Rejected
RCD02: Quantity received
RCD03: Unit of measure (EA = Each, CA = Case, PK = Pack)
RCD06: Quantity expected (from ASN or PO)
RCD07: Unit of measure for expected quantity

LIN - Item Identification

LIN**UP*012345678901*VN*WIDGET-A100

LIN02: Product/Service ID Qualifier (UP = UPC, VN = Vendor Part Number)
LIN03: Product/Service ID
LIN04: Additional qualifier
LIN05: Additional ID

SN1 - Item Detail (Shipment)

SN1**48*EA*52*EA

SN102: Number of units shipped
SN103: Unit of measure
SN104: Number of units received (actual count)
SN105: Unit of measure

Discrepancy Types

Over-Shipment

You sent more than ordered or more than the ASN stated.

RCD*OS*52*EA***48*EA
LIN**UP*012345678901

Impact: Retailer may refuse the excess, return it at your cost, or accept it but flag a compliance issue. Either way, your ASN accuracy score takes a hit.

Under-Shipment (Short Ship)

You sent fewer units than expected.

RCD*US*40*EA***48*EA
LIN**UP*012345678901

Impact: The retailer expected 48 units, got 40. This triggers a fill rate deduction and potentially a chargeback. The retailer may also adjust your invoice payment down to match what was actually received.

Damage

Items arrived in damaged condition.

RCD*DM*5*EA***48*EA
LIN**UP*012345678901

Impact: The 5 damaged units will be deducted from payment. Depending on the retailer, you may also face a damage chargeback. Repeated damage flags can lead to packaging or routing compliance reviews.

Wrong Item

The item received does not match what was ordered or what the ASN listed.

RCD*WI*48*EA***0*EA
LIN**UP*099999999999

Impact: The entire line is rejected. You shipped a product the retailer did not order. This is one of the most expensive discrepancy types because it affects receiving, returns, and potentially store inventory.

How the 861 Connects to the 856 ASN

The 861 closes the loop on the shipment cycle:

1. Buyer sends 850 PO         -> "We want 48 units of Widget A"
2. You send 855 PO Ack        -> "We can fulfill that"
3. You send 856 ASN           -> "48 units shipped, tracking #XYZ"
4. Buyer receives shipment
5. Buyer sends 861            -> "We got 40 units, 8 short"

When the 861 reports a discrepancy, the retailer compares it against your 856 Ship Notice. If your ASN said 48 units but only 40 arrived, that is an ASN accuracy failure on top of a fill rate failure. Two problems from one shipment.

Real-World 861 Example

ISA*00*          *00*          *ZZ*BUYER456       *ZZ*VENDOR123      *260305*1400*U*00401*000000055*0*P*:~
GS*RC*BUYER456*VENDOR123*20260305*1400*55*X*004010~
ST*861*0055~
BRA*RCV20260305*20260305*RD**RJ~
N1*ST*DC NORTHWEST*92*WH007~
N1*SF*ACME SUPPLY CO*92*VEND001~
RCD*US*40*EA***48*EA~
LIN**UP*012345678901*VN*WIDGET-A100~
SN1**48*EA*40*EA~
RCD*DM*3*EA***24*EA~
LIN**UP*012345678902*VN*WIDGET-B200~
SN1**24*EA*3*EA~
SE*11*0055~
GE*1*55~
IEA*1*000000055~

Translation: "We received your shipment at DC Northwest on March 5. Two problems:

Widget A (UPC 012345678901): Expected 48 units, only received 40. Short by 8.
Widget B (UPC 012345678902): 3 of 24 units arrived damaged."

How to Reduce 861 Discrepancies

1. Match your ASN to actual shipment contents

The number one cause of 861 discrepancies is an ASN that does not match what is in the box. Count and verify before generating the 856 Ship Notice.

2. Audit your pick-and-pack process

Short ships usually happen at the warehouse. Implement barcode scanning at pack-out to verify quantities before sealing cartons.

3. Improve packaging to prevent damage

If you see repeated DM codes on 861s, review your packaging specs. Inner pack protection, correct box sizing, and proper palletization all reduce damage at receiving.

4. Validate item identifiers before shipping

Wrong-item discrepancies often trace back to UPC or SKU mismatches. Confirm your item master matches the retailer's item setup. Use the EDI Inspector to cross-check your ASN item data before transmission.

5. Review your compliance checklist

Walk through the EDI compliance checklist quarterly. Many 861 discrepancies are preventable with tighter process controls.

Chargeback Implications

Major retailers tie 861 discrepancy data directly to their chargeback programs:

Discrepancy Type	Typical Chargeback	Notes
Short ship	Deduction for missing units + fee	Fee ranges from $50 to $500+ per incident
Over-shipment	Return freight cost + handling fee	Retailer may refuse delivery entirely
Damage	Deduction for damaged units + fee	Repeated damage triggers compliance review
Wrong item	Full line rejection + penalty	May require a return authorization
ASN mismatch	Flat chargeback fee	ASN quantity did not match received quantity

The exact fee structure varies by retailer and your vendor agreement. But the pattern is consistent: every 861 discrepancy costs money.

FAQ

Do all retailers send 861s?

No. The 861 is common among large retailers (Walmart, Target, Home Depot, Costco) and major distributors, but not universal. Some smaller trading partners report receiving results through email or portal entries instead of EDI. Check your trading partner agreement to know what to expect.

How soon after delivery will I receive an 861?

It depends on the retailer's receiving process. Most large retailers send 861s within 24 to 72 hours of dock receipt. Some distribution centers process same-day. If you have not received an 861 within a week of confirmed delivery, check with your trading partner contact.

Can I dispute an 861 discrepancy?

Yes, but the process varies by retailer. If you believe the 861 is wrong (for example, you have proof of shipment for the full quantity), you typically need to file a dispute through the retailer's vendor portal with supporting documentation like signed bills of lading, shipment photos, or carrier delivery receipts. Act quickly, as most dispute windows are 30 to 60 days.

Related Transaction Sets

856 Ship Notice/ASN - What you said you shipped (compared against the 861)
850 Purchase Order - The original order that started the cycle
810 Invoice - Payment document that may be adjusted based on 861 results
997 Functional Acknowledgment - Send a 997 when you receive an 861

Need Help?

Use the EDI Inspector to parse and validate your 861 Receiving Advice documents. If you are seeing repeated discrepancies, review the EDI compliance checklist to tighten your shipment and ASN processes.