🏛️ EU Registry

EU Registry Submission Errors

Updated 2026-04Essential reading

When the EU DPP Registry rejects a passport submission, DPP Cloud shows the rejection reason on the passport detail page. This article covers the most common errors and how to fix them.

⚠️Rejected passports are visible on the public viewer

A rejected submission does not remove the passport from DPP Cloud. The passport remains Active and the GS1 Digital Link QR code still resolves to the public viewer. However, customs authorities checking the registry will see the passport is not registered. Fix and resubmit promptly.

Common rejection reasons

Error	Cause	Fix
OPERATOR_ID_MISSING	No EU Operator ID is configured in DPP Cloud Settings.	Go to Settings → EU Registry Operator ID and add your ID. Then resubmit.
OPERATOR_ID_INVALID	The Operator ID entered in DPP Cloud does not match any registered operator in the Commission's database.	Verify your Operator ID matches exactly what was issued during registration. Check for typos or extra spaces.
GTIN_FORMAT_ERROR	The GTIN on the passport is not a valid 14-digit number.	Edit the passport's GTIN field. It must be exactly 14 digits, no spaces or hyphens.
DUPLICATE_PASSPORT	A passport with the same passport number or GTIN+level combination already exists in the registry.	Check if another passport has already been submitted for this battery. If you are resubmitting after a correction, use the Resubmit function rather than creating a new submission.
REQUIRED_FIELD_MISSING	One or more Annex XIII fields required by the registry are empty.	Open the passport, navigate to the Technical Data section, and complete all required fields. The registry requires a minimum data set beyond what DPP Cloud marks as required.
CATEGORY_MISMATCH	The battery category on the passport does not match the operator's registered product category in the Commission's system.	Verify your operator registration covers the battery category you are submitting. Contact the Commission if your registration needs updating.
SERVICE_PROVIDER_NOT_CERTIFIED	The DPP service provider (DPP Cloud) is not yet certified under the ESPR delegated act.	This error should not appear before the certification scheme takes effect. If it does, contact DPP Cloud support immediately.

How to resubmit

After fixing the issue:

Open the passport detail page

Navigate to the passport that was rejected. The rejection reason is displayed in the EU Registry section.

Fix the underlying issue

Depending on the error, this may mean editing passport data, correcting your Operator ID in Settings, or completing missing fields.

Click Resubmit to EU Registry

The passport will re-enter the Queued → Submitted → Registered flow. If the fix resolved the issue, the passport will reach Registered status.

Errors that require support

If you see SERVICE_PROVIDER_NOT_CERTIFIED or an error code you do not recognise, contact DPP Cloud support. Some registry errors are infrastructure-level issues that cannot be resolved by editing passport data.

ℹ️Mock mode resubmission

In mock submission mode, you can resubmit as many times as needed without consequence. Use this period to test your data and resolve any formatting issues before the registry goes live in July 2026.

Reading Registry Submission Status

Submitting a Passport to the EU Registry

Need more help?

Contact support →

On this page

Share on LinkedIn

Ready to get started?

Request a demo account at dppcloud.co.uk/demo/request

Request demo account

🏛️ EU Registry

Reading Registry Submission Status

Updated 2026-04