Closing an account does not close the file. MLR 2017 reg. 40 keeps the due-diligence record for five years after the business relationship ends, which is why a closure request rarely produces deletion. UK GDPR Art. 17 gives a right to erasure, but Art. 17(3)(b) disapplies it where processing is needed to comply with a legal obligation — and reg. 40 is one. Where the bank ends the relationship itself, the Payment Services Regulations 2017 require at least two months' notice on a framework contract. A balance nobody claims eventually moves under the dormant-accounts scheme rather than vanishing. anonym.plus marks each item on your machine, so the audit trail stays intact while the holder details go.
When this applies
A wind-down queue is reviewed by an analyst measuring how long closures take. The reason codes and the dates carry the answer. The former holder's name, the closed account and the account the balance moved to do not.
How anonym.plus handles it
- Open the termination file in anonym.plus on your device.
- Local OCR reads any scanned wind-down forms.
- It flags the holder, account, and final balance.
- Confirm the flags and keep the reason codes.
- Swap or black out the confirmed fields.
- Save the clean record locally.
What you need to provide
- The termination file (PDF, DOCX, or scan).
- An operator (Replace keeps the trail readable).
- Optional batch for a wind-down queue.
PII & financial identifiers detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | former holder K. Hale → [HOLDER] |
| Financial | UK_BANK_NUMBER | closed 11904456 → [ACCOUNT] |
| Money | MONEY | final £312.40 → [AMOUNT] |
| Financial | UK_SORT_CODE | disbursement 40-12-19 → [SORT_CODE] |
| Contact | EMAIL_ADDRESS | hale@example.co.uk → [EMAIL] |
| Dates | DATE_TIME | closed 06/2026 → [DATE] |
Compliance achieved
- Recognises that erasure under UK GDPR Art. 17 yields to a legal obligation through Art. 17(3)(b).
- Leaves the retained file intact for the five-year period in MLR 2017 reg. 40.
- Keeps the notice trail the Payment Services Regulations 2017 require where a bank ends a framework contract.
- Preserves the record an unclaimed balance needs under the Dormant Bank and Building Society Accounts Act 2008.
- Offline work keeps the termination record off any server.
Anonymise account-closure records offline — see plans & start free →
Limitations & cautions
A closure file usually names the account the money moved to, which can re-link the person even after the closed number is masked. Mask both. And never treat redaction as erasure — Art. 17(3)(b) and reg. 40 mean the original stays.
Frequently asked questions
A customer asked to be forgotten. Can I delete the closure file?
Usually not in full. UK GDPR Art. 17(3)(b) disapplies erasure where processing is necessary to meet a legal obligation, and MLR 2017 reg. 40 imposes five-year retention on due-diligence records. You keep the file, limit what you share from it, and explain the basis to the customer.
Does it catch the disbursement account too?
Yes. The tool flags every banking number on the page, including the sort code and account the final balance was sent to — the field most likely to defeat a partial mask elsewhere in the file.
Is the file uploaded anywhere?
No. The app works offline, so the termination record stays on your device.