WorkflowRegulatory Reporting

Regulatory Reporting Controls

Regulatory reporting controls that put tested, cited evidence behind every signature on the Call Report

The CFO attests on evidence the agents collected and tested, not on emails.

See one case, screen by screen ↓
demo22of 23sub-certifications ready on day 22 of 30, the one blocked branch named with its reason
demo702piecesof control evidence captured this quarter as each control ran, from six systems of record
demo349of 350sample items pass when the Tester re-performs 14 key controls before the CFO signs
target0self-reviewsself-reviewed control instances reach the CFO's attestation
In short

What is Regulatory Reporting Controls?

Regulatory Reporting Controls is software for banks that puts tested evidence behind the CFO's quarterly Call Report attestation. Seven agents capture control evidence as each control runs, challenge it for separation-of-duties breaks and late evidence, re-perform key controls on samples and trace the top Call Report lines to their sources. Process owners sign their sub-certifications, the Controller decides and recommends, and the CFO attests when all of them are signed.

AI use cases in banking: a buyer's guide to agentic AI for bank and credit union operations →

Updated

The problem

Why regulatory reporting controls still rest on emails and a tracker

Regulatory reporting controls are what stand behind one sentence: every quarter the Chief Financial Officer signs the officer declaration on the FFIEC Call Report, that it was prepared to the instructions and is true and correct. Behind that signature sit dozens of controls other people run: reconciliations, reviews, access reviews, change approvals, mapping checks. Today the sub-certification process is a template emailed to 20 to 30 process owners after quarter-end, a spreadsheet of who has signed, and control evidence requested weeks after the control ran.

The risk sits in what nobody checks before the CFO signs. Nobody re-performs the controls first. A preparer who reviewed their own reconciliation is found months later, if at all, by internal audit or the external auditor, and evidence dated after its sign-off is a finding on its own. Nobody can say, line by line, which controls stand behind a Call Report figure, and data quality in regulatory reporting draws enforcement in its own right.

typical30daysto file the Call Report after the report date, with the CFO's declaration and the directors' attestation
typical4,421banksinsured by the FDIC sign a Call Report every quarter
typical$135.6Mpaid by one large bank in 2024, in part over data quality in regulatory reporting
Where a quarter's attestation days goestimated
By hand19 days
With the solution2.2 days
  • Sending sub-certification requests and chasing late owners3 → 0.5 d
  • Gathering evidence from shared drives, logs and tickets6 → 0.5 d
  • Checking who prepared and who reviewed each control2 → 0.2 d
  • Tying the top Call Report lines to their controls3 → 0.3 d
  • Deciding deficiencies and writing the attestation memo2 → 0.5 d
  • Building the evidence pack for auditors and examiners3 → 0.2 d

Estimated split of the Controller's team's days in one quarterly sub-certification cycle, by hand and with the agents; our estimate, kept modest.

How it works

How a control reaches the CFO's signature

Seven agents capture, challenge, re-perform and trace; owners sign, the Controller decides, the CFO attests.

What comes in
Controls run61 key controls, 6 systems · general ledger, regulatory reporting, core, tickets, access, imaging
Agents at work
Evidence agentcaptured as it runs
Then
Skepticself-review, late evidence
Tester25-item samples re-performed
Then
Lineage agenta control on every hop
Deficiency agenta class proposed
Then
Certification coordinatorrequests and escalations
Attestation drafterpacks, every line cited
A person decides
Process owners, Controller, CFO23 owners sign · the Controller decides and recommends · the CFO attests
What comes out
A complete tree of 23 signatures
The CFO's attestation
Examiner evidence pack
One case, step by step

One quarter's attestation, from 22 of 23 to the CFO's signature

