ICM 3.1 and the Updated XSD: Which eCoC Templates Need Review?
The September 28 release changes axle, mass-context and bodywork checks and adds Euro 6 values. Review templates by vehicle category, manufacturing stage and actual data.
EUCARIS documents dated September 28, 2026 include ICM v3.1, an updated IVI 2.0 XSD and Messagebook V3.0. Existing eCoC templates should be reviewed for axle indicators, the context of in-service axle masses, bodywork tables and emission values.
A document date does not establish when each NAP deployed or began accepting the release. Confirm the receiving NAP's accepted version before submission.
Check three versions
The IVI 2.0 Release documentation section of the official documentation portal provides:
| Document | Verified version | Purpose |
|---|---|---|
| ICM Checking Module | v3.1, September 28, 2026 | Category, completion-stage and cross-field rules |
| Initial Vehicle Information XSD | File dated September 28, 2026 | XML structure, types and enumerations |
| Messagebook Excelformat | V3.0, change entry dated September 28, 2026 | Field meanings, regulatory references and values |
The message format remains IVI 2.0. The ICM version does not change it to “IVI 3.1”.
Four ICM changes to review
The following changes appear in the ICM v3.1 VersionInfo sheet, rows 3 to 6. The detailed rules and XSD supply the exact conditions and element names. Official files
Powered axle indicators
The release summary identifies a mandatory powered-axle check for M, N, T and C categories. The XML element is PoweredAxleIndicator. The current R226 mandatory condition includes StageOfCompletion=C; it also checks that the count of Y indicators matches NumberOfPoweredAxles.
Review axle-level indicators against the vehicle total. Do not create a new element named PoweredAxle or apply a complete-vehicle condition to every stage.
Loadable axles
R232 changes the condition requiring LoadableAxleIndicator=N from an axle count of two or fewer to fewer than two. This corrects an overly restrictive condition. It does not require every two-axle vehicle to use Y; category rules and approval facts still apply.
In-service axle mass needs its context
Under R249, InServiceMaximumPermissibleLadenMassAxle cannot carry a value when both its country and traffic-regulation context fields are empty. At least one applicable context must be supplied, subject to category restrictions.
A mass value copied from an ERP record may therefore be insufficient without its national or regulatory basis.
A parent bodywork table cannot bypass mandatory fields
ICM 3.1 closes a gap that allowed the entire bodywork table to be omitted despite mandatory child-field conditions. R312 sets the applicable parent-table requirement. The exact XML name is BodyworkTable.
Validation should check whether the table must exist before checking fields inside an existing table.
New XSD emission values
Page 3 of the September 28 Release Notes lists four new ExhaustEmissionLevel values: Euro 6 AS, Euro 6 AT, Euro 6 ED and Euro 6 EE. They also appear in the XSD and Messagebook V3.0 change overview. Official release documents
An older schema may reject these new values. Adding values does not invalidate every older record. Choose the emission value from the vehicle's applicable approval evidence; do not change a vehicle's classification merely because an enumeration is available.
A practical template review
- Record the XSD date, ICM and Messagebook versions, and the receiving NAP's accepted release.
- Identify affected templates by category, C/I/V completion stage and propulsion.
- Check the sources for axle facts, bodywork and mass context. Resolve missing evidence before supplying values.
- Exercise boundary cases, including two axles, omitted parent tables, missing mass context and new emission values.
- Confirm the receiving NAP's test and production requirements and retain validation results and receipts.
Multistage manufacturers should also review the September ICM 3.0 changes described in the completion-stage guide.
The official XML validation tool checks XSD and ICM compliance but expressly does not guarantee correctness or acceptance by external systems. Signing, manufacturer onboarding, NAP acceptance, VIN retrieval and registration remain separate checks.
Official sources
- EUCARIS eCoC Documentation:
20260928 -Version 2.0 - IVI Release Notes.pdf, Final, page 3. - On the same page:
IVI 2.0 - ICM Checking Module - v3.1.xlsx,VersionInforows 2 to 6 and rules R226, R232, R249 and R312. - On the same page: the XSD dated 2026-09-28 and
IVI 2.0 - Messagebook Excelformat - V3.0.xlsx. - EUCARIS XML validation: scope and limits of the tool.
Working on eCoC compliance?
Book a free 30-minute consultation and get a tailored roadmap for your business.