What Treasury Services and Payments actually is.

1.1The wholesale payments business in one paragraph

A bank's Treasury Services & Payments business — sometimes called Wholesale Payments, sometimes folded into a Commercial & Investment Bank segment, sometimes broken out as a Payments division of its own — is the part of the bank that moves money for other businesses. Not consumer banking. Not retail. Wholesale. The customer is a corporation, a financial institution, a government, or a marketplace platform; the activity is some combination of holding their cash, moving their cash, financing their working capital, and giving them tools to do all of that themselves. Globally, the largest banks in this business move trillions of dollars per day across more than a hundred currencies and most of the world's countries. That scale is the single most important fact about the business, because almost every economic mechanism we'll discuss in this handbook is, at root, a way to monetize the information, liquidity, and movement that flows through that pipe.

1.2Where TS&P sits in a bank's segment reporting

If you open a U.S. money-center bank's 10-K, the wholesale payments business is rarely a top-level reporting segment. It's usually nested inside a Commercial & Investment Bank or Wholesale Banking segment, sometimes broken out at the sub-segment level as "Payments" or "Treasury Services." That structural choice has real consequences for the controller: revenue, expense, and capital allocation between TS&P and adjacent businesses (Markets, Commercial Banking, Securities Services) is determined by internal rules that aren't always intuitive, and that the consolidated financials don't make visible.

For example, FX revenue from a cross-currency wire is typically booked in the Markets segment because Markets takes the price risk; TS&P gets a relationship credit through internal transfer pricing. Custody and securities lending revenue, which look adjacent to TS&P, sit in Securities Services. Merchant acquiring is in TS&P at most banks but is sometimes broken out separately. The TS&P controller's first job is to know exactly where the lines are drawn at their bank.

1.3The customer set

Five archetypes account for almost all TS&P revenue:

• Corporates — multinationals, mid-market companies, public sector. They need cash management, payments, FX, working capital, and trade finance. The largest single segment by revenue.
• Financial institutions — other banks, broker-dealers, asset managers, insurers. They use the bank as a correspondent or for specialty services like clearing, custody-adjacent flows, and FX.
• Public sector — federal, state, local governments and supranationals. Often large, often sticky, often low-margin but high-volume.
• Marketplaces and platforms — increasingly the fastest-growing segment. Marketplaces, gig platforms, embedded finance partners. Treasury-as-a-service revenue lives here.
• Fintechs — banked by specialized desks. The product set is similar to corporate but the operational and KYC profile is different.

1.4Why this business exists

Strip away the product catalog and TS&P does four economic things for its clients, simultaneously: it holds their cash (deposits), it moves their cash (payments), it informs them about their cash (reporting and channels), and it extends credit when their cash is short (committed lines, daylight overdrafts, trade finance). The bank gets paid in different ways for each function, and the same client transaction usually touches multiple functions at once. A cross-border wire, for instance, simultaneously involves a deposit movement (the source DDA debit), a payment (the wire), an information event (the client gets a confirmation, the analysis statement gets a fee line), and possibly a credit event (if the wire ran ahead of inflows, a daylight overdraft).

1.5The three economic engines

From a P&L perspective, those four functions collapse into three revenue engines:

1. Net interest income (NII) from holding deposits. This is the largest line for most relationships and is usually invisible on the client invoice.
2. Fee income for movement and service — the visible line on the analysis statement.
3. FX margin for currency conversion — booked in Markets, allocated operationally.

Chapter 2 takes this apart in detail. The point for now: a controller who looks at fee revenue alone will misread every TS&P relationship. The deposit-driven NII almost always dominates.

1.6What this handbook covers — and doesn't

This handbook covers the bank-side view of TS&P products: the mechanics of each product, how revenue is generated, the accounting policies that govern recognition and reserves, the operational reality of running the close, and the forward-looking trends that are reshaping all of it. It does not cover capital markets businesses (securities lending, prime brokerage, derivatives clearing), retail consumer banking, asset management, or insurance. It also intentionally leaves merchant acquiring at a high level — that vertical is covered in detail at paymentscontroller.com, and this handbook cross-references rather than duplicates.

The bank's balance sheet from a TS&P lens.

3.1The shape of a bank balance sheet

A bank's balance sheet, simplified to the level a TS&P controller cares about, has roughly this structure:

Most TS&P activity touches the deposit liability lines (right side, top) and the cash, repo, and securities lines (left side, top). The credit-adjacent products in TS&P — drawn LCs, supply chain finance receivables, working capital revolver draws — touch the loans line. Daylight overdraft exposure shows up in regulatory schedules but not on the balance sheet itself.

3.2Where TS&P deposits live

The deposit base is the largest single TS&P-driven balance-sheet line. For a U.S. money-center bank, deposits typically split:

• Non-interest-bearing demand deposits — operating DDAs of corporate, public-sector, and FI clients. The most valuable category by FTP credit, regulatory treatment, and stickiness.
• Interest-bearing demand deposits — including NOW accounts, money-market deposit accounts, and interest-bearing operating accounts.
• Time deposits — CDs, brokered CDs, and structured time deposits.
• Foreign deposits — booked at non-U.S. branches, primarily Eurodollar deposits.

For TS&P specifically, the operational deposit category (non-interest-bearing DDAs of operating clients) gets the most favorable treatment under both LCR and FTP. Time deposits and brokered deposits, while still TS&P-adjacent at some banks, are treated as non-operational and earn a smaller spread.

3.3How operating deposits get deployed

The asset side of the balance sheet shows where deposits go. Conceptually, every dollar of deposit either: (a) earns reserves at the Fed (IORB), (b) gets invested in securities, (c) funds a loan, or (d) sits in cash equivalents. The mix varies by bank and over time, but the deployment is what generates the spread that flows back as FTP credit.

For an "ample reserve" period like the post-2020 era, the largest banks hold significant excess reserves at the Fed. The IORB rate, set by the FOMC, is the floor on the bank's deposit deployment yield. A TS&P controller should know the prevailing IORB because the bank's deposit-deployment economics — and therefore the FTP curve — are anchored there.

3.4The capital stack

Banks are required to hold capital against their assets. The three layers that matter for TS&P:

• Common Equity Tier 1 (CET1) — common stock and retained earnings, the highest-quality capital. Minimum 4.5% of risk-weighted assets, plus buffers.
• Additional Tier 1 (AT1) — preferred stock and certain hybrid instruments.
• Tier 2 — subordinated debt and certain reserves.

For TS&P, the most relevant question is which products are capital-intensive (high RWA per dollar of revenue) vs. capital-light. Pure deposit products are very capital-light: a $100M operating deposit might consume only a few hundred thousand dollars of capital across all ratios. A drawn LC or supply chain finance receivable, by contrast, gets full credit RWA treatment and is capital-heavy.

3.5Risk-weighted assets and TS&P

Risk-weighted assets (RWA) are calculated under standardized or advanced approaches (Basel III). The standardized approach assigns a risk weight to each exposure category:

• Cash and Fed reserves — 0% (zero RWA).
• U.S. Treasury securities — 0%.
• Highly-rated corporate exposures — 20% to 100% depending on rating.
• Unrated corporate loans — 100%.
• Off-balance-sheet commitments — converted to on-balance-sheet equivalent via Credit Conversion Factor (CCF), then risk-weighted.

The TS&P controller's job in capital terms: tag each balance-sheet exposure with its correct risk weight, ensure off-balance-sheet exposures are CCF-converted correctly, and feed the resulting RWA into the bank's regulatory capital reporting.

3.6The leverage ratio constraint

Beyond risk-based ratios, U.S. banks are also subject to the supplementary leverage ratio (SLR) — Tier 1 capital divided by total leverage exposure (essentially total assets plus off-balance-sheet items, with limited netting). The SLR is non-risk-based: a low-risk Treasury security consumes the same SLR capacity as a high-risk corporate loan.

Why this matters for TS&P: when an FI client deposits a large balance with the bank, the bank receives a deposit liability and an offsetting reserve asset (earning IORB). The risk-weighted ratio impact is near-zero. But the SLR impact is meaningful — that reserve asset shows up in total leverage exposure even though it's risk-free. During periods of large FI deposit inflows, the SLR can become the binding capital constraint at the largest banks, and TS&P pricing reflects that.

3.7The LCR constraint

The Liquidity Coverage Ratio (LCR) requires banks to hold enough High-Quality Liquid Assets (HQLA) to cover 30 days of stressed net cash outflows. The numerator is HQLA; the denominator is stressed outflows minus capped inflows.

For TS&P, the deposit categorization rules in the LCR framework drive most product economics:

• Operational deposits from corporate, public-sector, and certain FI clients receive 25% outflow assumption (most favorable).
• Non-operational deposits from corporates receive 40% outflow assumption.
• Non-operational FI deposits receive 100% outflow assumption (least favorable).
• Brokered and unsecured wholesale funding receive 100%.

The LCR classification of a deposit is consequential. A single relationship's deposit balance, classified as operational, can be worth materially more to the bank than the same dollar amount classified as non-operational — because the lower outflow assumption frees up HQLA capacity that can be deployed elsewhere.

3.8Off-balance-sheet exposures

TS&P generates substantial off-balance-sheet exposure that doesn't appear in the simplified balance sheet above:

• Unfunded committed credit lines — undrawn portion of corporate revolvers.
• Unused standby letters of credit — issued and outstanding but not drawn.
• Trade letters of credit — documentary LCs in process.
• Daylight overdraft exposure — intraday extensions of credit.
• Notional amount of derivatives — FX forwards, options, IR swaps held for client business.

These show up in regulatory schedules (Call Report Schedule RC-L, Federal Reserve Y-9C) and in disclosures, but not in the GAAP balance sheet. They generate CECL allowance (Ch 43, recorded as a liability), regulatory capital consumption (via CCFs), and operational risk capital. For the controller, the off-balance-sheet schedule is its own reconciliation — and the most common place where regulatory disclosures and GL feeds drift apart.

Demand deposits, the Earnings Credit Rate, and hybrid pricing.

5.1What a corporate DDA actually is

A corporate demand deposit account is a deposit liability of the bank. Mechanically: the corporate hands the bank money (via wire, ACH, deposit, sweep), the bank credits the DDA, and the corporate has a contractual right to demand that money back at any time. On the bank's balance sheet, that's a deposit liability on the right side; on the corporate's balance sheet, it's cash (or cash equivalents) on the left side.

Two flavors matter for what follows:

• Interest-bearing DDAs. The bank pays explicit interest on the balance, recorded as interest expense.
• Non-interest-bearing DDAs. No interest is paid. Instead, an earnings credit is applied — but only to offset fees, never to be paid out as cash.

Whether an account is interest-bearing or not has real regulatory and capital consequences. Non-interest-bearing deposits get the most favorable treatment under the LCR (lower outflow assumption for operational deposits) and the lowest cost in capital terms. They also get the best FTP credit at most banks, because they're behaviorally stickier than interest-bearing balances.

5.2Why non-interest-bearing accounts exist at all

For most of U.S. banking history, paying interest on commercial demand deposits was illegal. Regulation Q, born of the Glass-Steagall era, prohibited it for nearly eighty years. Banks needed a way to compete for corporate deposits despite the prohibition, and the Earnings Credit Rate is what they invented.

Reg Q was repealed for commercial accounts in 2011. Banks could legally pay interest on commercial demand deposits starting then. And yet — fifteen years later — non-interest-bearing accounts and ECR pricing dominate corporate cash management. Why? Three reasons:

1. Regulatory and capital treatment. Non-interest-bearing operating deposits get favorable LCR treatment and tend to receive higher FTP credit. Banks earn more on them.
2. Corporate accounting and tax conventions. Many corporate treasuries find ECR easier to budget — fee offsets are predictable; interest income is a separate line that gets taxed and managed differently.
3. Bank revenue retention on unused credit. ECR is a "use it or lose it" credit. If a client's monthly earned credit exceeds their fees, the unused portion typically expires. The bank's economic value of the deposit is fully captured; only the portion needed to offset fees is "spent" on the relationship.

5.3The ECR mechanic

The standard ECR formula:

Earnings Credit = Average Collected Balance × ECR Rate × (Days / 360) × (1 − Reserve Requirement)

Each component:

• Average Collected Balance — the daily-average cleared balance over the period. "Collected" means after float on deposited items, not the ledger balance.
• ECR Rate — the bank-set crediting rate, usually a function of a benchmark (e.g., 90-day T-bill) plus or minus a spread. Posted on the analysis statement.
• Days / 360 — money-market convention. Some banks use 365.
• Reserve Requirement — a haircut representing the portion of the deposit that the bank can't deploy because of Reg D reserve requirements. Reserve requirements went to zero in March 2020 and have remained there, but the ECR formula often still includes a notional 10% haircut as convention.

5.4The account analysis statement

Every month (or quarter, depending on the structure), the bank produces an account analysis statement for the client. This document is part-bill, part-economic-summary. Its anatomy:

• Section 1 — Balance Summary. Average ledger balance, average collected balance, average negative balance (if any), reserve adjustment, balance available for ECR.
• Section 2 — Earnings Credit. The ECR rate applied, the credit calculation, the dollar credit earned for the period.
• Section 3 — Service Charges. Itemized fees by service: per-wire, per-ACH item, account maintenance, lockbox, FX, etc.
• Section 4 — Net Position. Earnings credit minus service charges. If positive (credit exceeds fees), the excess typically expires; if negative (fees exceed credit), the client owes a hard-money charge.

Reading an analysis statement well is one of the underrated skills in TS&P. The same client can look profitable or unprofitable depending on whether you read the gross-fee top line or the net-of-credit bottom line.

5.5Hybrid pricing

Most large clients don't run a single pricing structure. They run a hybrid. A typical large corporate setup:

• An operating DDA structured as non-interest-bearing with ECR. This funds day-to-day movement.
• An investment account structured as interest-bearing or as a sweep into a money market fund. This holds excess balances earning explicit yield.
• Sometimes a compensating-balance arrangement tied to a credit facility — the corporate agrees to maintain minimum balances in lieu of paying explicit fees on the credit.

The choice between ECR and interest is fundamentally a tax/accounting optimization for the corporate. The bank's economics are similar either way, but the regulatory and capital treatment differs. A controller modeling client-level economics needs to be explicit about which structure is in place and why.

5.6The accounting for ECR

This is where it matters most. The ECR mechanic creates a non-cash credit that offsets fees. From the bank's GAAP perspective:

• No interest expense is booked for the earnings credit. The credit doesn't represent a cash transfer or an obligation to pay cash. It's a fee-offset construct.
• Fee revenue is recognized net of ECR applied. If gross fees would have been $100,000 and $80,000 of ECR is applied, the bank recognizes $20,000 of fee revenue. The other $80,000 simply doesn't appear on the income statement at all.
• The economic value of the deposit is captured through net interest income on the bank's general books. The deposit funds the bank's investment book, generates spread, and shows up in NII independently of any client-facing fee accounting.

This double-entry creates the FP&A reconciliation problem that every new TS&P controller hits eventually:

5.7ECR rate-setting governance

The ECR rate is bank-set, but it isn't arbitrary. Rate-setting at most banks is governed by:

• A posted rate methodology — typically a benchmark plus or minus a spread, with the spread set by ALCO or a treasury committee.
• A relationship-specific override — for very large clients, negotiated ECR rates above the posted rate.
• Periodic recalibration — usually quarterly, sometimes monthly in volatile rate environments.
• An arms-length test — banks must be able to demonstrate that ECR is competitive with what other banks offer for similar relationships, lest they lose deposits.

For a controller, the things to verify: that the ECR rate applied to each account matches the published methodology or documented exception, that any negotiated overrides are properly approved, and that the rate movement over time is consistent with the methodology.

5.8Common controller failure modes

Five recurring problems in ECR accounting and reconciliation:

