Check Failure Triage
Classify quarterly control-check failures by cause, draft the fix and the ticket, and give the reviewer one decision per cause.
At a glance
Every quarter, control checks run across all entities and feed an issue log. A person reads each failure, works out the cause, writes a solution, and creates a ticket. The same failure types come back every quarter: interface issues, stale extracts, mapping gaps, missed process steps. The work is repetitive and concentrated in the busy quarter-end window.
The triage agent helps the team by handling the coordination and drafting. It groups failures that share one cause and drafts one proposal and one ticket per group, each with precedent and a proposed owner. Code checks that no failure was dropped. A reviewer approves, edits, or rejects each proposal, and the agent acts on that decision and logs the resolution. The team spends its time on judgement, not on repetitive work.
- Person: The allowed categories, the routing table, and the log of past resolutions.
- System: The issue log lists control-check results across all entities, with a stable ID for each failure.
- Agent: Failures that share one cause become one cluster with a governed category.
- Agent: One proposal with precedent and one draft ticket with an owner per cluster.
- Code: No failure dropped, no invented category or owner, confirmation flags set.
- Person: Approve, edit, or reject each proposal. One decision per cause.
- Agent: Create the ticket, trigger the re-run, and log the resolution.
- Closed tickets update the log for next quarter
- Primary user
- Finance controls team
- When to use
- Control checks produce failures
- Inputs
- Issue log, routing rules, past resolutions
- Outputs
- Grouped failures and draft tickets
Preview the workflow steps
This section follows through the workflow for one reporting period. Open the review package at the Review stage to see how the agent handles Approve, Edit and Reject.
Start with the issue log
The issue log records the results of control checks run across all entities. Each failure has a stable ID that the agent carries through grouping, review, and resolution. Nothing changes in the control framework.
Issue log | run 2026-Q2
- Checks run
- 41
- Passed
- 26
- Failed
- 15
- Entities
- 6
| Issue ID | Entity | Message |
|---|---|---|
| F-2026Q2-001 | MAA-EU | [ACC-007] Three Q1 accruals not reversed at snapshot time |
| F-2026Q2-005 | MAA-EU | [FX-001] GL rates dated 1 July. Treasury rates for 2 July not received |
| F-2026Q2-006 | MAA-UK | [FX-001] GL rates dated 1 July. Treasury rates for 2 July not received |
| F-2026Q2-010 | MAA-CH / MAA-BM | [IGR-003] Outward 48.2m against inward 44.9m on relationship R-114 |
| F-2026Q2-015 | MAA-UK | [TB-002] Residual 0.018m against a zero tolerance |
End of this guide
Return to the overview, or explore the other guides in the Applied AI library.