EDI Messaging (Trucking Industry)
Do you need an EDI VAN provider? Trucking companies are looking for ways to improve efficiency and reduce costs. Perhaps your customer has asked you to implement EDI and you don’t have a dispatch system that is able to send or receive EDI messages? EDI doesn’t have to be costly and there are ways to implement EDI using a web portal or even implemented using email.
What are the Common EDI Messages used in the Trucking Industry?
204 Motor Carrier Load Tender
990 Response to a Load Tender
210 Motor Carrier Freight Details and Invoice
211 Motor Carrier Bill of Lading
212 Motor Carrier Delivery Trailer Manifest
214 Transportation Carrier Shipment Status Message
215 Motor Carrier Pickup Manifest
216 Motor Carrier Shipment Pickup Notification
217 Motor Carrier Loading and Route Guide
820 Payment Order/Remittance Advice
997 Functional Acknowledgment
Trucking EDI Basics
If you have a dispatch system that can send or receive the above messages then that would normally be the first place to start. The file format used in the above messages is the American National Standards Institute (ANSI) which is also known as X12.
Sending X12 messages can happen directly between trading partners if both parties are agreeable to using the same communication method; The way to send the messages between trading partners would usually be FTP (file transfer protocol), sFTP (Secure File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), Web Services or AS2 (Applicability Statement 2). Customs City can facilitate connecting you to your trading partners in any of these communication protocols.
In some instances, a trucking company might not want to support connections to multiple trading partners. In this case, company A will connect to Customs City and then instruct its trading partners to connect to Customs City in whatever communication protocol they prefer. Customs City will then route the messages to company A that is received from its trading partners. This is also known as the hub and spoke method.
Translation and Mapping of Messages
Usually, company A and company B want to send & receive different file formats. For example company, A is comfortable using XML, while company B is comfortable using EDIFACT (Electronic Data Interchange For Administration, Commerce and Transport). In this case, Customs City will have to receive the file in XML format and then translate it to EDIFACT format before sending to company B. The communication protocol would also be agreed upon in advance i.e sFTP.
Mapping of EDI messages is a one-time effort where we analyse your file ie. XML and then map the XML data elements to the receiving file format ie. EDIFACT. Once the map is manually created the subsequent mapping of files is automated using Customs City translation engine.