Risk-Based JE
Turn individual flags into one combined score per entry.
- General ledger alone
How the result is read
No single flag condemns an entry — it is the co-occurrence of several weak signals that lifts one above the population, which only works if the flags are independent. Self-approval carries the heaviest weight, a round amount the lightest. Banding into high / medium / low lets testing effort follow the score rather than gut feel.
The worksheet, on the demo engagement
Risk-Based JE, as the application draws it for Harrow Precision Engineering Ltd, the fictional demo engagement — one row per journal entry.
Bars in severity order, High to Low. A fat High bar means the weights, not the ledger, need looking at. The height is a count of entries, never a conclusion about them.
- Population
- 41,338
- High 3+
- 214
- Med
- 1,902
- Low
- 39,222
ISA 240 testing for management override. Click a row to open the full journal entry.
Result grid4 rows
| journal_id | Man | Round | Timing | Keyword | Senior |
|---|---|---|---|---|---|
| JV-43880 | Y | Y | Y (Sun 12-29) | Y | |
| JV-44120 | Y | Y (per-end 12-31) | Y | Y | |
| JV-44131 | Y | Y (per-end 12-31) | Y | ||
| AP-90233 |
In the application
Risk-Based JE 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