miatzSign in

Ranking journal entries for management-override testing

Scores general-ledger postings against the attribute patterns that make an entry unusual — rarely paired accounts, a poster who does not normally post, a date after period close, a round value, no narration — and hands the auditor or the controller a ranked queue whose underlying support is then pulled and inspected by hand.

Effort
Weeks of work
Skill level
Some technical skill
Organisation size
Mid-market
Value
Risk reduced, Time saved

Tools named for this

  • An anomaly-detection model over encoded ledger attributes
  • A deterministic rules layer encoding the SA 240 characteristics
  • The ERP's own journal export with poster and timestamp retained

What to check before you ship it in India

  • SA 240 paragraph 32(a) makes journal-entry testing mandatory in a statutory audit irrespective of the auditor's assessment of management-override risk, and requires entries made at the end of a reporting period to be selected. It binds the auditor and nobody else. Note the circularity: paragraph 32 exists to test management override, so a screen operated by management is not that procedure and cannot discharge it — the auditor's own selection still has to happen.
  • A ranked posting names the person who made it. Section 8(5) requires reasonable security safeguards over personal data in the fiduciary's control, and a circulated ranking turns an audit working paper into an allegation about an identified colleague.

Sources

Every claim on this page traces to one of these, on the date it was read.