Here is the conclusion up front: an EDI 861 receiving advice is the warehouse's official reply to the shipper, stating what actually arrived, in what quantity, and in what condition. The 856 says what the supplier shipped. The 861 says what you received. When the two disagree, the difference lives in the 861. When an 861 lands, do not post it to inventory right away. Match it line by line against the 856 ASN and the purchase order first.
I have run more than 30 WMS go-lives, and most receiving disputes come back to the 861. The supplier says 1,200 units shipped, the warehouse says 1,152 received, and the supplier says the warehouse miscounted. Without an 861, that argument drags on for three weeks. With one, it becomes rows of data: which line was short, and by how many.
What an EDI 861 Receiving Advice Actually Carries
The BRA segment at the top carries the advice number, the date, and the purpose code. The RCD segment carries the line-level answer: quantity received, quantity accepted, quantity in question, and a receiving condition code. Watch BRA04 closely: when it carries a value of 8, the document becomes an acceptance certificate, meaning units received equal units accepted, and the goods are formally accepted for payment.
Here is the counter-intuitive part. Plenty of newcomers assume an 861 goes out with every shipment. It does not. Some large buyers only send an 861 when something is wrong. One major automotive manufacturer's guide says the 861 goes out only for overages, shortages, receipts with no ASN, returns, or scrapped material. Whether one should appear at all depends on the partner's implementation guide, not on your instincts.
I have seen this pit three times: a warehouse treats the 861 as the only trigger allowed to post a receipt, so no 861 means no putaway. Then a difference-only partner ships a clean load, no 861 arrives, and pallets sit in the receiving lane for two days. Receipts post on the warehouse's own physical count, not on a message that may never come.
Matching the 861 Against the 856 and the Purchase Order
The most common failure in the first week of 861 go-live is not a format error. It is three documents that do not agree. I use one fixed order and never change it: match the 861 against the 856 first, then against the purchase order, then match the result against the invoice.
In November 2023, a home-goods 3PL near Los Angeles called me: a big customer had rejected its 861 three times. The 856 said 1,200 units, the warehouse counted 1,152. The operator wrote "short" as the reason, but in the RCD segment the quantity in question was 48 while the condition code said there was no problem. The partner's system rejected the document. The fix was one line: change the code to the shortage code and resend. In an 861, the quantity and the condition code have to tell the same story.
In spring 2024, an auto parts warehouse in Texas sent its 861, received a 997 saying accepted, and assumed the job was finished. Two weeks later the invoice was still billed on the 856 quantity, including 36 units that had never arrived. A 997 only proves the message arrived and parsed, not that the partner's business system accepted the contents. Track two things after every 861: whether the 997 came back, and whether the partner adjusted the payable amount to the 861 quantity.
| Compare | 856 claims | 861 claims | Check first |
|---|---|---|---|
| Quantity | How much shipped | How much received | Scan records, then packing |
| Item | Which item shipped | Which item arrived | Barcodes, item mapping |
| Condition | Shipped in good order | Received, damaged, rejected splits | Photos, inspection notes |
| References | Shipment, carton numbers | PO and 856 numbers | REF segment |
When documents disagree, check the unit of measure first. The 856 says 100 cases, the 861 says 1,200 eaches, and the numbers look short when the only error is a missing conversion.
Short, Over, and Damaged: Three Problems, Three Roads
A shortage means goods are missing: hold the missing quantity open, wait for a reshipment, post only what physically arrived, and pay only on what arrived. An overage means goods are extra: isolate the extra units, do not touch them, and wait for the shipper to confirm whether they are a gift, a mis-shipment, or a return. Damage and rejection mean goods cannot be used: photograph them, move them to quarantine, record the quantity in question and the condition code, and run the return or claim separately.
In June 2024, I saw the most expensive overage of my career at a consumer electronics warehouse. The 856 said 800 units, the warehouse counted 860, sixty extra. The supervisor decided extra stock was good news and posted all of it to available inventory. Two weeks later a cycle count found the truth: those sixty units belonged to the next shipment, loaded early into this one by mistake, so the next shipment arrived sixty short. The two discrepancies cancelled each other out on paper while the physical stock stayed wrong for a month. Isolate extra units, report the overage honestly in the 861, and wait for confirmation. Extra goods are not your goods until someone confirms they are.
The trap with damage is the photograph. Warehouses report damage by word of mouth, write the quantity in the 861, and leave the photo on somebody's phone. When the claim goes in, the other side asks for evidence, the photo is gone, and the claim dies. Photograph damage at the dock when it is found, with the photo number in the receiving record before the 861 goes out.
| Discrepancy | 861 records it as | Warehouse action | Books |
|---|---|---|---|
| Shortage | Received quantity, short count in question | Hold missing quantity open | Post and pay only on received |
| Overage | Received quantity, over count in question | Isolate extra units, do not use them | No available stock until ownership confirmed |
| Damage | Received quantity, damaged count in question | Photograph at once, quarantine | Hold separately, await claim approval |
| Rejection | Received quantity, rejected count in question | Isolate the line, tag it rejected | No posting, await return instructions |
| No ASN | Notes no matching 856 | Isolate, ask purchasing to confirm | No posting until documents complete |
I have seen this pit three times, always in the same shape: the reason for the discrepancy lives in an email or a chat message and never makes it into the 861. The email gets lost, the chat scrolls away, and the other side refuses the claim. An EDI 861 receiving advice is the one record both systems recognize, so the reason has to live inside the message. Email is a tool for chasing people, not evidence.
The Night-Before-Go-Live Checklist
On the night before an 861 go-live, I walk the client through this list item by item. A checkmark means somebody verified it by hand. Lock the implementation guide first: the partner's 861 version, mandatory segments, condition code list, unit list, and whether they send difference-only or full advices all go into the mapping document. Confirm before go-live what BRA04 equal to 8 means to this partner.
Test the mapping with real messages: one clean receipt, one shortage, one damage case. Testing only the clean case is practicing only the easiest question on the exam. Watch the 997s, and assign someone to watch them. A rejection has to point at the exact segment that failed, and a 997 that never arrives needs an alarm too. Past the promised acknowledgement window, treat the message as lost and check the channel.
Run the discrepancy process in the warehouse before the system goes live. The receiver knows how to report a shortage, where overages go, where damage photos live. A system that can send an 861 is not the same as a warehouse that knows how to handle a discrepancy. The 861 numbers must never repeat or skip: the BRA advice number is the document's identity, a duplicate gets discarded, and a gap gets questioned at reconciliation.
My test for whether an 861 implementation has actually landed is direct: after the first month, every discrepancy should trace to a line in an 861, every line should have a status, a photo where needed, a named owner, and a close date, and invoice differences should be down by half. If the numbers do not show that, the messages are flowing but the process is not.
By Lin Xiao, WMS Implementation Consultant