Tessaly Community Bank, a $3.4 billion community bank, files its Q3 2026 Call Report (FFIEC 041) by Friday, October 30. It is Thursday, October 22, day 22 of 30. Here is how its regulatory reporting controls reach the CFO's signature, screen by screen, in the working solution.

  1. 01Thursday morning

    The attestation as a tree of named people

    Renata Okafor · Controller

    Renata's home screen is the CFO's attestation as one sentence. Below it she reviews 23 process owners in five areas: loans and credit; deposits, treasury and payments; ledger, tax and capital; reporting and allowance; technology and data. Behind them sit 61 key controls, 702 pieces of evidence, 350 sample items re-performed and 8 Call Report lines traced. One branch is blocked: Dana Ostrow, with a plain “Separation of duties” chip, and the screen offers one next step, open RR-07.

    “22 of 23 sub-certifications ready.”

  2. 02Flagged August 2, 19:07

    The same person prepared and reviewed July

    Skeptic

    RR-07 is the monthly loan subledger to GL reconciliation, owner Dana Ostrow, reviewer Theo Brandt, backup reviewer not set. The July instance was prepared by Dana at 18:52 on Sunday, August 2 and reviewed by Dana at 19:06, on the same workstation. Theo was on leave and no backup was set. Dana replied that she would route it for re-review; it was never routed. August and September were reviewed by Theo.

    The Skeptic never closes its own flag and never flags without a citation.

  3. 03One click

    Every statement opens to its source

    Renata Okafor · Controller

    Each citation in the finding opens the passage it rests on. Here it is the general ledger sign-off log entry GLS-0802-0418: the July loan reconciliation, reviewed by D. Ostrow at 19:06:41 on August 2, status Reviewed. The Evidence agent captured it when the control ran, with its time and hash, and nobody can edit it.

    “Captured by the Evidence agent with its time and hash. Read-only.”

  4. 04Before anyone re-signs

    July re-performed in full: it ties

    Tester

    The Tester re-foots the loan subledger at July 31, $2,481,659,357, and agrees the reconciling item to payment batch PB-0731-22: $246,857, in the subledger on July 31 and the ledger on August 3. The adjusted subledger, $2,481,906,214, matches the July 31 trial balance of GL accounts 1400–1490. Every line of the arithmetic cites its source.

    “Ties · difference $0.00”

  5. 05The fix, governed

    Only independent people can be picked

    Renata Okafor · Controller

    Renata assigns an independent reviewer with reason code IR-01, “Preparer reviewed own work”. The picker offers Theo Brandt, back from leave and read-only in the loan subledger, and Andre Whitaker, the Assistant Controller. Dana Ostrow cannot be chosen because she prepared the instance, and neither can Victor Almeida, who has posting rights in the loan subledger.

  6. 06Working as Dana

    The preparer cannot review her own work

    Dana Ostrow · Loan Accounting Manager

    Dana opens RR-07 and tries to re-review the July reconciliation herself. The system refuses, names the rule and names the person who must do it. Separation of duties in accounting is enforced here, not left to a policy document.

    “A preparer cannot review her own work. You prepared the July reconciliation of RR-07. The re-review must be done by Theo Brandt.” Rule SOD-1

  7. 07Signed

    An independent review, re-checked

    Theo Brandt · Senior Accountant

    Theo re-reviews with the tie-out in front of him and signs. The Skeptic re-checks his independence: he is not the preparer and has read-only access to the loan subledger. The Deficiency agent then proposes DEF-Q3-03 as a control deficiency, not significant, because the balance ties and the variance review RR-03 operated.

    “Independent review signed by Theo Brandt.”

  8. 08The decision

    The agent proposes, the Controller decides

    Renata Okafor · Controller

    The proposal shows its reasoning: likelihood, one instance of three this quarter; magnitude, re-performance ties with a difference of $0.00; compensating control, RR-03 operated. Renata accepts it as a control deficiency, with backup reviewer Andre Whitaker set for RR-07. Four deficiencies this year, none significant and no material weakness. Dana signs her sub-certification and the tree reads 23 of 23.

    Anything above a control deficiency goes to the Audit Committee.

  9. 09What stands behind a line

    From the core banking system to RC 4.b

    Lineage agent

    Loans and leases held for investment, Schedule RC item 4.b, is $2,512,384,906 at September 30. The Lineage agent traces it from the core banking system (18,412 loan accounts) to the loan subledger, GL accounts 1400–1490, the regulatory reporting system's mapping rule and the Call Report line, with a key control on every hop: RR-05, RR-07, RR-01, RR-04 and RR-03. All 8 top lines are covered; in June it found the brokered-deposit hop on RC-E that no control covered, and RR-26 was added.

    The Lineage agent never changes a mapping; it flags a gap and never fills it.

  10. 1010:31 · eight days early

    The Controller recommends, the CFO attests

    Graham Pell · Chief Financial Officer

    Everything that stands behind the officer declaration is listed and open, 7 of 7 clear: 23 of 23 sub-certifications, 61 of 61 key controls evidenced, 349 of 350 items re-performed, 8 of 8 lines traced, no open separation-of-duties breaks, every deficiency decided. Renata recommended; Graham attests. Three directors attest at the October 27 board meeting, and the report is filed from the regulatory reporting system by October 30.

    The Controller who recommends can never attest, and the CFO cannot recommend. Rule SOD-6

