Process an inbound EDI 861 Receiving Advice/Acceptance Certificate from a retail trading partner to confirm goods receipt
domain: stedi.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Configure an EDI 861 guide for the specific trading partner in Stedi, since field usage varies by retailer
Set up an inbound connection (SFTP, AS2, or VAN) to receive the trading partner's 861 transmissions
Parse the received 861 into structured JSON using Stedi's translation API
Match line-item quantities received against the original purchase order or ASN to detect shortages or overages
Post any discrepancies to your ERP or accounts payable workflow for resolution
Return an EDI 997 functional acknowledgment to confirm successful receipt of the 861 transaction
Known gotchas
EDI 861 field usage and qualifiers are trading-partner-specific — a generic 861 guide will misparse elements for partners like Ford, John Deere, or big-box retailers that have custom implementation guides
The 861 is a receipt/acceptance confirmation, not a payment authorization; downstream AP logic still needs a separate invoice match
Failing to return a 997 acknowledgment can cause the trading partner's EDI system to flag the transaction as undelivered and trigger a compliance chargeback
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?