Application advice transactions
The Application Advice transaction provides structured, actionable feedback about the outcome of business-level validation for previously received EDI transactions such as invoices, purchase orders, shipment notifications, and sales reports. It is a key tool in ensuring clarity, accountability, and alignment between trading partners.
After an EDI document passes initial syntax checks, trading partners including manufacturers, wholesalers, distributors, or EDI solution providers—use the Application Advice to communicate the results of deeper, application-level validations. These validations assess whether the content of the transaction meets the business rules of the receiving system.
Unlike Functional Acknowledgment (997) or Implementation Acknowledgment (999), which simply confirm that a file was structurally correct and received, the Application Advice provides more meaningful insight into how the document was interpreted and what actions were taken. Specifically, the 824 indicates whether the transaction was:
-
Accepted – All content passed business validation.
-
Rejected – One or more issues prevented the transaction from being accepted.
-
Accepted with changes – The transaction was processed, but required adjustments.
-
Partially accepted or rejected – Some parts of the transaction were valid, while others were not.
This distinction is critical for identifying issues like pricing mismatches, missing product identifiers, or contract discrepancies—problems that are not visible through syntax checks alone. Early detection of these business-level errors allows teams to act quickly, reducing downstream delays, rejections, and costly manual investigation.
Each Application Advice may include standardized error codes and descriptive text that pinpoint the exact issue—down to a transaction set, segment, or data element—making it easier to troubleshoot and resolve. By incorporating application advice processing into supply chain workflows, organizations can proactively detect and resolve pricing, contract, or compliance issues, improve data quality, reduce invoice and payment disputes, streamline communication with trading partners, and enhance financial accuracy and audit readiness.
The Application Advice provides structured, actionable feedback that helps trading partners resolve business‑level issues quickly, reducing delays, rejections, and manual investigation across integrated supply chain workflows.
Type = API Reference,; Topic = Multienterprise Information Network Tower (MINT), Transforms,;Persona = TraceLink Administrator, User, Solution Partner,; Orchestration = Manufacturing, Commerce,; Function = Supply Chain, IT, Procurement,
Application advice (X12)
The Application Advice (EDI 824) transaction communicates the results of business-level validation for previously received EDI documents, indicating whether they were accepted, rejected, or required changes.
Contact your TraceLink Services representative for more information about integrating with this message.
- Message Type: MPC_APPLICATION_ADVICE
- X12 Format: APPLICATIONADVICE
- B2B_EDI_X12_824_ApplicationAdvice_IB_V1
B2B_EDI_X12_824_ApplicationAdvice_OB_V1
Transform Names:
| Input Element | Occurs | Length | Description | Example | |||||
|---|---|---|---|---|---|---|---|---|---|
| ISA | 1…1 | - | Required. ISA interchange envelope. | - | |||||
| ISA01 | 1…1 | 2/2 | Required. Qualifier for authorization control number in ISA02. | 00 | |||||
| ISA02 | 1…1 | 10/10 | Required. Information used for additional identification or authorization of the interchange sender or the data in the interchange/ 10 spaces a valid entry. | - | |||||
| ISA03 | 1…1 | 2/2 | Required. Qualifier for security information in ISA04. | 00 | |||||
| ISA04 | 1…1 | 10/10 | Required. Identifies security information about the interchange sender or data. | - | |||||
| ISA05 | 1…1 | 2/2 |
Required. Interchange sender partner ID qualifier.
|
07 | |||||
| ISA06 | 1…1 | 15/15 | Required. Interchange sender identification mapping to fileSenderNumber with party type defined in ISA05. | 7777776067344 | |||||
| ISA07 | 1…1 | 2/2 |
Required. Interchange receiver partner ID qualifier.
|
01 | |||||
| ISA08 | 1…1 | 15/15 | Required. EDI receiver ID mapping to file control header and to ServiceLinkId. | 888888404358877 | |||||
| ISA09 | 1…1 | 6/6 | Required. Interchange date in 6 char YYMMDD format. | 231020 | |||||
| ISA10 | 1…1 | 4/4 | Required. Interchange time in 4 char HHMM format. | 1420 | |||||
| ISA11 | 1…1 | 1/1 |
Required. This value is dependent on X12 version.
|
^ | |||||
| ISA12 | 1…1 | 5/5 | Required. Interchange control version number. This could be any X12 version. | 00501 | |||||
| ISA13 | 1…1 | 9/9 | Required. Interchange Control Number mapping to file control header. | 0000000000619827 | |||||
| ISA14 | 1…1 | 1/1 |
Required. Interchange level acknowledgment requested. Valid values:
|
0 | |||||
| ISA15 | 1…1 | 1/1 |
Required. Indicates whether the interchange is for production, test, or information purposes. Valid values:
|
P | |||||
| ISA16 | 1…1 | 1/1 | Required. Component element separator. Delimiter that separates data elements within a composite data structure. Must be different than the data element separator and segment terminator. | > | |||||
| GS | 1…* | - | Required. GS group functional envelope. Child of ISA. Only one GS group expected per interchange. | - | |||||
| GS01 | 1…1 | 2/2 |
Required. GS group function code. Valid value is SO Shipping instruction Information |
SO | |||||
| GS02 | 1…1 | 2/15 | Required. Application Sender's Code. | 2222224043588 | |||||
| GS03 | 1…1 | 2/15 | Required. Application Receiver's Code. | TRACELINK | |||||
| GS04 | 1…1 | 8/8 | Required. Current date stamp in 8 char X12 date format YYYYMMDD. | 20241020 | |||||
| GS05 | 1…1 | 4/8 | Required. Current time stamp in 6 char X12 time format HHMMSS. | 142000 | |||||
| GS06 | 1…1 | 1/9 | Required. Group Control ID Number. | 619827 | |||||
| GS07 | 1…1 | 1/2 |
Required. Responsible Agency Code. Valid values:
|
X | |||||
| GS08 | 1…1 | 1/12 | Required. X12 message version code. This could be any X12 version. | 005010 | |||||
| ST | 1…* | - | Required. ST transaction set envelope. Child of GS group. Only one ST transaction expected. | - | |||||
| ST01 | 1…1 | 3/3 | Required. Transaction set identifier code. | 824 | |||||
| ST02 | 1…1 | 4/9 | Required. Transaction set ID number. Counter for each ST segment beginning with 1. | 0001 | |||||
| BGN | 1…1 | - | Required. BGN Beginning Segment. | - | |||||
| BGN01 | 1…1 | 2/2 | Required. Transaction Set Purpose Code identifying purpose of transaction set. Valid value is
11 - RESPONSE |
11 | |||||
| BGN02 | 1…1 | 1/50 | Required. Transaction unique reference identifier defined for a particular transaction set. The sender's internal number used to identify this transaction set within the sender's application system. | 8475 | |||||
| BGN03 | 1…1 | 8/8 | Required. Date the original transaction was generated in the sender's business application system, in X12 date format YYYYMMDD. This date is analgous to the date on the paper document, the date it was created. | 20160129 | |||||
| BGN04 | 0…1 | 4/8 | Transaction time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD | 223344 | |||||
| N1 Loop | 0…* | - | Required. N1 segment loop at header for party address and reference information. | - | |||||
| N1 | 1…1 | - | Required. Party identification. | - | |||||
| N101 | 1…1 | 2/3 |
Required. Entity qualifier for the Sender or Receiver party identifier and address information. (missing or bad snippet) |
SU | |||||
| N102 | 0…1 | 1/60 | Name Note: Either N102 or N104 is required. | Pharma customer | |||||
| N103 | 0…1 | 1/2 |
Identifier code qualifier. Valid values:
|
UL | |||||
| N104 | 0…1 | 2/80 | Party identifier as qualified by N103 mapping to companyIdentifierValue. | 3333331013655 | |||||
| N2 | 0…2 | - | N2: Additional names: Child of Party N1 segment., we do support one iteration of N2. | - | |||||
| N201 | 1…1 | 1/60 | Required. Additional name 2. | Pharma name2 | |||||
| N202 | 0…1 | 1/60 | Additional name 2. | Pharma name2 | |||||
| N3 | 0…2 | - | N3: Address: Child of Party N1 segment. | - | |||||
| N301 | 1…1 | 1/55 | Required. Street address 1. | 555 Neelan Road | |||||
| N302 | 0…1 | 1/55 | Street address 2. | Suite 123 | |||||
| N4 | 0…1 | - | N4: Geographic Location. Child of Party N1 segment. | - | |||||
| N401 | 0…1 | 2/30 | City name. | Sacramento | |||||
| N402 | 0…1 | 2/2 | State or province code. Code (Standard state/province) as defined by appropriate government agency. | CA | |||||
| N403 | 0…1 | 3/15 | Postal code. Code defining international postal zone code excluding punctuation and blanks. | 95833 | |||||
| N404 | 0…1 | 2/3 | Country code. | US | |||||
| N405 | 0…1 | 1/2 | Type of location. | CA | |||||
| N406 | 0…1 | 1/30 | Specific location. | 95833 | |||||
| N407 | 0…1 | 1/3 | Country subdivision. | US | |||||
| REF | 0…12 | - | Reference segment for mapping to the transaction references. | - | |||||
| REF01 | 1…1 | 2/3 |
Required. Reference identifier qualifier. Code identifies the type of ID number sent in REF02.
|
RF | |||||
| REF02 | 0…1 | 1/80 | Reference identifier value. | 123456 | |||||
| REF03 | 0…1 | 1/45 | Description defined by qualifier code in REF02. | - | |||||
| PER | 0…3 | - | PER segment explains about contact information for party business or location. | - | |||||
| PER01 | 1…1 | 2/2 |
Required. Contact type. Valid values:
|
IC | |||||
| PER02 | 0…1 | 1/60 | Contact name. | Grame Smith | |||||
| PER03 | 0…1 | 2/2 | Communication qualifier Note: If PER03 or PER04 present other one is required. We do support either TE or EM as PER03 qualifiers. | TE | |||||
| PER04 | 0…1 | 1/2048 | Contact phone number. | '897654 | |||||
| PER05 | 0…1 | 2/2 | Communication qualifier Note: If PER05 or PER06 present other one is required. We do support either TE or EM as PER05 qualifiers. | EM | |||||
| PER06 | 0…1 | 1/2048 | Contact email address. | gsmith@gmail.com | |||||
| OTI Loop | 1…* | - | Required. Line item loop start for Shipping instruction, referring a line number in a transaction set. | - | |||||
| OTI | 1…1 | - | Required. Original transaction identification. | - | |||||
| OTI01 | 1…1 | 1/2 |
Required. Application acknowledgment code. Identifies processing status of the original transaction in the system that sent the 824. (missing or bad snippet) |
TA | |||||
| OTI02 | 1…1 | 2/3 |
Required. Original transaction reference number qualifier. (missing or bad snippet) |
TN | |||||
| OTI03 | 1…1 | 1/50 | Required. Reference Identification defined for a particular Transaction Set. Identifies the transaction within the business application, such as the document number. If reporting errors on an 856, this should reference the ASN ship notification document number. | 0001 | |||||
| OTI04 | 0…1 | 2/15 | Application Sender's Code. Identifies the sender (GS02 sender) of the original transaction that the 824 is reporting on. | R23432 | |||||
| OTI05 | 0…1 | 2/15 | Application Sender's Code. Identifies the receiver (GS03 receiver) of the original transaction that the 824 is reporting on. | AA2343 | |||||
| OTI06 | 0…1 | 8/8 | Transaction date in YYYYMMDD format from the GS04 date field in the original transaction that the 824 is reporting on. | 20160129 | |||||
| OTI07 | 0…1 | 4/8 | Transaction time in 24 hour HHMM or HHMMSS or HHMMSSD or HHMMSSDD time format from the GS05 time field in the original transaction that the 824 is reporting on. | 223344 | |||||
| OTI08 | 0…1 | 1/9 | Group Control Number from the GS06 field of the original 856 ASN (or other) transaction that the 824 is reporting on. | - | |||||
| OTI09 | 0…1 | 4/9 | Transaction Set Control Number from the ST02 field of the original 856 ASN (or other) transaction that the 824 is reporting on. | - | |||||
| OTI10 | 0…1 | 3/3 | X12 transaction set code from the ST01 field of the original 856 ASN (or other) transaction that the 824 is reporting on. Valid values can be any X12 transaction set code. | - | |||||
| REF | 0…* | - | Reference segment for mapping to the transaction identifiers. List of documents and transactions referencing at the item level of the message, that are relate to original transaction. | - | |||||
| REF01 | 1…1 | 2/3 |
Required. Reference identifier qualifier. Code identifies the type of ID number sent in REF02. (missing or bad snippet) |
BM | |||||
| REF02 | 0…1 | 1/80 | Reference identifier value: | 123456 | |||||
| DTM | 0...* | - | Dates that will help transactionset to uniquely identify origin transaction / reference transaction set that this Application advice (824) is generating | - | |||||
| DTM01 | 1…1 | 3/3 |
Required. Date type related to shipment events at port, in date format YYYYMMDD and time format (IDoc/ X12) HHMMSS.
|
999 | |||||
| DTM02 | 0…1 | 8/8 | Date defined by referenced date type in date format YYYY-MM-DD. Transform will pass thru whatever it finds. | 20241215 | |||||
| DTM03 | 0…1 | 4/8 | Time expressed in 24-hour clock time as follows. | - | |||||
| DTM04 | 0…1 | 2/2 | Time zone for referenced dates. | ES | |||||
| DTM05 | 0…1 | 2/3 |
Describes the date format, time format, or date and time period format type.
|
DT | |||||
| AMT | 0…* | - | Monetary amount. Original transaction amount for which 824 is being generated Notes: which will be used to uniquely identify original transaction in sender system. | - | |||||
| AMT01 | 1…1 | 1/3 |
Required. Referenced transaction amount type.
|
TOT | |||||
| AMT02 | 1…1 | 1/18 | Required. Monetary amount. | 275.36 | |||||
| AMT03 | 0…1 | 1/1 |
Credit or debit flag code indicating whether the amount is a credit or a debit. Valid values:
|
D | |||||
| QTY | 0…* | - | Original transaction quantity for which 824 is being generated Notes: which will be used to uniquely identify original transaction in sender system. | - | |||||
| QTY01 | 1…1 | 2/2 |
Required. Type of quantity recorded. Most likely it will be Total.
|
TO | |||||
| QTY02 | 0…1 | 1/15 | Required. Quantity of product. | 25.00 | |||||
| QTY03.1 | 1…1 | 2/2 |
Required. Unit of measure used for pricing.
|
UN | |||||
| TED Loop | 0…* | - | Technical error and business error details. | - | |||||
| TED | 0…1 | - | TED Technical Error Description segment. Identifies the error in the original 856 ASN being reported on. Can also identify the segment and/or data element where the error occurred in the original transaction. Child of OTI loop. | - | |||||
| TED01 | 1…1 | 1/3 |
Required. Application error condition code describing the error condition in the original transaction.
|
024 | |||||
| TED02 | 0…1 | 1/60 | Free-form Message. Short description of the error for the error code used in TED01, and in conjunction with the long description listed in the NTE02. | Item Status (I)nactive ITEM = 000586765 VENDOR = 67345205 | |||||
| TED03 | 0…1 | 2/3 | Segment ID Code. Identifies segment in orginal transation that triggered an error. | BTS | |||||
| TED04 | 0…1 | 0/10 | Segment Position in Transaction Set. The numerical count position of this data segment from the start of the transaction set: the transaction set header is count position 1. | 3 | |||||
| TED05 | 0…1 | - | If TED05 present TED05.1 is Required | - | |||||
| TED05.1 | 1...1 | 0/2 |
Required. Position in Segment. Code indicating the relative position of the error data element within a segment, count beginning with 1 for position immediately after the segment ID. Also indicates: 1. Relative position of a repeating structure in error, beginning with 1 for the position immediately after the preceding element separator. 2. Relative position of a component of a composite data structure in error, count beginning with 1 for the position following the preceding element or repetition separator. |
3 | |||||
| TED05.2 | 0...1 | 0/2 | Component Data Element Position in Composite. | 13 | |||||
| TED05.3 | 0...1 | 0/4 | Repeating Data Element Position. | 373 | |||||
| TED07 | 0…1 | 1/99 | Copy of the bad data element. Data from the data element that is in error. | 000586765 | |||||
| NTE | 0…100 | - | NTE Note/Special Instruction loop. Child of TED. | - | |||||
| NTE01 | 0...1 | '3/3 | Note Reference Code. | - | |||||
| NTE02 | 1...1 | 1/80 | Required. Description. A free-form description to clarify related data elements and their content. Used as the long description for the error code in TED01, and in conjunction with the short description in TED03. | Item Status (I)nactive ITEM = 000586765 VENDOR = 67345205 | |||||
| RED | 0…100 | - | To provide business data related to an item within a transaction to which a business application editing process has been applied, and an error condition has resulted. | - | |||||
| RED01 | 1...1 | 1/80 | Required. Represents the actual business value or Error descriptive information, being referenced or cited in connection with a validation message or application result. This value indicates which specific field or transaction content is associated with the reported condition. | NA | |||||
| RED02 | 0...1 | 2/3 | Identifies the nature or classification of the business data referenced due to a validation or application edit result. The value corresponds to standardized codes (e.g., PO Number, Unit Price, GTIN, Quantity). Only one code is allowed and at least one must be present when reporting referenced business data | PO | |||||
| RED03 | 0...1 | 2/2 | Agency Qualifier Code. | 94 | |||||
| RED05 | 0...1 | 1/3 | Code List Qualifier Code. | IBP | |||||
| RED06 | 0...1 | 1/30 | Industry Code. | W050 | |||||
| SE | 1…1 | - | Required. ST … SE transaction set trailer envelope. Child of GS group. Only one ST transaction expected. | - | |||||
| SE01 | 1…1 | 1/10 | Required. Total count of segments in ST … SE transaction set including ST and SE segments. | 10 | |||||
| SE02 | 1…1 | 4/9 | Required. Transaction set control number. | 0001 | |||||
| GE | 1…1 | - | Required. GS … GE functional group trailer envelope. Child of ISA interchange. Only one GS group expected. | - | |||||
| GE01 | 1…1 | 1/6 | Required. Number of transaction sets in functional group. | 5 | |||||
| GE02 | 1…1 | 1/9 | Required. Functional group control number. | 619827 | |||||
| IEA | 1…1 | - | Required. ISA … IEA interchange control trailer envelope. Only one interchange expected per transmission. | - | |||||
| IEA01 | 1…1 | 1/5 | Required. Number of functional groups in interchange. | 1 | |||||
| IEA02 | 1…1 | 9/9 | Required. Interchange control number. | 0000000000619827 | |||||
Example
CopyISA*00* *00* *07*7777776067344 *01*888888404358877*250612*1332*<*00501*000619827*0*P*:~
GS*IO*2222224043588*TRACELINK*20250611*142000*619827*X*00501~
ST*312*0001~
BGN*00*8475*20251202*123222~
N1*CA*business_name1*1*s333~
N2*s27*s28~
N2*s20*s38~
N3*s334*s335~
N3*s20*s38~
N4*s336*s3*s338*US*CA*95833*US~
REF*SI*123*description1~
REF*TD*123*description3~
PER*IC*Grame Smith*TE*897654*EM*gsmith@gmail.com~
PER*FC*Grame Smith*TE*897654~
N1*SU*business_name2*2*s76~
N2*s27*s28~
N2*s45*s55~
N3*s77*s78~
N4*s79*s8*s81*US*CA*95834*US~
REF*CT*123*description1~
PER*IC*Grame Smith*EM*gsmith@gmail.com*TE*897654~
PER*RP*Grame Smith*EM*gsmith@gmail.com~
N1*ST*business_name3*9*s65~
N2*s10*s28~
N3*s66*s67~
N3*s20*s38~
N4*s68*s6*s70*US*CA*95836*US~
REF*SI*123*description1~
REF*CT*123*description2~
REF*TD*123*description3~
PER*IC*Grame Smith*TE*897654*EM*gsmith@gmail.com~
OTI*TA*IB*0001*1234*1212*20251202*123222*52*SCAC*100~
REF*SI*123*description1~
REF*AG*123*description2~
REF*TD*123*description3~
DTM*133*20251202*123222*03*D8~
DTM*372*20251202*12322211*03*DT~
AMT*A*62*D~
AMT*CH*62*C~
QTY*H8*65*EA~
QTY*QV*65*EA~
TED*B*s68*s69*70*71:72:73**s74~
NTE*BFD*s76~
NTE*BFD*s76~
NTE*BFD*s76~
RED*s77*PR*CX**BN*s81~
RED*s77*PR*CX**BN*s81~
RED*s77*PR*CX**BN*s81~
TED*B*s68*s69*70*71:72:73**s74~
NTE*BFD*s76~
NTE*BFD*s76~
NTE*BFD*s76~
RED*s77*PR*CX**BN*s81~
RED*s77*PR*CX**BN*s81~
RED*s77*PR*CX**BN*s81~
OTI*BA*IB*0001*1234*1212*20251202*123222*52*SCAC*100~
REF*SI*123*description1~
REF*AG*123*description2~
REF*TD*123*description3~
DTM*133*20251202*123222*03*D8~
DTM*372*20251202*12322211*03*DT~
AMT*A*62*D~
AMT*CH*62*C~
QTY*H8*65*EA~
QTY*QV*65*EA~
TED*MA*s68*s69*70*71:72:73**s74~
NTE*BFD*s76~
NTE*BFD*s76~
NTE*BFD*s76~
RED*s77*PR*CX**BN*s81~
RED*s77*PR*CX**BN*s81~
RED*s77*PR*CX**BN*s81~
TED*MB*s68*s69*70*71:72:73**s74~
NTE*BFD*s76~
NTE*BFD*s76~
NTE*BFD*s76~
RED*s77*PR*CX**BN*s81~
RED*s77*PR*CX**BN*s81~
RED*s77*PR*CX**BN*s81~
SE*82*s83s~
GE*84*85~
IEA*86*s87ssssss~
Tag end


