FR 2052a liquidity reporting where every position carries the instruction behind it, every table ties to the general ledger and the Call Report, and a second person approves every change
Every FR 2052a table tied to the ledger and every reclass cited before the ALCO sees it.
See one case, screen by screen ↓FR 2052a liquidity reporting is the Federal Reserve's Complex Institution Liquidity Monitoring Report: a bank with $100 billion or more reports its liquidity position in 13 tables, by product, counterparty, collateral class and contractual maturity bucket. FR 2052a Liquidity Reporting puts agents on the run: they classify each new position with the instruction cited, tie every table to the general ledger and the Call Report, and explain month-over-month moves. Analysts accept, the Treasury Reporting Manager approves and the second line reviews material changes.
AI use cases in banking: a buyer's guide to agentic AI for bank and credit union operations →
Updated
FR 2052a liquidity reporting asks a bank with $100 billion or more in assets for its whole liquidity position in 13 tables: every inflow and outflow by product, counterparty, collateral class and contractual maturity bucket, from Open and Day 1 out past five years. Category IV firms report monthly and submit by T+10. For Corvane National Bank, the fictional regional bank in the working solution, that is about 1.9 million position rows from 43 feeds, built by a team of six within ten business days.
The days go on finding what does not tie. Late or partial feeds are found when a table looks wrong. New products fall to a default mapping. Analysts tie table totals to the general ledger and the Call Report with bridge spreadsheets, differences become emails to data owners, and when a fix cannot land in time a top-side adjustment is booked that nobody retires. Why a position is coded the way it is lives in rule code and in a few people, and one wrong product quietly moves the liquidity numbers: $612.0 million of sweep deposits reported as stable retail understates derived LCR outflows by $58.4 million.
Estimated split of the Federal Reserve's 121-hour estimate for one monthly response, by hand and with the agents. Our arithmetic, kept modest.
Seven agents classify, check, tie out and explain the run; analysts accept, managers approve, risk reviews.
Corvane National Bank runs FR 2052a monthly in parallel ahead of crossing $100 billion. It is Tuesday, October 13, 2026, business day 8 of 10 for the September 30 run, which is due Thursday, October 15. Here is what happens, screen by screen, in the working solution.
Priya opens the September 30 parallel run: 1,899,000 position rows from 43 feeds in 13 tables, drawn as a maturity river from Open to beyond five years. Inflows run above the line and outflows below, and three gaps stand out: $43.7M above the general ledger, −$18.2M against the Call Report and a $612.0M rule break. Under the river, the breaks left today, each with an owner and a due time.
“Breaks today: 4 · 31 opened this month · 27 closed”
The Feed monitor found 42 of 43 feeds complete by 6:10 am. Feed F-27 delivered 3,840 of about 6,200 rows, so Derivatives & Collateral is marked provisional and the other 12 tables ran on. The Classifier proposed a classification for 14,812 new or changed positions, and the Rule agent re-checked every one, agreed with 14,789 and opened 1 rule break and 22 questions. The hand-off sent 4 breaks to their owners with due times.
Liquidity impact agent: 6 pending changes priced · 1 above $25.0M routed to the second line.
Break BRK-0930-014: 2,846 accounts in the treasury sweep program, product code TMS-SWP-03, are reported as O.D.2 Non-Transactional Relationship Accounts under mapping rule PM-118. The Classifier proposes O.D.8 Affiliated Sweep Accounts at 0.97 confidence and splits the insured flag: $560.1M stays FDIC and $51.9M in 96 accounts above $250,000 becomes Uninsured. The Rule agent checked it on its own and agrees.
Analyst accepts · Manager approves · Second line reviews
Every source chip opens what the agents read. The sweep program agreement, DOC-TMS-2291 §2.1 in document imaging, shows the sentence that makes these balances an affiliated sweep, beside the legal entity master entry LE-042 and the FR 2052a instructions for O.D.2 and O.D.8. The agents cite the agreement; they do not change it.
“At the close of each business day, available cash in your brokerage account at Corvane Investment Services LLC is transferred to a deposit account in your name at Corvane National Bank.”
Priya challenges the proposal in plain words. The Classifier answers that the sweeping firm is an affiliate, legal entity LE-042, and that O.D.9 is for unaffiliated firms, with numbered citations to the entity master and the instructions. Beside the conversation, the change is already priced: derived LCR outflows rise from $18.4M to $76.8M, and the derived LCR moves from 122.4% to 121.9%.
Above the $25.0M threshold, Helen Marsh reviews after the manager approves.
Priya accepts with reason code RC-02, instruction requires a different product, and leaves a note for the checker: sweep agreement §2.1 and LE-042 confirm an affiliated nightly sweep, and O.D.2 excludes sweep deposits. The dialog tells her what happens next before she signs.
“You are the maker. Daniel Okafor approves as checker; Helen Marsh reviews because derived outflows move +$58.4M.”
On the approvals queue Priya tries to approve her own reclassification, RC-0930-031, and is stopped: a different person with the Treasury Reporting Manager role must approve it. Every reclassification, top-side adjustment and break closure waits for a second person and is decided before the run's day 9; overdue items escalate to the Head of Treasury.
Policy SOD-01: the maker and the checker of any change must be different people.
Daniel sees exactly what he is signing: 2,846 sweep accounts from O.D.2 to O.D.8, $560.1M insured and $51.9M uninsured, the sources, and +$58.4M of derived outflows. Approving opens source fix SF-0930-022 for Marisol Vega, Deposit Data Owner, due Tuesday, October 20, five business days out, and sends the change to the second line. The override retires when the source is fixed.
“Agree with the analyst. Override until the source is fixed; no top-side adjustment.”
Because the change moves derived outflows by more than $25.0M, it waits for Helen. The derived liquidity view prices every pending change: the sweep reclass adds $58.4M to 30-day net cash outflows, moves the derived LCR from 122.4% to 121.9% and leaves the derived NSFR at 118.5%. She acknowledges it or challenges it.
“Internal view · not a filed ratio”
The readiness view turns six monthly parallel runs into the go-live decision: breaks opened per run fell from 58 in April to 31 in September, the run now completes in 9 business days against a target of 10, and open top-side adjustments fell from 22 to 4. Nine of 12 go-live checklist items are done; Model Risk validation of the Classifier and Rule agent is one of the three still open.
The Readiness agent never marks a checklist item done without its evidence.
The same break, seen by the four people who carry it: what their month looked like, and what it looks like now.
Seven agents classify, check, tie out and explain the run; analysts accept, managers approve, risk reviews.
Counts each of 43 feeds against its expected rows and time, marks partial runs and escalates late feeds to their data owner.
Proposes product, counterparty, collateral class, maturity bucket and insured flag for each new or changed position, from the instrument master, the deposit system, the agreements and the legal entity master.
Re-checks each classification against the FR 2052a instructions, the FAQ and the product mapping rules, and either agrees or opens a rule break.
Ties each table to the general ledger and to the Call Report bridge, and opens a break for the data owner above the tolerance.
Explains each table's month-over-month move by driver, tied to records such as journals and subledgers, with any residual shown.
Prices each pending change in derived LCR and NSFR terms and routes any change over $25 million in derived outflows to the Liquidity Risk Officer.
Builds the ALCO readiness pack from the parallel runs and the export pack for examiners and internal audit.
Accept, approve, review, fix at source. The agents propose; a named person decides.
Ask about the run in plain words, or ask for something to be done. Every answer cites its sources and opens the screen it talks about.
Why are the sweep balances not relationship accounts?
Because they are sweep deposits. The program moves client cash from brokerage accounts at Corvane Investment Services LLC into the bank at each business day's close, that firm is an affiliate, and the instructions exclude sweep deposits from O.D.2 and define O.D.8 for exactly this. Derived LCR outflows rise $58.4M.
What moved Outflows-Deposits since August?
O.D rose $708.3M to $74,612.4M: municipal tax receipts $412.6M, a retail CD promotion $261.0M, other growth $34.7M. Residual $0.0M. The sweep reclass moves $612.0M between products and leaves the total unchanged.
Which breaks could miss the October 15 deadline?
Two need watching. BRK-0930-029: feed F-27 delivered 3,840 of about 6,200 rows and is already past its 11:00 am due time, so it is escalated to Aaron Bell. BRK-0930-021: Kevin Tran's participations fix runs tonight; if it slips, the I.U explanation waits too. The other two are on track.
Prepare the examiner export for September
Ready to build: the September 30 run, 4 breaks, 31 decisions, every classification with its instruction passage, agent and model versions, masked customer data, marked confidential. Choose the audience and it is produced.
12 screens from the working solution, on its sample data. Pick one to see it large.
Tolerances, thresholds, clocks and confidence levels are settings. A change is saved as a new version and takes effect with the manager's approval.
| Setting | Default | Choose from |
|---|---|---|
| Tie-out tolerance per table | $0.5M | Above it, the Tie-out agent opens a break for the data owner |
| Second-line review when derived LCR outflows move by more than | $25.0M | Routes to the Liquidity Risk Officer after the manager approves |
| Classify without a person at confidence | 0.95 and above | 0.80 to 0.95 goes to an analyst; below 0.80 is classified by hand; the Rule agent checks every one |
| Residual limit in change explanations | $5.0M | A larger unexplained residual is shown to the analyst, never hidden |
| Source fix due | 5 business days | Breaks are due by run day 9; overdue items escalate |
| Top-side adjustment escalates after | 2 runs | Open adjustments age run by run on the readiness view |
| Feed counted late after | Calendar time + 60 min | A partial feed marks its table provisional; the other tables run on |
| Customer names and account numbers | Masked except for data owners | Runs, decisions and evidence kept 7 years under the records schedule |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
Sources: Federal Register 2025-02359, February 7, 2025 (121 hours per monthly and 221 per daily FR 2052a response, 1,027,896 hours a year) · FR 2052a instructions (who must report, frequency and timing, O.D products, maturity buckets) · 12 CFR 249.32 (outflow rates for stable retail and affiliated sweep deposits) · 12 CFR 261 (confidential treatment of FR 2052a data). “demo” = seen in the working solution, on its sample data · “target” = design goal, measured in the live solution · “typical” = published figures · “estimated” = our arithmetic, kept modest. Derived LCR and NSFR figures are internal estimates on the sample run, not filed ratios. The bank, its affiliate, its accounts and agreements, and the people named on this page are fictional: characters and sample data in the working solution.
FR 2052a liquidity reporting is the Federal Reserve's Complex Institution Liquidity Monitoring Report: a bank with $100 billion or more reports its liquidity position in 13 tables, by product, counterparty, collateral class and contractual maturity bucket. FR 2052a Liquidity Reporting puts agents on the run: they classify each new position with the instruction cited, tie every table to the general ledger and the Call Report, and explain month-over-month moves. Analysts accept, the Treasury Reporting Manager approves and the second line reviews material changes.
U.S. firms with $100 billion or more report, and Category IV firms report the consolidated entity and the parent company only. Category IV firms, and Category III firms with weighted short-term wholesale funding under $75 billion, report monthly; Category IV firms submit by T+10 and all others by T+2. The solution runs both reports and tracks the run against its due date.
The Tie-out agent checks every table against the general ledger and the Call Report bridge at a tolerance you set, $0.5 million per table in the working solution. A difference above it opens a break for the data owner, placed on the maturity river in the bucket where it sits. Re-running the tie-out after a source fix shows the break close.
The Classifier proposes product, counterparty, collateral class, maturity bucket and insured flag for each new or changed position, and a separate Rule agent re-reads the FR 2052a instructions and FAQ and agrees or opens a rule break. At 0.95 confidence or more, with the Rule agent agreeing, a position is classified without a person; from 0.80 to 0.95 an analyst reviews it, and below 0.80 it is classified by hand. Every position carries the passage that justifies it.
Yes. The Liquidity impact agent prices every pending reclassification and adjustment in derived LCR and NSFR terms, and a change that moves derived outflows by more than $25 million goes to the Liquidity Risk Officer. Every derived figure is labeled internal and is never presented as a filed ratio.
The Feed monitor counts each feed against its expected rows and time. A partial feed marks only its table provisional, the other tables run on, and the data owner is escalated. When the feed lands, the table is re-built and its break closes for review.
Yes. The agents propose, check, price and draft; they never approve, never book an adjustment and never change an approved classification. The analyst accepts with a reason code, a different person approves as checker, the second line reviews material changes, and data owners fix breaks at the source.
The Agentic Solution Engine builds and deploys it from your requirements and documents: your feeds, product mapping rules, general ledger and Call Report bridge, and the agreements behind your products. It goes live once every quality gate has passed; the working solution shows six months run in parallel before the ALCO's go-live decision.
Breaks found and fixed at the source before filing, not after an examiner asks.
1-min demoRegulatory Reporting ControlsThe CFO attests on evidence the agents collected and tested, not on emails.
1-min demoCOREP & FINREP ReportingEvery COREP and FINREP cell traced to its source, and each new release mapped in days.
1-min demoWe'll run FR 2052a Liquidity Reporting on one month of your own position feeds, general ledger and Call Report bridge.