1. Pricing exception drift. A negotiated ECR rate gets entered into the system at relationship onboarding. Years pass. The relationship ages, the original deal becomes uneconomic at current rates, but no one re-checks. The bank quietly bleeds margin. The fix: an annual exception review process owned by FP&A.
2. Reserve requirement mis-application. The 10% reserve haircut convention persisted after the actual reserve requirement went to zero. Some banks dropped it; others kept it; client agreements varied. Inconsistency across the book is common. The fix: a reserve-haircut audit of all active analysis statements.
3. Expired credit not properly retained. When ECR exceeds fees, the excess should be retained as bank economic value. If the system rolls it forward indefinitely or applies it to future fees beyond contractual rules, revenue is being implicitly given away. The fix: validate the rollover/expiration rules in the analysis-statement system match contractual terms.
4. Gross-vs-net reporting confusion. Internal management reporting that mixes gross fees (analysis statement view) with net fees (GAAP view) without explicit reconciliation. The fix: standardize on a single view per report and document the bridge.
5. Float convention drift. "Collected" balances depend on the bank's float conventions for deposited items. Modern check imaging has compressed float to near-zero, but the conventions in old systems may still impose multi-day delays. The result: clients are charged ECR on stale balance views. The fix: a periodic float convention audit.

5.9The strategic question

For a relationship manager, ECR is a competitive weapon — a flexible way to compensate clients for the deposit value they bring without paying explicit interest. For a controller, ECR is a fragile pricing construct — easy to misapply, easy to under-monitor, and consequential when it drifts.

The bank's overall approach to ECR — generous? stingy? bands or single rate? — is a strategic choice that ALCO makes. The controller's job is not to make that choice. It's to make sure that whatever ALCO decided is faithfully and consistently implemented across every account in the book, and that the GAAP fee revenue ties to the analysis statements through a clean reconciliation.

Virtual account management: one real account, infinite logical ones.

8.1The reconciliation problem VAM solves

A B2B company with thousands of customers traditionally has two unattractive options for managing receivables: (a) one big bank account that receives all customer payments, requiring extensive matching logic to attribute incoming wires and ACHs to the right invoice or customer, or (b) a multitude of dedicated bank accounts, one per customer or business unit, generating operational complexity and per-account fees.

Virtual account management offers a third option. The bank maintains a single real DDA (the "physical" account). Sitting on top of it is a hierarchy of "virtual" accounts — each with its own account number, each visible to the customer, each used to receive specific flows. All postings to the virtual accounts ultimately settle in the single physical account, but reporting, reconciliation, and reference data preserve the virtual-level detail.

8.2How VAM works mechanically

The bank's VAM platform creates a tree of virtual accounts under one or more physical accounts. Each virtual account has:

• A unique account number (in many systems, a routable virtual IBAN that can receive direct wire and ACH credits).
• A balance ledger maintained at the virtual level.
• Statements and reporting at the virtual level.
• Mapping to a parent physical account, where actual cash sits.

When a customer wires payment to a virtual account, the bank's system: (a) credits the underlying physical account in the GL (this is where the real money lives), (b) records a virtual posting against the virtual account, and (c) provides reporting that lets the corporate see the activity at virtual-account granularity. The corporate's ERP then reconciles invoices to virtual accounts cleanly, with one-to-one matching.

8.3Common VAM use cases

The product fits several distinct corporate problems:

• Receivables reconciliation. Each customer is assigned a unique virtual account; payments arrive pre-attributed. Eliminates the manual matching workload.
• Marketplace / platform pay-in. Each seller on a marketplace gets a virtual account. Customer payments to sellers route through the platform's master physical account but with seller-level visibility.
• In-house bank operating accounts. A multinational's central treasury maintains one physical account at the bank but issues virtual accounts to operating units, simulating decentralized banking with centralized control.
• Tenant trust accounts. Property managers, law firms, and brokerages can maintain commingled physical balances while preserving per-tenant or per-client segregation in the virtual layer.
• Subsidiary segregation. Each subsidiary in a corporate group operates from its own virtual account, simplifying internal P&L attribution without the tax complications of multiple physical accounts.

8.4The bank's deposit treatment

From the bank's accounting perspective, virtual account balances aggregate up to the physical account. The bank's deposit liability sits at the physical level — there is one deposit, owned by the legal entity that holds the physical account, with one set of T&Cs.

This matters for several reasons:

• Deposit insurance. FDIC insurance applies at the physical account level. A virtual account holding $5M for a tenant of a property manager has the same FDIC coverage as a single $5M deposit — typically capped at the per-depositor limit, which can create disclosure or fiduciary issues for the property manager that the bank should flag.
• Single legal owner. The bank's relationship is with the physical account holder. The virtual sub-account holders have no contractual relationship with the bank.
• FTP credit. The bank earns FTP on the consolidated physical balance, not virtual-account-level. This makes VAM relationships highly sticky and high-margin — large balances aggregating into one operational deposit.

8.5Virtual IBANs and direct addressability

Modern VAM implementations issue routable virtual IBANs (or virtual U.S. account numbers) that customers can use to send wires and ACHs directly. The bank's payment infrastructure routes incoming credits using the virtual identifier, posts to the virtual account, and aggregates to the physical.

From a payment-rail perspective, virtual identifiers are issued from the bank's allocation of routing/clearing identifiers. The bank takes responsibility for ensuring the virtual identifier resolves correctly. Some networks (including SEPA) have explicit support for virtual IBANs; in others (including U.S. domestic), virtual addressability uses bank-specific routing and addressing logic.

8.6Reconciliation and reporting

The product's value is in the data layer. A standard VAM reporting set includes:

• Real-time virtual-level balances via API, refreshed on each posting.
• Virtual-level statements, downloadable separately or aggregated.
• Hierarchy view of the virtual structure, with parent-child relationships.
• Cross-virtual transfers, posted as journal entries in the virtual ledger without affecting the physical balance.
• Bulk reconciliation files with virtual-level metadata for ERP ingestion.

8.7The controller's reconciliation perspective

For the bank's TS&P controller, VAM creates a specific control challenge: the virtual ledger has to tie exactly to the physical at all times. Any drift — a virtual posting that never made it to the physical, or vice versa — creates a customer-facing reconciliation break.

Standard controls:

• Daily aggregation of all virtual postings vs. the physical account daily activity.
• Sum of virtual balances at end-of-day equals physical balance, by definition.
• Audit trail on every virtual cross-posting, with double-entry validation.
• Real-time alerts on any imbalance condition.

Liquidity investment: sweep, repo, time deposit.

10.1The investment menu

For a corporate with excess operating cash, the standard menu of overnight and short-tenor instruments includes:

• Money market mutual funds (MMFs). Government, prime, or municipal MMFs. Daily liquidity, regulated under SEC Rule 2a-7.
• Bank time deposits / CDs. Fixed tenor (overnight, 7-day, 30-day, longer), fixed yield, deposit liability of the bank.
• Repurchase agreements (repo). Short-term collateralized lending, typically against Treasury or agency collateral.
• Treasury bills. Direct purchases of short-tenor government debt.
• Commercial paper. Short-term unsecured corporate debt.
• Brokered CDs and structured deposits. Variants offering structured payoffs.

Each option has its own yield, liquidity, accounting treatment, and counterparty risk. The corporate treasurer's job is to construct an investment portfolio that meets the company's cash needs, risk tolerance, and yield targets. The TS&P controller's job is to know how each option flows through the bank's books and the client's books.

10.2Bank-sponsored sweep products

The most common arrangement at large U.S. banks: the corporate's operating account is paired with an automatic overnight sweep into a designated investment vehicle. End of day, balance above a threshold sweeps out; beginning of next day, balance returns to fund operational outflows.

The sweep destination is one of:

• Bank-affiliated MMF. The most common. Cash leaves the bank's deposit base, goes into a money fund managed by the bank's asset management arm or a partner. The bank loses the deposit but keeps the asset management fee.
• Bank repo program. Cash technically leaves the bank's deposit base but stays "with" the bank in repo form. The bank retains funding, with collateral (typically Treasuries) pledged to the customer overnight.
• Bank time deposit. Cash stays in the bank as a time deposit, earning a higher rate than the operating DDA but losing daily liquidity.
• Off-bank MMF or other instrument. Cash leaves the bank entirely.

10.3The bank's economic preference

From the bank's perspective, sweep destinations are not equal. The hierarchy of preference, generally:

1. Stay in the bank as a time deposit — full deposit retention, higher FTP credit due to the term, same regulatory treatment.
2. Repo — secured funding, similar economic profile to a deposit but treated as borrowed funds.
3. Bank-affiliated MMF — deposit leaves but asset management fee captured.
4. Off-bank instrument — full economic loss of the relationship.

Banks structure sweep menus to incentivize the higher-preference options through pricing and convenience. A bank-affiliated MMF integrated into the bank's online portal is operationally easier than a competing fund that requires a separate trade execution.

10.4The MMF accounting and disclosure picture

For the corporate, MMF holdings are typically classified as cash equivalents under ASC 305 if the fund is a Government MMF (constant NAV, minimal credit risk) or as short-term investments otherwise. The classification matters for working capital ratios and bond covenants.

For the bank, sponsored MMFs raise their own complications:

• Sponsorship fees. Booked as fee revenue on the bank's books.
• Implicit support. Banks have historically extended unannounced support to their sponsored MMFs in stressed periods to avoid breaking the buck. Such support requires careful disclosure and capital treatment.
• Consolidation analysis. Whether the bank must consolidate the MMF on its balance sheet depends on power and benefits tests under ASC 810. Most sponsored MMFs are not consolidated.

10.5Repo accounting

A standard tri-party repo transaction: the bank sells securities to the corporate with an agreement to repurchase the next day at a price reflecting an overnight rate. Economically, this is overnight secured borrowing by the bank from the corporate, collateralized by the securities.

Accounting treatment under ASC 860:

• For the bank: the securities remain on the bank's balance sheet (no transfer of control); the proceeds are recorded as a secured borrowing (a "repo liability") rather than a sale. Interest accrues over the overnight period.
• For the corporate: recorded as a secured receivable from the bank. Cash equivalent treatment depends on tenor and characteristics.

Repo is not a deposit — it's a borrowing — and it shows up on the bank's balance sheet as such. The regulatory treatment also differs from deposits: repo doesn't get LCR's favorable operational deposit classification, but the secured nature reduces other risk weights.

10.6Time deposits and structured deposits

A time deposit is functionally a CD: cash deposited for a fixed tenor, earning a fixed rate, breakable only with a penalty. From the bank's perspective, a time deposit is a deposit liability with known maturity — generally easier to fund-match than a non-maturity deposit.

Structured deposits add a derivative wrapper: the principal is guaranteed (typically), but the yield is linked to some external reference (an equity index, an FX pair, a basket of rates). Structured deposits are sold by treasury services and capital markets desks jointly. Accounting follows ASC 815 — the embedded derivative may need bifurcation depending on the linkage.

10.7The controller's reconciliation

For the TS&P controller managing client liquidity investment relationships, daily reconciliation includes:

• Sweep file confirming the previous day's overnight movement.
• Investment vehicle statement (MMF position, repo settlement, time deposit balance) tied to the bank's records.
• Yield application and accrual posted correctly.
• For sponsored vehicles, sponsor fee accrual booked.
• For repo, collateral schedule and margin maintained correctly.

Intraday liquidity and the Fed master account.

11.1Why intraday is its own discipline

Most ALM literature treats liquidity as an end-of-day phenomenon: a bank's overnight position, its short-term funding stack, its 30-day LCR. But the bank has a separate, fundamentally different liquidity problem during the business day — and it's a problem the TS&P controller needs to understand, because every wire, every card settlement, every Fedwire deduction touches it.

The intraday problem: as the day progresses, payments flow out and in across the bank's Fed master account in real time. Outflows in any given hour can exceed the cash balance plus expected inflows. If outflows persist faster than inflows replenish, the master account goes negative — a daylight overdraft — and the Fed charges fees and consumes the bank's overdraft cap.

11.2The Fed master account

Every U.S. depository institution that participates in Fedwire has a master account at one of the regional Federal Reserve Banks. The master account is the bank's single most important operational asset: it holds the bank's reserves, settles its Fedwire transactions, and serves as the destination for FedNow and ACH settlements.

Mechanically, the master account behaves like a current account that the Fed maintains for the bank. Reserves earn IORB. Transactions settle in real time across it. Cap limits, daylight overdraft fees, and intraday monitoring are all administered against it.

11.3Reserves, excess reserves, and the ample-reserve regime

Pre-2008, banks held minimum reserves at the Fed roughly equal to required reserves under Regulation D. Excess reserves were near-zero because reserves earned no interest — banks deployed everything into income-earning assets.

Post-2008, the Fed began paying interest on reserve balances (initially "Interest on Excess Reserves," now unified as IORB — Interest on Reserve Balances). This, combined with quantitative easing, created the "ample reserve regime" the U.S. banking system operates in today: banks hold large reserve buffers because the Fed pays a competitive rate on them.

The reserve requirement itself was reduced to zero in March 2020 and has stayed there. Banks now hold reserves voluntarily — driven by intraday liquidity needs, regulatory ratios (LCR), and IORB economics rather than required-reserve mechanics.

11.4The daylight overdraft framework

When a bank's master account goes negative during the day, that's a daylight overdraft. The Fed allows daylight overdrafts up to a self-assessed cap, and charges a fee (Reg HH framework) for the negative position.

The cap calculation has two pieces:

• Single-day cap multiple — the bank's risk-based cap class (ranges from "exempt" through "high") multiplied by the bank's qualifying capital. The largest banks generally have caps in the tens of billions of dollars.
• Two-week average cap — a more conservative limit applied as a moving average to prevent gaming.

The Reg HH fee schedule: zero for the first portion of the cap that's collateralized, a per-minute basis-point charge for the uncollateralized portion. Banks that maintain very large daylight overdraft footprints can pay material fees over a year.

11.5BCBS 248 — the Basel intraday standard

Beyond Reg HH, the Basel Committee on Banking Supervision issued Standard 248 in 2013, "Monitoring Tools for Intraday Liquidity Management." BCBS 248 mandates that internationally active banks track and report seven specific metrics to their primary supervisor:

1. Daily maximum intraday liquidity usage
2. Available intraday liquidity at the start of the business day
3. Total payments (gross)
4. Time-specific obligations
5. Value of customer payments made on behalf of correspondents
6. Intraday credit lines extended to financial institutions
7. Intraday throughput

For the controller of a globally active bank, these metrics flow into supervisory reporting and have to tie to the same general ledger that produces the income statement. The reconciliation is non-trivial because intraday measurement is operational (not GL-native), but the regulatory disclosure depends on consistency.

11.6The intraday liquidity buffer

Banks maintain an intraday liquidity buffer — a pool of high-quality liquid assets and committed liquidity sources earmarked specifically for intraday use. This buffer is sized based on stress scenarios:

• What happens if a major counterparty fails to deliver expected inflows during the day?
• What happens if a payment system experiences a multi-hour outage that compresses payment processing into a shorter window?
• What happens if a market event triggers concentrated demand for intraday credit?

The intraday buffer is a real cost — the assets in it earn less than they would in a higher-deployment alternative. That cost is allocated through the bank's internal pricing back to the businesses generating intraday usage, including TS&P. Daylight overdraft fees charged to TS&P clients are partly a recovery of this buffer cost.

11.7Intraday monitoring infrastructure

Inside a major bank, the intraday liquidity desk runs a real-time monitoring system that tracks:

• The current Fed master account balance, refreshed every few seconds.
• A throughput dashboard showing payment outflows and inflows by rail (Fedwire, CHIPS, ACH, FedNow, RTP).
• Forecast inflows for the rest of the business day (large client wires expected, ACH credits scheduled).
• Queue management — which outgoing wires can be released now, which need to be held.
• Stress indicators — proximity to caps, deviation from historical patterns.

When stress indicators trip, the desk can take action: hold non-time-critical wires until inflows arrive, draw on intraday credit lines from correspondents, monetize collateral via intraday repo, or call the Fed for primary credit (the discount window) in extremis.

11.8The TS&P controller's interaction

For a controller in TS&P, intraday liquidity touches the close in several ways:

