Dimension Analysis
Profile who is posting, not just what, because authorization risk lives at the user level.
- General ledger alone
- Compares with last year
How the result is read
Breadth is only large relative to something: a GL clerk whose job is the close touches many accounts legitimately, while a warehouse contractor touching four is the anomaly. So it is judged against the preparer’s own peer group and their own prior periods, and against the span of the accounts rather than the count — reaching across unrelated statement areas is the signal.
The worksheet, on the demo engagement
Dimension Analysis, as the application draws it for Harrow Precision Engineering Ltd, the fictional demo engagement — one row per preparer.
- Wide-spread users
- 2
Result grid4 rows
| User | Distinct accounts touched | Top account (value) | Manual entries | Flag |
|---|---|---|---|---|
| SYSTEM | 142 | 4000 Revenue | 0 | |
| A.Lee (GL clerk) | 11 | 1200 AR | 410 | |
| J.Smith (Controller) | 9 | 2900 Suspense | 640 | senior + suspense conc. |
| R.Kahn (temp) | 24 | 6900 Other | 86 | rare wide spread |
In the application
Dimension Analysis 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