Who did what, when
without anyone writing it down
FigsFlow is audit trail software for accountants that records itself. Every action across the client lifecycle — the quote, the letter, the check, the rating, the request, the approval, the invoice — carries who did it, what changed, when, and why, captured as the work happens rather than reconstructed afterwards.
281 reviews from
G2 reviews
Google reviews
Verified reviews
Trusted by the best
Read a client’s trail, end to end
Ninety seconds through one client from first quote to last invoice: every event in sequence, filterable by person, by module and by date. Nothing in it was typed by anyone as a note.
VID-01 · film to supply
Eighteen months later,
and nobody kept a log
The reviewer asks when the letter was signed, who approved the rating, and why the fee changed in March. The answer is in four places: somebody's sent items, a folder nobody has opened since, a spreadsheet with a version number in the filename, and the memory of a person who left in June. So you reconstruct it, and the reconstruction takes longer than the work did.
Somebody's sent items.
A folder nobody has opened since.
A spreadsheet with a version number in the filename.
And the memory of a person who left in June.
Where it sits
The entries come from the work, not from a log
Nobody writes an audit trail. It accumulates because the work happens in the same place the record lives — the proposal, the letter, the AML check, the risk rating, the request, the approval, the invoice. Every one of those is an event, and every event lands on the same trail in sequence.
Six sources
One trail
What comes off it
Feeding this trail: AML and due diligence · risk assessment · e-signature · engagement letters
Capability · 01
Four things every event carries
Who, what, when and why. The person, the change, the timestamp, and the reason where a reason was required — an override, an approval, a deviation from a computed rating. Audit trail software for accountants that records the first three and not the fourth answers half the question a reviewer actually asks.
Choose an event to see its four fields.
- Who
- A. ShresthaPartner · authority to override
- What
- Risk rating Medium → LowComputed rating was Medium
- When
- 19 March 2026, 08:48Recorded at the moment of the change
- Why
- Reason required — deviation from computed rating“Source of funds verified against three years of filed accounts; no adverse media. Rating reduced with partner approval.”
Capability · 02
Readable. Not editable
Append-only. There is no administrator who can quietly amend an entry, which is the property that makes a trail worth anything at all. A correction is a new event that references the old one, so the record shows both what was thought and what was corrected.
Most systems that claim an audit trail have an admin role that can edit it. Stating plainly that yours cannot is a stronger claim than any feature list, and it is checkable. Try it.
EVT-38104 · original · retained
S. Gurung recorded fee £3,850.00 — 14 March 2026, 14:02
Capability · 03
The same trail answers four different questions
A file reviewer asks whether the work was done in the right order. A supervisor asks whether the due diligence preceded the engagement. A professional indemnity insurer asks what was known and when. A client asks why the fee changed. One record, four readings, no reconstruction for any of them.
“Was the work done in the right order?”
Capability · 04
What eighteen months looks like
A client relationship from first contact to current position, in one continuous sequence, with retention running to the period your supervisor requires rather than to whenever somebody archived the folder. The point is not that it is long. The point is that there are no gaps in it.
MLR 2017 reg 40 sets five years from the end of the relationship for AML records. Other records follow other periods, and UK GDPR storage limitation cuts against keeping anything indefinitely.
Scroll the chart sideways for all eighteen months
Month
March 2026
Events
93
Longest quiet period
11 days
Retention
Per obligation
Seen enough? Bring a file your last review picked up on.
Book a demoA folder and a good memory, or one continuous record
Most practices already have an audit trail. It is distributed across inboxes, folders, file names and people, and it only assembles when somebody spends a day assembling it. Audit trail software for accountants is the difference between having the evidence and being able to produce it.
Reconstructed after the fact
- Sent items
- A folder with version numbers in the filenames
- A spreadsheet
- Somebody’s recollection
- Assembled under time pressure, on the day a reviewer asks
- One sequence
- Four fields per event
- Append-only
- Filterable
- Already complete before anybody asks for it
WHO USES IT
What this looks like at your size
Pick the shape of your practice.
A regulator's query is the first thing that will outgrow your own memory, because it can land on any file, at any time — not just the ones you still remember clearly.
PREVIEW CLOCK — INTERACTIVE DEMO
A supervisory visit is the first thing that will outgrow whoever handled the file, because it can ask about any client, on any day — not just while that person is still around.
PREVIEW CLOCK — INTERACTIVE DEMO
A review season is the first thing that will outgrow your current process, because it touches every open file at once, not just the ones somebody happens to remember.
PREVIEW CLOCK — INTERACTIVE DEMO
A regulator's request is the first thing that will outgrow three separate packs, because it expects one answer — not three different ones from three different people.
PREVIEW CLOCK — INTERACTIVE DEMO
Where the entries come from
Every module writes to the same trail. Documents stay in your own SharePoint tenancy and the trail holds the references, not the files — so the record of what happened survives independently of where the documents live.
Ridgeline Foods Ltd
CT600 · 2026
- Engagement letter signed09:14
- Risk rating overridden11:02
- Reviewer sign-offOutstanding
Files stay in your SharePoint · the trail keeps the reference
Your tenancy at both ends. The documents start in the systems you already run and stay there — what the trail records is that they were requested, received, signed and reviewed.
No module keeps a private log. An entry is written once, by the module that did the work, and nobody edits it afterwards.
Built inside a working UK practice
Built inside working practices, not in a lab — by people who had returned their own work with review points on it.
Placeholder
0:48
Placeholder
1:02
Placeholder
0:55
Placeholder
1:14
Everything an audit trail connects to
An audit trail does not sit on its own. These four write to it directly; the rest of the platform sits around them on the same client record.
AML and due diligence
The events a supervisor asks about.
See the AML moduleRisk assessment
Where the overrides and reasons come from.
See the risk assessment moduleE-signature
The signing certificate and timestamps.
See the e-signature moduleDocuments
Where the files themselves live.
See the documents moduleQuestions a reviewer will ask
Can anyone edit or delete an entry?
Do we have to turn it on?
How long is it kept?
Is viewing a record itself logged?
Can we export it?
Does an audit trail make us compliant?
Bring a file your last review picked up on
No scripted demo. Bring the file that came back with a question on it, and we will show you what the same client looks like in audit trail software for accountants — in sequence, with the four fields on every event, and nothing reconstructed.
Want the decisions behind the entries? Risk assessment