How to generate eCoC XML
Learn how to generate eCoC XML and review XSD and ICM validation results.
eCoC.tr · IVI 2.0 XML validation
IVI 2.0 XML validation checks whether an electronic certificate of conformity follows the required structure and whether its vehicle data is consistent. Electronic COC Platform brings validation into the manufacturer's certificate workflow, before signing and NAP submission.
Review our XML validation workflow01
An XSD check tests the XML structure, data types and required elements. Business checks examine relationships between values, such as vehicle category, masses, fuel and approval references. The receiving authority then applies its own checks. A schema-valid file alone is not evidence of authority acceptance.
Learn how to generate eCoC XML and review XSD and ICM validation results.
The recorded interface is in English.
02
Start with one VIN, its approved type, variant and version, and the production values used for its CoC. Use the schema version required by the selected submission channel. Resolve errors in the source record or template so that the next vehicle does not inherit the same mistake.
03
Retain the validation result with the vehicle record and the XML version it describes. After correcting a value, validate again before signing. If a signed file changes, repeat the signing step. Record the receiving system's response separately from the internal validation result.
Technical references and channel requirements should be checked against the current official versions.
Updated: 30 September 2026
No. XSD validation checks the XML schema. The IVI Checking Module checks additional vehicle-data rules. Keep these results separate and review the receiving NAP's response.
Yes. Request a workflow demonstration using a representative vehicle category and a redacted sample. Agree the schema version and the expected checks before the demonstration.
No. Signing, manufacturer access, channel requirements and the receiving authority's checks still apply.
Contact
Tell us what you are trying to solve in one short message. Share your name and email; our team will respond directly with the right next step.
Use the form here or open the full contact page for more context.
Open full contact page