Tracking German, EU and Madrid trademark renewals in one routine
If you need one internal routine for a small-to-mid-sized portfolio, the practical answer is to track the renewal date, check status in the relevant official system, and separate German, EU, and Madrid actions before each file reaches its own renewal path. The three systems do not run on one identical timetable, so the routine has to hold both the date and the source of truth for each mark.
By Limetree Legal Editorial Team
Start with one register, but do not treat every mark the same
A workable portfolio routine starts with a single internal register that records the mark type, registration number, renewal date, and where the current status should be checked. That shared register helps the team see the whole portfolio at once, but it should not flatten the differences between German, EU, and Madrid rights. Each system has its own renewal mechanics and its own official place to confirm status.
For German trade marks, the protection period runs for ten years and renews for further ten-year periods. The renewal takes effect the day after expiry. DPMA also states that the renewal fee is due six months before expiry, which means the internal record has to show both the expiry date and the earlier payment point.
For international registrations under the Madrid System, WIPO states that registrations are valid for ten years and can be renewed directly through eMadrid. That is a different workflow from a German national renewal, so the register should make the route visible at a glance.
Build the date record around the official term rules
The date field in the register should be more precise than a simple anniversary note. DPMA explains that the calculation of the German trade mark term changed for marks registered on or after 14 January 2019. That makes date handling in portfolio systems more than an administrative convenience; the system has to store the correct registration basis and calculate the relevant renewal point accordingly.
For German marks, the internal routine should show the expiry date and the fact that the renewal fee falls due six months before expiry. For Madrid registrations, the routine should show that renewal is available from six months before expiry or during the six-month grace period. Those are not identical timelines, and the internal record should reflect that difference rather than forcing every mark into one reminder rule.
Hypothetical example: if a team keeps only a single annual reminder, it may know that a renewal year is coming but still miss the earlier fee due point for a German mark or the renewal window for a Madrid registration. The better routine ties each mark to its own official term rule and reminder interval.
Use the official systems as the status check, not the spreadsheet
An internal tracker is useful, but it should be paired with checks in the official systems. EUIPO’s official trade mark search and application pages are meant to support filing and status checks in the EU system, rather than leaving the team to rely only on informal internal notes. That matters when the team wants one routine that can show whether a record is still live, how it is filed, and where the official information sits.
For Madrid registrations, WIPO’s eMadrid and Madrid Monitor tools support status checks, portfolio management, and renewals. In practice, that gives the team a clearer division of labour: the internal register holds the portfolio view, while the official system confirms the current status and renewal path.
For German marks, the same discipline applies. The internal record should not be the only source used to decide whether the file is ready for renewal. The renewal routine works best when the team confirms the record against the relevant official source before taking action.
Separate the three action paths before reminders go out
A single routine does not mean a single action. The internal process should separate German, EU, and Madrid marks early so the team knows which renewal route applies and which official system to use for the status check.
For German marks, the key points are the ten-year term, the six-month pre-expiry fee point, and the fact that for an overall renewal, payment of the fee is sufficient. That means the internal reminder should identify the mark as German and show the payment point clearly.
For Madrid registrations, the routine should route the file toward eMadrid, where renewals can be handled directly and status can also be checked in the Madrid tools. For EU marks, the routine should direct the team to the official EUIPO system for filing and status verification instead of treating the mark as if it followed the German or Madrid path.
A practical workflow is to assign each record one of three tags: German, EU, or Madrid. The reminder then carries not only the date, but also the action route. That avoids a common internal problem, where the team knows a renewal is coming but still has to stop and work out which system governs the file.
Set the routine so it can be checked by more than one person
Portfolio routines work better when they are simple enough for another team member to audit quickly. The register should show the registration type, the relevant term rule, the next renewal point, and the official system used for status confirmation. It should also show whether the mark is handled as a German, EU, or Madrid matter.
That structure helps when a colleague covers leave, when a portfolio review is due, or when the team wants to compare records across different rights. It also reduces the risk that an internal note is read as if it were an official status source. The official systems remain the place to confirm the current position; the internal routine just makes the review process repeatable.
If the team keeps the routine focused on those functions, it can track deadlines, separate action paths, and confirm status without adding unnecessary complexity. This article provides general information and is not legal advice.