F0136: Treasury Concentration Account Framework

Quality / Updated / COI

Quality

Reviewed

Updated

02/14/2026

Source

Citations & Trust

COI

none

TL;DR

Treasury Concentration Account Framework is used for consolidating cash across entities and banks. It organizes idle cash percentage, bank fees per account, sweep yield and balance by entity, payment cutoff times, bank pricing schedule, clarifies the trade off between control and visibility versus operational friction, and preserves assumptions for future cycles.

Applicability

Use this when consolidating cash across entities and banks requires alignment across finance, operations, and leadership. It fits decisions that need numeric justification, clear ownership, and a written rationale. Apply it when balance by entity, payment cutoff times, bank pricing schedule are scattered or when reversal costs are high.

Steps

1. Define scope and horizon, then lock success metrics (idle cash percentage, bank fees per account, sweep yield) and data definitions so teams compare the same baseline.
2. Gather inputs (balance by entity, payment cutoff times, bank pricing schedule) and normalize timing, units, and ownership to remove inconsistencies before analysis.
3. Model scenarios to test how the balance of control and visibility versus operational friction shifts; record thresholds that would change the recommendation.
4. Select a preferred option, document decision criteria, and list approvals or constraints before execution.
5. Set monitoring cadence, owners, and revisit triggers so the decision log stays current as evidence changes.

Template

Template: Background and objective; Scope and time horizon; Success metrics (idle cash percentage, bank fees per account, sweep yield); Key assumptions (balance by entity, payment cutoff times, bank pricing schedule); Options A/B/C; Scenario ranges; Trade off summary (control and visibility versus operational friction); Risks and mitigations; Decision criteria; Recommendation; Owner and timeline; Review triggers. Add data sources, confidence notes, and variables that would change the conclusion.

Pitfalls

• Using inconsistent definitions for idle cash percentage, bank fees per account, sweep yield makes comparisons misleading and erodes trust.
• Ignoring how control and visibility versus operational friction priorities shift over time leads to reversals later.
• Leaving balance by entity, payment cutoff times, bank pricing schedule unverified creates audit challenges and weakens accountability.

Case

Case: A group treasury standardized cash pools across multiple countries. The team mapped idle cash percentage, bank fees per account, sweep yield and aligned balance by entity, payment cutoff times, bank pricing schedule before ranking options. They documented how control and visibility versus operational friction affected the final call and set review checkpoints to prevent drift.

Citations & Trust

• Principles of Finance (OpenStax)