• Daylight overdraft fee allocation. Reg HH fees the Fed charges the bank are passed through to clients (with a markup) via daylight overdraft fee schedules. Validating that the right clients get charged the right fees is an ongoing reconciliation.
• Intraday liquidity cost transfer pricing. The intraday buffer cost is transfer-priced to TS&P. Validating that the allocation is correct and reasonable is a periodic exercise.
• Behavioral deposit assumptions. The "operational deposit" classification under LCR — and the favorable FTP credit that comes with it — depends on the bank being able to demonstrate, with data, that the deposits behave operationally. Intraday usage data is part of that evidence.
• BCBS 248 reporting. Customer payments made on behalf of correspondents — a TS&P metric — feeds the regulatory submission.
• Stress test linkage. Bank-wide intraday stress scenarios assume certain TS&P deposit behaviors and payment volumes. The controller has to ensure that the assumptions used in stress tests are consistent with what TS&P is actually observing.

Overnight liquidity markets and bank treasury.

13.1The bank's overnight problem

At end of day, every bank has either a positive or negative residual position relative to its desired overnight balance. Positive residuals need to be invested or lent overnight. Negative residuals need to be funded. The bank's treasury function operates the overnight markets that absorb both sides.

13.2The federal funds market

Historically the most important overnight market: banks with excess reserves at the Fed lend to banks with deficit reserves, on an unsecured overnight basis. The effective federal funds rate (EFFR) is the volume-weighted average of these transactions, calculated daily by the New York Fed.

In the post-2008 ample-reserve regime, the fed funds market has shrunk dramatically — most banks have excess reserves earning IORB at the Fed and have less need to borrow from each other. The remaining fed funds activity is largely between FHLBs (which can lend their member-bank deposits) and depository institutions, plus some between banks managing GSE deposit flows.

13.3The repo market

Far larger than fed funds today: the repurchase agreement market for collateralized overnight funding. Banks, money funds, hedge funds, and corporates all participate. The Secured Overnight Financing Rate (SOFR) is the volume-weighted average of overnight Treasury repo transactions, published by the New York Fed and now the primary U.S. dollar reference rate post-LIBOR.

For a large bank, repo provides:

• Overnight funding against the bank's Treasury holdings.
• Investment for cash-rich corporate and FI clients (the bank lends to them, secured by Treasuries).
• Term funding at tenors out to several months.
• Collateral transformation for clients needing specific securities for settlement or pledge purposes.

13.4IORB as the floor

The Fed pays Interest on Reserve Balances at a rate set by the FOMC (typically 5–15 bps above the lower bound of the target range). This is the rate at which any bank can hold reserves at the Fed risk-free.

IORB acts as a floor on overnight rates: no rational bank would lend overnight at a rate below IORB, because depositing at the Fed is risk-free at IORB. In practice, fed funds and SOFR trade slightly below IORB at times because non-depository participants (FHLBs, money funds) can't earn IORB and accept lower rates to invest cash overnight. The spread between IORB and SOFR is one of the most-watched indicators of money market stress.

13.5The Standing Repo Facility

Established in 2021, the Fed's SRF allows primary dealers and eligible depository institutions to borrow overnight against Treasury and agency collateral at a rate slightly above IORB (typically 5–10 bps). The SRF acts as a ceiling on the overnight repo rate: no rational counterparty would lend overnight repo at a rate above SRF when they could lend to the Fed instead.

SRF + IORB define a corridor for overnight rates, with the EFFR and SOFR generally trading inside it. The corridor mechanism is the operational expression of FOMC monetary policy in the post-2008 regime.

13.6The discount window

The Fed's traditional lender-of-last-resort facility. Banks can borrow at the discount rate, which is set above the federal funds target. Three programs:

• Primary credit — for sound banks with adequate collateral, at the discount rate.
• Secondary credit — for less-sound banks, at a higher rate.
• Seasonal credit — for smaller banks with predictable seasonal needs.

Historical stigma associated with discount window borrowing has reduced its routine use, though the Fed has worked since 2008 to normalize it. For TS&P, the discount window is the backstop for extreme intraday or overnight liquidity shortfalls; routine activity uses fed funds and repo instead.

13.7Treasury bills and the bill market

Direct Treasury issuance provides the most secure short-tenor instrument available. T-bills are issued at weekly auctions in 4-, 8-, 13-, 17-, 26-, and 52-week tenors. The bill market is deep and liquid; bill yields anchor the high-quality short-tenor curve.

For corporate treasurers and bank treasury alike, T-bills serve as a yield-bearing, fully-liquid alternative to bank deposits or MMFs. For the bank, holding T-bills consumes balance sheet (SLR impact) but generates HQLA Level 1 treatment (best LCR economics).

13.8The FHLB system

Federal Home Loan Banks function as wholesale lenders to U.S. depository institutions, secured by mortgage and other eligible collateral. FHLB advances are a major term funding source for many banks, particularly mid-sized regionals. The largest U.S. money-center banks use FHLB more selectively but maintain access.

Advances are available at tenors from overnight to 30 years, fixed or floating, with various amortization profiles. FHLB advances also have Carve-out treatment under various capital and liquidity ratios that makes them attractive funding for certain balance-sheet objectives.

13.9How bank treasury connects to TS&P

The bank's treasury function operates these markets to keep the overall bank funded. TS&P interacts at four points:

• Intraday liquidity buffer. The size of the bank's required intraday buffer flows from how cleanly TS&P payment volumes can be predicted and timed.
• FTP curve. The bank's overnight funding cost (IORB, SOFR, fed funds) is the short-tenor anchor for the FTP curve. Treasury sets the curve; TS&P uses it.
• Client-facing investment products. Bank treasury creates the products (sweep, repo, time deposits) that TS&P sells to clients (Ch 10).
• NSFR compliance. The Net Stable Funding Ratio depends on both the bank's overall funding mix (treasury's responsibility) and on TS&P-driven deposit categorization. Both teams work together at quarter-end disclosure time.

Daylight overdrafts and intraday credit.

15.1The Reg HH framework

Federal Reserve Regulation HH governs daylight overdrafts at depository institutions. The framework has three components:

• The cap. Each bank has a self-assessed daylight overdraft cap, expressed as a multiple of qualifying capital. Cap classes range from "exempt" (no overdrafts allowed) through "high" (largest multiple).
• The fee. Per-minute fees on the negative balance, with a portion potentially waived if collateralized. Fee rates are set in basis points and rebated for collateralized positions.
• The two-week monitoring. Average overdrafts over a moving two-week window also have to comply with cap rules, preventing peak gaming.

15.2Pass-through to clients

Banks recover Reg HH costs (and add a markup) by charging their corporate clients daylight overdraft fees on negative intraday balances. The mechanic mirrors the Fed's: per-minute or per-occurrence fees on the negative balance, with potential collateralization arrangements for large clients.

The TS&P controller's job:

• Confirm fee schedules in client contracts match the bank's published policy.
• Validate that the system applies fees correctly based on actual intraday positions.
• Reconcile total client daylight overdraft fee revenue to the bank's external Reg HH cost.
• Identify and review exceptions where intraday positions appear to indicate uncovered client risk.

15.3Committed daylight credit lines

For larger corporate clients, simple daylight overdraft fees aren't sufficient. The bank instead provides a committed daylight credit line — a contractual commitment to provide intraday credit up to a specified limit, in exchange for a commitment fee.

From a regulatory capital perspective, a committed daylight credit line is an off-balance-sheet exposure subject to Credit Conversion Factor treatment under Basel III. The undrawn commitment generates RWA, and any drawn portion (typically only known at end-of-day reconciliation if any spilled into overnight) creates a funded loan exposure.

15.4Collateralization arrangements

To reduce both bank and client cost on intraday credit, large clients sometimes pledge collateral against their daylight overdraft. Eligible collateral typically includes Treasury and agency securities, with haircuts. Pledged collateral reduces:

• The bank's CCF on the off-balance-sheet exposure.
• The client's daylight overdraft fee, since the bank can pass collateralization benefits down.
• The bank's own Reg HH cost, since collateralized portions of the master account overdraft are exempt or reduced-rate.

15.5Common controller failures

Patterns to watch for:

• Stale collateral pledges. Securities pledged years ago, no longer marked-to-market, with haircut assumptions long since outdated. Result: insufficient collateralization on paper, unrecognized exposure.
• Pricing exception drift. Negotiated daylight overdraft pricing for a specific large client, never revisited as the relationship evolved. Result: the bank earns less than it should on the exposure.
• Cap class mis-assignment. A client classified for cap-monitoring purposes incorrectly, often when ownership or structure changes weren't pushed through to the Reg HH classification.
• Overnight spillage not detected. A daylight overdraft that wasn't covered at end-of-day, becoming an overnight extension of credit, with the documentation and accounting requirements that triggers.

15.6The disclosure

Reg HH metrics — peak daylight overdraft usage, average usage, fees paid — are part of the bank's confidential supervisory reporting and don't typically appear in public disclosures. Internal reporting cycles them through the bank's risk committee monthly. Auditors review the underlying control framework annually under BCBS 248, which requires banks to monitor intraday liquidity against a defined set of tools and report results to supervisors.

For TS&P specifically, the bank-level intraday liquidity reporting is a fixed cost. What TS&P can control is the margin between that cost and the revenue recovered through client daylight overdraft fees. That margin is the business unit's contribution from intraday credit — and it is almost never broken out in standard segment reporting.

ACH and Same-Day ACH.

17.1The ACH model

The Automated Clearing House network is operated by two operators (the Federal Reserve via FedACH and The Clearing House via EPN). Unlike RTGS systems, ACH is a batch-and-net system: payments are originated in batches, transmitted to the operator, processed in scheduled windows, settled net at specific times.

Two transaction types:

• ACH credit. Originator pushes funds to receiver. Examples: payroll, vendor payments, government benefits.
• ACH debit. Originator pulls funds from receiver (with prior authorization). Examples: utility bills, mortgage payments, subscription charges.

The dynamics differ. Credits have less return risk (the originator controls timing and authorization). Debits have substantial return risk — the receiving party can return for various reasons (insufficient funds, account closed, unauthorized).

17.2NACHA — the rule-setter

NACHA (formerly the National Automated Clearing House Association) writes the NACHA Operating Rules, the contractual rule framework binding on all ACH participants. Annual rule updates take effect each March, requiring system, operational, and contractual updates by all originators and ODFIs.

Recent rule themes:

• Same-Day ACH expansion (multiple windows added through 2021).
• Account validation requirements for first-use credits to consumer accounts.
• Enhanced fraud risk management for credit-push fraud.
• Limit increases (Same-Day ACH limit raised to $1M per transaction in 2022).

17.3Same-Day ACH

Same-Day ACH was introduced phased starting in 2016, allowing ACH transactions to settle the same business day rather than next-day or two-day. Three settlement windows currently operate (10:30am, 2:45pm, 4:45pm ET cutoffs) with end-of-day net settlement through Fedwire.

Use cases:

• Same-day payroll for hourly workers and gig economy.
• Emergency vendor payments avoiding next-day delay.
• B2B working capital optimization.
• Consumer bill-pay timing flexibility.

Premium pricing (Same-Day ACH carries a higher per-item fee than next-day ACH) creates incentive for routine activity to remain on next-day, while same-day captures urgent or high-value flows.

17.4Originator-side accounting

For an originator (a corporate paying via ACH), the transaction flow:

1. Originator generates ACH file from payroll or AP system, formatted per NACHA file specifications.
2. File transmitted to ODFI (originating depository financial institution).
3. ODFI validates file, signs, and forwards to ACH operator.
4. Operator processes file, sorts to RDFIs (receiving depository financial institutions).
5. RDFIs post entries to receiver accounts.
6. Settlement happens via Fedwire entries between ODFI and operator on settlement date.

The originator's funds debit the originator's DDA on settlement date. The receiver's account credits on settlement date. For the originator, the ACH liability shows up only briefly in transit.

17.5The return process

ACH returns are the most operationally complex part. RDFIs can return entries within timeframes specified by the rules (typically 2 business days for most return reasons; 60 days for unauthorized consumer debits). Common return codes:

• R01 — Insufficient funds.
• R02 — Account closed.
• R03 — No account / unable to locate.
• R04 — Invalid account number.
• R10 — Customer advises unauthorized (consumer).
• R29 — Corporate customer advises unauthorized.

Each return generates a reversing entry, an originator notification, and (for many return types) a delay or operational adjustment. High-return-rate originators face NACHA scrutiny and potential ODFI termination of access.

17.6The bank's revenue economics

ACH per-transaction pricing is low — typically $0.10–0.50 per item to corporate clients, with substantial volume discounts. The economics work on volume: a bank processing 100M ACH transactions per month earns meaningful revenue at low per-unit margin.

Revenue components:

• Per-item origination fee.
• File transmission fees.
• Same-Day ACH premium.
• Returns and notifications-of-change fees.
• ACH risk monitoring services (premium product).
• Float revenue on intraday balances during processing.

17.7Fraud and risk management

ACH fraud has expanded substantially with ACH credit-push capabilities. Patterns include:

• Credit-push fraud. Unauthorized ACH credits initiated through compromised originator credentials.
• Account takeover. Compromised consumer or business banking access used to initiate or authorize debits.
• Authorized fraud. Consumer or business knowingly initiates ACH that they later dispute.

NACHA's account validation rule (effective 2021–2022) requires ODFIs to validate consumer account ownership for first-use credits, meaningfully reducing certain credit-push fraud patterns. Banks invest in ML-based ACH fraud detection that flags anomalous origination patterns.

Cards and acquiring (cross-reference).

19.1What's covered elsewhere

The four-corner model, MDR/interchange-plus pricing, card scheme economics (Visa/Mastercard interchange and assessments), chargeback handling, principal-vs-agent classification under ASC 606, interchange revenue recognition, scheme network fees, and merchant acquiring revenue mechanics are all covered in depth at paymentscontroller.com.

This handbook treats cards as a TS&P-adjacent business and focuses on the points where cards interact with treasury services, deposits, and corporate liquidity.

19.2Commercial cards as a TS&P product

Within TS&P, the card business primarily appears as commercial card products:

• Corporate cards. Issued to corporate employees for T&E spend, with central billing and reporting.
• Purchasing cards (P-cards). Used for small-dollar procurement, replacing PO/invoice processing.
• Virtual cards. Single-use card numbers generated for specific transactions or vendors, commonly used in B2B AP.
• Fleet cards. Specialty cards for fuel and vehicle expense.

Commercial cards generate higher interchange than consumer cards (typically 2.5–3% on commercial transactions vs. ~1.5–2.5% on consumer), creating the economics that allow rebate programs and rich loyalty propositions for the corporate.

19.3The float dynamic

Commercial cards have a unique cash management dynamic: the corporate card account aggregates spend across all employees throughout the billing cycle, with a single payment at cycle close. The corporate effectively gets a 25–55 day "float" between purchase and payment, depending on when in the cycle the purchase falls.

From the bank's perspective, this float is funded credit — the bank pays the merchant (via the card scheme) immediately, then collects from the corporate at cycle close. The float is a short-term receivable on the bank's balance sheet, generating interest income (or being offset against interchange and fees).

19.4Spend-and-rebate economics

For most large corporate card programs, the bank shares some portion of the interchange revenue with the corporate as a "rebate." Rebate structures:

• Volume-based. Higher rebate as annual spend volume increases.
• Speed-of-payment-based. Higher rebate for faster payment (shorter float).
• Category-based. Different rebate rates for different spend categories.

Rebate accounting (ASC 606): typically treated as a reduction of revenue (variable consideration). The bank books gross interchange revenue, then applies rebate as contra-revenue at the relationship level.

19.5Acquiring within TS&P

Some banks operate merchant acquiring within TS&P; others operate it as a separate division (e.g., a dedicated Merchant Services unit). Where it sits in TS&P, the controller's responsibility includes:

• Interchange and assessment reconciliation.
• Settlement processing and net-settlement to merchant DDAs.
• Chargeback reserves and dispute processing.
• Merchant onboarding, KYC, and risk underwriting.
• Network compliance (PCI-DSS, scheme operating rules).

For full coverage of all of the above, see paymentscontroller.com.

19.6What the acquiring relationship means for TS&P

When a bank provides merchant acquiring services through TS&P (as opposed to through a separate acquiring subsidiary), the deposit relationship is the strategic anchor. Merchants receiving card settlement need accounts to receive those funds — and they're almost always opening those accounts at the acquiring bank. This makes merchant acquiring a deposit-gathering strategy as much as a revenue strategy.

