YRC

204   |   210   |   211   |   212   |   214   |   216   |   820   |   997 | Flat File Bill of Lading

Load Tender/Pickup Notification (transaction set 204)

• Although ANSI ASC X12 standards say that the 204 should not be used by less-than-truckload carriers for pickup notification and load tendering, YRC is allowing the use of the 4010 204 so that trading partners will not have to design new systems around the 216 transaction set.
• For best service, submit pickup requests 24 hours before the requested pickup date.
• Use the SCAC code for YRC: RDWY.
• Provide your requested pickup date.
• YRC requires the Load Number in the B204.
• Always include the name and phone number of the person who should be contacted for clarification on pickup details.
• Provide detailed shipper and consignee information: name, address, city, and state and ZIP/postal code. ** You must provide Shipper ZIP code information.**
• When acting as a third party, always provide detailed shipper and consignee address information.
• Include details about the shipment, such as quantity and weight.

Email 204 technical questions.

Invoice (transaction set 210)

• Accurately identify and provide the main components of the EDI transaction, receiver ID, version and proper communications methods. YRC supports AS2, FTP or Value-Added Networks inter-connected through Sterling Commerce.
• Provide specifications outlining your system requirements.
• Work through your YRC representative to ensure the proper locations to be included in the invoice files are identified. Location should be defined down to the address, city, state and ZIP code level.
• Determine how your systems will match the invoice data to the YRC shipment: by carrier Pro, PO or bill of lading number. If there is a set pattern for those numbers, YRC can apply a mask in the system for data entry to comply with the requirements.
• Determine whether EDI invoices should be sent for shipments inbound and/or outbound from the above locations or billed to a third party.

Email 210 technical questions.

Bill of Lading (transaction set 211)

• The 211 must be used as a bill of lading (BOL) with complete shipment information. The 211 is NOT to be used as a load tender to notify YRC that a shipment is available.
• YRC prefers ALL BOLs shipped with YRC be transmitted electronically. Because of system constraints, we understand this is not always possible, and only shipments destined to certain consignees can be sent.
• The BOL must be transmitted within one hour of the YRC trailer leaving the shipping dock. (It can be transmitted up to five days before if the shipment information is accurate). This ensures the data will be available to the service center when the shipment arrives.
• YRC accepts only an original BOL. Corrections and cancellations are handled manually at the service center.
• YRC traces and bills all shipments by pro number. YRC offers pre-pros so shippers can store pro numbers in their systems and assign them before transmitting. This gives you control over the pro number assigned to a BOL, which makes tracing and billing control more efficient. Check with your YRC account executive for a block of pro numbers.
• The electronic BOL must provide YRC an actual street address for shipper and consignee information. YRC cannot pick up from or deliver to a post office box.

The following details are mandatory in the electronic bill of lading:

• The YRC SCAC: RDWY
• Shipment Terms: Code identifying payment terms for transportation charges
• Pickup Date: The pickup date is the date YRC picks up the shipment.
• Bill of Lading Number: Customer's shipment identification number
• YRC PRO Number: YRC requires this field in the BOL06. It must match the PRO number on the paper BOL
• Transaction Set Purpose Code: Always 00 for an original BOL
• All Special Handling Requirements: Examples include notify contact before delivery, inside delivery required, lift gate required at destination, etc.
• Shipper Information: Shipper name; shipper identification code assigned by the shipper or provided by YRC; shipper address (no P.O. boxes); shipper city, state and ZIP/postal code
• Consignee Information: Consignee name; consignee address (where YRC will deliver the shipment); consignee city, state and ZIP/postal code; and consignee contact information for delivery appointments
• Third-Party Information: When a third party pays the shipping charges, the information for the third party must be supplied (name, address, city, state and ZIP/postal code)

This information is required for each product (line item):