Who it’s for

Built for everyone who signs behind the CFO.

The same quarter, seen by the four people who carry the attestation: what it looked like, and what it looks like now.

RO
Renata OkaforController · reviews all 23 sub-certifications
Controller
Before
Emails templates to the process owners, tracks signatures in a spreadsheet and asks for evidence weeks after each control ran.
Now
Opens a tree of named people with the one blocked branch and its reason; spends her day on the decisions: who reviews, how to classify, whether to recommend.
DO
Dana OstrowLoan Accounting Manager · owns RR-05 to RR-08
Process owner
Before
With her reviewer on leave, reviewed her own July reconciliation and meant to route it back; nobody noticed it was never routed.
Now
The system will not let her review her own work. Her sub-certification is blocked until an independent review is signed, then she signs it.
SA
Simone AchebeInternal Audit Manager · reports to the Audit Committee
Internal Audit Manager
Before
Tests six key controls herself, with her own samples, and must show she stays independent of management.
Now
Reads the agents' re-performance without relying on it, records her own results in her own lane, and cannot sign, assign or revoke anything.
GP
Graham PellCFO · signs the Call Report's officer declaration
Chief Financial Officer
Before
Signs the declaration every quarter on the strength of a tracker full of sub-certification emails.
Now
Attests only when 23 of 23 have signed and the Controller has recommended, with everything behind the declaration listed and open.
Built on the engine

7 agents. Each with one job, and hard limits.

Seven agents capture, challenge, re-perform and trace; owners sign, the Controller decides, the CFO attests.

Evidence agent

Captures evidence the moment each control instance completes: GL sign-offs and reconciliations, change tickets, access reviews, checklists and committee minutes. Records when and by whom each piece was produced, and hashes it.

  • Never accepts evidence it cannot timestamp
  • Never edits a source file
Skeptic

Challenges every piece of evidence: a preparer who reviewed their own work, evidence dated after its sign-off, a reviewer without independence or with posting rights. Holds the sub-certification until a person decides.

  • Never closes its own flag
  • Never flags without a citation
Tester

Re-performs 14 key controls on 25-item samples, and every flagged instance in full: re-foots, re-ties and re-checks independence, showing the arithmetic and marking each item pass or exception.

  • Never concludes for internal audit
  • Never re-performs on data it cannot cite
Lineage agent

Traces the top Call Report lines from the source systems through the mapping rules and the GL to the line, and names the key control that guards every hop.

  • Never changes a mapping
  • Flags a hop with no control, never fills it
Deficiency agent

Proposes a classification (control deficiency, significant deficiency or material weakness) with its likelihood, magnitude and compensating-control reasoning, using the bank's severity guide.

  • Never decides
  • Anything above a control deficiency goes to the Audit Committee
Certification coordinator

Sends the sub-certification requests on day 6, reminders 7 and 2 days before the due date, and escalations to the Controller on day 21 and to the CFO on day 24.

  • Never signs
  • Never extends a deadline
Attestation drafter

Assembles the attestation memo and the evidence packs for the external auditor, examiners, the Audit Committee and internal audit, every statement cited to its evidence.

  • Never signs
  • Never includes data the recipient may not see
Process owners, Controller, CFO

Sign · decide and recommend · attest. The agents propose; a named person decides.

Ask in plain words

Ask about any control, owner or Call Report line

Ask the agents in plain words about a control, a person, a piece of evidence or a line. Every answer cites its source, and some open the screen for you.

Why is Dana Ostrow's sub-certification blocked?

Because one of her four controls has an open flag. RR-07, the monthly loan subledger to GL reconciliation, was prepared and reviewed by Dana Ostrow for July: prepared at 18:52 and reviewed at 19:06 on Sunday, August 2. Her reviewer, Theo Brandt, was on leave and no backup was set. August and September were reviewed by Theo. Next step: assign an independent reviewer.

Which controls stand behind the loans line on the Call Report?

Schedule RC item 4.b, $2,512,384,906, passes through five hops. Each has a key control: RR-05 core to subledger, RR-07 subledger to GL, RR-01 GL to the report, RR-04 the mapping rule LN-RC4B, and RR-03 the second-preparer variance review. RR-07 is the only one with an open flag.

