Skip to main content
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
Accountant working carefully through client records at her desk
Reason recordedFee change approved
Nothing editedCorrections are new events

Happy on FigsFlow

  • Taxule
  • Ledgian
  • Sterling Wells
  • UK Property Accountants
  • Crane & Partners
  • 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.

Colleagues in a meeting piecing together documents and notes
Events recordedlast 12 weeks
Reconstructing the story
A trail that writes itself
Decisions
Decisions recorded in emails, if at all
Every action recorded as it happens
Timing
File notes written days after the event
Who, what, when, and why where it matters
Reasons
No record of why a fee or rating changed
Corrections added, never overwritten
Review
Hours spent assembling a file for a reviewer
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 →

Reviewer going through a client file during a meeting

Where it sits

Underneath every stage

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

  • Every stage writes to the trail
  • Append-only, never edited
  1. 01CRM
  2. 02Proposals
  3. 03Letters
  4. 04Onboarding
  5. 05Jobs
  6. 06Portal
  7. 07Billing
Underneath every stageOne client trail, written as the work happensRecording

Comes in

  • From proposals

    Sent by R. Basnet, $3,850

  • From the letter

    Signed, certificate issued

  • From jobs

    Reviewed and signed off

Okafor & Co.

Client trail · 1,284 events

Append-only
  1. Act
  2. Record
  3. Correct
  4. Read
ASWhoA. Shrestha
RBSent byR. Basnet

Who, what and when 1,284 of 1,284

Goes out

  • To a reviewer

    One export of the client record

  • To reporting

    Patterns across the whole firm

Live for every firm

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

Depends on your country

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

Works with

Related modules

Records the signature. Signatures and approvals on the record.

Explore e-signature and approvals

Keeps every version. Every version of every letter, kept.

Explore engagement letters

Records the review. Review and sign-off, recorded.

Explore jobs and workflow

Reads the pattern. Patterns across the whole firm.

Explore reporting and analytics

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.

Your privacy choices

We use cookies to improve site performance, remember preferences, and measure marketing effectiveness. You can accept all cookies, reject non-essential ones, or choose categories.