Cross-border service of documents: costs drivers
Cost in cross-border service of documents is driven by four things: how many jurisdictions the recipient touches, whether a verified address exists, whether the receiving state requires a certified translation, and whether the recipient cooperates or has to be traced. Each factor adds time before the response period even starts running.
In a patent dispute the stakes are higher than in ordinary correspondence. A claim, an opposition, or a request for provisional measures only has effect once it has actually reached the other side in a form the receiving state recognises. Getting that step wrong does not just cost money — it can reset the clock on the whole dispute.
What drives the cost
The single biggest driver is the number of jurisdictions involved. A defendant with one registered office in one country is a different job from a group with entities in three. Each additional jurisdiction adds its own channel, its own language requirement, and its own timeline.
The second driver is the method chosen. Service through a central authority is slower but harder to challenge later. A private process server or a commercial courier is faster where the receiving state allows it, but the proof of service has to be built more carefully to survive a later objection.
| Factor | Effect on cost and timing |
|---|---|
| Number of jurisdictions touched | Each one adds a separate channel, language and deadline to track |
| Method of service | Faster private channels need a stronger proof-of-service file; slower official channels need less |
| Availability of a verified address | An unverified address forces a tracing step before service can even start |
| Translation requirement | A certified translation adds a fixed step that cannot be compressed by urgency alone |
| Recipient's conduct | Evasion or refusal to accept moves the file into substituted or public service, which takes longer |
None of these factors is fixed in advance. A file that looks simple at filing can turn complex the moment the recipient's address turns out to be outdated, which is why the tracing step is worth doing properly the first time.
What changes once the clock starts
Service is not a formality that happens quietly in the background. From the date the court or authority treats service as effective, a response period starts running, and everything downstream depends on that date being correct.
If service is later found defective, the response period restarts, and any deadline calculated from the wrong date becomes unenforceable. This is the practical risk that makes cross-border service worth planning rather than rushing: a shortcut that saves a week at the outset can cost a month later if it is challenged.
Steps to take
- Confirm the correct entity and address before anything is filed — the case team traces the registered office rather than relying on the address used in prior correspondence.
- Choose the service channel that fits the receiving state — the instructing lawyer decides between a central authority, a private server, or post, based on what that jurisdiction accepts.
- Commission a certified translation of the documents into the language the receiving state requires — a certified translator handles this in parallel with filing, not after it.
- File the request with the sending authority or court, together with proof of the correct address — the filing lawyer keeps a copy of everything submitted.
- Track acknowledgment and calculate the response deadline from the date of effective service, not the date of dispatch — the case team logs both dates separately.
- Escalate to substituted service or public notice if the recipient cannot be traced or refuses acceptance — this step needs the court's authorisation, not a unilateral decision.
Where a file spans several registries and several service channels at once, the same case team usually carries the whole sequence through. Working with this team in detail sets out how that coordination is structured.
Who decides and how long it takes
The court seized of the main proceedings decides whether service was effective and from what date the response period runs. That decision is not automatic — it follows from the proof of service submitted with the file.
Where a central authority carries out service, that authority certifies the date. Where a private server is used instead, an affidavit of service performs the same function, and the court checks it before accepting the file as properly served.
Timing depends heavily on the channel and the receiving state. Service within a network built for judicial cooperation between EU states tends to move in a matter of weeks. Service into a state outside that network, or through consular channels, routinely takes several months, and delays compound if the first attempt fails.
If your situation differs
A comparable issue appears when a corporate group has moved the operational team without moving the underlying entity — When a group restructuring moves the team, not the rights themselves, the entity you served last year may no longer be the one that holds the patent today.
If the dispute also touches tokenised or on-chain rights, tracing the correct party to serve follows a similar logic to Chain of title reconstruction on-chain step by step explained: the record of who holds a right today does not always match the name on the original registration.
If the other side has already filed an opposition instead of waiting to be served, the sequence changes again — service still has to happen, but the deadlines run alongside the opposition rather than instead of it.
What this page does not cover
This page describes the service mechanism, not the underlying dispute. It does not establish who currently controls the counterparty abroad, or whether the address on file is still accurate — that check sits outside legal procedure and belongs to a factual verification step, ideally done before service is attempted rather than after it fails.
For a counterparty incorporated in Malta, that check follows its own pattern — see Counterparty in Malta in practice for what can be established before the first document goes out.
Related reading
Cross-border service usually appears alongside another procedural fork, not on its own. Opposition before the granting office step by step covers what happens when the other side challenges the patent instead of waiting to be served.
Verified
Verified as at 6 March 2025. This page describes the general mechanism of cross-border service as it applies in practice across the jurisdictions we work in. It does not cite a single named instrument, because the applicable channel and timeline depend on the receiving state and on whether the parties fall inside or outside a judicial cooperation network. Primary sources are the courts and central authorities of the jurisdictions involved, checked at each stage of a live file rather than quoted from a fixed text.
Frequently asked questions
How long does cross-border service of documents take in practice?
It depends on the channel and the receiving state. Service within a network built for cooperation between EU states usually takes weeks. Service outside that network, especially through consular channels, usually takes months, and a failed first attempt adds further delay.
Which documents are needed to start?
At minimum: the claim or pleading to be served, a certified translation where the receiving state requires one, proof of the recipient's correct address, and the request form used by the sending authority or court. Missing any one of these delays the file.
What happens if the other side does not respond?
A default outcome is possible, but the court checks that service was properly carried out before granting one. If service is later found defective, the default is exposed to challenge, and the response period restarts from the corrected date.
Getting service wrong rarely stops at a delay. What it costs to be wrong in this situation looks at a related example: what an overlooked deadline costs a licensee who kept trading after termination.