Trade confirmation redaction is the removal of personal data from an execution note. FCA COBS 16A requires a firm to confirm an executed order to a retail client promptly — no later than the first business day after execution. The same trade generates a transaction report to the FCA under Art. 26 of UK MiFIR (Regulation (EU) No 600/2014 as retained in UK law), with order records held under Art. 25, and the execution itself must meet the standard in FCA COBS 11.2A: all sufficient steps to obtain the best possible result. anonym.plus marks each identifier on your device, so price, size and venue stay while the counterparty goes.
When this applies
An execution note names the client, the venue, the settlement instructions and the consideration. A best-execution analyst, a transaction-cost model or an external reviewer needs the trade, not the person. You trim the personal parts before the file leaves; the confirmation you sent and the Art. 26 report stay untouched.
How anonym.plus handles it
- Open the note in anonym.plus on your device.
- Local OCR reads a scanned broker confirmation.
- The tool flags name, IBAN, sort code and client reference numbers.
- Keep the instrument, ISIN, price, quantity and venue intact.
- Swap or black out the marked items.
- Save the clean copy locally.
What you need to provide
- The confirmation (PDF, DOCX, or scan).
- An operator (Mask suits reference numbers).
- Optional batch for a whole day of notes, up to 20 files per run.
PII & financial identifiers detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | buyer K. Warner → [PARTY] |
| Financial | IBAN_CODE | GB29 NWBK 6016 ... → [IBAN] |
| Financial | UK_SORT_CODE | settle 20-00-00 → [SORT_CODE] |
| Money | MONEY | consideration £48,200 → [VALUE] |
| Dates | DATE_TIME | trade date → [DATE] |
| Contact | EMAIL_ADDRESS | k.warner@example.co.uk → [EMAIL] |
Compliance achieved
- FCA COBS 16A requires an executed order to be confirmed to a retail client promptly, and no later than the first business day after execution; the confirmation you issued is the record, and only a copy is redacted.
- UK MiFIR Art. 26 (Regulation (EU) No 600/2014 as retained) requires the transaction to be reported to the FCA no later than the close of the following working day, with order records under Art. 25 — separate obligations that a redacted analysis copy does not touch.
- FCA COBS 11.2A requires all sufficient steps to obtain the best possible result for the client; the execution data an analyst needs for that test survives redaction, because only identifiers are marked.
- Offline processing across 340+ PII types keeps counterparty and settlement data inside the firm, with AES-256-GCM protecting working copies at rest.
Anonymise trade confirmations offline — see plans & start free →
Limitations & cautions
A single large trade in a thin instrument still points to one party once the name is gone, and a settlement reference can be reused across notes. The tool flags named items, not unique market footprints. Review unusual notes before you circulate them.
Frequently asked questions
What stays after I redact a confirmation?
The instrument, ISIN, price, quantity, venue, trade date and consideration can all stay — those are what a best-execution review under COBS 11.2A actually needs. Names, IBANs, sort codes and client references are marked for removal.
Does redaction affect the MiFIR transaction report?
No. UK MiFIR Art. 26 requires the transaction report to reach the FCA by the close of the following working day, with the full identifying detail. That report is a separate submission; a redacted copy of the confirmation is only a working document.
Can I clean a whole day of notes at once?
Yes. Batch mode handles up to 20 files per local run, with OCR for any scanned broker confirmations in the set.