Introduction
Meridia Verify provides a direct integration with the EU Information System (EU IS), allowing users to submit and manage Due Diligence Statements (DDS) directly from the Verify Portal.
The integration has now been updated to support EU IS API V3, following the European Commission's transition away from the previous API version.
With this integration, users can link datasets to Shipments, submit DDS directly to EU IS, track submission status, and manage submitted DDS without the need for a manual export and import process.
Terminology update: What was previously referred to as a Parcel in Meridia Verify is now called a Shipment.
Why is this important?
This feature is critical as it not only addresses the EUDR traceability pillar but also resolves a major gap in the compliance workflow.
While customers can already generate EUDR-compliant Due Diligence Statements (DDS), the lack of direct integration with the EU Information System (EU IS) makes the process manual, time-consuming, and error-prone—introducing inefficiencies and increasing the risk of non-compliance.
By enabling direct DDS submission to the EU IS, our solution evolves into a true end-to-end compliance platform. This reduces administrative burden, strengthens regulatory adherence, and enhances our competitive advantage by positioning us as a comprehensive and reliable partner for EUDR compliance.
Key benefits of this feature include:
Associating physical Shipments with datasets, enabling clear and auditable traceability.
Tamper-proof data vault ensuring records cannot be modified or deleted.
Ability to generate or upload DDS for each linked Shipment.
Creation of permanent, auditable records that combine Shipment, dataset, and DDS in one secure location.
Greater customer confidence, with reliable, transparent, and compliant supply chain data.
In this tutorial, we’ll walk through the improved workflow, from creating and linking datasets to submitting DDS directly to the EU IS system.
How to upload EU IS-ready datasets
Below are how you can maximise the newly-improved features, with screenshots inserted at each relevant step to guide you through the process visually.
Step 1: Configuring EU IS credentials for the Verify portal
To enable uploads from the Verify portal to the EU IS, the client’s EUDR API credentials must be shared with the Customer Success team. The required credentials are:
EUDR username: the email address used to log in to the EU IS.
EUDR password: the password associated with this email.
EUDR environment: the EU IS provides two environments, Production and Acceptance; the correct environment must be specified when configuring the setup.
WebServiceClientId: required for submissions to the Production environment.
Where to find your WebServiceClientId
For Production submissions, EU IS requires a WebServiceClientId.
You can find your WebServiceClientId directly in the EU Information System:
Log in to the EU Information System.
Open your Profile.
Find the Web Services Access section.
Locate your Web Services client.
Copy the client identifier displayed next to it.
The WebServiceClientId is required for Production submissions. If it has not been configured, submission to the Production environment will be blocked.
The Acceptance environment is unaffected and continues to work as before.
If you are setting up a Production configuration for the first time, please contact the Meridia team so we can support the initial setup.
Step 2: Submitting to EU IS
Once a Shipment has been created and all the mandatory fields have been completed, the status will automatically change to Submission Ready, indicating that it is ready to proceed.
See “Parcels: Understanding the Parcels” for instructions on creating a parcel
You can now submit directly to EU IS without the old export–import routine.
Open a Submission Ready parcel.
Click the Submit DDS button to send it directly to EU IS — no file export/import needed.
Once submitted, the system records the submission date and confirms EU IS has received it.
Along with this, you’ll see an EU IS reference number and the original submission date. This makes it easy to track what’s been sent and when.
The status of the Parcel will change to DDS available.
You can also check the Parcel ID and reference number to confirm that the EU IS has received your data with the geodata and that it was successfully submitted, eliminating the uncertainty of manual uploads.
Submission size limit
EU IS enforces a maximum size of 25 MB per submission. Very large Shipments may therefore need to be split into multiple submissions.
Meridia Verify now checks the submission size before sending it to EU IS. If a submission exceeds the 25 MB limit, you will receive a clear message before it is sent, rather than an unreadable error from EU IS.
The payload sent by Meridia Verify has also been significantly reduced in size, meaning fewer submissions are expected to reach this limit.
Step 3: Tracking and managing submissions
It is important to note that you have 72 hours to amend or retract a submission:
Amend: Update the parcel or dataset and send the changes to EU IS.
Retract: Cancel the submission entirely.
After 72 hours have passed, a message will appear stating that the dataset can no longer be amended or retracted.
Additional features
Handling submission errors
Sometimes EU IS may reject a submission, usually due to data issues such as invalid polygon shapes. In these cases, the status changes to Submission Error.
Opening the shipment will display the exact error message returned from EU IS, allowing you to identify the issue quickly.
The message is straightforward: correct the dataset (for example, repair invalid shapes), re-link it, and resubmit. This targeted feedback prevents guesswork and avoids unnecessary repetition.
Optional: Manual DDS PDF generation
The manual DDS PDF generation is still available. The process is unchanged — generate, save, and use the file as needed. This ensures that teams can transition at their own pace without losing established methods.
End result
By following this updated process, you can link datasets more quickly and with fewer errors. The merged table layout means you no longer have to juggle between separate pages, while the EU IS integration removes the need for manual file handling.
Even more importantly, the system now supports quick corrections, whether that’s updating a submission within the 72-hour window or responding to a EU IS error message with precise edits. This agility translates to fewer delays and greater confidence that your data is correct and compliant.
For busy teams, the result is less administrative overhead and a much smoother compliance workflow, allowing more focus on strategic and operational priorities.
With the EU IS integration now running on API V3, the same workflow can continue as the European Commission phases out the previous API version.
⚠️ Note:
A WebServiceClientId is required for Production EU IS submissions.
The Acceptance environment continues to work as before.
EU IS enforces a maximum size of 25 MB per submission; very large Shipments may need to be split.
Ensure datasets meet compliance criteria before linking to avoid EU IS rejections.
Remember the 72-hour window for amendments or withdrawals after EU IS acceptance.
Keep an eye on the new critical farm plots indicator when assessing dataset suitability.
Even with automation, occasional manual checks are wise to ensure data accuracy.
The manual PDF export remains available if your process requires offline documentation.
Summary
This update is a real step forward in simplifying Shipment management and DDS submissions. By cutting out unnecessary clicks, merging views, and integrating directly with EU IS, it removes the friction that slowed down the old process.
The EU IS integration is now running on API V3. For Production submissions, a WebServiceClientId must be configured, while EU IS enforces a maximum submission size of 25 MB. Meridia Verify checks these requirements as part of the submission workflow to help identify issues before data is sent.
Whether you’re an experienced user or just starting with these tools, the improved workflow means you can focus less on the mechanics of submission and more on the quality of your data.