What has changed since last quarter's attestation?

Three things. One new deficiency is waiting for you: DEF-Q3-03 on RR-07. Two were decided this quarter, on RR-44 and RR-33. And the FDIC's Part 363 thresholds moved on January 1: the internal control assessment now applies from $5 billion, so Tessaly keeps it under board policy.

Prepare the evidence pack for the external auditor

Started the external auditor pack for Q3 2026: 23 sub-certifications, 61 controls with 702 pieces of evidence, the Tester's 350 sample items, 8 lineage traces and 4 deficiencies, with every sign-off and reason from the audit trail. Customer account numbers are masked, and no BSA records are included. It is waiting for your release.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

The attestation treeThe CFO's Call Report attestation as one sentence, 22 of 23 sub-certifications ready, with the 23 process owners behind it in five areas and the one blocked branch named.
The Skeptic's findingControl RR-07, the loan subledger to GL reconciliation: the July instance prepared and reviewed by the same person, 14 minutes apart, with the sign-off log cited.
Every statement opens to its sourceA citation opens the general ledger sign-off log entry that shows the same user reviewed the July reconciliation, captured with its time and hash.
Re-performed before anyone re-signsThe Tester re-performs the flagged July reconciliation in full: the subledger ties to the general ledger at $2,481,906,214, difference $0.00, each line cited.
Assign an independent reviewerOnly independent people can be picked, with a reason code; the preparer and anyone with posting rights in the loan subledger cannot be chosen.
Separation of duties, enforcedWorking as the preparer, a re-review of her own reconciliation is refused, naming rule SOD-1 and the person who must do it.
Independent review signedThe independent reviewer signs, the Skeptic re-checks his independence, and the Deficiency agent proposes a control deficiency for the Controller.
Deficiencies, proposed and decidedFour deficiencies this year, none significant and no material weakness, each with the agent's likelihood, magnitude and compensating-control reasoning and the Controller's decision.
Lineage to the Call Report lineRegulatory reporting data lineage for the top eight Call Report lines, from the source systems to the line, with the key control that guards each hop.
Control testing and internal audit349 of 350 sample items pass across 14 key controls, the one exception decided with a reason code, beside internal audit's own independent results.
The CFO's attestationEvery branch signed and every deficiency decided: the Controller has recommended, and the CFO attests with everything behind the officer declaration listed and open.
Audit trail and examiner packEvery action by people and agents with its reason and evidence, and a watermarked pack for FDIC examiners that waits for the Controller's release.
Roles and separation-of-duties rulesThe administrator area: roles and who sees customer data, and six separation-of-duties rules that are enforced, never advisory.
Governance

Regulatory reporting controls that are cited, separated and signed.

Every statement cites its sourceEach finding, value and answer links to the passage it rests on: the GL sign-off log, a ticket, an access review, a reconciliation, a mapping rule. Evidence is timestamped and hashed when the control runs, and read-only.
Separation of duties, enforcedSix rules, never advisory: a preparer never reviews the same instance, an owner never tests their own controls, only the owner signs a sub-certification, internal audit stays independent, and the Controller recommends while the CFO attests. A blocked action names its rule.
A maker and a checker on every decisionOwners sign and the Controller reviews; an agent proposes a deficiency and the Controller decides; the Controller recommends and the CFO attests. A settings change proposed by one administrator is approved by the other.
Agents propose, people decideAgents never sign, never close their own flags, never change a mapping and never decide a deficiency. Instructions and models are versioned, and below its confidence threshold a finding shows as “possible”, never as a flag.
One audit trail, packs for examinersEvery action by people and agents is recorded with who, what, when, the reason code and the evidence, kept 7 years. Packs for the external auditor, FDIC examiners, the Audit Committee and internal audit are watermarked, released by the Controller and expire after 14 days.
Customer data stays protectedLoan and deposit numbers in samples are masked; the Controller and internal audit can unmask for 5 minutes, logged. BSA and SAR records are never sampled or exported, and a SAR's existence never appears here.
Configuration

Your control program, your calendar, your rules

The calendar, sample sizes, thresholds and data rules are settings. Every change waits for a second administrator and is on the change history.

