Taskunverified
Revenue and expense anomaly detection
Screen transactions for entries that deviate from expected pattern — unusual timing, round numbers, atypical approvers — before they reach the statements.
consumes
2A canonical data object the task needs as input.
owned by
1The business-partner org unit accountable for the task.
runs in
1The end-to-end shared-services process the task sits inside.
serves
1The verb-level intent the task exists to satisfy.
performed in
2Software the task is actually carried out in.
Unresolved from the source registry
not yet modelledFree-text strings from the source spreadsheet that have not been resolved to a node. Preserved verbatim so nothing is silently dropped — these are backlog, not content.
Produces: Anomaly detection ruleset · Benford analysis