The FTP economics on merchant settlement accounts are favorable: settlement accounts are operational deposits (25% LCR outflow rate), the balances are sticky and predictable (next-day settlement creates a reliable daily inflow pattern), and they're difficult to move because the settlement account is tied to the acquiring relationship through direct documentation. For the TS&P controller, these accounts sit at the intersection of the acquiring P&L and the deposit P&L — making relationship profitability analysis particularly important to ensure both sides are captured.

ISO 20022 and modern messaging.

21.1What ISO 20022 is

ISO 20022 is a standard developed by the International Organization for Standardization for financial messaging. It defines:

• A common business model for financial transactions.
• A message-creation methodology and a global repository.
• XML and (more recently) JSON syntax for messages.
• Standardized data fields for parties, amounts, references, and other transaction details.

The format replaces the legacy MT (SWIFT-developed, fixed-format) standard for many payments and securities messages globally.

21.2The migration timeline

Major migration milestones:

• 2017+: RTP launched on ISO 20022 from inception.
• 2022: Eurosystem (TARGET2) migrated to ISO 20022.
• 2023: FedNow launched on ISO 20022. CHIPS migrated.
• March 2023 – November 2025: SWIFT cross-border payments migration, with MT/MX coexistence ending November 2025.
• 2025+: Fedwire migration completed.

By the end of 2025, virtually all major U.S. and international payment messaging operates on ISO 20022. Legacy MT messaging persists only in pockets.

21.3What's different in ISO 20022

The most consequential differences for TS&P:

• Structured remittance information. Free-form remittance text replaced by structured fields (invoice numbers, amounts, dates, references). Massively improves automated reconciliation.
• Richer party data. Beneficiary, originator, and intermediary parties identified with structured names, addresses, IDs, and roles.
• Regulatory reporting fields. Sanctions, AML, and tax reporting requirements expressible in dedicated fields.
• Larger message sizes. XML overhead means messages are several times larger than MT equivalents.
• Greater complexity. Hundreds of optional fields create implementation choices that vary by bank and corridor.

21.4The implementation challenge

ISO 20022 migration has been the largest payment-system transformation in decades. For banks, the implementation work spans:

• Message schema implementation. Parsing, validating, and generating XML messages across hundreds of message types.
• Field mapping. Mapping internal data structures to ISO 20022 fields, both directions.
• Translation services. Bridging between MT and MX during coexistence periods, with information loss risk.
• Sanctions and screening. Updated screening logic to handle structured names and addresses.
• Customer interface updates. Channel changes to capture and display the richer data.

For a TS&P controller, the migration has reshaped reconciliation infrastructure. Structured remittance information allows automated invoice matching at percentages that legacy MT could not achieve, but the upgrade required significant re-engineering of receivables processes.

21.5The downstream value

The strategic case for ISO 20022 isn't the messaging itself — it's the data ecosystem that becomes possible:

• Automated invoice-to-payment matching at >90% straight-through-processing rates.
• Regulatory reporting drawn directly from message data without separate operational capture.
• Cash flow forecasting and analytics with structured field-level inputs.
• Network visibility into payment patterns, fraud signals, and operational health.

For corporates, ISO 20022 is the foundation for treasury automation. For banks, it's the foundation for the next generation of TS&P products built on rich payment data.

21.6The controller's ISO 20022 touchpoints

ISO 20022 isn't just a messaging format — it generates accounting and reporting implications that TS&P controllers need to understand:

• Richer transaction data for reconciliation. ISO 20022 MX messages carry structured remittance data (invoices, purchase orders, references) that MT messages couldn't. For cash application and reconciliation, this is a step-function improvement — automated matching rates rise when remittance data is machine-readable rather than free-form text jammed into a 35-character field.
• UETR as a reconciliation key. Every gpi payment carries a UETR (Unique End-to-End Transaction Reference). This UUID travels through every leg of a cross-border payment and enables end-to-end reconciliation that was impossible with MT messaging. A break in the UETR chain signals a processing failure at a specific hop — much faster root-cause identification than legacy investigation processes.
• Fee billing accuracy. Message-type-based fee schedules (different fees for different message types) need to be updated as MX replaces MT. A fee schedule calibrated to MT103 may not map cleanly to the MX equivalent (pacs.008). Controllers should audit billing logic during and after migration.

21.7What the migration didn't fix

ISO 20022 adoption improved message richness and standardization across the network. It did not fix underlying settlement infrastructure. SWIFT still carries messages; Fedwire and CHIPS still settle USD; correspondent banks still intermediate cross-border flows. The inefficiencies in the correspondent banking model — cost, opacity, settlement timing — persist even in the MX world. ISO 20022 is a necessary but insufficient condition for the payment system modernization the industry is working toward.

Cross-currency payments: the embedded FX problem.

23.1The bundled vs. unbundled question

When a U.S. corporate pays a EUR-denominated invoice, two things happen: USD funds get converted to EUR (FX), and EUR funds get delivered to the beneficiary's bank (payment). The bank can offer this as:

• Bundled: single price for the combined service, with FX margin embedded in the rate.
• Unbundled: separate FX execution at a transparent spread, plus a separate wire fee for the payment leg.

Sophisticated corporates with FX execution capability tend to prefer unbundled — they execute FX with their preferred counterparty, then send the resulting foreign-currency amount as a payment. Less sophisticated corporates use bundled, accepting a higher all-in price for the simplicity of one transaction.

23.2Where FX margin sits in a bundled wire

For a bundled cross-currency wire of $1M USD to a EUR beneficiary:

• Interbank EUR/USD spot rate: 1.0850 (illustrative).
• Bank applies markup: 1.0815 (35 pips).
• EUR delivered: $1,000,000 / 1.0815 = €924,642 (vs. €921,659 at interbank).
• FX margin: ~€2,983 USD-equivalent ≈ $3,225.

Plus a wire fee on the payment leg ($25–50). Total bank revenue: $3,250+ on the transaction.

23.3Multi-currency accounts

For corporates with regular foreign-currency activity, multi-currency accounts allow holding balances in multiple currencies at the same bank. EUR receipts settle into a EUR account; future EUR payments go directly from the EUR account, eliminating intermediate FX conversion.

Multi-currency accounts:

• Reduce FX cost by avoiding round-trip conversions.
• Generate deposit balances at the bank in foreign currencies, with corresponding FTP credit at the bank's foreign-currency curves.
• Require AML and tax reporting consideration for non-functional-currency holdings.
• Need accounting consideration under ASC 830 for the corporate's books.

23.4Real-time FX pricing

Modern corporate banking platforms increasingly offer real-time FX pricing on cross-currency transactions: when the corporate initiates a payment, the system streams a live executable rate, the corporate sees and accepts the rate, and the trade is locked in at that rate.

This contrasts with historical "deferred pricing" where the corporate initiated the wire and the bank applied an end-of-day or batch FX rate. The real-time model improves transparency and aligns with modern client expectations but requires integration between corporate channels and trading-desk pricing engines.

23.5The accounting view

For a bundled cross-currency wire, ASC 606 considerations:

• Performance obligations. Generally treated as a single performance obligation (the bundled service).
• Transaction price. The all-in fee plus FX margin on the conversion.
• Recognition. Point-in-time at execution.
• Principal vs. agent. Bank is principal — bears the FX market risk during execution and warehouses the position.

23.6The FX problem in transaction pricing

Cross-currency payments embed FX conversion at a rate determined at the time of execution. The pricing question: how much of the total client payment is wire fee, and how much is FX margin? Most cross-currency payment products bundle both — the client pays one total amount, the bank takes fee + margin. Unbundling for revenue recognition requires an allocation methodology.

The ASC 606 treatment: fee revenue (wire processing) is typically recognized point-in-time as the payment executes. FX margin is recognized at the same moment as the rate is locked. The two are often separate performance obligations — a client who asks for a rate quote and then chooses not to execute has received the FX quoting service but not the payment service. Most banks treat them as a bundled single performance obligation given how tightly they're operationally linked, but the analysis is required.

ASC 815 hedge accounting in TS&P.

25.1The accounting problem hedge accounting solves

Without special accounting, derivatives are marked to market through the income statement (ASC 815-10). The hedged item, depending on its nature, may not be — it may be at amortized cost, at FVOCI, or recognized only on settlement. The mismatch creates artificial earnings volatility: derivative gains/losses hit the P&L immediately, but the offsetting movements on the hedged item don't.

Hedge accounting realigns the timing. When applied successfully, the derivative's mark-to-market gets matched against the hedged item's adjustments, producing economically faithful results that reduce reported volatility.

25.2The three hedge designations

ASC 815 recognizes three hedge categories:

• Fair value hedges. Hedging changes in the fair value of a recognized asset or liability. Both derivative and hedged item are marked to market through earnings, with offsetting effects.
• Cash flow hedges. Hedging variability in expected future cash flows. Derivative gains/losses initially go to OCI, then reclassified to earnings when the hedged cash flow occurs.
• Net investment hedges. Hedging foreign currency exposure of a net investment in a foreign operation. Derivative effects flow through OCI alongside the underlying CTA.

25.3Documentation and effectiveness

To qualify for hedge accounting, the relationship must be:

• Formally documented at inception. The hedging relationship, hedged item, hedging instrument, risk being hedged, and effectiveness assessment methodology all written down before any qualifying treatment.
• Highly effective. Initially and on an ongoing basis, the hedging instrument must be expected to be highly effective in offsetting the hedged risk.
• Periodically tested. Effectiveness must be assessed at every reporting period.

The 2017 ASU 2017-12 amendments simplified some testing, expanded eligibility for last-of-layer hedges, and reduced some operational burden, but the documentation requirement remains strict.

25.4Common TS&P applications

Bank-side hedges that touch TS&P operations:

• FX forwards on foreign-currency-denominated operating expenses. A U.S. bank with London operations hedges expected GBP operating expenses with forward sales of GBP — a cash flow hedge.
• Interest rate swaps on fixed-rate deposits. Converting fixed-rate deposit liabilities to floating to align with floating-rate loan assets — a fair value hedge.
• Net investment hedges of foreign branches. Hedging the bank's USD-denominated investment in EUR-denominated subsidiary equity.
• Cross-currency swaps on foreign-currency funding. Converting EUR-denominated bond proceeds to USD funding for the U.S. bank.

25.5The bank's role hedging clients' exposures

Beyond the bank's own hedges, TS&P sells client-facing FX hedging products. The bank is the dealer; the client is the hedger. From the bank's perspective:

• The trade enters the bank's FX trading book.
• The bank's own position is marked to market through earnings.
• The trade may or may not net against the bank's existing positions; residual risk is hedged externally.
• Trading P&L from the bid-offer spread accrues to Markets segment, with sales credit to TS&P.

The corporate's hedge accounting (whether the corporate qualifies for ASC 815 hedge accounting on the trade) is the corporate's problem, not the bank's. The bank may provide effectiveness testing reports as a service.

25.6De-designation and discontinuance

If a hedging relationship ceases to be highly effective, or the hedged item is sold, or the entity de-designates voluntarily, hedge accounting stops. The accounting consequences depend on the hedge type:

• Fair value hedges: cumulative basis adjustments unwound through earnings prospectively.
• Cash flow hedges: amounts in OCI either retained for eventual reclassification (if hedged transaction still expected) or immediately reclassified to earnings.
• Net investment hedges: amounts remain in OCI as part of CTA until the foreign investment is divested.

For the controller, hedge discontinuance is a tracked event with specific accounting and disclosure requirements.

25.7Disclosure requirements

ASC 815 disclosure (in 10-K and 10-Q) includes:

• Hedging objectives and strategies.
• Notional amounts of derivatives by hedge designation.
• Fair values by category, with offsetting netting where applicable under ASC 210-20.
• Gains and losses from derivatives, by location in earnings or OCI.
• Effectiveness of hedging relationships.
• Reclassifications from OCI to earnings.

The disclosures are tabular and standardized. The controller's role: ensure the disclosed numbers tie to the GL and to the underlying derivative inventory, that hedge designations are correctly captured, and that any de-designations are properly reflected.

Supply chain finance: payables financing.

27.1The basic structure

A buyer with strong credit and slow-paying terms (60–120 days standard) has suppliers who'd prefer faster payment. The bank steps in: when an invoice is approved by the buyer, the supplier can elect to receive early payment from the bank at a small discount. The buyer pays the bank on the original due date.

Economic effect:

