Firmwatcher
Audit trail · Per-user attribution

Evidence your auditor will actually read.

Every acknowledgement is recorded automatically – who made it, when, and their comment – and so is every firm or individual added to or removed from your watchlist. So when the auditor asks how you monitor your counterparties, you don’t have to reconstruct the answer.

Audit trail · Illustrative entries
Today · 14:21 (BST)Acknowledged
A. Reviewer
“Reviewed scope; no action required.”
Requirement · Example Invest Ltd · FRN 000002
Today · 09:05 (BST)Acknowledged
B. Reviewer
“Escalated to head of compliance – see ticket #248.”
Disciplinary · Example Payments Ltd · FRN 000003
Yesterday · 16:40 (BST)Added to watchlist
A. Reviewer
Example Wealth Ltd (FRN 000005) added to the watchlist.
Recorded against your workspace
01 · Why it matters

The check itself isn’t the deliverable. The record is.

Regulated firms are expected to demonstrate that they actively monitor the firms they work with. It isn’t enough to say you checked – you need the dates, the details, and evidence of what you found and how you responded.

Spreadsheets and ad hoc logs are fragile: they rely on someone remembering to update them, and they get harder to keep up as your watchlist grows. Firmwatcher records each acknowledgement as your team makes it, so the record builds itself. Combined with daily FRN monitoring, you get both the coverage and the evidence.

02 · What gets recorded

Captured automatically – no manual upkeep.

  • Acks
    Acknowledgements

    When a team member reviews and acknowledges an alert, their name, the time and their comment are recorded.

  • Watchlist
    Watchlist changes

    Every firm or individual added to or removed from the watchlist, with who did it and when.

  • Dates
    Effective and detected dates

    Each alert shows the effective date the register gives and when Firmwatcher detected it, so you can show how quickly your team responded.

  • Export
    CSV export

    Export alerts and the audit log as CSV for your own records, an internal audit or a supervisory visit.

03 · What you can show

Four things an auditor tends to ask for.

  1. 01
    Daily monitoring, not periodic

    The audit log shows when each firm was added to the watchlist, and the watchlist shows when each was last checked – every morning, not just at quarterly intervals.

  2. 02
    Timely response to new entries

    Detected dates on alerts and timestamps on acknowledgements show how quickly your team picked up each one.

  3. 03
    Reasoning, not just the outcome

    The comment on each acknowledgement captures why you decided an alert did or didn’t need escalation.

  4. 04
    A record you can hand over

    Export alerts and the audit log as CSV and filter them to the firm or period the auditor asks about.

Book a walkthrough

Build the record before the supervision visit.

We’ll walk you through the audit trail on a live workspace – acknowledgements, comments, watchlist changes and CSV export.

Pick a slot

Fifteen minutes with the team. No deck – just the product and your questions.

Book demo →
UK-hosted database (London, AWS eu-west-2) · Checked every morning