X12 ANSI Standard |
 |
| 204 - Load Tenders |
Purpose | | A 204 is load information sent from the company that controls the freight to the motor carrier. It is considered an offer of freight to the carrier and it may or may not be binding depending on the agreement between the company and the carrier. It contains all the pertinent information required to book a load such as shipper, consignee, weight, and bill of lading number. |
Version | | Preferably 4010, but we will support any other version, older or newer |
| 210 - Invoice |
Purpose | | The 210 is used to provide an itemized detail of freight charges for relevant parties. It is also used to request payment for services provided by the carrier. |
Version | | Preferably 4010, but we will support any other version, older or newer |
| 213 - Shipment Status Inquiry |
Purpose | | This transaction can be used to request shipment status from the motor company by the shipper or the consignee. |
Version | | Preferably 4010, but we will support any other version, older or newer |
| 214 - Shipment Status Message |
Purpose | | This transaction is used to report the status of a shipment to the shipper, consignee or other parties to the shipment. It can be used to provide pick-up/delivery dates and times, transit status, identification number, and the bill of lading number for tracking shipments. |
Version | | Preferably 4010, but we will support any other version, older or newer |
| 820 - Payment Order/Remittance Advice |
Purpose | | An 820 allows the motor carrier to receive a remittance advice from the customer or their bank. Cash can be applied to the carriers accounts receivable system. |
Version | | Preferably 4010, but we will support any other version, older or newer |
| 824 - Application Advice |
Purpose | | An 824 tells the load carrier if a 214 was accepted in the customer’s system. It also tells why it wasn’t accepted such as missing weights, pieces, locations, bill of lading number, etc. |
Version | | Preferably 4010, but we will support any other version, older or newer |
| 858 - Advance Ship Notice |
Purpose | | This is similar to a 204 load tender. It contains all the load information required to book a load in advance. |
Version | | Preferably 4010, but we will support any other version, older or newer |
| 864 - Text Message |
Purpose | | This is a simple text message. It can contain any information the customer needs to send. |
Version | | Preferably 4010, but we will support any other version, older or newer |
| 980 - Invoice Summary |
Purpose | | This is a summary of a batch or group of invoices sent to a customer through 210 transactions. It gives the total dollar amount and number of invoices sent. |
Version | | Preferably 4010, but we will support any other version, older or newer |
| 990 - Load Tender Response |
Purpose | | This allows the customer to know if we accepted or declined the 204 load tender. It provides the customer with our load number for tracking purposes. If the load is declined, the 204 load tender can be used to return a reason for not accepting the load. |
Version | | Preferably 4010, but we will support any other version, older or newer |
| 996 - File Transfer |
Purpose | | This is a generic document. It is a plain flat file of data sent from the customer and can contain whatever information the customer needs to send. This is used to send and receive text data files; much like you would download from your system or use in a word-processor. |
Version | | Preferably 4010, but we will support any other version, older or newer |
| 997 - Acknowledgment |
Purpose | | This is a document that just acknowledges other documents as being received. A 997 tell us whether or not our customer received a 210 or a 214. This is similar in concept to return receipts for normal mail. |
Version | | ALL |
| | |
EDI FACTS Standard |
|
| APERAK - Application Error and Acknowledgement Message |
Purpose | | The function of the APERAK is to inform the customer that his original message was received by the addressee’s application and has been rejected due to errors encountered during its process in the application. We are currently set up to receive an APERAK when a DESADV fails to process in our system. |
Version | | Preferably D98B but other versions are acceptable |
| DELJIT - Delivery Just in Time Message |
Purpose | | We receive DELJITS from our customer to convey precise delivery sequence and just in time schedule requirements to the supplier. |
Version | | Preferably D98B but other versions are acceptable |
| DESADV - Dispatch Advice Message |
Purpose | | We receive/send DESADV from and to our customer. This message specifies details for goods dispatched, or ready for dispatch, under agreed conditions. It can also be used for returns. |
Version | | Preferably D98B but other versions are acceptable |
| RECADV - Receiving Advice Message |
Purpose | | This document is used to report discrepancies in products, quantities, terms, packages, etc. It is also used to report the physical receipt of goods. |
Version | | Preferably D98B but other versions are acceptable |
|