Platform capabilities
What eCoC EU can handle for your team
Use this page to see which parts of the eCoC workflow can be handled through the platform, from access models and XML signing to EUCARIS, UK VCA delivery, VECTO import, ERP/API work, and optional service support.
26
capabilities mapped
3
commercial access models
2
authority routes
Capability table
A clear view of available capabilities
Every customer setup is a little different, so the final scope is reviewed around access model, vehicle volume, signing route, and implementation depth.
Access models
Choose the way of working that fits your rollout and expected volume.
XML delivery
Handle XML generation, signing, and EUCARIS/NAP or UK VCA transfer without separating the process.
Trust layer
Use an eIDAS-aligned eQSeal where qualified signing is part of the workflow.
Integration services
Connect VECTO, ERP/API needs, automation work, and optional service support.
| Platform feature | Licenses | What the feature does |
|---|---|---|
| AccessAnnual platform access | Annual platform license | Yearly access works best for teams that expect regular eCoC activity throughout the year. It keeps the platform available for day-to-day operations within the agreed scope. |
| AccessMonthly platform access | Monthly platform license | Monthly access gives teams a lighter way to start using the platform. It is useful when the operating model is still being tested or volumes are expected to change. |
| AccessPay-as-you-go platform access | Per XML generation | Pay-as-you-go access fits occasional or lower-volume XML work. Each XML generation event can be handled through the same controlled platform workflow. |
| XML & submissionIVI-compliant XML generation, signing, and submission | Per vehicle | The platform can prepare, sign, and deliver IVI-compliant XML files for EUCARIS and UK VCA workflows. This is usually scoped around vehicle-level production and release activity. |
| User managementUser accounts | Included with monthly and annual licenses | Manufacturer teams can give the right people access to the platform. Account capacity is reviewed with the customer during scope definition. |
| Document outputXLSX and PDF output generation | Included with monthly and annual licenses | Users can create XLSX and PDF outputs from generated eCoC records. These files help with internal review, archiving, and document-style handoffs. |
| Document outputCustom XLSX and PDF layouts | Available with monthly and annual licenses | Custom layouts help when the standard output does not match a manufacturer's preferred document style. They are useful for teams that still need paper-oriented CoC outputs from structured data. |
| ImportDOCX, XLSX, and PDF import module | Included with monthly, annual, and pay-as-you-go licenses | Existing DOCX, XLSX, or PDF CoC material can be used as a starting point for template creation. This helps reduce repetitive setup work when legacy documents already exist. |
| SupportTechnical support | Included with monthly, annual, and pay-as-you-go licenses | Users can reach the support team through the platform support panel. Requests are easier to follow because they are handled as trackable tickets. |
| SupportAdministrative and technical homologation guidance | Included with monthly, annual, and pay-as-you-go licenses | Teams can get administrative and technical guidance while preparing eCoC records. This is helpful when footnotes, data meaning, or regulatory references need a second look. |
| XML & submissionSubmission Center | Included with monthly, annual, and pay-as-you-go licenses | The Submission Center keeps submitted eCoC records in one place. Teams can follow delivery progress without chasing status across separate channels. |
| RegistrationCNIT code support for France | Included with monthly, annual, and pay-as-you-go licenses | CNIT information for France can be handled inside the same platform workflow. This keeps country-specific certificate data close to the record it belongs to. |
| RegistrationEUCARIS and UK VCA registration management | Per type approval certificate | We can support EUCARIS/NAP access work and UK VCA account or API onboarding. UK VCA submission is handled outside EUCARIS through the VCA route. |
| Trust layereQSeal qualified electronic seal | Valid for 5 years | The eQSeal is the trust layer used for qualified XML signing workflows. It is arranged through trusted service provider partners and aligned with eIDAS requirements. |
| ImportVECTO import module setup | One-time module setup | Manufacturer-specific VECTO PDF or XML outputs can be mapped into the eCoC creation flow. Parsed values are reviewed by the user before they are applied to controlled records. |
| ImportVECTO structure update | Per source-structure change | When a VECTO source format changes, the existing import mapping can be updated. This keeps the module aligned with the manufacturer's latest source files. |
| Document outputType approval document entry | Per document optional service | The service team can enter type approval documents into the platform when the manufacturer wants help with setup. This is often useful during the first rollout. |
| Document outputeCoC template creation service | Per template optional service | The platform team can prepare eCoC templates on behalf of the manufacturer. This helps teams move faster when they prefer supported setup instead of doing every template internally. |
| ServiceeCoC creation service | Per eCoC optional service | The service team can create eCoC records for customers that do not want to operate the platform directly. This can fit low-volume work or a transition period before internal rollout. |
| IntegrationERP and API data access | Annual access license | API access lets manufacturers transfer generated eCoC data or selected output data into their own systems. It is the access layer, not a full custom automation project by itself. |
| IntegrationFull ERP automation setup | Initial consulting project | Full ERP automation is a larger implementation project for customers that want eCoC creation to start from their ERP environment. Scope discovery and written approval are needed before delivery begins. |
| IntegrationFull ERP automation annual license | Annual license | The annual license keeps the full ERP automation capability available after the initial setup. It is normally paired with the setup project and transaction-based operation. |
| IntegrationFull ERP automation signing and authority submission | Per eCoC, monthly invoiced | This covers signing and authority submission for eCoC records created through the customer's ERP automation flow. EU and UK routes are scoped separately during implementation. |
| XML & submissionXML signing and authority submission setup | Per type approval certificate | Manufacturers that already create their own XML files can use the platform as the signing and delivery layer. This can cover EU NAP/EUCARIS or UK VCA routes, depending on the approval scope. |
| XML & submissionXML signing and authority transfer | Per eCoC | Customer-prepared XML files can be signed and transferred through the relevant authority workflow. This supports teams that already have their own XML generation process. |
| SupportAdditional live platform training | Per session, up to 1 hour | Additional live training is available when documentation is not enough. It can be used for onboarding, new team members, or refresher sessions. |
Scope note: This is a capability view, not a fixed commercial proposal. The final offer should be scoped around the manufacturer entity, vehicle categories, expected volume, XML/signing route, and integration requirements.