Cross-border service of documents: stages and deadlines
Cross-border service of a patent claim runs as a fixed sequence, not a single mailing. Papers move from the originating court to a receiving body abroad, get translated where needed, and are delivered through that country's own channel. A certificate of service then returns to the court, and only then does the response clock start.
How the process works
The sequence has several distinct stages, and each one has its own gatekeeper. The court that receives the claim forwards the papers to a body designated to handle incoming service in the defendant's country. That body checks the paperwork, arranges a translation if the defendant will not accept the original language, and organises delivery through whatever local channel applies — post, a court officer, or a registered delivery service.
Once delivery happens, the receiving body issues a certificate confirming it and sends that certificate back to the originating court. No later stage in the file moves until that certificate arrives. If any single stage is skipped or done out of order, the usual outcome is not a warning — it is repeating the stage from scratch.
The point of no return
At some stage, the process stops being reversible. Once the receiving body certifies delivery and that certificate reaches the court, the response clock runs whether or not the defendant has actually read the papers. Contesting service after that point means proving delivery never happened, not simply that it went unnoticed — a materially harder argument to make. Before the certificate arrives, gaps in the address or the translation can usually be corrected without cost to the timeline. After it arrives, correcting a defect usually means restarting the sequence rather than adjusting it.
What changes in practice
A cross-border claim rarely moves at the pace of a domestic one. Translation adds time before the defendant even sees the papers. A wrong or outdated address sends the whole packet back, and the clock resets rather than pauses. Underlying ownership questions add another layer: if a founder has already left with the prototype at the centre of the dispute, service failures compound a position that is contested before the papers even land. A related situation, covered in Media, content and streaming a founder leaves with the prototype, shows how that ownership question is assessed separately from any service question.
What to do
- Confirm the defendant's correct registered address before the claim is filed, not after.
- Prepare the translation package while drafting the claim, so it is ready the moment service is requested.
- Ask the court clerk which receiving body will handle delivery abroad, and confirm its expected channel.
- Track acknowledgement from that receiving body, and calendar the response deadline from the date of delivery, not dispatch.
- If no acknowledgement arrives within a reasonable time, ask the court to check status before assuming the deadline has started.
- Keep the certificate of service in the file — it is the only proof the response window has actually opened.
Stages at a glance
| Stage | What happens | Who acts |
|---|---|---|
| Filing | Claim and annexes lodged with the court | Claimant |
| Transmission | Court forwards the papers to the receiving body abroad | Court registry |
| Translation | Documents translated unless the defendant accepts the original language | Receiving body or claimant |
| Delivery | Receiving body delivers to the defendant through its own local channel | Receiving body |
| Confirmation | Certificate of service returned to the originating court | Receiving body |
| Deadline start | Response window opens from the date of actual delivery | Court |
Who decides and how long it takes
The forum holding the claim decides how service must proceed. For a national patent, that is the national court seized of the case. For a unitary patent, it is the Unified Patent Court, sitting in the division where the claim was lodged. Neither forum carries out delivery itself — that task sits with the receiving body in the defendant's country, which follows its own domestic timetable and reports back once delivery is confirmed.
There is no single fixed period for the whole sequence. Timing depends on the receiving country's channel, whether translation is required, and how quickly the certificate of service comes back. Build in a wide margin rather than assuming a set number of weeks, and treat any early estimate as provisional until the certificate is actually in the file.
Common scenarios
If the defendant is based in another EU member state, delivery usually runs through the receiving body designated in that state, and translation depends on whether the defendant accepts the language the claim was drafted in.
If the defendant is outside the EU, the process typically takes longer, because everything depends on the receiving state's own channel and its willingness to cooperate with an incoming request.
If the defendant avoids acceptance or the address turns out to be wrong, the court may need to authorise an alternative method of delivery, and the response clock restarts from that authorisation rather than from the original attempt.
If the underlying right is not a registered patent but a tokenised one, the practical problem often shifts away from service altogether — the real fight becomes whether a platform can be forced to reverse a decision, a situation examined in When a marketplace delists the collection in detail.
What this page does not cover
This page does not decide which court has jurisdiction over a given patent dispute, and it does not cover the cost of translation or delivery. It does not replace advice on a specific claim, and it does not cover disputes that settle privately before any court becomes involved.
Sources and limits
This overview reflects publicly available procedural information about how service abroad is organised, checked at the time of writing. It avoids citing specific statutory provisions, because service rules and channels differ by country, and a wrong citation would be worse than a general description.
Every date and every source used across this site follows a fixed check before publication. See Methodology: collection, cross-checking and dating and the deadline for how that check works.
If the dispute also involves a counterparty you have not fully vetted — a distributor, a licensee, a supplier abroad — the risk profile is different from a service question. See Counterparty report before onboarding a distributor in detail for that separate check.
FAQ
How long does cross-border service of documents take in practice?
There is no single fixed period. Timing depends on the receiving country's own channel, whether translation is needed, and how quickly delivery is confirmed and the certificate returned to the court. Build in a substantial margin rather than assuming a fixed turnaround, particularly where the defendant's country lies outside the EU.
Which documents are needed to start?
The claimant needs the claim itself, any annexes referenced in it, and a translation package if the receiving country or the defendant requires one. The defendant's exact registered address is essential — service to the wrong address restarts the sequence rather than merely delaying it, so this detail is worth confirming twice before filing.
What happens if the other side does not respond?
If no response arrives within the window set by the court, the claimant can ask the court to proceed on the basis of default. Before doing so, the court checks that service was actually completed and that the certificate of service is in the file, because a default judgment issued on defective service stays vulnerable to challenge later, sometimes long after it was entered.
Related publications
See Opposition before the granting office step by step for the stage that often runs in parallel with a service dispute.
Next step
If the dispute at hand also involves field-of-use restrictions in a licence, read When field-of-use limits are ignored in practice next.