Demonstration
User Scenarios
Five scenarios that can be run end to end in this prototype. Each one uses fictional personas and synthetic journals.
Accounting reconciliation exception
Sarah Thompson, Senior FP&A Analyst
JE-2026-09161Not assessedNot submitted$12,840,000.00
- Trigger
- A network infrastructure accrual is prepared for the September close.
- Agent work
- Source Data, Preparation, Controls, Anomaly Detection and Risk Scoring agents review the journal and reconcile it to the vendor statement.
- Detection
- Deterministic control FIN-CTL-014 fails: the journal amount exceeds the supporting evidence by CAD 18,250.
- Human decision
- Sarah inspects the evidence, corrects the amount and records a reason.
- Outcome
- Controls rerun and pass, risk falls from high to low, the controller approves and a simulated submission is created.
- Business value
- The exception is caught before submission rather than after an Oracle rejection or a post-close adjustment.
Structurally invalid upload template
Daniel Brooks, Financial Analyst
JE-2026-09125BlockedNot submitted$1,245,430.00
- Trigger
- A completed template is prepared using an outdated version.
- Agent work
- The Oracle Upload Readiness agent evaluates file integrity, structure, headers, lines and accounting validity.
- Detection
- Missing cost centre, wrong date format, invalid batch characters, an unbalanced entry and a stale template version.
- Human decision
- Daniel applies safe automatic fixes, resolves the judgment items and reruns validation.
- Outcome
- The template becomes upload ready and moves into the approval queue.
- Business value
- Failure detection moves from Oracle submission time to journal preparation time.
Segregation of duties conflict
Priya Shah, Accounting Manager
JE-2026-09149Corrections requiredNot submitted$684,200.00
- Trigger
- The preparer is also listed as the approver on a material journal.
- Agent work
- The Controller Review Routing Agent validates authority and independence before routing.
- Detection
- Self-approval is blocked by control FIN-CTL-020 and a security event is raised.
- Human decision
- An independent approver is assigned with a mandatory comment.
- Outcome
- The journal is approved by an independent controller and the denied attempt remains in the audit trail.
- Business value
- Segregation of duties is enforced by the system, not by convention.
Historical anomaly
Alex Morgan, Controller
JE-2026-09172Ready with warningsAwaiting approval$4,725,000.00
- Trigger
- A wireless revenue reclassification is materially larger than its historical pattern.
- Agent work
- Anomaly Detection compares the entry with twelve periods of synthetic history and explains the variance.
- Detection
- The amount is well outside the historical band, raising the risk score.
- Human decision
- The controller reviews the explanation and requests further evidence before deciding.
- Outcome
- The journal is returned for correction with a recorded reason.
- Business value
- Unusual entries are surfaced with an explanation instead of being discovered in review.
Evidence mismatch
Samantha Roy, Internal Audit
JE-2026-09138Corrections requiredReturned$937,500.00
- Trigger
- Supporting evidence does not agree with the journal amount.
- Agent work
- The Audit and Evidence agent checks completeness, classification and checksum linkage.
- Detection
- Evidence total differs from the journal total and one artefact is classified Restricted Financial.
- Human decision
- Audit inspects the evidence chain and the export attempt blocked by data loss prevention.
- Outcome
- The journal stays blocked until reconciled evidence is attached.
- Business value
- Every approved journal carries a complete, attributable evidence chain.
All personas, vendors, journals and amounts are fictional. Scenario outcomes are produced entirely inside the browser with no production connectivity.