Monthly Activity
Detect accounts posting an abnormal amount in a given month relative to their own history.
- General ledger alone
- Compares with last year
How the result is read
Twelve observations is a thin baseline, so the dispersion is taken robustly and with the month under test excluded — a large entry otherwise inflates the yardstick it is measured against. Seasonality belongs in the baseline: December is a spike only against prior Decembers. A dormant account waking at period end is itself the finding.
The worksheet, on the demo engagement
Monthly Activity, as the application draws it for Harrow Precision Engineering Ltd, the fictional demo engagement — one row per account per fiscal period.
- Anomalies |score|>3
- 47
- Dormant reactivated
- 6
Result grid4 rows
| Account | Month | Net Movement | Median (ex-month) | 1.4826 x MAD | Robust score |
|---|---|---|---|---|---|
| 6500 Professional fees | Dec | 902 | 281 | 68 | +9.1 |
| 7200 Repairs & maint | Aug | 0 | 44 | 12 | (3.7) |
| 2900 Suspense (dormant) | Dec | 318 | 0 | 0 | n/m |
| 4000 Revenue | Dec | (1,940) | (1,070) | 260 | (3.3) |
In the application
Monthly Activity is filed under Planning & analytics, index letter A. "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 A, 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