Walmart Reverses ASN Fines on the 997. Almost Nobody Keeps One.

Walmart's guidance says it plainly: OTIF and ASN fines are routinely reversed when the 997 functional-acknowledgment gap proves the ASN was transmitted within the window. The instruction that follows is shorter and harder to argue with, always attach the 997 transmission log.

Most teams cannot. Not because the document is hard to obtain. It arrives automatically, seconds after you send an ASN, into a folder nobody opened. By the time a deduction needs it, the folder is gone.

What a 997 actually is

Strip it back and the 997 is the receiver telling you whether it took what you sent. When you transmit an EDI functional group, the envelope around a batch of transactions: the receiver is expected to answer with a 997, the functional acknowledgment, saying accepted or rejected.

Accepted means the document arrived and was parsed. It does not mean the shipment was correct, the quantities agreed, or the ASN matched what was on the pallet. Sent and accepted are two different facts, and the gap between them is where the money is. Your transmission log says the bytes left your building. The 997 says the retailer took them. A timing argument stands on the pair. With one of them you have an opinion.

There is a second acknowledgment one layer down. A TA1 acknowledges the interchange itself, the outermost envelope around the group. If the envelope is malformed, you get a TA1 and no 997 at all. So a missing 997 is genuinely ambiguous: it can mean you never sent it, the envelope was rejected, or it arrived and nobody filed it. Three different problems, one identical symptom.

What identifies a 997 is not the file name. It is the AK1 segment, naming the functional group covered, and the AK2 loop, naming each transaction set inside it and carrying the group control number from your transmission. An AK2 for 856 ties the acknowledgment to the ASN you sent. An AK1 group code on its own is the coarser answer: a shipment group was acknowledged, but not which transaction sets inside it failed.

The deduction memo cannot do this job

A deduction memo tells you a window was missed. That is all it is, an assertion, carrying a date, from the party that took your money.

It cannot tell you when your ASN went out, because it is the retailer's record of its own conclusion, nor whether the document arrived at all. An ASN that never arrived and an ASN that arrived and was misread leave the same absence in the retailer's system.

Two documents carry timing, and you need both. The 856 transmission log with a timestamp is yours. The 997 is theirs. Target's ASN availability packet names them together: the EDI 856 ASN transmission log with timestamp, and the EDI 997 acknowledgment from Target. Target asks for the 997 by name, from Target, because it is the retailer's own record that your document arrived. You cannot produce a document your trading partner wrote.

Retailers name the 997 in their own document lists

Nine of the eleven retailer profiles we hold name the 997 inside a required document list. That makes it a routine part of the packet, and it is why a 997 is a compliance obligation and not a courtesy.

Walmart is the interesting one. Its SQEP/ASN document list names the transmission log, the EDI 856 confirmation and the SSCC scan records (no 997), and then its guidance tells you to attach the 997 transmission log anyway. Home Depot sits at the other end: an ASN reason code, HD-ASN, where a pre-arrival timestamp is required and the finding is disputable, but no ASN document set and no 997. If you supply Home Depot, ask rather than assume.

Retention is an operating requirement

Retention is where the 997 quietly disappears, because nothing asks for it until a dispute is live.

Target sets the floor at 12 months or more. Its guidance is that ASN-accuracy disputes succeed with VRS entry confirmations, BOL, POD and EDI transmission logs archived 12+ months, and ASN errors are the leading driver of its chargebacks. Twelve months is longer than most teams keep anything transactional, and shorter than the window you are defending: Target's dispute window runs 547 days from chargeback posting for prepaid terms, so a deduction can arrive comfortably inside a window your archive has already outlasted.

Costco runs the opposite clock: the 997 acknowledgment is due within 24 hours of receiving any Costco EDI document. That is an obligation on the return leg, and nobody catches a 24-hour gap by remembering to look. Only a process that captures the acknowledgment on arrival satisfies it.

The other end of the same problem is Walmart. OTIF runs about 30 days counted from invoicing, with ASN and labeling penalties of $50 to $500 per incident and OTIF itself at 3% of cost of goods on the non-compliant case. A retention period tuned to the dispute window is tuned to the wrong end.

The failure mode

Teams archive what they sent. The ASN you generated is a record in your own system, it is easy to find, and it feels like the audit trail. The 997 that came back is somebody else's inbound message, in a format nobody built a screen for, and it is the first thing a retention policy discards.

The result is the weak version of the argument. You can prove transmission but not acceptance, which leaves a gap the retailer fills. Or you cannot prove either, because the transmission log lives in a rotation nobody told you about. Either way an ASN availability deduction is unanswerable, and it is not a small number: 3% of cost of goods at Target, $50 to $500 per incident on Walmart's ASN line.

What to log, and for how long

Three records, kept together and indexed by ASN number and PO number: the 856 transmission log line with its timestamp; the 997 that came back, carrying the AK2 group control number that ties it to the transmission; and the TA1 if one arrived, since an envelope rejection is the only explanation for a 997 that never appeared.

Hold them on the retailer's clock, not yours. Costco wants the acknowledgment in 24 hours. Target wants the logs kept 12 months or more. A retention period shorter than the retailer's own guidance is not a policy; it is a gap you chose.

And keep the two transmission records joined. A 997 with nothing to attach it to is a receipt with no order, which is why the guidance is to attach the 997 transmission log every time.

The message the 997 is answering is in what the 856 ASN is and why it is expensive, the rest of the shipment packet is in what wins a shortage dispute, and the queue that decides whether a Walmart ASN dispute is opened at all is in APDP and HighRadius are not the same queue.

Costco expects a 997 within 24 hours of any Costco EDI document, and Target expects EDI transmission logs archived for 12 months or more. Go and check whether your archive holds both, because a 997 nobody saved is a window nobody can argue you met.