• Supplier gets paid early — improving their working capital.
• Buyer's payment timing is unchanged from buyer's perspective.
• Bank earns the discount (which approximates short-term borrowing rate at the buyer's credit profile).

The bank's exposure is to the buyer's credit, not the supplier's. This is what allows the bank to offer rates tied to the buyer's (typically stronger) credit profile to suppliers (who individually may have weaker credit).

27.2The accounting controversy

The historical question: should the buyer's accounts payable to suppliers participating in SCF be classified as accounts payable (operational liability) or as bank debt (financing liability)? Reclassification has direct impacts on debt covenants, leverage ratios, and credit analysis.

FASB issued ASU 2022-04 (effective fiscal years beginning after December 15, 2022) requiring buyers to disclose:

• Key terms of SCF programs.
• Outstanding balance at period-end.
• Roll-forward of activity.
• The presentation in the balance sheet (and where amounts are classified).

The disclosure doesn't change classification per se — buyers still have latitude depending on the program structure. But the transparency lets analysts and credit committees see SCF separately from organic AP.

27.3The bank's accounting

For the bank:

• When bank pays supplier early: bank books a receivable from buyer (loan-like asset).
• Discount earned: recognized over the period until buyer pays — interest income equivalent.
• Capital treatment: the receivable is a corporate exposure to the buyer, risk-weighted accordingly.
• CECL: allowance reflecting expected credit losses on the receivable from buyer.

27.4Dynamic discounting variant

Dynamic discounting is similar but funded by the buyer's own cash rather than by the bank. The buyer offers to pay early at a discount; suppliers elect; cash flows from buyer to supplier through a platform. The bank's role is providing the platform and earning a fee.

From an accounting perspective, dynamic discounting is cleaner than bank-funded SCF — there's no third-party financing in the chain, just early payment of an existing AP balance.

27.5The platform layer

SCF runs on technology platforms. Some banks build proprietary platforms; others partner with fintechs (PrimeRevenue, Taulia, Demica, others). Platform mechanics:

• Buyer's ERP feeds approved invoice data to the platform.
• Suppliers see their approved invoices and an early-payment offer.
• Suppliers elect to receive early payment.
• Bank funds the supplier; bank's book reflects a receivable from buyer.
• At maturity, buyer pays the bank.

27.6The risk concentration

SCF concentrates buyer credit risk meaningfully. A bank running a $5B SCF program for a single large buyer has a $5B exposure to that buyer's credit. This is corporate lending, just structured differently. Banks underwrite SCF capacity the same way they underwrite revolver capacity — through credit limits, by counterparty, with formal credit committee approval.

For the controller, the SCF book has to be visible in the bank's overall corporate exposure aggregation. Greensill Capital's 2021 collapse highlighted what happens when SCF becomes opaque, concentrated, and disconnected from underlying buyer credit.

27.7Program economics from the bank's perspective

The bank's SCF economics are straightforward on the surface: the bank buys approved invoices at a discount (the early payment rate applied to the days between early payment and invoice due date) and receives the full face amount from the buyer at due date. The spread is the bank's return. But the real economics are more layered:

• Funding cost. The bank must fund the purchased receivables. For short-tenor SCF (30-90 day invoices), the funding cost is close to SOFR. The net margin above funding is the NIM on the program.
• Capital cost. SCF exposures consume RWA — typically at the buyer's risk weight, since the credit analysis is on the buyer's obligation to pay, not the supplier's ability to deliver. For investment-grade buyers, RWA is modest; for sub-investment-grade buyers, it's substantial.
• Operational cost. Program setup, invoice validation, supplier onboarding, and reconciliation are real costs. Large SCF programs with thousands of suppliers are operationally intensive.

The resulting RORC (Return on Regulatory Capital) for SCF is often attractive relative to funded loans for the same buyer — the short tenor and defined obligor make it capital-efficient. But the economics deteriorate if the buyer's credit quality deteriorates or if the program requires renegotiation in a rising-rate environment. Track the SCF portfolio yield against funding cost at the program level, not just in aggregate.

Trade loans and structured trade finance.

29.1The trade loan family

Specialized loans for trade transactions:

• Pre-export financing. Loan to a producer to fund production for a confirmed export sale. Repaid from export proceeds.
• Post-shipment financing. Loan to an exporter after shipment, against documents of title. Repaid from buyer payment.
• Import financing. Loan to an importer to pay for goods, repaid from sales of imported goods.
• Inventory finance. Loan secured by warehoused commodities or finished goods, repaid as inventory turns to receivables to cash.
• Trade-receivable-secured loans. Lending against specific trade receivables.

29.2Self-liquidation

The defining feature: each trade loan is structured to be repaid from the underlying trade transaction. Pre-export financing is repaid when the export sale settles. Post-shipment financing is repaid when the buyer pays. Inventory financing is repaid as inventory sells.

This self-liquidating nature limits the bank's tenor risk and links repayment directly to commercial performance. For commodity trading firms, where balance sheets can otherwise look opaque, the loan-by-trade structure provides credit transparency.

29.3Structured trade for commodities

For oil, metals, soft commodities, and agricultural commodities, structured trade goes further:

• Borrowing base facilities against commodity inventory in storage.
• Pre-payment financing for futures-purchase or forward-purchase contracts.
• Tolling agreements where the bank funds a refining or processing operation.
• Repurchase structures on physical commodities (the bank buys, holds, and resells to the corporate).

These structures often involve complex collateral arrangements, hedging requirements, and operational controls (warehouse receipts, third-party verification, field audits). The accounting can involve ASC 815 (derivatives) and ASC 610 (commodity contracts) in addition to standard loan accounting.

29.4The risk profile

Trade finance has historically lower default rates than general corporate lending — the self-liquidating structure and underlying-cargo collateral provide protection. However, recent decades have seen high-profile failures (Hin Leong, Greensill-related, others) involving misrepresentation, double-financing of the same cargo, or fraudulent inventory.

Modern controls emphasize:

• Independent verification of underlying transactions.
• Direct relationships with warehouse operators and inspection firms.
• Limits on counterparty concentration.
• Enhanced due diligence on commodity trading firm clients.

29.5The accounting and capital treatment

Trade loans typically receive standard short-term loan accounting and standardized risk weighting under Basel III. Some short-term, self-liquidating, off-balance-sheet trade exposures (commercial LCs, documentary collections) get reduced CCFs (20% rather than 100%) under regulatory rules — recognizing their lower risk profile.

29.6Revenue recognition on trade loans

Trade loan interest income accrues over the loan tenor at the contractual rate. For short-tenor self-liquidating trade loans (30-90 days), the accrual period is short and the recognition pattern straightforward. The accounting complexity arises at period-end when a loan straddles the month-end: interest must accrue through month-end at the correct daily rate, then continue accruing in the subsequent period after month-end through maturity.

For structured trade finance with embedded options or variable pricing (commodity-linked, performance-linked), the effective interest rate method under ASC 835 applies — the loan is recorded at amortized cost using an EIR that incorporates all expected cash flows. When those cash flows change (commodity price moves, performance trigger fires), a catch-up adjustment is required.

Uncommitted lines and money market lines.

31.1What "uncommitted" means

An uncommitted line is a facility under which the bank may extend credit at its discretion. The bank can refuse to fund any individual borrowing request without breaching the agreement. The corporate has access to the bank's willingness to lend, but no contractual right to require it.

Functionally, uncommitted lines work in normal market conditions like committed facilities — the bank routinely funds requests as part of the relationship. In stressed conditions, the bank can refuse, which is precisely the point.

31.2Why corporates accept uncommitted

Pricing. Uncommitted lines carry no commitment fee (or a much smaller one) because the bank takes no contractual obligation. For routine working capital needs where backstop certainty isn't required, uncommitted is much cheaper.

Common uses:

• Overdraft lines on corporate operating accounts.
• Money market lines for short-tenor (1-day to 30-day) working capital.
• Trade finance lines backing specific transactions.
• FX settlement lines covering daily settlement obligations.

31.3Capital and accounting treatment

Under Basel III, unconditionally cancelable uncommitted lines receive 10% CCF (recently moved from 0% in some jurisdictions for retail; commercial treatment varies). The reduced CCF reflects that the bank can decline drawings, but doesn't go to zero because of operational and reputational expectations.

For accounting (CECL), uncommitted lines may or may not require allowance depending on the bank's reasonable expectations of usage. If the bank reasonably expects to fund routine drawings, an allowance is appropriate. If the bank has clear practice of declining specific draw types, allowance may be lower or zero for those.

31.4The reputational reality

While uncommitted lines are legally cancelable, declining to fund routine draws can damage relationships meaningfully. Banks generally fund uncommitted draws as part of normal course unless something specific has changed (deteriorating credit, fraud concerns, sanctions developments, market stress).

For TS&P, the controller's monitoring includes tracking the bank's actual decline rate on uncommitted draws and the patterns of decline (counterparty, geography, product type) — useful for understanding whether the "uncommitted" treatment is being supported by actual practice.

31.5Pricing dynamics and capital cost

Uncommitted facilities generate commitment fee revenue (when any fee is charged at all) but consume minimal capital — the 0% CCF for unconditionally cancellable facilities means no regulatory capital charge for the undrawn portion. This makes them attractive from a return-on-capital perspective as long as the bank is comfortable with the operational risk of having a large unused credit available with no binding commitment.

The tension: a large corporate that depends on an uncommitted facility for day-to-day liquidity is operationally exposed to the bank withdrawing it without notice. Post-2008, regulatory pressure has pushed sophisticated treasuries toward committed RCFs for liquidity needs, with uncommitted facilities reserved for incidental borrowing. The TS&P controller should track the split between committed and uncommitted exposure by client — it affects CECL analysis, capital modeling, and the bank's own liquidity stress testing.

31.6Money market lines in context

Money market lines are the most stripped-down credit product in the bank's inventory: short tenor (typically overnight to one week), no commitment, available at the bank's discretion, priced near money market rates. They serve working capital needs that are too short-term and too routine for a formal credit facility.

From an accounting standpoint, money market line drawdowns are loans — they appear on the balance sheet, carry interest income, and require CECL allowance. But given the very short tenor and typically strong counterparty quality, allowance rates are minimal. The operational risk is operational rather than credit: these facilities can be cancelled without notice, which means a client who has become dependent on them for overnight liquidity is taking on liquidity risk that may not be fully visible in their own treasury management.

Embedded banking and Banking-as-a-Service.

33.1The basic concept

A non-bank platform (a marketplace, fintech app, payroll provider, vertical SaaS) offers banking-like services to its end users — checking accounts, debit cards, payments, lending. Behind the platform, a chartered bank provides the actual banking — holding deposits, issuing cards, settling payments. The platform handles user experience, marketing, and product design; the bank handles regulatory compliance, settlement, and the deposit/credit balance sheet.

The arrangement is often invisible to the end user — they see the platform's brand. The bank's brand may appear in fine print or on card backings. The platform pays the bank for access, sometimes plus per-account fees, sometimes plus revenue share.

33.2Why banks do BaaS

Three economic reasons:

• Deposit growth. BaaS programs can rapidly scale deposit acquisition through the platform's customer base.
• Fee revenue. Per-account fees, transaction fees, and interchange revenue from BaaS-program cards.
• Distribution leverage. Access to customer segments the bank wouldn't reach through its own channels.

33.3The regulatory challenge

The bank remains the regulated entity for BaaS deposits and cards. The platform is the bank's third party. Regulatory expectations:

• Third-party risk management. The bank must conduct due diligence, ongoing monitoring, and contingency planning for the platform partner.
• BSA/AML. The bank is responsible for AML compliance on platform-originated activity, even though customer interactions happen at the platform layer.
• Consumer protections. Reg E, Reg DD, Reg Z all apply to BaaS-issued accounts and cards as if directly issued.
• Capital and liquidity treatment. BaaS deposits flow into the bank's regulatory ratios with their own classification considerations (operational vs. non-operational, retail vs. wholesale).

33.4Recent enforcement and disruption

2023–2024 saw substantial regulatory enforcement and operational disruption in BaaS. Several BaaS-focused banks faced consent orders, restrictions on growth, and operational deficiencies findings. The Synapse Financial Technologies bankruptcy (April 2024) caused customer-fund disruption affecting hundreds of thousands of end users at multiple BaaS partner banks, prompting significant regulatory attention.

The lessons for TS&P controllers operating in BaaS:

• Reconciliation between bank-side ledger and platform-side ledger has to be continuous, not periodic.
• Customer-fund segregation must be unambiguous in legal documentation and operational practice.
• Deposit insurance pass-through to end users requires careful structural documentation.
• Operational continuity planning has to assume platform failure as a realistic scenario.

33.5Accounting treatment

For the bank:

• BaaS-program deposits are bank deposits, classified under standard rules (operational/non-operational, FDIC-insured/uninsured).
• Platform fees received are revenue (ASC 606 — service fees recognized as services performed).
• Card interchange flows through normal interchange revenue recognition (ASC 606, principal-vs-agent analysis).
• Balances held in trust for platform end-users may require off-balance-sheet treatment depending on legal structure.

33.6The future shape

BaaS post-2024 is consolidating. Banks investing in BaaS are doing so with substantially heavier compliance and reconciliation infrastructure than first-generation programs. The list of bank participants is shrinking; the average partner-program size is growing. Expect continued evolution as regulatory frameworks (interagency guidance, FDIC rule changes, OCC examinations) catch up with the operational reality.

33.7The controller's BaaS checklist

Before a bank launches or expands a BaaS program, the controller should be able to answer yes to all of the following:

• Daily reconciliation confirmed. Is there a documented, automated, daily reconciliation between the bank's ledger and the platform's user-level records? Is there a defined break-resolution SLA? The Synapse collapse demonstrated that FBO programs without continuous reconciliation create systemic customer-fund risk that no one at the bank may be tracking.
• Regulatory classification established. Are the platform's end-user deposits classified correctly in the bank's LCR model? FBO deposits are typically non-operational, with less favorable outflow assumptions than the operating deposits in a direct corporate relationship. Has the LCR model been updated to reflect the program's deposit profile?
• Revenue recognition documented. For BaaS fee arrangements — platform fees, per-account fees, interchange sharing — is there an ASC 606 memo documenting performance obligations and recognition timing? Who is principal and who is agent across each revenue stream?
• Capital consumption modeled. BaaS programs that include credit products (buy-now-pay-later, earned wage access loans) generate credit exposure. Are the RWA implications reflected in the program's economics? Undercounting capital consumption is a common source of BaaS program profitability surprises.
• Exit plan exists. What happens to the customers and their funds if the platform or the bank exits the relationship? The wind-down playbook should be documented before launch, not after.

API-first treasury services.

35.1The traditional file paradigm

Historical corporate banking integration: nightly batch files via host-to-host SFTP. The corporate's ERP generates a payment file (NACHA-formatted ACH file, or ISO 20022 XML); the file transmits to the bank; the bank processes; reports flow back the next day.

This model worked for the volumes and pace of decades past but struggles with modern requirements: real-time visibility, instant payments, dynamic FX execution, automated reconciliation, embedded finance use cases.

35.2The API model

API-first treasury offers:

• Real-time balances via API queries.
• Programmatic payment initiation through individual or batch API calls.
• Webhook event streams notifying the corporate of payment events as they happen.
• Transactional reporting with structured data, retrievable in real-time.
• FX execution APIs for instant pricing and trade execution.
• Reconciliation APIs with rich match data.

35.3Authentication and security

The security model differs fundamentally from file-based:

• OAuth 2.0 or mTLS for API authentication.
• API key management with rotation and scope-limited access.
• Rate limiting and throttling.
• Detailed audit logging at API call level.
• Encryption in transit (TLS) and at rest.

35.4The product unbundling

API-first banking enables corporates to mix-and-match bank services rather than buying integrated packages. A corporate might use one bank for FX APIs, another for payment APIs, another for collections — orchestrating the mix in their own ERP or treasury system.

This challenges traditional bank pricing and relationship economics. The bank's response: invest in API quality and reliability to win the right slice; develop partnerships and integrations that increase switching costs.

35.5The controller's reconciliation

API-driven activity creates new reconciliation requirements:

• API call logs vs. backend processing logs vs. GL postings.
• Webhook delivery confirmation and replay handling.
• Real-time balance API consistency vs. batch GL close.
• Idempotency on retried API calls — preventing double-processing.

35.6The future direction

Open Banking frameworks (in EU, UK, Singapore, others) and emerging U.S. open banking via CFPB's Section 1033 rulemaking establish standardized API frameworks across banks. The intent: customers can move their data and authorize third-party access without bank-specific integrations.

For TS&P, the implication is API quality becoming a baseline competitive feature rather than a differentiator. Banks will compete on the products built on top of standardized APIs, not on the APIs themselves.

35.7The controller's view of API-first economics

API-first treasury services change the revenue structure in a specific way: they shift revenue from relationship-bundle pricing toward per-call or per-transaction pricing. This has two accounting implications. First, revenue recognition becomes more granular — instead of recognizing a monthly access fee ratably, the bank recognizes a fee on each API call or each transaction triggered by an API call. Second, the revenue is more volatile — API call volumes vary with the client's business activity, seasonality, and technology choices, in a way that monthly fee schedules don't.

For the controller, this means the forecast and accrual models for API-priced products need to account for volume variability rather than treating the revenue as fixed within the month. A corporate that processes 80% of its annual payment volume in Q4 will generate 80% of its API fee revenue in Q4 — a concentration that needs to be reflected in both the budget and the reserve for variable consideration.

Host-to-host connectivity.

37.1The H2H model

Host-to-host (H2H) refers to direct system-to-system file exchange between the corporate and the bank, typically via SFTP. The corporate's ERP or treasury management system generates payment files; the H2H connection transmits them to the bank; status and reporting files flow back.

Common file formats:

• NACHA-formatted ACH files for U.S. domestic batch payments.
• ISO 20022 XML (pain.001) for cross-border and modern domestic payments.
• Proprietary bank formats for specific products.
• BAI2 format for incoming reporting.
• MT940/MT942 for end-of-day and intraday reporting.
• SWIFT MT/MX for cross-border instructions.

37.2The security and operational layer

H2H requires:

• SFTP server infrastructure with key-based authentication.
• File encryption (PGP/GPG) for sensitive content.
• Digital signatures for authenticity.
• File transfer monitoring and alerting.
• Connection redundancy and disaster recovery.
• Periodic key rotation and access review.

37.3The reconciliation cadence

H2H operates on file cycles, typically daily. The reconciliation cycle:

• Outbound payment file transmitted by corporate cutoff.
• Bank acknowledgment file confirming receipt and validation.
• Bank processing file confirming individual payment status.
• End-of-day reporting file with all activity.
• Corporate ERP reconciles report file against original payment file.

37.4Migration to API

Many H2H workflows are migrating to API equivalents — particularly for activities that benefit from real-time processing (instant payments, FX execution, balance inquiry). However, for high-volume batch payroll or AP runs, file-based H2H remains operationally efficient. A 50,000-record payroll file transmitted via SFTP is faster and cheaper to process than 50,000 individual API calls. The migration is happening at the edges — same-day items, exceptions, status inquiries — while the core batch flow persists.

37.5Fee structure and revenue recognition

H2H fees typically bundle implementation fees (one-time, ASC 606 analysis required for whether these are distinct or modify the ongoing obligation) with ongoing monthly maintenance and per-file or per-transaction processing fees. For large corporates, H2H connections are often negotiated into broader relationship pricing, making revenue attribution to the H2H channel specifically a judgment call that needs documentation.

37.6H2H file format governance and the accounting implication

H2H file formats are not standardized across banks. Each bank's implementation specifies its own file layout for different payment types (ACH, wire, cross-currency). When a corporate switches banks or adds a bank to its panel, the H2H file format change is an operational project. For the receiving bank, the risk is file misparse — a file that doesn't map cleanly to the expected format gets rejected, or worse, partially processed.

The accounting implication of partial processing is significant: if a batch file containing 500 payroll transactions is partially processed — some posted, some rejected — the GL captures only the processed portion. The reconciliation between the file (client-expected) and the GL (bank-actual) will show breaks that are not timing differences. They require investigation, client communication, and potentially reprocessing. Until resolved, the GL does not reflect the client's expected state.

File format governance is therefore a control. The bank should maintain a version-controlled register of approved H2H file specifications by client and payment type. Changes to specifications should go through a formal change process — with testing in a non-production environment before cutover. Undocumented format changes are the leading cause of H2H processing failures.

SWIFT for Corporates.

39.1The SCORE model

SWIFT for Corporates uses the SCORE (Standardised Corporate Environment) framework. A qualifying corporate joins SWIFT directly, gets a BIC, and can send/receive standard SWIFT messages to/from any of its banks through the SWIFT network.

Eligibility historically required substantial scale (large multinational with multi-bank relationships), but the bar has lowered over time. Mid-cap corporates with significant international activity can qualify.

39.2Why corporates do it

• Bank-agnostic connectivity. One technical channel reaches all banks, eliminating per-bank integration costs.
• Standardized messaging. ISO 20022 and MT formats consistent across all bank counterparties.
• Direct beneficiary tracking. SWIFT gpi UETR tracking on payments without bank-specific tooling.
• Negotiation leverage. Easier to switch banks or split flow when not locked into bank-specific channels.

39.3The fee model for SCORE clients

SCORE clients pay SWIFT directly for network access and message fees. The bank's revenue from SCORE clients therefore comes from transaction processing (same fee schedule as any other client initiating a payment), cash management services, and FX — not from channel connectivity fees. This is a meaningful shift from the bank's perspective: the channel revenue that a non-SCORE client generates through portal and H2H fees disappears, replaced only by service revenue. SCORE clients are often the bank's most profitable relationships on a product-revenue basis, but their channel-fee contribution is structurally lower.

39.4ISO 20022 and the SCORE migration

SWIFT's ISO 20022 migration (mandatory for cross-border payments since November 2025) affects SCORE corporates directly. Unlike bank-facing migration, where the bank can run MT-to-MX translation services and shield clients from format changes, SCORE corporates connect to the network directly and must manage their own message format migration. Banks provide advisory support, implementation guidance, and testing environments — but the corporate owns the outcome. For large multinationals on complex TMS platforms, the migration was significant work.

39.5The controller's view

For SCORE clients, the bank's role shifts: less channel-management friction, more emphasis on service quality and pricing discipline. The TS&P controller verifies SWIFT message receipt and processing completeness, reconciles SWIFT-routed transactions through standard payment ledgers (the routing path doesn't change the accounting), monitors corporate relationship volume and pattern shifts that might indicate wallet-share loss, and works with the relationship team on ensuring fee schedules are current.

