--- title: "EDI 928 Automotive Inspection Detail | X12 | Stacksync" description: "EDI 928 is the X12 Automotive Inspection Detail, used when vehicle condition is inspected. See key segments (BIX, TI, VC) and mapping checks." canonical: https://www.stacksync.com/edi/x12/928-automotive-inspection-detail last_modified: 2026-09-29 --- X12 transaction code # EDI 928 Automotive Inspection Detail (X12 928) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md EDI 928 is the X12 Automotive Inspection Detail transaction set, used when vehicle condition is inspected. It carries the data for the vehicle inspection result, matched on vehicle identification number, inspection event and damage location. Standard X12 Code 928 Partner references 1 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 928 at a glance What the 928 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 928 Automotive Inspection Detail summary** | | | | --- | --- | | Document | X12 928 Automotive Inspection Detail | | Business record | Vehicle inspection result | | When it is sent | When vehicle condition is inspected. | | Match on | Vehicle identification number, inspection event and damage location | | Partner references | 1 trading partner in this directory | | Related documents | [X12 120 Vehicle Shipping Order](https://www.stacksync.com/edi/x12/120-vehicle-shipping-order) | ### Key segments in an EDI 928 The business segments in the one partner document reference listed below. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send. | Segment | Name | Purpose | Partner references | | --- | --- | --- | --- | | BIX | Beginning Segment for Automotive Inspection | To transmit identifying numbers, dates, and other basic data relating to the transaction set. | 1 of 1 | | TI | Transport Information | To identify origin and destination carriers, equipment carrying shipment, date shipped, seal status, and equipment type. | 1 of 1 | | VC | Motor Vehicle Control | To define motor vehicle identification and logistics. | 1 of 1 | | ID | Inspection Detail Segment | To report the inspection results on automotive vehicles. | 1 of 1 | Stacksync connects EDI documents such as the X12 928 to your ERP, CRM and databases with two-way sync. Read the [EDI overview](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/book-a-demo) to walk through your partner guide. Implementation guide ## X12 928 mapping and validation X12 928 Automotive Inspection Detail is used when vehicle condition is inspected. Preserve vehicle identification number, inspection event and damage location so the vehicle inspection result in your business system stays connected to the original document. Use the version and implementation guide agreed with your trading partner to confirm required fields and responses. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **vehicle inspection result** vehicle identification number, inspection event and damage location | Define which combination of vehicle identification number, inspection event and damage location identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the vehicle inspection result** ID assigned by the receiving system and processing result | Retain damage observations from separate inspections of the same vehicle. Test an unknown damage code and hold it for interpretation instead of dropping the observation. | | Check the processing result | **Processing status for the vehicle inspection result** Original document reference and matching response | Reconcile the vehicle inspection result with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### 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. - [X12 120 Vehicle Shipping Order](https://www.stacksync.com/edi/x12/120-vehicle-shipping-order) **vehicle movement order:** a vehicle is ready to be assigned for transport or service. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when vehicle condition is inspected. Name the operational owner of the vehicle inspection result and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map vehicle identification number, inspection event and damage location. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner 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 vehicle inspection result 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 vehicle inspection result processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 928 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic vehicle inspection result 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 vehicle inspection result without processing it twice. ### Related documents and resources - [X12 120 Vehicle Shipping Order](https://www.stacksync.com/edi/x12/120-vehicle-shipping-order) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) Document structure ## X12 928 Automotive Inspection Detail at the element level The X12 928 reference contains 9 segment entries and 43 data elements; 35 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 9 Data elements 43 Mandatory elements 35 **Segments with elements marked mandatory in this reference** | Segment | Elements | Mandatory | | --- | --- | --- | | BIX | 6 | 4 | | VC | 4 | 1 | | ID | 3 | 3 | Key identifiers in 928 - 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 ## Find your trading partner for X12 928 1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context. - [Rivian Automotive, Inc](https://www.stacksync.com/edi/rivian-automotive-inc) [Rivian Automotive, Inc](https://www.stacksync.com/edi/rivian-automotive-inc/rivian-automotive-inc/x12-928-automotive-inspection-detail) Catalog breakdown ## Where X12 928 Automotive Inspection Detail appears in this catalog The largest groups of classified 928 catalog entries are in automotive. ### By industry - automotive 1 channel Partner entries with the most listed channels - [Rivian Automotive, Inc](https://www.stacksync.com/edi/rivian-automotive-inc) FAQ ## EDI 928 questions ### What is an EDI 928? EDI 928 is the X12 Automotive Inspection Detail transaction set. Trading partners use it when vehicle condition is inspected. It carries the data for the vehicle inspection result, and your system matches it on vehicle identification number, inspection event and damage location. ### What are the key segments in an EDI 928? The one partner document reference listed here includes BIX (Beginning Segment for Automotive Inspection), TI (Transport Information), VC (Motor Vehicle Control), ID (Inspection Detail Segment). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 928 and EDI 120? The 928 carries the vehicle inspection result and is used when vehicle condition is inspected. The 120 carries the vehicle movement order and is used when a vehicle is ready to be assigned for transport or service. ### What should I map for X12 928? Start with vehicle identification number, inspection event and damage location and the target vehicle inspection result. 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 928 error handling? Retain damage observations from separate inspections of the same vehicle. Test an unknown damage code and hold it for interpretation instead of dropping the observation. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 928? The directory on this page links 1 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires. ### How does 928 relate to other EDI messages? X12 120 Vehicle Shipping Order is a related document linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete. ## Connect 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. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)