Accounting › Finance Intelligence
Detector Performance
Precision — of the signals it raised, how many were real. The only number that decides whether a detector should keep running, and the reason outcomes are recorded at all.
Where to find it
- Module: Accounting
- Group: Spend & Risk
- Section: Finance Intelligence
- Screen: Detector Performance
Address in the console: /accounting/detector-performance
Read-only list · 14 columns
This list is read-only: its records are written by the work that produces them. A correction, where one is possible at all, is made where the record was created.
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Period | Code | period_code |
| Detector | Code | detector_code |
| Name | Text | detector_name |
| Domain | Status | domain |
| Signals | Number | signals_raised |
| Cases | Number | cases_opened |
| Real | Number | true_positives |
| Noise | Number | false_positives |
| Precision % | Number | precision_pct |
| Alerts / finding | Number | alerts_per_finding |
| Flagged | Amount | amount_flagged |
| Confirmed | Amount | amount_confirmed |
| Recovered | Amount | amount_recovered |
| Median hours | Number | median_resolution_hours |
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.