Skip to content
X12 EDI

Ryder X12 210 Motor Carrier Freight Details and Invoice

Plan X12 210 Motor Carrier Freight Details and Invoice for Coty (via Ryder). Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
23
Loops
4
X12 210
Partner references ↗

Implementation guide

Coty (via Ryder): 210 mapping and validation

X12 210 Motor Carrier Freight Details and Invoice is used when transport charges are ready for audit. Preserve carrier invoice, shipment reference and charge line so the freight invoice in your business system stays connected to the original document.

This document is listed for Coty (via Ryder). Confirm the version, required fields and responses that apply to your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record freight invoice

carrier invoice, shipment reference and charge line

  • Define which combination of carrier invoice, shipment reference and charge line identifies one business record, its lines and any later revision.
Update the receiving system Processing the freight invoice

ID assigned by the receiving system and processing result

  • Separate line-haul, fuel and accessorial charges before comparing the invoice with the agreed rate.
  • Test a second invoice for the same shipment and distinguish a revision from a duplicate.
Check the processing result Processing status for the freight invoice

Original document reference and matching response

  • Reconcile the freight invoice with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

The document reference includes 23 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when transport charges are ready for audit. Name the operational owner of the freight invoice and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map carrier invoice, shipment reference and charge line. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Ryder guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic freight invoice data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful freight invoice processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 210 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic freight invoice data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out freight invoice without processing it twice.

Transaction context

Where 210 Motor Carrier Freight Details and Invoice fits on Coty (via Ryder)

On Coty (via Ryder), the X12 210 Motor Carrier Freight Details and Invoice can follow the 204 Motor Carrier Load Tender, 990 Response To A Load Tender and 214 Transportation Carrier Shipment Status Message in an example Logistics cycle. Confirm the required sequence for your trading agreement.

Ryder channels
13 of 21

13 of Ryder's 21 channels list 210

Trading partners
113

partner references list 210

Channels
176

channel entries list 210

The directory associates Ryder and 210 with 21 channels.

Document structure

X12 210 Motor Carrier Freight Details and Invoice at the element level

The X12 210 reference contains 74 segment entries and 504 data elements; 91 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
74
Data elements
504
Mandatory elements
91
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
B3 14 5
C2 7 3
C3 4 1
N9 6 1
R3 2 2
K1 2 1
N1 6 1
N2 2 1
N3 2 1
N7 24 1
M7 5 1
Key identifiers in 210
  • Invoice Number
  • Shipment Method of Payment
  • Date
  • Net Amount Due
  • Standard Carrier Alpha Code
  • Bank Client Code
  • Identification Code Qualifier
  • Identification Code
Segment reference — 23 segments 4 loops · X12 210 Motor Carrier Freight Details and Invoice
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

B3 Beginning Segment for Carrier's Invoice 9 elements

To transmit basic data relating to the carrier's invoice

C2 Bank ID 3 elements

To specify data required for electronic payment

C3 Currency 4 elements

To specify the currency being used in the transaction set

N9 Reference Identification 3 elements

To transmit identifying information as specified by the Reference Identification Qualifier

G62 Date/Time 2 elements

To specify pertinent dates and times

R3 Route Information - Motor 5 elements

To specify carrier and routing sequences and details

N1 Loop Repeat: 10
N1 Name 4 elements

To identify a party by type of organization, name, and code

N3 Address Information 2 elements

To specify the location of the named party

N4 Geographic Location 4 elements

To specify the geographic place of the named party

N7 Loop Repeat: 10
N7 Equipment Details 7 elements

To identify the equipment

S5 Loop Repeat: 999
S5 Stop Off Details 4 elements

To specify stop-off detail reference numbers and stop reason

LX Loop Repeat: 9,999
LX Assigned Number 1 element

To reference a line number in a transaction set

POD Proof of Delivery 3 elements

To provide proof of delivery

L5 Description, Marks and Numbers 2 elements

To specify the line item in terms of description, quantity, packaging, and marks and numbers

L0 Line Item - Quantity and Weight 7 elements

To specify quantity, weight, volume, and type of service for a line item including applicable \"quantity/rate-as\" data

L3 Total Weight and Charges 7 elements

To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

L1 Rate and Charges 8 elements

To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements

L4 Measurement 4 elements

To describe physical dimensions and quantities

L7 Tariff Reference 1 element

To reference details of the tariff used to arrive at applicable rates or charge

Related references

Other transactions in Coty (via Ryder)

Other EDI documents listed on this channel.

Coty (via Ryder) EDI 210 questions

Common questions about 210 Motor Carrier Freight Details and Invoice on the Coty (via Ryder) channel.

What is X12 210 Motor Carrier Freight Details and Invoice used for?

210 is used when transport charges are ready for audit. It carries information for the freight invoice. Match it to your business system using carrier invoice, shipment reference and charge line.

Is 210 required for Coty (via Ryder)?

210 is listed for Coty (via Ryder). Confirm the required version and direction for your business unit and account with the partner.

What should I map for X12 210?

Start with carrier invoice, shipment reference and charge line and the target freight invoice. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 210 error handling?

Separate line-haul, fuel and accessorial charges before comparing the invoice with the agreed rate. Test a second invoice for the same shipment and distinguish a revision from a duplicate. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 210 relate to other EDI messages?

X12 204 Motor Carrier Load Tender; X12 214 Transportation Carrier Shipment Status Message are related documents also listed on Coty (via Ryder). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 210 and 204?

210 is used when transport charges are ready for audit. 204 is used when a shipper offers a load to a carrier. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect Ryder EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.