X12 133 — Vehicle Application Acceptance

The manufacturer confirms to the dealer that the vehicle allocation request is accepted: assigned VIN, production date, delivery lane.

Purpose

Reply to an allocation request from a dealer or fleet customer. Includes the assigned VIN (generated manufacturer-side after production scheduling), the expected production date, source plant, and transport lane. Starts the 120 → 121 → 129 shipping cycle.

Envelope structure

The 133 travels inside the three X12 envelope levels (ISA/IEA, GS/GE with functional group VA, and ST/SE). Didactic example in 004010:

ISA*00*          *00*          *ZZ*ACMEAUTOMFR   *ZZ*DEALER01      *260516*1530*U*00401*000000133*0*P*>~
GS*VA*ACMEAUTOMFR*DEALER01*20260516*1530*1*X*004010~
ST*133*0001~
B2A*VA*20260516*ACC-001~
N9*AP*REQ-2026-447~
SC*AC*ACCEPTED~
N9*VIN*1HGBH41JXMN109200~
DTM*064*20260601~
SE*6*0001~
GE*1*1~
IEA*1*000000133~

Common segments

• Header — ST, B2A.
• Application reference — N9*AP referenced application.
• Decision — SC*AC Accept.
• VIN assigned — N9*VIN.
• Production — DTM*064 production date.
• Summary — SE.

Common pitfalls

• No application reference: the dealer does not know which request the acceptance is for.
• VIN without plant code: positions 11-17 of the VIN encode the plant — verify consistency with the production plant.
• Past production date: anomaly — use a separate service event instead.

Related transactions

• 120
• 132
• X12 — Hub

Documentation

The 133 code and the Vehicle Application Acceptance name are public and listed at x12.org/products/transaction-sets. The full loops/qualifiers/code-lists structure is distributed by DISA via proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.