Notebook with charts beside a laptop on a desk

The detection map

A shared picture of which ledger surfaces matter, which behaviours are expected, and which exceptions earn review time before close.

Four layers we chart before the first flag

Anomaly work without a map produces noise. We draw the map with your finance owners, then run detection against it.

Entity and period boundaries

We name the legal entities, books, and close periods in scope. Out-of-scope ledgers stay listed so silence is intentional.

Account behaviour profiles

Quiet accounts, calendar-pulsing accounts, and temporary clearing accounts get different expectations. Outliers are judged against those profiles.

Journal and suspense pathways

Manual journals, automated feeds, and suspense clearances are traced to owners. Broken pathways become detection priorities.

Exception routing

Each flag type maps to a reviewer, a materiality cue, and a close-calendar checkpoint—so findings arrive with somewhere to go.

What we ask you to bring

  • A named finance owner for access and scheduling
  • Read access to the ledgers and journal reports in scope
  • Your current close calendar and materiality guidance
  • Two or three recent exceptions you already know about

What this page is not

  • A software product demo or dashboard preview
  • A guarantee that every irregular posting is fraudulent
  • A checkout path—engagements are scoped and invoiced separately