Organisation validation & the QSeal question
The EU DPP registry went live on 20 July 2026. For many operators the first practical blocker is not the 71 data points but the identity gate in front of them: organisation validation. Under the current validation flow, legal persons need an eIDAS qualified electronic seal (QSeal) before validating — a regular e-signature or scan-based signature does not qualify.
Confirm the registering entity first
Validation attaches to whoever registers. If your Chinese manufacturer is only the data supplier and your EU entity or importer is the first placer, you — not your supplier — need validation. Run the triage before buying any seal.
1. What the registry does and who must register
- Implementing Regulation (EU) 2026/1778 (published 16 July 2026) sets the rules: operator registration → identity/organisation validation → passport registration → unique registration identifier;
- Registration follows the passport: battery passports become mandatory on 18 Feb 2027, and the unique identifier must be uploaded at passport creation (Art 77(10) of Regulation 2023/1542);
- Customs and market-surveillance authorities are connected to the registry and verify at the border.
2. Why a QSeal, and what it takes
- Who issues: qualified trust service providers (QTSPs) listed on the EU Trusted List (eIDAS);
- Who can apply: legal entities, including non-EU companies, via QTSPs and their local partner channels; expect corporate registration documents and authorisation checks on the representative;
- Lead time: weeks — entity verification plus issuance; slower in request-peak seasons;
- Alternatives: Implementing Regulation (EU) 2026/1778 Art 4 also lists other electronic-attribute routes; always check the current User Guide before purchasing.
| Registering entity | Validation route | QSeal needed now? |
|---|---|---|
| Our legal entity (we first place / we are mandated) | QSeal → organisation validation | Yes (or an Art 4 alternative route) |
| Our EU buyer (common supplier case) | Handled on the buyer’s side | Not yet — get the duty split in writing |
| Natural person / sole trader | Legal-person QSeal route does not directly apply | Follow the current user guide |
| Entity not decided | — | Don’t buy |
3. Five questions before you buy a seal
- Are you on the EU Trusted List as a QTSP, and is the product a qualified organisational seal (not a personal qualified signature)?
- For a non-EU parent / Chinese subsidiary: document checklist and lead time in working days, plus remote video verification options;
- Certificate validity, renewal and replacement pricing;
- Technical support for registry integration (container format, invocation) — who answers when it fails;
- If organisation validation is rejected, what does your assistance process and pricing look like?
4. Prepare these documents once
- Company registration extract (certified translation where applicable) and registration number;
- ID and contact details of the legal representative / authorised user;
- Exact legal name and address spelling in Latin characters — it must match registry entries;
- Power of attorney if a service provider applies on your behalf;
- A corporate-domain contact mailbox for the registration.
5. Common rejection reasons
- Mismatch between translated company names and registry entries;
- Stale or inconsistent representative identity documents;
- Wrong certificate type (personal signature instead of an organisational seal);
- Legal-person data in the registry not matching the seal payload;
- Seals bought from non-QTSP “e-signature” vendors.
Disclaimer
Compiled from public information verified 2026-10-23; the validation flow is still evolving (user guide at v1.03). Always follow the current official User Guide and the EU Trusted List. Not legal advice.