Electronic Data Interchange (EDI) Resource Center

EDI is an electronic exchange of data, usually between businesses.

Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to retype the data. This electronic link can result in more-effective business transactions.

Trading Partner Profile

To begin the process of integration, regardless of the solution chosen, YRC needs a Trading Partner Profile (TPP), which you can complete online. The TPP provides our analyst information vital to the project and contact information from your company’s project partner. After you complete and submit the TPP, we will assign an analyst to work with you.

YRC supports  the following standard EDI transaction sets.

  • 210: Electronic Freight Bill (Invoice). YRC (the carrier) sends this transaction set to the customer (you) or third party as an invoice to request payment for services rendered. It provides detailed information of charges.

  • 211: Bill of Lading. The shipper (you) sends this transaction set to YRC (the carrier) to provide us detailed bill of lading information pertinent to a shipment.

  • 212: Delivery Trailer Manifest. YRC (the carrier) sends this transaction set to the consignee or other interested parties, listing the contents of a trailer that contains multiple shipments that have been tendered for delivery.

  • 214: Shipment status messages. YRC (the carrier) sends this transaction set to the shipper and/or consignee to provide up-to-date information on your shipments. Data includes dates, times, locations, route and reference numbers.

  • 204/216: Pickup request. The shipper (you) sends this transaction set to YRC (the carrier) to request a shipment pickup.

  • 820: Remittance Advice. The payer (you or your third-party payer) sends this transaction set to YRC (the carrier) to provide YRC remittance/payment information.

  • 997: Acknowledgement. This transaction set is sent in response to each transaction set received to indicate acceptance by shipper, carrier or payee. It is an acknowledgement by any party to another party of data received.

  • Flat File Bill of Lading: The shipper (you) FTPs a flat file to YRC (the carrier) to provide us detailed bill of lading information pertinent to a shipment.
Implementation Guides
ANSI X12 Transaction Set
Transaction Sets
We Support:
Tech Tips
Trading Partner
Profile (TPP)
Check Status
of TPP Request
 
V4010
204: Load Tender/Pickup Notification
210: Invoice
211: Bill of Lading
212: Delivery Trailer Manifest
214: Shipment Status
216: Shipment Pickup Notification
820: Remittance Advice
997: Functional Acknowledgement
Flat File Bill of Lading    
Communication Tips
Get Adobe ReaderYou need Adobe Reader to view the forms listed above. If you don't already have it, click here to download a free copy.
VICS Bill of Lading (BOL)
The VICS BOL is a standardized BOL developed through a consortium of shippers and carriers to meet the needs of all parties. YRC offers an online Bill of Lading on my.yrc.com that will produce an electronic VICS BOL that meets the guidelines of the VICS committee. Read more about the VICS BOL.

Communications
YRC has developed a communication system that gives our trading partners the flexibility to transmit EDI transactions directly to YRC, our preferred method, or through a VAN (value-added network). If you use a VAN, YRC prefers Sterling Information Broker, Kleinschmidt or Transettlements. If you choose to use another VAN, please have the data interconnected to one of the VANs mentioned above.

YRC provides for direct connections via AS1 (SMTP), AS2 (HTTP), or FTP, which eliminates the use of a VAN. You can choose a connection method when you complete a Trading Partner Profile. For more specific information, read our technical tips.

Questions?

Contact us by email.

In This Section:

Read about our systems power

Related Links:
Click to Login to MY.YRC.COM



Customer Support

Log Out Edit Info