One nuance worth understanding: a SCORE corporate's payment initiating via SWIFT still settles through the same payment system infrastructure (Fedwire for USD wires, CHIPS for large-value international, ACH for batch) as any other client. SWIFT is the messaging channel; settlement is unchanged. The reconciliation should treat SWIFT-initiated transactions identically to portal-initiated or H2H-initiated transactions for accounting purposes.

39.6SWIFT corporate connectivity and the multi-bank challenge

The defining feature of SWIFT-connected corporate clients is multi-bank connectivity — they use SWIFT precisely because they have relationships with multiple banks and want a single channel for all of them. This creates an asymmetry in the relationship: the corporate has full visibility across all of its banking relationships through one interface; each bank sees only its own slice of the corporate's total activity.

For the TS&P controller, this visibility asymmetry has pricing implications. A corporate that moves $500M per month through your bank over SWIFT may be moving $5B per month total across five banks. The pricing case for the SWIFT channel — which is expensive to maintain relative to direct H2H or API — depends on capturing the right share of that total wallet. If the corporate sees equivalent service at a lower-cost direct channel competitor, SWIFT's justification erodes.

The fee structure for SWIFT corporate services typically has two layers: a connectivity fee (for maintaining the SWIFT link and the associated operational overhead — KYC of the SWIFT bureau, traffic monitoring, message validation) and a per-message or per-transaction fee on top. The per-message fee is increasingly under pressure as corporates negotiate volume-based pricing across their banking panels.

Net interest income recognition.

41.1What NII actually is in TS&P

Net interest income at a bank is the spread between what the bank earns on assets and what it pays on liabilities. For TS&P specifically, the segment doesn't directly hold loans or investment securities — it holds deposits. The NII that accrues to TS&P is almost entirely the FTP credit the segment earns for providing those deposits to the bank's funding pool.

The mechanism: when a corporate client parks $50M in a non-interest-bearing operating DDA, the bank's treasury function "buys" that funding from TS&P at the FTP curve rate. TS&P books FTP credit income; bank treasury books a FTP funding cost. Neither represents external cash movement — it's an internal allocation. But it drives the P&L that segment management and the board review.

TS&P NII has four main components:

• FTP credit on operating deposits. Largest component by far. Applied to non-interest-bearing DDAs, MMDAs, and other operating balances at the FTP curve rate for the behavioral tenor of the deposit.
• FTP credit on time deposits. Applied at the deposit's contractual tenor — a 90-day time deposit gets the 90-day FTP rate at the time of origination, locked for the deposit's life.
• Interest on credit-adjacent products. Drawn revolvers, SCF receivables, trade loans carry actual interest income at contractual rates. These are genuine external earnings, not FTP.
• FTP charges on capital and credit. Internal charges for the capital allocated to credit exposures and the funding the segment uses for credit drawdowns. Reduces NII.

41.2FTP recognition timing and GL mechanics

FTP credits and charges accrue daily based on end-of-day or average daily balances and the applicable FTP curve rate. The daily accrual posts to an internal P&L account. At month-end, the accumulated accruals represent the period's FTP-driven NII.

The GL mechanics are typically:

• Daily: Dr. Internal FTP Receivable / Cr. FTP Credit Income (TS&P books credit)
• Daily: Dr. FTP Funding Cost (Bank Treasury books charge) / Cr. Internal FTP Payable
• Month-end: Intercompany netting eliminates the receivable/payable pair at consolidation

The FTP credit income line in TS&P's income statement is entirely eliminated at the consolidated bank level — it only exists in the segment reporting. This is the reconciliation item between segment NII and consolidated bank NII.

41.3Rate sensitivity and NII at risk

TS&P NII is highly rate-sensitive, but in a counterintuitive direction for operating deposits: when rates rise, FTP credits on non-interest-bearing deposits rise (the bank earns more on the funding), but the bank also faces higher rates on its interest-bearing liabilities. The net effect on TS&P NII depends on how much of the deposit base is non-interest-bearing vs. interest-bearing.

The 2022-2023 Fed tightening cycle demonstrated this clearly. Banks with large operating DDA franchises saw TS&P NII surge as the FTP rate on those non-interest-bearing balances rose from near-zero to 5%+. The deposit base was the asset; higher rates made it more valuable.

The ALCO monitors NII at risk — the estimated change in NII for a given rate scenario. TS&P's contribution to that metric is dominated by its deposit behavioral assumptions. The controller should understand which rate scenario drives the most NII pressure for the segment.

41.4Non-accrual and impaired assets

For credit-adjacent products (drawn revolvers, SCF receivables, trade loans) that become impaired, ASC 326 and regulatory guidance require non-accrual treatment. Once a loan is placed on non-accrual:

• Interest income recognition stops immediately.
• Previously accrued but uncollected interest is reversed.
• Cash collected applies to principal first; interest recognized only after principal is recovered.

For TS&P, the non-accrual population is typically small relative to the funded credit book, but the NII impact can be material on individual relationships. Track the non-accrual roll-forward as part of the close cycle.

41.5Disclosure requirements

External NII disclosure for bank segments follows ASC 280 (segment reporting). TS&P is typically disclosed as a reportable segment if it meets the quantitative thresholds (10% of combined revenue, profit/loss, or assets). The segment disclosure includes revenue (NII + fee revenue), segment profit, and total assets. The FTP elimination is disclosed as a reconciling item between segment totals and the consolidated total.

41.4The FTP reconciliation that closes the loop

External financial statements show NII as a single line: interest income minus interest expense. Internally, the bank's FTP system bifurcates that line into the spread earned by each business unit and the interest rate risk retained by treasury. For TS&P, the internal NII line is composed of: FTP credits on deposits (positive), FTP charges on capital allocation and credit commitments (negative), and direct interest expense on any interest-bearing deposits the bank pays to clients.

Reconciling internal segment NII to the external NII disclosure is a standard quarterly control. The reconciliation should account for: the netting of intra-company FTP charges and credits that eliminate on consolidation, the treatment of rate risk, and any hedge accounting allocations that the ALM function runs through NII. If the reconciliation breaks at quarter-end, it almost always traces to a FTP methodology change that wasn't communicated to the segment reporting team, or an allocation that was updated in the transfer pricing system but not reflected in the segment P&L system.

41.5Rate sensitivity and NII volatility

TS&P segment NII is highly rate-sensitive. When the Fed raises rates, FTP credits on operational deposits reprice upward — but with a lag determined by the behavioral tenor assumption and the speed of FTP curve recalibration. Clients simultaneously seek higher yields, pushing some balances from non-interest-bearing DDAs into interest-bearing alternatives. The net effect on NII depends on the rate of balance migration relative to the rate of FTP credit increase. Managing this dynamic is an ALCO-level decision; the TS&P controller tracks the outcome and explains the variance.

Off-balance-sheet exposures and CCFs.

44.1What's off-balance-sheet

Common off-balance-sheet exposures in TS&P:

• Unfunded committed credit lines (RCFs).
• Undrawn standby letters of credit.
• Documentary letters of credit outstanding.
• Daylight overdraft commitments.
• Loan commitments not yet drawn.
• Notional amounts of derivatives held for client business.
• Pending purchase or sale commitments.

These don't appear in the balance-sheet face but appear in regulatory schedules (FFIEC 031 Schedule RC-L, Y-9C off-balance-sheet supplements) and financial statement footnotes.

44.2Credit Conversion Factor mechanics

Under Basel III standardized approach, off-balance-sheet exposures are multiplied by a CCF to produce a credit-equivalent on-balance-sheet amount, then risk-weighted normally:

• 0% CCF: rare in TS&P; some short-term self-liquidating trade loans on commercial LCs.
• 20% CCF: short-term documentary LCs (under one year).
• 50% CCF: over-one-year commitments that aren't unconditionally cancelable.
• 100% CCF: direct credit substitutes (standby LCs, financial guarantees).

44.3Recent CCF rule changes

Basel III endgame proposals in the U.S. (with proposals from 2023 onwards) include changes to off-balance-sheet treatment, particularly for commitments. The proposed treatment generally increases CCFs for unfunded commitments — meaning higher RWA and capital consumption for revolvers and other commitment products.

Implementation timing remains subject to ongoing rulemaking. The TS&P controller should follow the rulemaking timeline and prepare for prospective changes through capital impact analysis.

44.4The reconciliation challenge

Off-balance-sheet exposures are notoriously difficult to reconcile because they live in multiple systems:

• Loan/credit system holds the commitment record.
• LC system holds standby and documentary LC outstanding amounts.
• Derivative trading system holds derivative notional.
• Regulatory reporting system aggregates from all of the above.

Drift between these systems is the most common source of off-balance-sheet reporting errors. The controller's monthly close routine should include explicit cross-system reconciliation — commitment balance per the credit system vs. commitment balance per the regulatory schedule, tied to the penny.

44.5CECL allowance on off-balance-sheet

Under ASC 326, unfunded commitments that are not unconditionally cancellable require an allowance for expected credit losses — the "reserve for unfunded commitments." This allowance is a liability on the balance sheet (not a contra-asset) and reflects lifetime expected losses on the amounts expected to be drawn.

The mechanics: for an unfunded $100M RCF with 35% expected utilization, the expected funded amount is $35M. Apply the same PD × LGD × EAD model as the funded allowance to that $35M expected draw. Record the result as a liability.

Movement in this reserve runs through provision expense on the income statement, the same line as funded allowance provisions. Many banks present funded and unfunded provisions together; the controller should understand the two components independently to explain changes.

44.6Capital impact modeling

Off-balance-sheet exposures often drive more capital consumption per dollar of exposure than funded assets, because the CCF translates the full notional (not just the funded portion) to a credit-equivalent amount. A $100M standby LC at 100% CCF consumes the same RWA as a $100M funded loan — even though no cash has moved.

The practical implication for relationship economics: a large standby LC in a corporate relationship may consume as much capital as a drawn revolver at the same commitment size. Relationship pricing must account for the full off-balance-sheet capital footprint, not just the drawn portion.

44.4The CCF and CECL interaction

For off-balance-sheet credit exposures, the CCF determines what fraction of the undrawn commitment to include in the CECL calculation. An unfunded commitment with a 50% CCF means 50% of the undrawn is treated as if it were drawn for expected-loss purposes. The resulting expected credit loss runs through the allowance for credit losses — recorded as a liability ("reserve for unfunded commitments"), separate from the contra-asset for funded exposures.

The quarterly movement in the off-balance-sheet reserve feeds provision expense, same income statement line as the funded allowance movement. A large new commitment added in the quarter drives reserve build; a commitment that expires or gets cancelled drives reserve release. For TS&P, the largest off-balance-sheet credit exposures are typically revolving credit facilities (which have a CCF of around 50% for unfunded portions and 100% for drawn), standby letters of credit (100% CCF), and committed daylight overdraft lines.

44.5Common controller traps

Three recurring CCF-related errors: First, misclassifying standby LCs as documentary LCs. Standby LCs carry a 100% CCF; documentary LCs under one year carry only 20%. The difference is material. Second, failing to update CCFs when the underlying commitment structure changes — for example, when a bilateral commitment converts to a syndicated structure with a different bank's CCF methodology. Third, not capturing commitment expirations in the period they occur, which causes the off-balance-sheet reserve to be overstated until the next reconciliation cycle.

ASC 815/830 — FX in TS&P.

46.1The functional currency concept

ASC 830 establishes "functional currency" — the currency of the primary economic environment in which an entity operates. For most U.S. bank entities, USD. For a London branch, GBP. For a Singapore subsidiary, SGD.

Functional currency drives:

• Which currency is used for primary measurement.
• How foreign-currency transactions get remeasured.
• How financial statements translate for consolidation.

46.2Remeasurement vs. translation

• Remeasurement. Converting foreign-currency transactions and balances of an entity into its functional currency. Gains/losses to earnings.
• Translation. Converting an entity's functional-currency financials into the reporting currency for consolidation. Gains/losses to OCI as Cumulative Translation Adjustment (CTA).

46.3Where TS&P sees FX impact

• Foreign-currency operating deposits — remeasurement at each reporting date if held by USD-functional entity.
• FX trade settlements — gains/losses on FX trades flow through trading P&L.
• Foreign branch operations — translation through CTA on consolidation.
• Net investment hedges — derivative gains/losses to OCI alongside CTA.

46.4The hedge accounting application

For ASC 815 application to FX hedges, see Ch 25. Common patterns in TS&P:

• Cash flow hedges of forecasted foreign-currency operating expenses.
• Net investment hedges of foreign branch equity.
• Fair value hedges of recognized foreign-currency assets or liabilities.

46.5The functional currency question

Before any FX accounting can be applied, the functional currency of each legal entity must be determined. ASC 830 defines functional currency as the currency of the primary economic environment in which the entity operates. For most U.S. bank entities, this is USD. For foreign branches or subsidiaries that primarily transact in the local currency, the functional currency may be the local currency.

The determination matters enormously: if a foreign entity's functional currency is the local currency, the entity's financial statements are translated to USD at period-end rates (with CTA accumulating in OCI). If the functional currency is USD, the entity's foreign-currency transactions are remeasured to USD using historical or current rates depending on the account type, with remeasurement gains/losses going directly to earnings. Remeasurement volatility flows through the income statement; translation volatility is captured in OCI.

46.6The controller's practical FX workflow

For TS&P operations with foreign-currency activity:

