The Problem: Accountability and Verification in Compliance
On October 13, 2026, FinCEN announced a $1.2 billion penalty against Bank of America for failures under the Bank Secrecy Act. The bank failed to report over $5 billion in suspicious transactions on time. Regulators noted the bank's over-reliance on external inquiries to identify activities its own monitoring should have detected.
The lesson for risk managers extends beyond anti-money-laundering rules. It highlights a broken chain: detection was inadequate, escalation was weak, corrective action was inconsistent, and verification was missing. The consent order's requirement for independent reviews of key program elements indicates where regulators see the gap.
This guide outlines a finding-to-verification workflow you can implement in any control environment, focusing on evidence rather than mere documentation.
Prerequisites for Implementation
Before you begin, gather these essential inputs:
- A control inventory with a specific owner for each control. If your register lists a department or shared mailbox as the owner, correct this first.
- Your current issue log, whether it's in a GRC platform, ticketing system, or spreadsheet. Export it and keep a baseline copy.
- A Three Lines Model role map detailing who executes safeguards (first line), who monitors and challenges (second line), and who provides independent assurance (third line).
- Executive sponsorship to enforce escalation deadlines. Without it, the workflow becomes ineffective.
- Your risk appetite or tolerance statements, aligned to the COSO ERM Framework, ensuring severity ratings are consistent.
Step-by-Step Implementation
Step 1: Define a Finding Record with Mandatory Fields.
Configure your issue-tracking tool so no finding can be saved without these fields: control ID, finding description, severity, accountable decision-maker, remediation owner, due date, verifier, and verification evidence link. In systems like Jira or ServiceNow, make these fields mandatory and use a custom workflow to ensure a ticket can't move to "Closed" without a verifier and evidence attachment.
Step 2: Separate Three Roles Often Collapsed into One.
For each finding, assign three distinct roles:
- The decision-maker, who has authority to accept, fund, or defer the fix.
- The remediation owner, who performs the work.
- The verifier, who confirms the fix works and is independent of the remediation work.
Enforce this separation in your tools. A validation rule that prevents the same user ID from appearing in both the owner and verifier fields is effective.
Step 3: Set Escalation Triggers by Severity.
Document these as rules, not judgment calls. For example, any high-severity finding should route to a named executive within a set number of business days. Findings past their due date should auto-escalate one level. Set timeframes according to your risk tolerance and implement these as automated notifications with a documented escalation ladder.
Step 4: Create Distinct Status Values.
Replace a single "Open/Closed" flag with actionable statuses:
- Not yet tested
- Test failed
- Remediation in progress
- Remediation overdue
- Fix awaiting verification
- Verified effective
- Verified ineffective (reopened)
"Completed" is not a status. A finished corrective action isn't evidence the risk is addressed.
Step 5: Define Verification Standards by Severity.
Write a short verification procedure for each severity tier. Lower-severity items may need a second-line review of evidence. Material findings should require re-performance of the control test on a fresh sample, reviewed by someone outside the remediation chain, ideally internal audit. Document the sample selection method and rationale for sample size in the procedure to ensure repeatability.
Step 6: Integrate Monitoring Outputs into the Issue Workflow.
Avoid disconnects between systems. For automated monitoring (SIEM alerts, transaction monitoring queues, access review exceptions), configure an integration or scheduled export that automatically creates a finding record when a threshold is breached or an exception ages past a set limit. Track alert-to-finding conversion to assess whether warning signs are being absorbed or acted upon.
Step 7: Build the Leadership View.
Create a single dashboard or report with status values from Step 4, aging by severity, and overdue items by accountable executive. This shows boards and executives which decisions are pending, not just a compliance percentage.
Validation: How to Verify It Works
Test the workflow to ensure its effectiveness.
- Trace Test. Select a sample of recent findings across severities. Trace each from identification to decision-maker, remediation, verification, and evidence. Any broken link indicates a process defect.
- Seeded Finding Test. Have the second line introduce a controlled test finding and observe whether it reaches the right decision-maker within your defined escalation window. Document actual versus expected timing.
- Reopen Rate Review. If nothing ever fails verification, question the verifier's independence or rigor. A healthy process reopens some fixes.
- Independence Check. Confirm from system logs that verifiers were not remediation owners on the same finding.
- External-Detection Check. Determine how many significant issues in the past year were first identified by regulators, customers, auditors, or other outside parties rather than your own monitoring. This is a direct indicator of monitoring effectiveness.
Maintenance and Ongoing Tasks
- Monthly: Review overdue and awaiting-verification items with accountable executives. Address stalled escalations.
- Quarterly: Re-test a sample of previously verified fixes to confirm they remain effective. Review ownership assignments for departures and role changes.
- Annually: Have internal audit independently assess the workflow itself, covering design and operating effectiveness, consistent with the third-line role. Recalibrate severity thresholds and escalation timelines against current risk tolerance.
- After any significant incident or enforcement action in your sector: Run the trace test against your own environment. Public enforcement outcomes are a prompt to check your own chain.
The measure of success is straightforward. If one of your most critical safeguards stopped working today, you should know how quickly you'd be informed, who is accountable for the fix, and who will confirm it worked.





