# Receive EU E-evidence Orders at Your Own Endpoint | Kodex

Source: https://www.kodexglobal.com/regulations/eu-e-evidence

> Kodex operates the endpoint EU E-evidence orders arrive at. Orders land in the queue your team already runs, with every deadline tracked, including where a member state’s system is not operational.

EU E-evidence · Regulation (EU) 2023/1543

## Your own endpoint on Kodex

The regulation has applied since August 18, 2026. In-scope cross-border orders run on clocks as short as 8 hours, and most member-state systems are not yet operational. Receive orders at your own Kodex endpoint, in the process you already run.

Request a demo

Photo pending
Kodex brand photo to come.

The risk

### A government portal is a system you don’t control
Request a demo

01

#### Outside your workflow
A new system to log into and monitor, apart from the tools your team already runs.

02

#### Easy to miss an order
A binding order can sit in a portal nobody’s watching until its deadline passes.

03

#### On a tight clock
10 days to produce. 8 hours in an emergency.

How Kodex helps

### We’re already live across Europe

#### Orders reach you inside the process you already run

EU E-evidence orders land in the same Kodex queue as the requests your team handles now. There is no separate portal to watch.

01

#### One queue

EU E-evidence orders land with every other request. No new tool.

01A receiving endpoint registered to your designated establishment

02The same queue as the requests your team handles now

03No separate portal to watch

#### Every deadline is tracked

Kodex tracks the clock on every order, flags emergencies, and escalates over email, Slack, and PagerDuty as a window closes.

02

#### Deadlines tracked

Kodex watches every clock, with alerts by email, Slack, and PagerDuty.

01Production orders: 10 days

02Emergencies: 8 hours

03Preservation orders: up to 60 days

#### The whole lifecycle is covered

Production orders, preservation orders, deadline updates, grounds for refusal, withdrawals, extensions, and correspondence, all on one record.

03

#### One record

Orders are addressed to you, certificates are issued in your name, and every decision on every order stays with you.

01Production and preservation orders

02Deadline updates, extensions and withdrawals

03Grounds for refusal and correspondence

#### It works where the government system does not

API integration where a state’s system is live, and an Article 19(5) path where it is not. Evidence over 25MB cannot move through the government system at all; that path is permanent.

04

#### Two intake paths

Direct API where states are ready. An Article 19(5) path where they are not.

01API integration where a state’s system is live

02An Article 19(5) path where it is not

03Evidence over 25MB

FAQ

### Frequently asked questions

Can we just use the government portal?

Yes. It is a working option. The cost is operational: it is one more system to log into and monitor, outside your existing workflow, and the deadlines run whether or not anyone is watching it. Companies with steady request volume usually decide the portal is the riskier path.

Can we build our own intake instead?

Yes, and the regulation allows it. You would be building intake, routing, and deadline tracking from scratch while orders are already flowing. Kodex already runs across Europe, so the practical question is whether building buys you anything that adopting does not.

Our member state’s portal isn’t ready. Does that delay anything?

No. Your obligations started on August 18 regardless. Where a state’s system is not available, Article 19(5) of the Regulation requires transmission by the most appropriate alternative means, and the Commission’s contingency guidance lists secure provider platforms among them. The issuing authority selects the channel. What you control is having an endpoint to nominate when asked, as Germany’s BKA has already asked providers to do.