SettingDefaultChoose from
Sub-certification requests go outDay 6 after quarter-endReminders 7 and 2 days before due, by email and chat
Sub-certifications dueDay 20Escalate to the Controller on day 21 and to the CFO on day 24
CFO attests byDay 29The Call Report is due on day 30
Sample size25 items for daily and per-transaction controlsEvery instance for monthly and quarterly controls
Agent confidence thresholdsSkeptic 0.80 · Lineage agent 0.90 · Deficiency agent 0.85Below the threshold a finding shows as “possible”, never a flag
Customer numbersMasked to the last 4 digitsThe Controller and internal audit can unmask for 5 minutes, logged
Keep evidence and sign-offs7 years, bank policyAny BSA record kept at least 5 years; BSA and SAR records never sampled or exported
Examiner and auditor accessRead-only, released packs onlyExpires after 14 days
Connections

Works with the systems your controls already run in

General ledgersign-off log, reconciliations, journal entries
Regulatory reporting systemedit runs, mappings, variance reviews
Core banking systeminterface totals, payment batches
IT service managementchange tickets and approvals
Identity and access managementaccess reviews, entitlements
Document imagingchecklists, committee minutes, workpapers
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
61 of 61
key controls with evidence captured as they run, not requested at quarter-end
61 key controls
702 pieces of evidence this quarter
target
0
self-reviewed control instances reach the CFO's attestation
target
8days
before the 30-day Call Report deadline, the CFO attests

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures and rules: FDIC FIL-44-2013, Call Reports due within 30 calendar days of the report date; FFIEC 041 cover page, the officer declaration and the directors' attestation; FDIC Quarterly Banking Profile, second quarter 2025, 4,421 FDIC-insured institutions; Federal Reserve and OCC enforcement actions of July 10, 2024, $135.6 million in penalties against one large bank, in part over data quality in regulatory reporting; 12 CFR 363 guidance and the FDIC's thresholds from January 1, 2026. Tessaly Community Bank, the people, controls and balances named on this page are fictional: characters and sample data in the working solution.

Questions

What Controllers and CFOs ask us.

What is Regulatory Reporting Controls?

Regulatory Reporting Controls is software for banks that puts tested evidence behind the CFO's quarterly Call Report attestation. Seven agents capture control evidence as each control runs, challenge it for separation-of-duties breaks and late evidence, re-perform key controls on samples and trace the top Call Report lines to their sources. Process owners sign their sub-certifications, the Controller decides and recommends, and the CFO attests when all of them are signed.

How does the sub-certification process work?

The Certification coordinator sends each process owner a request on day 6 after quarter-end, reminds them 7 and 2 days before the day-20 due date, and escalates to the Controller on day 21 and to the CFO on day 24. An owner can sign only when their controls have no open flags. The Controller can revoke a signature with a reason when its evidence changes.

How does it catch separation of duties breaks?

The Skeptic compares the preparer and reviewer of every control instance in the sign-off log, checks reviewers for independence and posting rights, and flags evidence dated after its sign-off. Each flag cites the log entry and holds the sub-certification until a person decides. The system itself refuses a preparer who tries to review the same instance.

Does it test the controls or only collect evidence?

It tests them. The Tester re-performs 14 key controls on 25-item samples and every flagged instance in full, showing the arithmetic with its sources and marking each item pass or exception. In the sample quarter, 349 of 350 items pass and the one exception is decided by the Controller with a reason code. Internal audit tests on its own and records its own results.

Can we trace a Call Report line back to its source systems?

Yes, for the top Call Report lines. The Lineage agent traces each one from the core banking system through the subledger, the general ledger and the mapping rule to the line, and names the key control on every hop. A hop with no control is flagged for a person to close; the agent never changes a mapping.

Do people stay in control?

Yes. Agents never sign, never close their own flags and never decide a deficiency. Owners sign their sub-certifications, an independent reviewer re-reviews, the Controller decides deficiencies and recommends, and the CFO attests; anything above a control deficiency goes to the Audit Committee. Every override needs a reason code.

What do examiners and auditors get?

One audit trail of every action by people and agents, with who, what, when, the reason and the evidence, and packs built for the external auditor, FDIC examiners, the Audit Committee and internal audit. Packs are watermarked, mask customer numbers, exclude BSA and SAR records, and are released by the Controller; examiner access is read-only and expires after 14 days.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents, such as your control library, sub-certification templates and a past quarter's sign-offs, and it goes live once every quality gate has passed. We will walk you through it on your own controls first.

See it on
your Call Report.

We'll run Regulatory Reporting Controls on your own control library and a past quarter's sign-offs.