Skip to main content
Practice management joins FigsFlow on 7 OctoberFree until 28/02/2027
FigsFlow

Run the work · Audit trail

An audit trail for accounting firms that records itself

Every action across the client lifecycle carries who did it, what changed, when, and why. FigsFlow captures it as the work happens rather than asking anyone to reconstruct it afterwards.

  • Append-only
  • Who, what, when and why
  • Exportable for a reviewer
Reason recordedFee change approved
Nothing editedCorrections are new events

Built by accountants, used by the firms behind FigsFlow

  • Taxule
  • Ledgian
  • Sterling Wells
  • UK Property Accountants
  • Property SPV

The problem

Evidence scattered is evidence missing

When a reviewer, an insurer or a client asks what happened and when, most firms piece the answer together from emails, file notes and memory.

Reconstructing the story

  • Decisions recorded in emails, if at all
  • File notes written days after the event
  • No record of why a fee or rating changed
  • Hours spent assembling a file for a reviewer

A trail that writes itself

  • Every action recorded as it happens
  • Who, what, when, and why where it matters
  • Corrections added, never overwritten
  • One export for anyone who needs to read it

How it works

Recorded once, readable forever

  1. Act

    Your team works normally. Sending, signing, approving and changing are all events.

  2. Record

    Each event stores who did it, what changed, when, and the reason where one is required.

  3. Correct

    Nothing is edited or deleted. A correction is a new event that points to the original.

  4. Read

    Filter one client’s trail by person, module and date, or export it for a reviewer.

What you get

An activity log for client work

It is not a feature you switch on. It is how the work is recorded.

01

Append-only

No administrator can edit or delete an entry. The history stays as it happened.

02

Four fields, every time

Who, what, when, and why where a reason was required, on every event.

03

Reasons when it matters

Overrides and fee changes ask for a reason at the moment they are made.

04

One continuous record

From first enquiry to last invoice, one trail per client across every module.

05

Filters that answer questions

By person, by module, by date, so a specific question has a specific answer.

06

Export for a reviewer

A readable package of one client’s record, decisions and evidence references.

One event, opened

Everything a reviewer would ask about it

Open any event to see the person, their authority, the change made, the time it was made and, where a reason was required, the reason in their own words.

The audit trail evidences what your firm did. Whether it was the right thing remains your firm’s professional judgement.

Explore the full platform →

Where it sits

Underneath every stage

The audit trail is not a stage of the lifecycle. It runs beneath all of them.

CRM·Proposals·Letters·Onboarding·Jobs·Portal·Billing

Live for every firm

  • Append-only events across every module
  • Reasons captured where required
  • Filters and reviewer export

Depends on your country

  • How long records must be kept
  • AML and client due diligence records are available in the UK

See what is live in your country → · AML (UK only)

FAQ

Questions firms ask us

Can anyone edit or delete an entry?

No. The trail is append-only and there is no administrator override. A correction is a new event that references the original, so both remain visible.

Do we have to turn it on?

No. It is not a feature you enable; it is how the work is recorded. There is no version of FigsFlow without it.

How long is it kept?

For the retention period your firm's obligations require in the countries you work in, with a hold where one applies. Your firm sets the period.

Does an audit trail make us compliant?

No. It evidences what you did. Whether what you did was right is a matter for your procedures and your professional judgement. FigsFlow evidences and assists; it does not advise.