Excel → XML
From Excel to XML, with checks at the right stage.
Register, link, update, report: one template and one XML per operation, across 31 scenarios.
ModulesMDR · IVDR · Legacy — EUDAMED data
Upload your file: every issue is reported with its row, its column and the rule that found it. Fix, then download an XML validated against the official schema, ready for bulk upload.
30 days · 50 UDI-DIs · every module · no credit card · account opened immediately
The team completes a readable template; every row remains identifiable during checks.
2 blocking errors · Fix before generation
<device:MDRBasicUDI>
<basicudi:riskClass>IIb</basicudi:riskClass>
<basicudi:identifier>
<commondevice:DICode>04056…0012</commondevice:DICode>
</basicudi:identifier>
<basicudi:MFActorCode>FR-MF-[…]</basicudi:MFActorCode>
</device:MDRBasicUDI>
Check report retained · The XML and findings remain linked to the generation.
Regulatory calendar
The UDI/Devices module has been mandatory since 28 May 2026. For devices placed on the market before that date and still marketed, MDR, IVDR and legacy alike, the grace period ends at the end of November 2026.
Who is affected, with sourcesHow it works
One Excel template per EUDAMED operation, with the expected value lists and a dictionary that explains every column.
The file is analysed before anything is generated. Every issue gives the row, the column, the reason and the rule identifier.
The XML is validated against the official XSD. Beyond 300 entities per message, it is split into batches automatically.
What is checked
An issue with no rule to cite is not a check. Every issue in your report carries the identifier of the rule that detected it, and that identifier is never reassigned: an archived report stays readable years later.
See all 56 checks, namedChecks are applied only when the data or condition requires them.
Each column is checked against its format and expected value list.
Languages, classes, countries, warnings, storage conditions and other lists.
A field that is required “depending on the case” is checked in its real context, row by row.
Packages, SRNs, manufacturers, markets and dependent fields.
The generated XML is validated against the selected XSD schema, whose version is displayed.
The same UDI-DI repeated in the file is flagged as a warning; a repeated Basic UDI-DI, on the other hand, is normal.
A compliance record that can be shared with quality and regulatory teams.
33 of these 56 rules do not come from the initial core: they were born from a conformity audit against the official schema, from internal qualification, or from a client deployment. The library grows with every difficult case.
Both ways
Excel → XML
Register, link, update, report: one template and one XML per operation, across 31 scenarios.
ModulesXML → Excel
Your devices are already registered in EUDAMED? Drop the registry's response here: it becomes an Excel template again, ready to be corrected and resubmitted.
The values come from EUDAMED itself, so non-updatable fields are echoed unchanged — which avoids the “… is not updatable” rejection on update.
Functional coverage
One Excel template, a rule set and an XML file per operation.
Supported XSD version3.0.30EUDAMED playground: XSD 3.0.36.1
Creation and update of UDI-DI / Basic UDI for classic medical devices.
Management of procedure packs and systems.
Creation and update of in vitro diagnostic devices.
Devices under the former MDD / AIMDD / IVDD directives.
Adding market information, packaging or original designer details.
Reporting incidents, corrective actions, safety notices and periodic reports to the authorities.
Generating download requests (certificates, actor profiles, device data).
Commitments
Understand before acting
Dated answers linked to official sources.
Start by identifying your organisation's role. Actor registration comes before user access and, depending on the role, device registration.
An SRN is obtained through an actor registration request. Following review and approval by the competent national authority, EUDAMED generates the Actor ID or SRN.
The manufacturer prepares the dataset for the device type, including UDI identifiers and required information. Data quality and consistency should be checked before submission.
To request actor registration, a non-EU manufacturer needs an active authorised representative and must provide a mandate summary with the request.
Since 28 May 2026, four modules have been mandatory: Actor registration, UDI/Device registration, Notified Bodies & Certificates, and Market Surveillance.
30-day free trial
30 days · 50 UDI-DIs · every module · no credit card · account opened immediately