Application Advice (824) Usage within VICS EDI
The first way of Application Advice (824) usage involves the reporting of errors (i.e. incorrect unit cost, invalid combination, etc.). The transaction needs to report all applicable errors encountered for a transaction set and it is recommended that a unique interchange file be generated for each transaction type being reported (i.e., one interchange for invoices, a second interchange for ship notices, etc.). The Application Advice (824) should not be used in place of a transaction set designed as a specific response to another transaction set, e.g., the Purchase Order Acknowledgment (855) is the response to the Purchase Order (850).
This transaction eliminates the need to communicate application errors by phone, fax, or mailed paper reports. It allows the originator of the transaction set to correct inconsistencies in a timely manner, minimizing the impact on time sensitive applications.
The second use of the Application Advice (824) involves buyers, suppliers, and financial institutions. The Application Advice (824) is the vehicle used by a financial institution to report acceptance and/or discrepancies to either the sender or receiver of the Payment Order/Remittance Advice (820). In this application, as well as others, the Application Advice (824) may be used to communicate a ’zero’ error condition as a result of application edits on the original transaction set.
Application Advice (824) Benefits
- Automated means to communicate errors in transactions which do not have a designated
response document - Eliminates need for problem determination/resolution by phone, fax, or mailed reports
- Strengthens the relationship between trading partners by resolving inconsistencies as they occur, rather than after time has elapsed.
To learn more about EDI and become a CEDIAP® (Certified EDI Academy Professional), please visit our course schedule page.