To start and identify an interchange of zero or more functional groups and interchange-related control segments
Newell X12 210 Motor Carrier Freight Details and Invoice
Plan X12 210 Motor Carrier Freight Details and Invoice for Newell via Ryder - LOGCRPNWLD. 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
Newell via Ryder - LOGCRPNWLD: 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 Newell via Ryder - LOGCRPNWLD. Confirm the version, required fields and responses that apply to your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | freight invoice carrier invoice, shipment reference and charge line |
|
| Update the receiving system | Processing the freight invoice ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the freight invoice Original document reference and matching response |
|
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.
Implementation steps
-
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.
-
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 Newell guide. Preserve the source reference alongside any new destination identifier.
-
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.
-
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 Newell via Ryder - LOGCRPNWLD
- Newell channels
- 2 of 2
2 of Newell's 2 channels list 210
- Trading partners
- 113
partner references list 210
- Channels
- 176
channel entries list 210
Frequently listed alongside 210
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
| 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
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To transmit basic data relating to the carrier's invoice
To specify data required for electronic payment
To specify the currency being used in the transaction set
To transmit identifying information as specified by the Reference Identification Qualifier
To specify pertinent dates and times
To specify carrier and routing sequences and details
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
N7 Loop Repeat: 10
To identify the equipment
S5 Loop Repeat: 999
To specify stop-off detail reference numbers and stop reason
LX Loop Repeat: 9,999
To reference a line number in a transaction set
To provide proof of delivery
To specify the line item in terms of description, quantity, packaging, and marks and numbers
To specify quantity, weight, volume, and type of service for a line item including applicable \"quantity/rate-as\" data
To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements
To describe physical dimensions and quantities
To reference details of the tariff used to arrive at applicable rates or charge
Related references
210 Motor Carrier Freight Details and Invoice on other Newell channels
Compare the listed channel references and confirm their current implementation guides.
Newell via Ryder - LOGCRPNWLD EDI 210 questions
Common questions about 210 Motor Carrier Freight Details and Invoice on the Newell via Ryder - LOGCRPNWLD 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 Newell via Ryder - LOGCRPNWLD?
210 is listed for Newell via Ryder - LOGCRPNWLD. 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?
Keep 210 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the freight invoice workflow; confirm any required companion messages with your partner.
Connect Newell 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.
