X12 transaction code
X12 928 Automotive Inspection Detail
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 928
- Trading partners
- 1
Specification summary
X12 928 Automotive Inspection Detail at the element level
The X12 928 specification defines 9 segments carrying 43 data elements, 35 of which are mandatory.
- Segments
- 9
- Data elements
- 43
- Mandatory elements
- 35
| Segment | Elements | Mandatory |
|---|---|---|
| BIX | 6 | 4 |
| VC | 4 | 1 |
| ID | 3 | 3 |
- Transaction Set Purpose Code
- Standard Carrier Alpha Code
- Date
- Inspection Location Type Code
- Vehicle Identification Number
- Damage Area Code
- Damage Type Code
- Damage Severity Code
Trading partners that support X12 928
1 partner, 1 channel. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 928 Automotive Inspection Detail
928 is used most heavily in automotive.
The 928 reports motor vehicle inspection results among parties in the finished-vehicle supply chain. One transaction can cover multiple vehicles: the BIX beginning segment carries identifying numbers and dates, an optional TI segment identifies origin and destination carriers, equipment, and seal status, and each VC loop identifies a vehicle with up to 99 ID inspection detail segments. Interested parties use it to record vehicle condition at inspection points as vehicles move between manufacturers and carriers. An automotive manufacturer, inspection agency, or carrier sends the 928 to other interested parties in the finished-vehicle distribution chain. A vehicle inspection is completed at a point in the distribution chain, such as a carrier handoff, and the results must be reported electronically to the manufacturer, carrier, or other interested parties.
By industry
- automotive 1 channel
FAQ
X12 928 questions
What is X12 928 Automotive Inspection Detail?
X12 928 (Automotive Inspection Detail) is an EDI transaction set defined by ANSI ASC X12 for exchanging automotive inspection detail between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 1 Stacksync trading partner supports this code across 1 channel.
Which trading partners use X12 928?
1 Stacksync partner accepts X12 928: Rivian Automotive, Inc. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 928 with my ERP?
Stacksync handles the full X12 928 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