• Bill of Lading Line Item Number: Sequential number, beginning with 1 to identify each individual product line item
• Lading Description: Text description of the product being shipped
• Lading Quantity: Number of handling units for which the carrier is responsible (master handling units). If the master handling unit is pallets, then pallet information must be provided.
• Lading Package Form Code: Type of package being shipped (e.g., CTN, PLT, SKD, etc.)
• Weight Qualifier: Net weight, tare weight, etc.
• Weight: Product weight
• If products are palletized the carton information must also be provided (quantity and package form code)
• The NMFC Number (National Motor Freight Classification code): Obtained from your traffic department or from your YRC Account Executive
• Purchase Order information: PO number, PO department, total carton count for the PO on this shipment and the total weight for the PO on this shipment
• Hazardous Information for all hazardous goods: The UN/NA identification code, hazardous material shipping name and hazardous material technical name.

Email 211 technical questions.

Shipment Trailer Manifest (transaction set 212)

Work through your YRC representative to ensure the proper locations to be included in the shipment trailer manifest are identified (i.e., the business name of each location and the complete address, including street, city, state and ZIP/postal code).

Email 212 technical questions.

Shipment Status (transaction set 214)

• Work through your YRC representative to ensure the proper locations to be included in the shipment status are identified (i.e., the business name of each location and the complete address, including street, city, state and ZIP/postal code).
• Determine to what your systems will match the shipment status data: PO, bill of lading and reference numbers are common. Also, determine whether there is a set pattern (format) for those numbers. Provide all formats and indicate whether a location has different formats than other locations.
• Determine whether the shipment status should be sent for inbound and/or outbound shipments.
• Identify the third-party and/or bill-to addresses (if any).
• Identify the transaction segments needed (the data needed).
• Please read the chapter on "System Considerations and Options" in the YRC 214 Implementation Guide.
• Determine shipment status codes and status options needed.
• The customer must determine whether the shipment status should be sent for inbound and/or outbound shipments.

Email 214 technical questions.

Shipment Pickup Notification (transaction set 216)

• For best service, submit pickup requests 24 hours before the requested pickup date.
• If using a pickup authorization or reference number, always provide this information in the PUN04.
• Use the SCAC code for YRC: RDWY.
• Provide requested pickup date.
• Always include name and phone number of the person who should be contacted for clarification on pickup details.
• Provide detailed shipper and consignee information: name, address, city, and state and ZIP/postal code.  ** Shipper ZIP code information MUST be provided **
• When acting as a third party, always provide detailed shipper and consignee address information.
• Include details about the shipment, such as quantity and weight.

Email 216 technical questions.

EDI Remittance Advice (transaction set 820)

• Always provide the YRC freight bill number for each detail line item that you are paying.
• The check detail must equal the total check amount. When paying multiple detail items (or multiple freight bills) on one check, make sure that the accumulated totals of all detail items equal the amount of the total check.
• Always provide the customer's name with each check. When paying multiple customers on one check, provide the customer name for each detail item.
• When adjusting your payment, supply the appropriate adjustment reason code.

Email 820 technical questions.

Transaction Acknowledgement (transaction set 997)

1. The acknowledgement is used to report the results of the syntactical analysis of the functional groups according to the published ASC X12 standards. The acknowledgement is not used to report on the semantic meaning of the transaction sets, for example, the receiver's ability to comply with the request of the sender.
2. It is important that you use the same sender and receiver IDs in reverse in the ISA/GS combination when acknowledging an EDI transaction.
3. The 997 can be sent back at a group level, which will acknowledge the total number of transactions that were received in the transmission, or it can be sent at the transaction level, which acknowledges each individual transaction. YRC will accept both methods.
4. You must send YRC an acknowledgement when we send an EDI 210 Invoice. This information is key to both companies to save time and money by preventing past-due issues.

Email 997 technical questions.

Flat File Bill of Lading (BOL)

