EDI Document

824 Application Advice.
Know exactly what was rejected.

A trading partner sends an 824 when a document you sent fails their business rules. Fulfil links it to the original document and decodes the errors into plain words, so you know what to fix.

What's included in an 824.

The 824 reports application-level errors in a document you already sent.

Reference to the Original

  • ✓ Control number of the original document
  • ✓ Transaction type (856, 810, etc.)
  • ✓ Error codes for each problem found
  • ✓ Free-form descriptions of what failed

Typical Errors Reported

  • ✓ Invalid or missing product identifiers
  • ✓ Quantity or price mismatches between PO and ASN or invoice
  • ✓ Missing required fields
  • ✓ Business rule violations

How 824 works in Fulfil.

Fulfil receives each 824 and ties it back to the document it rejects.

1

Partner sends an 824

Your trading partner finds a problem with a document you sent, such as an ASN or invoice, and sends an 824 through your EDI integration.

2

Fulfil links it to the original

Fulfil parses the 824, identifies the original document from its control number, stores the 824 against it, and shows the 824 as Processed in the EDI monitor.

3

Errors decoded into plain words

The specific errors appear on the original document, in the rejected notification, and in Slack. The segment view highlights each segment the 824 names and lists the errors next to it.

✓

Correct and resend

The 824 does not change the original document. You correct the source record in Fulfil and retransmit.

Why 824 matters for your business.

Business-level rejection, not just syntax

A 997 tells you the retailer could read your document. An 824 tells you whether it passed their rules. An ASN with a wrong UPC or an invoice with a price that doesn't match the PO can pass the 997 and still be rejected with an 824.

Errors you can act on

Raw 824 error codes are hard to read. Fulfil decodes them into plain words and points to the exact segments that failed, so your team can see what to fix without reading X12.

Rejections reach the person who can fix them

The errors show on the original document, in the rejected notification, and in your EDI Slack channel, so a rejected ASN or invoice doesn't sit unnoticed in the EDI monitor.

FAQ

Questions? Answers.

What is an EDI 824?
The 824 Application Advice is a document a trading partner sends to report errors or rejections in a document you sent them. It references the original document by control number and transaction type, and includes one or more error codes with descriptions of what failed. Fulfil receives the 824 and links it to the original document so you can review and correct the issue.
How is an 824 different from a 997?
A 997 Functional Acknowledgement is syntax-only: it confirms the document could be parsed. An 824 reports application-level errors, such as invalid or missing product identifiers, quantity or price mismatches between the PO and an ASN or invoice, missing required fields, or business rule violations. A document can pass the 997 and still be rejected with an 824.
Where do I see the errors from an 824?
When a trading partner rejects an outbound document with an 824, Fulfil keeps the specific errors, decoded into plain words, instead of a generic rejection message. The errors appear on the original document, in the rejected notification, and in the EDI Slack message. The segment view of the original document highlights each segment the 824 names and lists the errors next to it.
Does Fulfil fix the original document automatically?
No. The 824 tells you what the trading partner rejected, but it does not change the original document. You correct the source record in Fulfil, such as the shipment behind an 856 or the invoice behind an 810, and retransmit.
Does Fulfil send 824s?
No. The 824 is inbound only in Fulfil. Your trading partners send 824s to Fulfil to report problems with documents you sent them.
How do I set up 824 processing?
On the trading partner's document configurations, add Application Advice (824) with the direction set to Inbound and save. Fulfil then parses each 824 the partner sends, links it to the original document, and shows it as Processed in the EDI monitor.

Ready to trade EDI
with confidence?