Your ASN said forty cartons; the partner's dock found thirty-eight intact, one crushed, and one missing entirely. Until something reports that back, you're invoicing a fiction. The EDI 861 Receiving Advice/Acceptance Certificate is that report — the receiving side's official account of what physically arrived, in what condition, and what was accepted, and one of the few EDI documents that tells a supplier the truth about the end of the journey.
The dock's side of the story
The document's spine is the RCD segment: for each line, the quantity received, and where relevant the quantities rejected or noted in exception, with condition codes explaining why — damaged, short, over, wrong item. A BRA header identifies the advice and its date; references tie the whole document back to the PO and shipment; item identifiers echo the ones the order used. Read together with your 856 ship notice, the 861 completes a before-and-after pair: what you claimed left the warehouse versus what the partner certifies arrived.
That pairing is the fastest discrepancy detector in the chain. Shipped-versus-received gaps surface within a day of delivery — not weeks later as an unexplained short-pay — and each gap comes pre-classified: damage points at packaging or the carrier, shortages at picking or theft, wrong-item receipts at labeling or master data.
Timeliness gives the pairing its force. A receipt advice processed the day it arrives can still be argued from evidence — the trailer, the seal, the driver's paperwork. The same discrepancy noticed at month-end reconciliation is just an accounting entry with a story nobody can verify.
Where the 861 carries real weight
In everyday retail replenishment, many partners skip the 861 and simply deduct when receipts disagree with invoices. The document becomes central in flows where received quantity is the commercial trigger:
- Consignment and vendor-managed inventory, where acceptance — not shipment — moves ownership and starts the billing clock.
- Manufacturing and government programs, where the acceptance certificate function matters contractually.
- Any relationship settling on receipts, where the 810 invoice should bill exactly what the 861 accepted, closing the gap that deduction disputes grow in.
Where a partner does send it, treating it as authoritative changes your posture in disputes. An invoice generated from accepted quantities can't short-pay on quantity grounds; a claim contradicted by the partner's own receiving advice is an argument you win by forwarding their document back to them. Consignment flows add one more wrinkle worth planning for: accepted quantities may be what triggers your revenue recognition, which puts an EDI document unusually close to the financial close and makes its reliable processing an accounting control, not just an operations nicety. Formal adjustments that follow — theirs or yours — travel as an 812.
Wiring receipts into the order-to-cash loop
The integration pattern is straightforward and underused: land the 861 against the shipment record in your ERP, auto-compare against shipped quantities, and branch. Clean receipts close silently. Discrepancies open tasks with the evidence already attached — ASN, receipt, delta — routed to billing (adjust before invoicing, where sequencing allows), to the carrier-claims process, or to warehouse quality, depending on the condition codes. EDISQ runs that comparison automatically across 30+ ERP integrations, so the only receipts a human reads are the ones that disagree with something.
The cost side
An 861 is billed like any other document at EDISQ — the pricing page has the full ladder, but the short version: your first 25 documents each month are free, after which per-document rates start at $0.50 and settle to $0.10 at the top tier, applied marginally, with AS2, SFTP, and VAN transport included and nothing charged for mapping or setup. For a document whose job is catching money leaks at the dock door, that's about as favorable as cost-benefit gets.
FAQ
What is the difference between an 856 and an 861?
Direction and moment. The 856 is you telling the partner what you shipped, before arrival; the 861 is the partner telling you what they received and accepted, after unloading. One is the claim, the other is the verdict.
Do all retailers send 861s?
No — many rely on the ASN plus exception-based deductions instead. The 861 is most common in consignment, vendor-managed inventory, and programs where received quantities drive settlement.
What should trigger action from an 861?
Any gap between shipped and received: rejected or damaged quantities, overages, and shortages. Those discrepancies feed invoice adjustments and carrier claims, and they age badly if ignored.
How much does receiving 861s cost?
With EDISQ, one document each — nothing for the first 25 documents in a month, then from $0.50 downward with volume. The visibility usually pays for itself in one avoided dispute.