The Compliance Dashboard, and the year it cannot show
This is where on time against late lives, with rejections, named risk violations, and per-user performance for preparation and review. It reads the open period well. The audit question is about the year, and that is the gap this page closes.
Note: ARCS, Oracle's account reconciliation module, tracks whether each period's reconciliations were finished on time and finished properly. The Compliance Dashboard is where that record lives, and this page is how to read it.
One question this page answers: what was our on-time rate, and can we still answer that in October for February? The whole module is mapped on the Account Reconciliation index.
◆ What it shows, doc-verified, on time, late, rejections, violations, per-user metrics, traffic lights.
Per Oracle's dashboards doc, the Compliance Dashboard separates reconciliations completed on time from late ones. It counts rejections and risk conditions, debit and credit violations and aging violations by name. It shows user performance for both preparation and review, with traffic-light indicators you configure against your own quality policy. Everything is security-trimmed: users see the reconciliations assigned to them.
| June, sixty-entity group | Reading |
|---|---|
| On time: 247 of 268 closed, 92.2% | The headline. The other 7.8%, 21 reconciliations, closed late. |
| Rejections: 6 | Counted as events. On the status page those six are invisible, sitting at Open with Preparer, which is why the two reports answer different questions. |
| Risk conditions | Debit and credit violations and aging violations flag themselves; the aging side connects straight to the over-90 story. |
◆ The cross-period gap, the live asks at the edge, and the owned year.
Two live asks mark the edge of the dashboard: exporting a custom dashboard to PDF, and running the numbers across periods, both open questions on the reporting board. The dashboard is a window on the open period; the audit conversation is about the year. The owned model keeps every period's on-time rate, rejection count, and violations, so the February number in October is a query, not a memory. The nightly route is the status export.
The problem: February's on-time rate is unanswerable by October.
What we build: Every period's compliance metrics are kept in your warehouse as they happen.
What you get: The year view of on-time, late, rejections, and violations is a saved query.
- on time
- Closed by the due date. The dashboard's headline split.
- rejection
- A reviewer sends it back. An event, counted here, invisible in status.
- risk condition
- Debit-credit violations and aging violations, flagged by name.
- traffic lights
- Your quality bands, configured, colored, security-trimmed.