• Daily: capture all foreign-currency transactions at the transaction-date spot rate.
• Month-end: remeasure monetary assets and liabilities (foreign-currency bank balances, receivables, payables) at the closing rate. Non-monetary items (goodwill, fixed assets) stay at historical rates.
• Month-end: record remeasurement gains and losses to the FX gain/loss income line (for USD-functional entities) or to CTA (for local-currency-functional entities).
• For entities with FX hedges: apply hedge accounting per ASC 815, with the effective portion of cash flow hedge gains/losses flowing through OCI and ineffective portions to P&L.

The TS&P close cycle.

48.1The close timeline

Typical TS&P close cadence:

• Last business day of month: daily activity continues; no special close events.
• Day +1: overnight processing finalizes; opening balances locked.
• Days +2 to +4: revenue accruals, FTP allocations, fee reversals, intercompany matching.
• Days +5 to +7: reconciliations across systems and to GL, exception clearing.
• Days +8 to +10: management reporting prepared, segment management review, attestations.
• Days +10 to +15 (quarter-end): external reporting preparation, disclosures drafted, SOX certifications.

48.2The sequence of close activities

1. Daily and intraday cutoffs finalized.
2. Operational systems closed for the period; postings locked.
3. Sub-ledger balances reconciled to GL.
4. Intercompany transactions matched and eliminated.
5. Revenue and expense accruals recorded.
6. Reserve methodologies applied (CECL, ASC 450).
7. FTP credits and charges posted.
8. Segment reporting compiled.
9. Management review and adjustments.
10. Final lock and reporting submission.

48.3The pain points

Most TS&P close challenges concentrate in:

• Accrual accuracy. Fee revenue accruals across millions of transactions; misclassifications surface here.
• Reconciliation breaks. Sub-ledger to GL mismatches; reconciliation queues clearing.
• Reserve sufficiency. Whether posted reserves capture what they need to capture; CAO sign-off if material.
• Intercompany matching. Cross-entity flows reconciling, especially in multi-currency environments.
• Foreign branch consolidation. Translation, elimination, CTA tracking.

48.4The controller's checklist

• All sub-ledger balances reconciled to GL.
• All revenue accruals supported by source-system data.
• All reserves at proper level with documentation.
• All intercompany matched and eliminated.
• All exceptions cleared or escalated.
• All required disclosures drafted and supported.
• SOX certification ready for sign-off.

48.5Continuous close

Modern TS&P operations increasingly aim for "continuous close" — daily completion of close activities so that month-end is largely a snapshot rather than an extended exercise. Achieving this requires:

• Daily reconciliations across all subsidiaries and systems.
• Daily accrual postings rather than month-end-only entries.
• Real-time data feeds rather than batch.
• Automated exception identification and routing.

Few organizations achieve full continuous close, but progress in this direction reduces close cycle time and improves earnings predictability.

48.6The controller's close calendar

A practical TS&P close runs roughly:

• Day 1-2 after month end: Flash close — preliminary revenue and expense; major accruals posted. Catch material variances early while the business still has context.
• Day 3-4: Reconciliations tied, system-to-GL confirmed, sub-ledger reconciliations cleared. Reserve roll-forwards complete. FTP true-up if applicable.
• Day 5-6: Income statement and balance sheet finalized. Footnote disclosures drafted. Segment reporting package prepared.
• Day 7-10: Management review, CFO/CAO sign-off, regulatory reporting inputs submitted.

The earlier in this cycle you can surface surprises, the better. A variance flagged on Day 2 can be explained and documented. A variance surfaced on Day 8 becomes a fire drill.

48.4The accrual cut-off problem

TS&P fee revenue accrues continuously but often settles on a lag. Wire fees processed on the last day of the quarter may not appear in the billing system until the next day; ACH return fees may hit in the following settlement window; FX margin earned on a spot trade executed at 4:55 PM may settle T+2 into the next quarter. Getting the accrual cut-off right requires knowing, for each product, what the recognition event is (when the performance obligation is satisfied) versus when the cash settles. They are different things, and confusing them creates both over-accruals and under-accruals.

For interest income, the daily accrual on deposits and credit products is mechanical but not trivial at scale. The accrual engine needs to correctly handle day-count conventions (Actual/360 for most money market products, Actual/365 for some), stub periods at the beginning and end of facilities, and rate resets on floating-rate products. A wrong day-count convention on a large deposit or credit facility can misstate NII by a meaningful amount over a quarter.

48.5Month-end vs. quarter-end close

Most TS&P controllers run a full close each month, with additional steps and reviews at quarter-end for external reporting. The incremental quarter-end work includes: management representation letters on significant accounting estimates, variance analysis with narrative explanations, review of off-balance-sheet commitments for completeness, CECL and ASC 450 reserve recalibration, FTP curve validation, and regulatory reporting tie-outs. Building a clean quarter-end close calendar with specific owners for each deliverable is one of the highest-leverage things a TS&P controller can do.

49.4Aging and escalation

Every reconciliation break needs an owner, a root-cause analysis, and a resolution timeline. The reconciliation control is not complete when the break is identified — it is complete when the break is resolved and the root cause is documented. Aging breaks are the most common SOX finding in TS&P: a reconciliation item that has been outstanding for 60 or 90 days, with no documented resolution path, is a control deficiency regardless of whether it's ultimately a balance-sheet error or a timing difference.

Escalation criteria should be defined in the procedure: any break over a dollar threshold gets escalated to the controller within 24 hours; any break open beyond a defined number of business days gets escalated to the CAO; any break that can't be explained after investigation gets an ASC 450 reserve analysis. These thresholds should be calibrated to materiality and reviewed annually.

49.5The reconciliation hierarchy

In a well-run TS&P close, reconciliations cascade: sub-ledger to general ledger, general ledger to management reporting, management reporting to regulatory reporting. Each layer should foot to the layer above it. When they don't, finding the break is a matter of working down the cascade — the break will be between two adjacent layers, and narrowing it to the right pair of layers usually isolates the error quickly.

SOX 404 in TS&P.

50.1The SOX framework

Section 404 of Sarbanes-Oxley requires public companies (and large bank holding companies as registered issuers) to:

• Establish and document internal controls over financial reporting (ICFR).
• Test those controls' design and operating effectiveness.
• Management certifies controls each fiscal year (Section 302 quarterly, 404 annually).
• External auditor opines on ICFR effectiveness.

50.2The control inventory in TS&P

Common TS&P SOX controls:

• Authorization controls. Approval of transactions above thresholds.
• Reconciliation controls. Daily/monthly reconciliations between systems and to GL.
• Segregation of duties. Different individuals initiate, approve, and record transactions.
• System access controls. Logical access to systems matches role requirements.
• Change management controls. System changes follow documented approval and testing.
• Estimate controls. Reserves and accruals follow documented methodologies.
• Disclosure controls. Quarterly and annual disclosures supported by documented review.

50.3The testing cycle

Annual SOX testing cycle:

• Q1: Walkthroughs and design assessment.
• Q2-Q3: Operating effectiveness testing.
• Q4: Roll-forward testing through year-end.
• Year-end: Final attestation and opinion.

50.4Key controls and entity-level controls

SOX testing distinguishes:

• Key controls. Specific controls over financially material processes.
• Entity-level controls. Tone-from-the-top controls (governance, risk culture, compliance program).
• IT general controls. Cross-cutting IT controls supporting application controls.

50.5Deficiencies and remediation

SOX deficiencies are categorized:

• Control deficiency: control not operating as designed.
• Significant deficiency: deficiency or combination resulting in less than reasonable assurance.
• Material weakness: reasonable possibility of material misstatement.

Material weaknesses must be disclosed publicly, trigger external audit qualifications, and require remediation plans. The TS&P controller's role: identify, escalate, remediate.

50.6The highest-risk TS&P control areas

Not all SOX controls carry equal audit scrutiny. In TS&P, the following consistently attract the most attention:

• Reserve methodology controls. CECL allowance, ASC 450 operational reserves, and fee accruals all require documented methodologies and quarterly sign-off by qualified reviewers. Any change to methodology requires its own change-control process — mid-year methodology switches without documentation are a perennial finding.
• FTP credit controls. The FTP allocation is the largest revenue line in segment reporting and exists nowhere in external financials. Auditors test that the rate, the balance, and the calculation are all controlled. A missing control over who can change the FTP curve parameters is a classic significant deficiency.
• Payment hub-to-GL reconciliations. High transaction volume means high materiality. Missing daily reconciliations or systematic breaks that were signed off without resolution are tested intensively.
• Revenue cut-off controls. Ensuring that fee revenue is recognized in the correct period. Late transaction postings that push revenue across period boundaries are particularly watched.
• User access reviews. Segregation of duties within payment processing systems — who can initiate payments, who can approve them, who can modify system parameters — is heavily tested. Access that hasn't been reviewed quarterly is an automatic finding.

50.7Practical control documentation

A well-documented SOX control has five elements: (1) the risk it mitigates, (2) the control activity — what happens, who does it, how often, (3) the evidence produced — what document or system record proves the control ran, (4) the review — who reviewed the evidence and when, (5) the escalation path if the control fails. Controls documented at this level survive walkthroughs. Controls documented as "reviewer signs off" without specifying what they reviewed fail on design.

51.4Basel operational risk capital

Under Basel III's Standardised Approach for operational risk (effective for large U.S. banks under the Basel III endgame rules), operational loss history directly affects the capital the bank must hold against operational risk. The ILM (Internal Loss Multiplier) component of the Standardised Approach incorporates the bank's 10-year average annual loss ratio relative to the industry. A bank with high historical op losses holds more capital than a bank with clean loss history. This makes operational loss management a capital-efficiency question, not just a compliance question.

51.5Recovery and insurance

Operational losses are reported gross and net of recoveries. A wire fraud loss of $2M that results in a $1.5M recovery from law enforcement asset forfeiture is recorded as a $2M loss and a $1.5M recovery, not as a $500K net loss. This matters for Basel reporting, which requires gross loss data, and for internal P&L, where the timing of recovery (often quarters or years after the original loss) creates distortions in period reporting. Insurance recoveries add another layer: insurance claims are often settled long after the loss event, and the receivable needs to be assessed for collectibility before it's recognized.

Payment hub architecture.

52.1What a payment hub does

A payment hub provides:

• Single ingress point for payment instructions across channels (portal, H2H, API).
• Validation, enrichment, and routing logic by payment type, currency, urgency, value.
• Sanctions and AML screening on every payment.
• Authorization and approval workflow.
• Outbound transmission to specific payment rails (Fedwire, ACH, RTP, CHIPS, SWIFT, FedNow).
• Status tracking and event publishing.
• Reporting and reconciliation feeds.

52.2The "rail-agnostic" promise

Modern hub architectures aim to be rail-agnostic — the same payment instruction can execute on any appropriate rail. The hub's routing engine selects based on rules: cost, speed, recipient bank capability, customer preference. This decouples customer experience from underlying rail differences.

In practice, full rail-agnosticism is difficult. Different rails have different field requirements, limit structures, and operational characteristics. Most hubs achieve partial rail-agnosticism — basic routing flexibility with rail-specific logic preserved where needed.

52.3Vendor vs. proprietary hubs

Major commercial payment hub products: Volante, Finastra Total Messaging, ACI Worldwide, FIS, Bottomline. Many large banks have built proprietary hubs; mid-sized banks more commonly buy.

The build-vs-buy decision considers customization needs, scale, internal capability, and vendor risk. Recent industry direction: hybrid approaches with vendor cores plus proprietary extensions for differentiating capabilities.

52.4Resilience, failover, and the controller's continuity concern

Payment hubs are single points of failure if not architected for resilience. A hub outage doesn't just disrupt operations — it disrupts accounting. If the hub goes down mid-day and transactions fail to post, the master account reconciliation for that day will have unexplained gaps. The GL feed stops. Accruals go stale. The question of which transactions were sent, which were accepted, and which were queued is answered only after the hub recovers and the event log is replayed.

For the controller, the continuity concern is specific: what is the documented procedure when the hub fails? Banks with mature operational resilience frameworks have tested runbooks for hub outage — including the accounting procedure. What gets accrued, what gets deferred, and when does the close team get notified? This should be written down before an outage, not reconstructed after one.

Secondary concern: payment hub vendors. A hub that is operated by a third-party technology provider introduces vendor risk. If the vendor has an outage, the bank's payment operations stop. Third-party risk management for the payment hub should include not just operational SLAs but accounting recovery procedures — how long before the bank can reconstruct a clean GL from the hub's audit logs after an extended vendor outage.

Product interaction & relationship economics.

54.1The relationship-level view

For a TS&P-anchored corporate relationship, profitability comes from:

• Deposit revenue (FTP credit on operating balances).
• Fee revenue (wire, ACH, FX, lockbox, card).
• Interest spread (drawn revolver, SCF, trade finance).
• FX margin (cross-currency activity).
• Capital markets revenue (where attribution flows back).

Cost: capital allocation, FTP charges on credit, operational cost, sales cost.

54.2Cross-product economics

Common interaction patterns:

• RCF anchors relationship, generates ancillary TS&P fee revenue.
• Operating deposits feed sweep products generating MMF or repo revenue.
• Payment volume creates reconciliation needs justifying portal/API premium.
• FX activity bundles with payments at higher margin than standalone FX.
• Multi-currency accounts capture deposit value across multiple FTP curves.

54.3The "share of wallet" concept

Most large corporates use multiple banks. Each bank captures a "share" of the corporate's banking activity. Share of wallet directly drives profitability — a 30% share corporate generates roughly 30% of the relationship economics.

Banks track share of wallet as a primary relationship metric. Increasing share is the highest-leverage relationship activity. Cross-product capability is the typical lever.

54.4The relationship attribution challenge

Attributing revenue to relationships is operationally difficult:

• Subsidiary accounts may belong to parent relationships but be operationally separate.
• FX trades execute in capital markets but originate in TS&P relationships.
• Capital markets revenue may flow back through indirect channels.
• Cost allocation across products is methodology-dependent.

The controller's reconciliation: ensuring relationship-level reporting ties to product-level reporting and to overall segment results.

54.5The product interaction multiplier

The most important insight in TS&P relationship economics is the multiplier: products don't add value independently; they multiply. A corporate with operating deposits, a revolving credit facility, cross-currency payment activity, and a supply chain finance program generates more total economic value than the sum of the four products independently — because the operating deposit is the collateral for the credit, the credit enables the supply chain finance, and the payment volume generates data that improves FX pricing. Each product makes the others more valuable and more sticky.

Quantifying the multiplier is difficult but important. One approach: compare the per-dollar revenue yield on single-product relationships (deposit-only, credit-only) against multi-product relationships of similar size. At most large banks, the multi-product premium is 40-60% in revenue yield terms. This is the empirical case for relationship banking over transactional banking, and it's the economic justification for the "anchor product" model — accept lower margin on the credit to win the deposits and payments.

Bank-permissioned blockchain.

56.1What permissioned means

A permissioned blockchain restricts who can read, write, and validate transactions on the ledger. Participants are known, KYC'd, and contractually bound. Consensus is among permitted parties rather than open mining or staking.

For banks, permissioned blockchains preserve the AML, KYC, and regulatory standing that public chains lack while delivering the operational benefits of shared ledgers — atomic settlement, programmable logic, transparent state.

56.2Major institutional examples

• Institutional deposit token platforms. Several G-SIBs operate live deposit token infrastructure as of 2025-2026 — covering interbank repo settlement, institutional payment rails, and hybrid permissioned/public-chain deployments. These platforms are actively processing live transactions.
• Citi Token Services. Cash and trade tokenization for Citi's institutional clients.
• Fnality. Multi-bank consortium operating tokenized central-bank money for wholesale settlement.
• Partior. Singapore-led multi-bank network for cross-border settlement.
• HSBC Orion. Bond tokenization platform.

56.3Use cases that have stuck

• Intraday repo settlement among consortium participants.
• Cross-border payments with token-based atomic settlement.
• Tokenized deposit movements within a single bank's books.
• Securities settlement (DvP via on-chain).
• Trade finance documentation and settlement.

56.4The accounting question

Tokens issued on a bank-permissioned blockchain that represent claims on bank deposits are still bank deposits — the legal nature doesn't change because the recordkeeping medium does. Accounting treatment follows the underlying instrument, with disclosure attention to the token-specific operational features.

56.5The interoperability question

