The required response time for regulated correspondence requesting information related to dividend or interest payments paid or payable more than six months prior is generally one month from receipt of the request. That deadline comes from data protection and shareholder-rights frameworks — most directly, GDPR Article 12(3) for personal data and the EU Shareholder Rights Directive II transposition for issuer–shareholder correspondence. The clock starts when the request lands with the responsible entity, not when it reaches the right department.
That single-month answer hides a stack of conditions. Some correspondence is data-subject access (DSAR) territory. Some is corporate-records territory. Some is a trustee or paying-agent query that sits under a different service standard entirely. The response time, the extension rules, and the failure consequences all follow from which category the letter falls into — and "more than six months prior" is the trigger phrase that usually pushes a request out of the ordinary enquiry lane and into a regulated one.
What "Regulated Correspondence" Actually Covers Here
Regulated correspondence means a written request that a law or binding rule obliges the recipient to answer within a set period. The phrase doesn't describe tone or formality. It describes legal consequence: if the entity ignores it, a regulator can act.
In practice, three regimes dominate requests about dividend or interest payments older than six months. The first is data protection law — GDPR Article 12(3) requires a controller to respond to a data subject request "without undue delay and in any event within one month." The second is the shareholder-rights regime under Directive (EU) 2017/828, which national law transposes with deadlines for issuer responses. The third is sector service regulation for banks, registrars, and paying agents, where the local conduct authority sets complaints and enquiry timetables.
A dividend statement, an interest payment record, or a year-end tax voucher naming the requester is almost always personal data. That classification is what converts a polite letter into a deadline-bearing DSAR. The six-month marker matters because most operational service promises — reissue of a certificate, statement resend, duplicate advice — expire or change character after two full payment cycles.
The boundary is narrower than people assume. A general question about dividend policy isn't regulated correspondence. A request for someone else's payment details isn't either, unless a legal representative has standing. Get those two wrong and the one-month clock never started.
The One-Month Clock And How It Runs
The one-month period in GDPR Article 12(3) runs from the day the controller receives the request. Receipt doesn't require the letter to reach the correct department. A request lodged with a branch, a registrar's mailbox, or a customer-service address counts.
You can extend by a further two months where requests are complex or numerous. GDPR Article 12(3) allows that, but only with notice to the requester within the first month explaining the delay and the reason. An extension without notice is a breach even if the substantive answer eventually arrives.
Under UK GDPR, the same one-month and two-month structure applies, with the Information Commissioner's Office as regulator. The ICO's guidance treats day one as the date of receipt and counts calendar days, not working days. A request arriving on 30 April is due by 30 May; a request on 31 January is due by 29 February in a non-leap year.
Weekends and bank holidays do not stop the clock. That trips up internal workflows built on five-day service-level targets, because a request landing the Friday before a long weekend still burns three calendar days before anyone opens it.
When A Two-Month Extension Is Lawful — And When It Isn't
The extension exists for complexity, not for inconvenience. GDPR Recital 63 ties it to the volume of requests and their complexity, and regulators read that narrowly. A single archived dividend record from seven years ago is unlikely to qualify; a portfolio-wide request covering twelve issuers, three nominee accounts, and two closed brokers probably does.
Notice is the operative condition. The controller must tell the requester within one month that it is extending, and explain why. Regulators such as the ICO and the Dutch Autoriteit Persoonsgegevens have treated missing notice as an infringement in their enforcement decisions, regardless of how complex the underlying files were.
Complexity has limits. If the entity holds records in a legacy system that requires manual retrieval from offsite archives, that's an internal cost, not automatically a legal complexity ground. The test looks at the request, not the recipient's filing habits.
Practical arithmetic: a 31 January request extended by two months is due 31 March in a non-leap year. If the notice of extension arrives on 2 March, the extension is late — the first month already closed without the required communication.
Dividend Payment Data Requests: What Counts As Received
Receipt is the single most litigated fact in these disputes. Under GDPR, receipt occurs when the request reaches the controller or its processor, and a registrar acting as processor for an issuer is a valid receiving point. A letter to the registrar's registered office starts the clock for the issuer.
Email is receipt too. If the entity publishes a data-protection contact address, a request delivered there is received even if it lands in a monitored-inaudible mailbox. The Article 29 Working Party guidance (now reflected in EDPB positions) says controllers can't dodge receipt by routing requests through an unmonitored channel they themselves published.
Verbal requests count where the controller can reasonably verify identity, though proving a phone call is harder on both sides. Written is safer for everyone, and a letter or email gives the requester a timestamp.
The failure case to know: a request posted to the wrong subsidiary of a group. The clock starts with that subsidiary only if it's a controller for the data. Send it to the issuer's investor-relations team at the holding company and you may not have triggered the issuer's obligation at all. Confirm the legal entity first.
Interest And Bond Payment Records Under Sector Rules
Bond interest records sit in a different lane. A request to a paying agent or trustee for interest payment history from an earlier year touches both data protection and the contractual terms of the trust deed or agency agreement.
The one-month GDPR period still applies where the record contains personal data — an individual bondholder's payment history is personal data even for a corporate issuer. What changes is the retrieval route: paying agents typically hold payment records for a defined retention period, often six to ten years under anti-money-laundering rules such as the EU's 4AMLD/5AMLD retention requirements, and records outside that window may genuinely not exist.
A record that doesn't exist is still owed an answer. The controller must tell the requester within the one month that no data is held, rather than let the clock expire in silence. Silence is itself an infringement under GDPR Article 12.
The "more than six months prior" phrase matters most here. Contemporary interest statements are usually reissued on request through ordinary digital banking. Older records fall outside self-service, which is why they become regulated requests in the first place.
A Comparison: Which Deadline Applies To Which Request
| Request type | Governing rule | Base deadline | Extension | Notice required? |
|---|---|---|---|---|
| DSAR for own dividend statement, 3 years old | GDPR Art. 12(3) / UK GDPR | 1 month | +2 months | Yes, within month 1 |
| DSAR for own interest payment history, 2 years old | GDPR Art. 12(3) | 1 month | +2 months | Yes, within month 1 |
| Shareholder register inspection | National companies act (e.g., UK Companies Act 2006 s.116) | 2 working days | None for register access | No |
| Issuer response under Shareholder Rights Directive II | National transposition | Set by member state | Varies | Varies |
| Bank complaint about payment posting | Local conduct rules (e.g., FCA DISP) | 8 weeks for final response | None standard | Interim response in 4 weeks |
The verdict is blunt: if the request is personal data, assume one month and plan for three only with documented complexity. Everything else is a narrower regime with its own number, and quoting "30 days" across the board will be wrong somewhere.
Two cells in that table carry real cost. UK Companies Act 2006 section 116 gives five working days for a copy of the register if the requester doesn't use the inspection route — not two days — so verify the exact statutory route before promising a date. The FCA's Dispute Resolution rules (DISP 1.6) require a final response within eight weeks of a complaint, with a prompt holding reply inside four.
Failure Cases: What Goes Wrong At Day 30
The typical failure isn't a refusal. It's a clock that quietly expires while the request travels between a registrar, a transfer agent, and the issuer's legal team. Nobody breaches on purpose; the handoff has no owner.
Excessive verification is the second trap. GDPR Article 12(6) lets a controller request additional identity information only where there are reasonable doubts, and the one-month clock continues to run while identity is checked. Requesting a certified passport copy for a routine dividend statement query pushes the response past deadline for no lawful reason.
Third-party data is a genuine red flag. A dividend statement covering a joint holding exposes the co-holder's details, and those need redaction before release — redaction time counts against the month, not automatically as an extension ground.
The remedy path runs through the regulator. In the UK, a complaint to the ICO can follow; in Germany, the Landesdatenschutzbeauftragte; across the EU generally, the national supervisory authority. Outcomes vary from reprimand to fine, and compensation for material harm is separately available under GDPR Article 82.
How To Calculate And Document The Deadline
Number the working: day of receipt, plus one calendar month, plus up to two months if the extension notice is served in time. Nothing else changes the arithmetic.
1: Log the receipt date the moment the request arrives, including channel and mailbox. 2: Confirm the receiving entity is the controller for the data requested. 3: Classify the request: personal data, statutory register access, or conduct complaint. 4: Count one calendar month for DSARs; set a diary flag at day 20 for extension decisions. 5: If extending, serve written notice with reason before month one closes. 6: Redact third-party data before release; don't let redaction drift past deadline. 7: For refusals, cite the specific GDPR article and state complaint rights.
Failure handling: if the deadline passes, don't bury it. Log the breach, send an apology with the substantive answer promptly, and note that the requester can complain to the supervisory authority. A late answer is better than silence, and regulators distinguish between the two.
Why "Six Months Prior" Changes The Process
The phrase signals that the record is no longer in live service. Contemporary dividend and interest data sits in portals and apps; older data moves to archives, and retrieval takes longer. That's exactly why the extension mechanism exists — but the complexity must be real.
Operationally, most firms keep instant-access data for the current and prior two tax years. Anything older requires a search request to a records management team, and that queue is where day 25 surprises live. A request covering payments from four years ago likely crosses two archive tiers.
Retention caps also matter. Anti-money-laundering rules require payment records to be kept for five years after the transaction or relationship ends under EU 4AMLD, with member states able to extend to ten. A request beyond the retention window may yield a lawful "no data held" response within the month — not a breach.
Don't confuse retention with response. Evidence of a payment posted eleven years ago still sits in tax filings or trustee accounts, even where the personal payment record has been lawfully deleted.
The Thirty-Day Claim: Where It Comes From And Where It Breaks
Thirty days is a folk number. It arrived in UK practice through old Data Protection Act 1998 language and survives in internal service promises and third-party advice, but the statutory UK GDPR period is one calendar month, not thirty days.
The difference is material. A one-month deadline from 31 March is 30 April; a thirty-day deadline from 31 March is 30 April too — coincidence in that example, but not in February. A 31 January request is due 29 February in a non-leap year under the one-month rule; the thirty-day rule lands on 1 March.
For cross-border requests, the rule is the controller's local law. A Greek issuer answering a UK-based holder applies the Greek transposition and GDPR; a UK issuer answers under UK GDPR. Neither applies the other's national add-ons.
If a policy manual states "respond within 30 days," treat that as a tighter undertaking than the law requires — and one the requester can hold you to.
FAQ
Does the one-month period include weekends and public holidays?
Yes — GDPR counts calendar days, so a request received on 1 November is due 1 December. A public holiday inside the window doesn't push the deadline. Only a formal extension notice, served within the first month, moves it.
What happens if the data no longer exists because retention expired?
The controller must still reply within the month, stating that it holds no relevant data and explaining the retention basis. GDPR requires a response even where the answer is "nothing held." Silence remains an infringement.
Do I need to pay a fee for dividend records older than six months?
Normally no. GDPR Article 12(5) makes responses free unless the request is manifestly unfounded or excessive, and a single historical dividend query won't clear that bar. Some national companies acts set a modest register-inspection fee — check the local statute, not the payment scheme.
Is the deadline different for a bond interest query handled by a trustee?
The underlying GDPR one-month rule applies to the trustee or paying agent as controller for its records. What differs is the retrieval route and the retention cap, so the substantive answer may take longer fruitfully without an extension being unlawful.
Can the issuer reset the clock by asking for ID?
No. Asking for identity verification doesn't pause the one-month deadline; GDPR Article 12(6) allows the request only where reasonable doubts exist. Excessive verification is a known enforcement trigger across EU supervisory authorities.
How does the Shareholder Rights Directive II deadline compare?
SRD II's national transpositions set issuer-response rules that vary by member state; the one-month GDPR period governs personal data regardless. Where the two apply, the earlier deadline controls for compliance purposes.
What's my remedy if the response arrives after the extension window?
A complaint to the national supervisory authority first, then a civil claim for material or non-material damage under GDPR Article 82. UK holders can escalate to the ICO. Compensation awards vary by jurisdiction and evidence.
Does a query about unpaid dividends from an insolvent issuer still carry the deadline?
Yes, if the entity — or its administrator — remains the controller for the records. Insolvency affects payment, not the obligation to answer a lawful data request within one month. The liquidator's insolvency practitioner is usually the named contact.
This article is general educational information about regulatory response timetables, not a legal opinion or a substitute for advice on your specific request. Deadlines and remedies vary by jurisdiction, so consult a locally qualified data protection lawyer or the relevant supervisory authority before relying on any figure here. For immediate risks — such as suspected fraud or identity theft tied to payment records — contact your local emergency services or national cybercrime reporting centre.