• The BOL must be FTP'ed within one hour of the YRC trailer leaving the shipping dock. (It can be FTP'ed up to five days before if the shipment information is accurate). This ensures the data will be available to the service center when the shipment arrives.
• YRC accepts only an original BOL. The service center handles corrections and cancellations manually.
• YRC traces and bills all shipments by pro number. YRC offers pre-pros, so you can store pro numbers in your systems and assign them before transmitting. This gives you control over the pro number assigned to a BOL, which makes tracing and billing control more efficient. Check with your YRC account executive for a block of pro numbers.
• The Flat File BOL must provide YRC an actual street address for shipper and consignee information. YRC cannot pick up from or deliver to a post office box.

The following details are mandatory in the flat file bill of lading:

• The YRC SCAC: RDWY
• Method of Payment: Code identifying payment terms for transportation charges
• Ship Date: The pickup date is the date YRC picks up the shipment.
• Bill of Lading Number: Customer's shipment identification number
• YRC PRO Number: YRC requires this field. It must match the PRO number on the paper BOL
• Shipper Information: Shipper name; shipper identification code assigned by the shipper or provided by YRC; shipper address (no post office boxes); shipper city, state and ZIP/postal code
• Consignee Information: Consignee name; consignee address (where YRC will deliver the shipment); consignee city, state and ZIP/postal code; and consignee contact information for delivery appointments
• Third-Party Information: When a third party pays the shipping charges, the information for the third party must be supplied (name, address, city, state and ZIP/postal code)

This information is required for each product (line item):

• Product Description: Text description of the product being shipped
• Packaging Quantity: Number of handling units for which the carrier is responsible (master handling units). If the master handling unit is pallets, then you must provide pallet information.
• Packaging Type Code: Type of package being shipped (e.g., CTN, PLT, SKD, etc.)
• Weight: Product weight

Email Flat-file BOL technical questions.

Communications
YRC provides for direct connections by AS1 (SMTP), AS2 (HTTP), or FTP.

• SMTP Defined:
  Short for Simple Mail Transfer Protocol, a protocol for sending email messages between servers. Most email systems that send mail over the Internet use SMTP to send messages from one server to another; the messages can then be retrieved with an email client, using either POP or IMAP. In addition, SMTP is generally used to send messages from a mail client to a mail server. This is why you need to specify the POP or IMAP server and the SMTP server when you configure your email application. The AS1 standard extends the base SMTP standard.
   
• HTTP Defined:
  Short for HyperText Transfer Protocol, the underlying protocol used on the Internet. HTTP defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. For example, when you enter a URL in your browser, this actually sends an HTTP command to a web server, directing it to fetch and transmit the requested web page. The AS2 standard extends the base HTTP standard.
   
• FTP Defined:
  Short for File Transfer Protocol, the protocol used on the Internet for exchanging files. FTP works in the same way as HTTP for transferring web pages from a server to a user's browser and SMTP for transferring electronic mail across the Internet in that, like these technologies, FTP uses the Internet's TCP/IP protocols to enable data transfer.

For additional definitions see www.webopedia.com.

• Advantages of choosing SMTP, HTTP or an FTP Protocol
  • Cost Savings—eliminates the need for VAN services
  • Can be used with all the transaction sets YRC trades
     
• How to Establish the SMTP (AS1) Protocol with YRC 
    Required Information:
  • Email Address (data must be sent/received from the same account)
  • Certificate information for encryption
     
• How to Establish the HTTP (AS2) Protocol with YRC 
    Required Information:
  • URL: HTTP://
  • Secure URL: HTTPS://
  • Password to access your HTTP server
  • Username
  • Certificate information for encryption
     
• How to Establish the FTP Protocol with YRC
   
    Required Information:
  • Your FTP host name
  • Server name/IP address
  • Password to access your FTP server
  • Destination directory
  • Port
  • Active/passive
     
• Format
  • Wrapped 80-byte record
  • One record with no line feeds
     
• EDI Data Requirements (ASCII Only)
  • Sub element separator: > (Hex 6E)
  • Element separator: * (Hex 5C)
  • Segment terminator: ~ (HEX A1)

Email communications technical questions.