Permissioned blockchains face the interoperability question — how to settle transactions across chains operated by different banks or consortia. Common patterns: trusted bridges, atomic-swap mechanisms, central settlement layers (CBDCs or commercial bank money). The technical solutions are evolving; the regulatory framework is partial.

56.4The accounting for deposit tokens

When a bank issues a deposit token on a blockchain, the token represents a claim on the bank — it is functionally a deposit liability. The accounting mirrors traditional deposit accounting: the bank records a deposit liability when the token is issued and extinguishes it when the token is redeemed. The token doesn't create a new asset; it's a different representation of an existing liability. Under ASC 305, whether the token constitutes "cash or cash equivalents" for the holder depends on redeemability and maturity — a bank-issued deposit token that is immediately redeemable at par in USD is likely cash-equivalent for the holder's balance sheet.

The complexity comes in two places. First, if the token trades on a secondary market at a discount or premium to par (possible if redemption is restricted or the issuing bank is perceived as risky), fair value measurement questions arise. Second, if the token accrues interest, the accrual mechanics on a blockchain instrument may differ from traditional deposit interest mechanics, and the accounting needs to follow the economic substance.

56.5Accounting for bank-permissioned blockchain activities

When a bank operates a permissioned blockchain network (not just participates in one), several novel accounting questions arise that don't have settled GAAP answers. The FASB has not issued definitive ASC on most of these:

• Transaction processing fees on blockchain. If the bank charges a fee for processing a tokenized payment or settling a smart contract, the ASC 606 performance obligation analysis applies. The blockchain is the delivery mechanism; the performance obligation is the settlement service. Point-in-time recognition at transaction execution is the natural conclusion for most atomic settlement arrangements.
• Network infrastructure costs. Blockchain node operation has real costs — compute, storage, connectivity, compliance. These are operating costs that belong in non-interest expense. The controller should ensure they're categorized correctly and not buried in technology overhead without visibility to the TS&P segment.
• Token issuance accounting. If the bank issues deposit tokens (bank-created digital instruments representing deposit liabilities), the issuance is not a revenue event — it's a liability creation. The bank has received an asset (cash, in most cases) and issued a liability (the token). Revenue is earned subsequently through the deployment of that funding (FTP credit on the deposited funds).
• Smart contract failures. If a smart contract executes incorrectly — paying the wrong amount, to the wrong address, under the wrong conditions — the bank may bear remediation liability. This is an operational loss event under Basel categories. The accounting treatment follows ASC 450: probable and estimable test, reserve or expense recognition.

Deposit tokens vs. stablecoins.

57.1What a deposit token is, mechanically

A deposit token is a tokenized claim on an existing bank deposit, issued by a chartered bank to its institutional clients. Mechanically: when an institutional client wants to use the token, the bank issues an equivalent face amount of deposit tokens against the client's existing deposit balance. The token is transferable on a permissioned or public blockchain. When tokens are received, they can be redeemed back into deposit balance at the issuing bank.

The token is fungible with the underlying deposit. It is, accounting-wise, the same instrument — just with a different rail for moving it. The bank's deposit liability doesn't change in nature; only its presentation and movement mechanics do.

57.2What a stablecoin is, mechanically

A stablecoin is a token issued by a non-bank issuer, backed by a separate pool of reserves (typically T-bills, repo, and bank deposits). The stablecoin is not a claim on a bank deposit — it's a claim on the issuer, which in turn holds reserves. The end user holds the stablecoin; the issuer holds the reserves.

57.3The GENIUS Act framework

The Guiding and Establishing National Innovation for U.S. Stablecoins Act (2025) established the federal regulatory framework. Key provisions:

• Payment stablecoin issuers must be chartered banks or licensed nonbanks.
• 1:1 reserve backing required, in specified high-quality liquid assets.
• Issuers may not pay interest on stablecoin holdings.
• Disclosure requirements (monthly reserve composition, attestation).
• Bankruptcy treatment — stablecoin holders have priority claims on reserves.

The act normalized U.S. stablecoins for the first time, but also constrained them — particularly the no-interest provision, which is the structural feature that opens the door for deposit tokens to compete on different terms.

57.4The interest-bearing distinction

A bank-issued deposit token can pay interest. The token is a deposit, and deposits can earn interest under standard banking rules. A stablecoin cannot, by GENIUS Act rule.

For institutional users — particularly trading firms, treasuries, and asset managers — the interest-bearing question is meaningful. A trading firm holding $500M of stablecoins as on-chain working capital is forgoing the yield it could have earned holding the same balance as bank deposits. A deposit token gives them on-chain liquidity and yield. The economic argument for institutional adoption tilts heavily toward deposit tokens.

57.5The accounting argument for deposit tokens

From an institutional client's accounting perspective, deposit tokens are a much cleaner instrument than stablecoins. Banks have explicitly stated that institutional clients can treat deposit tokens as bank deposits on their balance sheet — fungible with their existing deposit accounts at the same bank, eligible for the same accounting treatment, no new policy required.

Stablecoins, by contrast, raise multiple unresolved accounting questions:

• Are they cash, cash equivalents, or financial assets at fair value?
• How are they classified in the LCR for the holder?
• How are they treated for credit risk concentration analysis?
• What's the accounting for the gain/loss on a stablecoin that briefly de-pegs from $1.00?

The institutional accounting answer for deposit tokens is "treat them as deposits — same as before." That clarity is a major selling point.

57.6Public-blockchain deployment

Several major U.S. banks moved their deposit tokens from private permissioned chains onto public blockchain infrastructure (typically Ethereum Layer 2 networks like Base) starting in mid-2025. This is a substantial step for institutional finance: traditional bank deposits, as tokens, transferring on the same public infrastructure as DeFi applications.

The deployment is permissioned: only KYC-approved institutional counterparties can hold or transfer the tokens. The public chain provides the rail; the bank provides the access control. The result is the speed, transparency, and 24/7 availability of public chains combined with the regulatory and accounting clarity of bank deposits.

57.7The fragmentation question

The structural risk for deposit tokens is fragmentation. If every major bank issues its own deposit token, and the tokens aren't interoperable, the result is many bank-specific tokens that look like loyalty points rather than money. Institutional users would have to maintain balances at each issuing bank, manage cross-bank conversions, and absorb the friction.

Industry leaders have flagged this. The traditional dollar maintains "singleness of money" because the Fed's central role allows any bank's dollar to be functionally equivalent to any other bank's dollar at par. The same property doesn't yet exist for digital dollars. The market will likely consolidate around interoperability layers — whether bank-led tokenized FedNow, third-party bridges, or eventual wholesale CBDC for interbank settlement.

57.8What the controller needs to track

For a TS&P controller, deposit tokens introduce several new questions:

• Interest accrual on tokens. When the token starts paying interest, the accrual logic on a 24/7-traded instrument breaks legacy batch-based accrual systems. Implementation work is non-trivial.
• LCR treatment. Are tokenized deposits classified the same as conventional deposits? Regulatory guidance is evolving.
• Reconciliation. Tokens transferring on public chains generate on-chain settlement events that need to flow into the GL on a continuous (not batch) basis.
• Reserves and disclosure. No new methodology required, but disclosure of tokenized deposit balances may emerge as a standard practice.
• Cross-product implications. When tokens enable 24/7 settlement, the products that depend on settlement cutoffs (sweeping, FX, supply chain finance) all change.

Real-time treasury: 24/7.

59.1The traditional treasury day

Historically, corporate treasury operated in cycles: morning balance review, midday position-taking, end-of-day funding decisions, overnight close. Cash flow forecasts updated daily. Hedge decisions made periodically.

This rhythm matched the underlying payment infrastructure — file-based ACH, batch wire processing, end-of-day settlement. Treasury and payments operated on compatible cycles.

59.2The 24/7 reality

With instant payments (RTP, FedNow, SEPA Instant, etc.) operating continuously, with real-time balance visibility through APIs, with stablecoin and tokenized deposit infrastructure that doesn't sleep — corporate treasury can operate continuously. The question is whether to.

Use cases:

• Just-in-time liquidity — funds positioned to specific accounts as needs emerge.
• Continuous FX hedging — small position adjustments throughout the day.
• Dynamic supplier payment — accelerating or delaying based on real-time cash position.
• Automated cash sweeping — across geographies and currencies in real time.

59.3The operational implications

For the bank's TS&P side:

• 24/7 client service capability becomes table stakes for high-end relationships.
• Reconciliation processes must operate continuously, not in nightly batches.
• Status APIs and event streams must achieve real-time SLA.
• Operations teams must cover non-business hours for high-priority clients.

59.4The control challenge

Continuous operations create continuous exposure. Authorization workflows, segregation of duties, and fraud monitoring all need to function continuously without the natural batch breaks that historically created human check-points. Banks investing in real-time treasury invest equally in automated control infrastructure.

59.4The 24/7 close cycle problem

Traditional close cycles assume a business day. Transactions accumulate during the day, close at end-of-day, and reconcile overnight. RTP and FedNow break this model: transactions process at 2:47 AM on Saturday, and they're final and irrevocable when they do. For a bank's TS&P controller, this means the reconciliation can't wait for business hours. The system has to reconcile continuously, or the daily reconciliation has to be able to handle 24/7 transaction flows correctly — which requires the systems downstream (GL feed, reporting) to accept and correctly timestamp off-hours entries.

Quarter-end is particularly complex. A quarter that ends on a Friday now has transactions processing through the weekend that technically occur in the new quarter, even if they relate to pre-quarter-end business activity. The cut-off disciplines that work cleanly for Fedwire (which closes at 7 PM ET and gives you overnight before the next business day) don't apply cleanly to always-on rails.

59.7What the controller needs from treasury technology

Real-time treasury as a client capability requires real-time data infrastructure from the bank. The controller's interest is in making sure the bank's accounting systems can keep pace with what the bank is selling the client:

• Real-time balance feeds. If the bank provides real-time balance reporting through its portal or API, those balances should reconcile to the bank's ledger at any point in time. A stale balance that shows the client a higher available balance than the bank's actual ledger is both an operational risk and a representation issue.
• Intraday accounting events. High-frequency RTP and FedNow activity creates intraday GL events — not just end-of-day postings. For segment reporting, intraday GL posting helps eliminate the timing difference between when revenue economically accrues and when it hits the books. Banks still running batch end-of-day GL postings for instant payment fee revenue are systematically understating same-day revenue recognition accuracy.
• Continuous reconciliation infrastructure. The move from daily to continuous reconciliation is a technology investment, not just an operational one. The controller should be involved in business case development for that investment — the accounting and SOX control benefits are part of the justification, not an afterthought.

59.5The close cycle problem

Real-time treasury and traditional accounting close cycles are structurally misaligned. Close cycles are monthly events. Real-time treasury operates on seconds. The gap creates a specific accounting challenge: when a corporate's treasury moves cash continuously based on real-time decisions — sweeping balances between accounts at 2am, executing FX at 11:30pm, receiving RTP payments on weekends — the close cycle has to capture all of it accurately regardless of when it happened.

For the TS&P controller, the practical implication is that end-of-period snapshots may not reflect the month's activity accurately without intraperiod reconciliation. A corporate that was net-long USD on the last day of the month but managed intramonth FX positions aggressively has a very different story than the balance sheet snapshot suggests.

The accounting response is increased frequency of reconciliation and accrual cycles — moving from monthly to weekly to daily for high-activity relationships. Tools to support this: automated balance feeds, daily transaction-level P&L attribution, API-connected ERP that posts automatically rather than batching for month-end.

59.6Bank-side implications

For the bank's TS&P operations, 24/7 real-time treasury activity means:

• Continuous reconciliation requirement. The bank's master account, RTP joint account, and FedNow service account all need to be reconcilable at any point in time, not just at end of business day.
• Intraday liquidity monitoring at all hours. BCBS 248 intraday liquidity monitoring doesn't end when Fedwire closes. For banks with 24/7 payment obligations (RTP, FedNow, stablecoin settlement), the intraday liquidity model extends into overnight and weekend windows.
• Fee accrual for 24/7 activity. Per-transaction fee revenue on RTP and FedNow accrues continuously. Monthly fee schedules need to capture weekend and overnight transactions accurately.

CBDCs, tokenization, and the long horizon.

61.1The CBDC landscape

Central bank digital currencies fall into two categories:

• Wholesale CBDCs. Tokenized central bank money for use among banks and financial institutions. Most major central banks have active research and pilot programs (BIS Project Agorá, ECB digital euro wholesale work, Bank of England RTGS renewal).
• Retail CBDCs. Tokenized central bank money available to general public. Live in some jurisdictions (China e-CNY, several Caribbean nations); piloted broadly; politically contested in others (notably U.S., where Congressional action has restricted Federal Reserve retail CBDC development).

61.2The U.S. position

As of 2026, the U.S. has explicitly disavowed retail CBDC development. The 2025 GENIUS Act focused on stablecoin regulation rather than CBDC issuance. Wholesale CBDC research continues at the Federal Reserve through Project Hamilton and successor initiatives.

For TS&P, the practical implication: the U.S. wholesale settlement infrastructure modernization is happening through Fedwire ISO 20022 migration, FedNow expansion, and tokenized commercial bank money rather than through a U.S. CBDC.

61.3The tokenization trend

Beyond CBDCs, the broader tokenization wave includes:

• Tokenized deposits. Multiple G-SIBs operate live deposit token programs. Bank money on permissioned or hybrid blockchain chains.
• Stablecoins. USDC, USDT, plus emerging GENIUS Act-compliant institutional issuers. Non-bank-issued tokens redeemable for fiat.
• Tokenized money market funds. Franklin Templeton FOBXX, BlackRock BUIDL, others. Yield-bearing alternatives to stablecoins.
• Tokenized securities. On-chain bond issuance, real estate fractionalization, fund interests.
• Tokenized real-world assets (RWAs). Receivables, commodities, intellectual property.

61.4What's settled vs. unsettled

Settled by 2026:

• Bank-permissioned blockchain settlement is operational at scale.
• Stablecoins have a regulatory framework (GENIUS Act in U.S.; MiCA in EU).
• Cross-chain settlement remains technically complex but operationally workable.

Unsettled:

• Whether deposit tokens or stablecoins win which use cases.
• How CBDC interoperability with commercial bank tokens works at scale.
• What happens when tokenized assets, programmable payments, and AI orchestration combine.
• How regulatory frameworks evolve as adoption increases.

61.5The controller's positioning

For a TS&P controller in 2026:

• Treat tokenized infrastructure as a real but evolving channel.
• Apply standard accounting frameworks (ASC 305, ASC 326, ASC 815) until regulators or FASB indicate otherwise.
• Insist on documentation, governance, and audit standards equal to traditional infrastructure.
• Build understanding incrementally — each pilot, each new client use case, each rule change.
• Don't extrapolate too aggressively from announcements; track what's actually in production.

61.6The closing thought

The work of a TS&P controller in 2030 will look meaningfully different from 2026. The accounting frameworks won't change much. The systems, the rails, the products, and the operational rhythms will. The controller's responsibility — accurate financial reporting, sound controls, faithful representation of the bank's economics — won't change at all. That's why the foundations chapters of this handbook matter more than the forward-looking chapters: the foundations are durable; the surfaces change.

61.7The accounting frontier

Tokenized deposits and CBDCs create accounting questions that current GAAP doesn't fully address. Three live debates:

• Classification of tokenized deposits: Is a deposit token a deposit (ASC 942) or a financial instrument (ASC 825)? Most current structures treat them as deposits — the token is a digital representation of a claim on the issuing bank, economically equivalent to a deposit. The FASB has not issued definitive guidance; practitioners use the economic substance test.
• Stablecoin liabilities: If a bank issues a stablecoin backed 1:1 by reserves, is the stablecoin a deposit liability or something else? The GENIUS Act (2025) classifies federally regulated payment stablecoins similarly to deposits for regulatory purposes. Accounting treatment follows regulatorily-analogous treatment pending formal FASB guidance.
• Smart contract assets and liabilities: When a bank operates a smart contract that holds client funds pending conditional release, is the escrowed amount a deposit liability? Current consensus: yes, if the bank is the counterparty. But as arrangements become more complex, the analysis requires case-by-case review.