Ryder EDI

Ryder (Ariba Inc.) EDI Guidelines

As a service to suppliers preferring to transact via EDI, Ariba SN accepts the ANSI X12 004010 810 (Invoice) transaction set and translates it to a cXML InvoiceDetailRequest. Because the 810 implementation ultimately maps to an InvoiceDetailRequest, it must conform to its rules. On receiving the 810, Ariba SN validates the EDI content, returns a 997 to the Supplier, and then converts it to the cXML InvoiceDetailRequest. The final cXML document is internally posted to process the actual invoice. 810 documents must strictly conform to these implementation guidelines. The 810 is implemented using ANSI X12 Version 004010.

The EDI information is specific to Ryder internal requirements, not necessarily the Ariba standard EDI 810 specification. Ryder, for example, may specify that a particular field is required, even if that field is not required per the general Ariba EDI guidelines. The Ariba EDI Guideline may require segments or fields which Ryder does not use, but none the less must be present as deemed by the Ariba specs. Invoice
documents that do not adhere to the following requirements are likely to be rejected by the Ariba Supplier Network (Ariba SN) or the Ryders end processing application.

Ryder EDI Documents

  • ANSI X12 810
  • ANSI X12 850
  • ANSI X12 855
  • ANSI X12 856
  • ANSI X12 ICS (Interchange Control Structure)
  • ANSI X12 997

If you will be accepting purchase orders (850) from Ryder through the Ariba Network you will want to review all related 850 documentation.

To learn more about EDI partner guidelines and become a certified EDI Professional please visit our course schedule page.

Leave a Reply

Your email address will not be published.

Post Navigation