DIRECT ANSWER
A positive EDI acknowledgment does not establish that Walmart accepted an invoice for payment. Match the acknowledgment to the sent invoice and read its result, then check invoice-specific AP evidence. A 997 reports syntax results; it does not establish business acceptance, a payment due date or money received.
Your integration dashboard says the invoice was acknowledged. The person researching payment cannot find it. Before anyone sends another copy, identify what was acknowledged, which invoice it belongs to and the last processing stage supported by evidence.
This guide is for Walmart US first-party merchandise suppliers using an invoice-based payment process, especially warehouse suppliers sending EDI invoices. In X12, the 810 is the Invoice transaction set. Marketplace settlements, DSV order-based payments and receipt- or scan-based payment programs need their own investigation.
Start with the short invoice investigation note. It has two columns and nine prompts. Capture one invoice, the evidence already checked and one next request. You do not need to reconstruct your entire payment history tonight.
What exactly does “acknowledged” mean here?
Ask for the underlying document or application status, including its source and timestamp. A provider’s dashboard label, an X12 acknowledgment and Walmart’s WebEDI status are different evidence.
X12 defines the 997 Functional Acknowledgment as reporting syntax-analysis results, without establishing the business meaning of the transaction. Receiving a 997 also does not mean its result was acceptance: have your EDI owner interpret the actual response against the applicable implementation guide.
| Evidence in front of you | What to establish next |
|---|---|
| Provider label such as Sent or Delivered | Which underlying receipt or response supports the label, and who received what? |
| A 997 matched to the outbound invoice | What result does it report for the relevant group or transaction? Business acceptance remains a separate question. |
| WebEDI’s Acknowledged status | Walmart’s help describes translation and handoff to AP. Research acceptance in an AP application. |
| An invoice visible in an AP application | Read its specific processing status and any unresolved requirement. Visibility alone does not establish when payment is due. |
| A payment or remittance record | Match its invoice reference and amount, then reconcile the bank receipt separately. |
The WebEDI distinction comes from Walmart’s official overview, whose indexed text says an acknowledged invoice can subsequently be rejected. The help page requires sign-in for direct access. Its WebEDI labels should not be treated as the definitions of a separate provider’s dashboard.
Prove that the response belongs to this invoice
Put the supplier ID, invoice number, PO, amount and sent-file reference together. Ask the EDI owner to reconcile the relevant outbound control references with the acknowledgment, including direction and environment. A response for a purchase order, another invoice or a test transaction does not answer this invoice question.
When opening the CSV in a spreadsheet, import identifiers as text so leading zeros and long reference numbers stay intact. Preserve the original records alongside your note.
Keep the original sent file and received response. Record an interpretation beside them, rather than replacing the evidence with “EDI is good.” If an acknowledgment is missing, the supported finding is that confirmation has not been located. That alone does not prove the invoice never reached processing.
If this invoice has already been corrected or resent, list each attempt with its file, control references, time and response. Keep the versions separate so an acknowledgment for one attempt is not assigned to another.
Check AP processing without treating a blank search as a verdict
Record the exact application, supplier selection, invoice identifier, date filters and time of the search. “Not found in this search” is more useful and more accurate than “Walmart never received it.” Check whether the screen shows paid transactions, unpaid invoices or another defined subset.
Walmart’s WebEDI overview points US and Canadian suppliers to Accounting Scorecard’s EDI Performance for invoices passed to AP, automatic rejections and manual processing. It also says Automated Supplier Invoice Inquiry (ASII) does not show invoices undergoing manual processing. That is a documented reason to investigate a visibility gap, not proof that your missing invoice is in manual processing. Confirm current access and labels in your account. Walmart’s invoice-research guidance.
For unanswered WebEDI questions, the same Walmart guide directs suppliers to Retail Link > Apps > Supplier Self Service. Confirm the current route in your account and bring the invoice-specific evidence below.
A batch count cannot identify an individual invoice unless the supporting detail makes that connection. Likewise, not finding a rejection message does not establish business acceptance. Preserve any response you do find, including its full explanation and original reference, and request the invoice-specific processing state through the current support route.
A fictional example: the missing invoice and the manual-processing count
A supplier sends invoice 700481 for $4,800 against PO 8800311. Its EDI owner matches the returned 997 to the outbound file and confirms a positive syntax result. The finance owner searches ASII for that invoice under the intended supplier ID and finds no result.
Accounting Scorecard shows three invoices passed to AP in the selected period and one in manual processing. The available summary does not identify that invoice. No business rejection has been found in the response records checked so far.
The supported conclusion is narrow: syntax acknowledgment is confirmed; the AP state of invoice 700481 is unresolved. The manual-processing count is a lead. It does not identify invoice 700481, prove acceptance or establish that $4,800 should already have arrived.
The next request is: “Please confirm the processing state of invoice 700481 using these supplier, PO and control references. If further information is required, identify the requirement and the responsible contact.” The supplier attaches the original evidence and records who will follow up.
Download the completed fictional note to see how that handoff looks. Its dates and identifiers are illustrative, not processing targets or a real claim.
Once AP locates it, ask the next payment question
Request the invoice’s actual status, any outstanding requirement, the applicable terms or due date, and any issued payment reference. Walmart’s public invoice-report documentation lists invoice status, due date, check details and invoice amounts separately. Acknowledgment is not a substitute for those records.
If a recorded deduction explains a difference, continue with the deduction investigation guide. If AP identifies an account debit-balance issue, use the debit-balance guide. Neither should be inferred from one missing invoice search.
For repeatable ownership across the account team, Startup Success Lab’s account-review and follow-through process provides a related framework for evidence, decisions and assigned actions. Keep the live invoice question assigned to the appropriate EDI or AP contact.
Source scope and limits
Source review completed September 13, 2026. X12 and Walmart’s invoice-report documentation were read directly. Walmart’s WebEDI guidance was reviewed through indexed official text; current authenticated screens were not checked. The note and example are original diagnostic aids. This guide does not set a processing deadline, establish payment eligibility or instruct you to delete, correct or resend an invoice.