Explainability
Produce a documented breakdown of why any flagged entry received its score.
- General ledger alone
How the result is read
Each contributing weight is shown individually, so the file carries the full chain of reasoning rather than a black box. That is what makes the score defensible under ISA 230: the auditor can show which flags fired, the values observed and how much each added — and equally defend why a low-scored entry was not pursued.
The worksheet, on the demo engagement
Explainability, as the application draws it for Harrow Precision Engineering Ltd, the fictional demo engagement — one row per contributing flag for one journal entry.
Flags ranked by how many entries each one tops, with the cumulative share. The first bar carrying most of it — the cumulative line jumping to near the cutoff at once — is a single rule driving the score.
- Per-transaction why
- Yes
- Standard
- ISA 230
Result grid2 rows
| journal_id | score | band | top contributor |
|---|---|---|---|
| JV-44120 | 94 | HIGH | Self-approval +31 |
| JV-43880 | 88 | HIGH | Rare flow +26 |
In the application
Explainability is filed under Journal entries, index letter B. "Run all analyses" runs it with every other analysis the ledger can answer. The worksheet states the population it tested on its face — or "Not applicable" with the reason when a column it depends on is empty — and the Excel workbook the engagement exports files it under B, beside an index of the source files with their SHA-256 fingerprints.
Read it with
Run your next audit file test without the Excel crash.
One free engagement to evaluate, valid 60 days. The ledger never leaves the machine.
- 20 minutes
- Runs on a fictional engagement
- No client data required