972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Government and regulatory

EDI 285 Commercial Vehicle Safety and Credentials Information Exchange

The X12 document enforcement officials and authorized parties use to request information on carriers' safety, compliance and credentials.

Sent by
Enforcement official or authorized party
Received by
Government information system
Standard
ANSI ASC X12

What is an EDI 285?

The EDI 285 Commercial Vehicle Safety and Credentials Information Exchange is the ANSI X12 transaction set enforcement officials, government administrators and other authorized parties can use to request information on the safety performance, regulatory compliance and credentials of commercial vehicle carriers, vehicles and drivers.

At weigh stations and roadside checks, officials need to know quickly whether a carrier is authorized, registered and in good safety standing. Electronic queries return that information while the vehicle is stopped, helping officials focus inspections on high-risk carriers.

How the EDI 285 worksDiagram of the EDI 285 Commercial Vehicle Safety and Credentials Information Exchange. Enforcement official or authorized party sends it to government information system. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and detail: the required NX1 loop with NX1 (Property or Entity Identification) and N9 (Extended Reference Information). 1 optional loops are listed by their first segment.How the EDI 285 worksCommercial Vehicle Safety and Credentials Information Exchange: who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 285SENDEREnforcement official orauthorized partyRECEIVERGovernmentinformation system997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code CVGS … GETransaction set 285ST … SEHEADINGBGNBeginning SegmentDETAILRequired loop NX1 · repeats many timesNX1Property or Entity IdentificationN9Extended Reference Information+ 1 optional loop, starting with:LMBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 285. Your trading partner's implementation guide adds its own requirements.
How the EDI 285 worksDiagram of the EDI 285 Commercial Vehicle Safety and Credentials Information Exchange. Enforcement official or authorized party sends it to government information system. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and detail: the required NX1 loop with NX1 (Property or Entity Identification) and N9 (Extended Reference Information). 1 optional loops are listed by their first segment.How the EDI 285 worksCommercial Vehicle Safety and CredentialsInformation Exchange: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 285SENDEREnforcementofficial orauthorized partyRECEIVERGovernmentinformationsystem997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code CV (GS … GE)Transaction set 285 (ST … SE)HEADINGBGNBeginning SegmentDETAILRequired loop NX1 · repeats manytimesNX1Property or EntityIdentificationN9Extended ReferenceInformation+ 1 optional loop, starting with:LMBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 285. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 285, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 285 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Checking a carrier's safety rating at roadside
  • Verifying vehicle registration and credentials
  • Screening vehicles at weigh stations

Where it fits in the document flow

This document 285 Commercial Vehicle Safety and Credentials Information Exchange
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 285 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BGN
  • NX1
  • N9
  • LM
  • LQ
  • NM1
  • TC2
  • N4
  • SE

Practical example

The 285 in practice

A truck arrives at a weigh station. The officer queries the carrier's identifier and the truck's registration, and the system returns the carrier's operating authority, safety record and credential status. Because the carrier's record shows a high violation rate, the officer selects the truck for inspection.

Implementation

Implementation considerations for the 285

  • Restrict access to authorized officials.
  • Return results fast enough for roadside use.
  • Use official carrier and vehicle identifiers.
  • Follow the regulator's current data systems.

How ECOM helps

Automate the 285 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related government and regulatory documents

All 29 government and regulatory documents

Need help with the EDI 285?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us