The entity category is the member bank itself, together with its affiliate group, acting through the bank's board and compliance function. Regulation W, the Federal Reserve's implementation of Sections 23A and 23B of the Federal Reserve Act, imposes the market-terms requirement on the member bank in every covered transaction with an affiliate. A "bank chain entity" is not a separate regulatory class, so the duty sits with the insured depository institution, not with the parent holding company, the nonbank affiliate, or the counterparty.

That answer cuts against a common assumption. Many compliance teams treat market-terms compliance as a holding-company project because the holding company owns the chain. The statute assigns the obligation differently. Sections 23A and 23B govern transactions between a member bank and its affiliates, and the bank must be able to demonstrate that each covered transaction is on terms at least as favorable to the bank as those available in arm's-length dealings with unaffiliated parties.

This matters because the phrase "bank chain entity" appears in internal policies, vendor questionnaires, and audit workpapers far more often than in regulation. The term is descriptive, not statutory. Identifying the accountable entity therefore requires translating internal language into the statutory framework before any control can be designed.

Mechanism: how Regulation W allocates the market-terms duty

Section 23A imposes quantitative limits on covered transactions between a member bank and its affiliates. Section 23B imposes the qualitative requirement: a covered transaction must be on terms and under circumstances, including credit standards, that are substantially the same, or at least as favorable to the member bank, as those prevailing at the time for comparable transactions with nonaffiliates. The Federal Reserve's Regulation W, at 12 CFR Part 223, operationalizes both sections.

The market-terms test is transaction-specific. For a loan from the bank to an affiliate, the bank must show that the interest rate, collateral, covenants, and maturity match what an unaffiliated borrower of similar credit quality would receive. For a purchase of assets from an affiliate, the bank must show the price and representations are no worse than the bank could obtain elsewhere. For a service contract, the bank must show the fee and service level are at least as favorable as third-party alternatives.

The mechanism has a timing dimension that thin explainers usually miss. Section 23B requires the comparison to reflect terms prevailing at the time of the transaction, not terms reconstructed after the fact. A bank that prices an affiliate loan in January and documents the benchmark in July has created an evidentiary problem even if the price was fair. The comparison must be contemporaneous, and the benchmark must involve actual nonaffiliate transactions or credible third-party quotes.

Accountability flows through the bank's governance, not the holding company's. The bank's board, or a committee delegated by the board, approves policies that define covered transactions and market-terms methodology. The bank's compliance function tests adherence. The bank's internal audit reports on control effectiveness. When the Federal Reserve examines the bank, it examines the bank's files, not the parent's.

The covered-transaction definition is broader than many assume. It includes extensions of credit, purchases of assets, deposits of affiliate funds in the bank, and certain guarantees. It also captures transactions with an affiliate's customers if the proceeds benefit the affiliate. The bank must map each relationship to the definition before it can determine whether the market-terms duty attaches. A plain-language version: the bank must treat its affiliates as if they were strangers, and it must be able to prove it.

Quantified context: thresholds, limits, and examination findings

The quantitative limits in Section 23A give the market-terms requirement its practical bite. A member bank's covered transactions with any single affiliate are capped at 10 percent of the bank's capital and surplus. Aggregate covered transactions with all affiliates are capped at 20 percent. These are statutory thresholds, and they do not vary by bank size or charter type.

The market-terms requirement operates independently of the caps. A transaction can be well within the 10 percent and 20 percent limits and still violate Section 23B if the terms are worse than nonaffiliate alternatives. Examiners test the two requirements separately. A bank that focuses only on the caps will miss the qualitative failures that generate the most findings.

The definition of capital and surplus for these purposes draws on the bank's regulatory capital, and the Federal Reserve's Regulation W provides the calculation method. For a community bank with USD 50 million in capital and surplus, the single-affiliate cap is USD 5 million and the aggregate cap is USD 10 million. For a regional bank with USD 2 billion in capital and surplus, the caps are USD 200 million and USD 400 million. The market-terms analysis applies at every size.

Enforcement history illustrates where banks fail. The Federal Reserve has issued cease-and-desist orders and civil money penalties against banks whose affiliate transactions lacked contemporaneous market-terms documentation. The recurring theme is not that the terms were demonstrably unfavorable, but that the bank could not demonstrate the comparison. Documentation gaps are treated as control failures.

The Section 23B requirement also extends to certain transactions that are not covered transactions under Section 23A. The market-terms duty reaches transactions with affiliates that fall outside the quantitative limits. A bank that treats Section 23B as an appendage of Section 23A will under-scope its compliance testing. The two sections have different reach.

Comparison: who bears the duty versus who is often blamed

Entity in the chain Regulatory status Bears Section 23B market-terms duty Typical misassignment
Member bank (insured depository) Subject to Sections 23A and 23B Yes, primary duty Assumed to be a holding-company responsibility
Bank holding company Separate legal entity No, unless it is itself a member bank Frequently named in policies as accountable
Nonbank affiliate (broker-dealer, finance company) Affiliate of the bank No, the bank must treat it at arm's length Often assumed to police its own terms
Bank subsidiary that is not a depository Affiliate No, duty runs to the member bank Confused with the bank itself
Foreign bank office Depends on charter and status Only if it is a member bank Assumed covered by the U.S. bank's policy
Third-party vendor serving both Nonaffiliate Not directly, but may be a benchmark Mistaken for an affiliate in scope reviews

The table captures the core allocation problem. The bank is the obligated entity, but the documentation and data needed to prove market terms often sit with affiliates. That creates a dependency the bank must manage contractually and operationally. A bank that waits for affiliates to volunteer benchmark data will fail the contemporaneous-documentation test.

Edge cases: where the duty shifts or becomes contested

The first edge case involves transactions between the bank and a nonbank affiliate that is itself regulated. A broker-dealer affiliate may argue that its own conduct rules govern the pricing. Section 23B does not defer to those rules. The bank must still demonstrate that the terms it received were at least as favorable as nonaffiliate alternatives.

The second edge case involves shared services. When the bank and an affiliate share a technology platform, the allocation of cost must reflect the benefit received. If the bank pays a disproportionate share, the transaction is effectively an extension of credit to the affiliate and fails the market-terms test. Cost-allocation methodologies must be documented and reviewed.

The third edge case involves guarantees and credit enhancements. A bank that guarantees an affiliate's obligation has engaged in a covered transaction, and the guarantee fee must be at market. A guarantee issued for no fee, or for a fee below what a third-party guarantor would charge, creates a Section 23B problem even if the underlying obligation performs.

The fourth edge case involves transactions with an affiliate's customer where the proceeds benefit the affiliate. The bank must look through the customer relationship to determine whether the affiliate is the real beneficiary. If it is, the transaction is covered and the market-terms duty applies.

The counterintuitive detail: a transaction that is demonstrably unfavorable to the bank can still pass Section 23B if it is equally unfavorable to nonaffiliates. The test is relative, not absolute. A bank that charges an affiliate the same punitive rate it charges all high-risk borrowers has met the requirement, though other safety-and-soundness concerns may arise. The benchmark is the nonaffiliate population, not an idealized fair price.

Misconceptions: what the market-terms rule does not require

The most common misconception is that the market-terms duty belongs to the holding company. It does not. The holding company may adopt enterprise-wide policies, and those policies may be sensible, but the statutory obligation rests with the member bank. A bank that outsources the analysis to the parent without retaining its own documentation has not discharged the duty.

The second misconception is that a fair price is sufficient. Section 23B requires favorable terms and circumstances, including credit standards. A loan priced at market but underwritten with weaker collateral requirements than nonaffiliate loans fails the test. The comparison covers the full package of terms, not just the rate.

The third misconception is that the requirement applies only to loans. It applies to purchases of assets, deposits, service contracts, guarantees, and more. A bank that scopes its Section 23B review to the credit portfolio will miss the service and asset transactions that generate findings.

The fourth misconception is that a one-time benchmark suffices. Market terms change, and the comparison must be contemporaneous. A benchmark established at the inception of a multi-year contract may not support a transaction executed two years later. The bank must refresh its benchmarks on a defined cycle.

Red-flag warnings worth treating as triggers for immediate review:

An affiliate transaction with no contemporaneous third-party quote or nonaffiliate comparable. A pricing methodology that has not been refreshed since the contract was signed. Cost allocations to the bank that exceed the bank's measured benefit. Guarantees or credit enhancements issued to affiliates without a market-based fee. Affiliate transactions approved outside the bank's covered-transaction policy. Documentation that identifies the holding company, not the bank, as the responsible party.

Timeline: how a Section 23B compliance failure typically unfolds

Stage Typical timing What happens Control weakness exposed
Transaction execution Month 0 Bank enters agreement with affiliate No pre-trade benchmark obtained
Documentation Month 0-1 File assembled by affiliate, not bank Bank lacks its own record
First review Month 3-6 Compliance samples the transaction No nonaffiliate comparable in file
Remediation request Month 6-9 Bank asks affiliate for benchmark data Affiliate cannot reconstruct prior terms
Examination Month 9-18 Regulator reviews covered transactions Contemporaneous comparison absent
Finding or order Month 12-24 Examiner cites Section 23B weakness Governance and documentation failure

The timeline shows why the contemporaneous requirement is the pivotal control. By the time a benchmark is needed for examination, the market conditions at execution may be unrecoverable. The bank that builds the comparison into the transaction workflow avoids the reconstruction problem entirely.

Practical actions: building a defensible market-terms program

The bank should start by mapping every relationship with an affiliate to the covered-transaction definition. The map should identify the transaction type, the affiliate, the dollar amount, and the benchmark source. Transactions without an identified benchmark should be flagged before execution, not after.

The bank should adopt a written market-terms methodology that specifies the benchmark sources it will use. Acceptable sources include actual nonaffiliate transactions of similar size and risk, third-party quotes, and published market indices where appropriate. The methodology should define how the bank documents the comparison and how often benchmarks are refreshed.

The bank should require pre-execution sign-off for covered transactions above a defined threshold. A common approach sets the threshold at a dollar amount tied to the bank's capital, with lower-level approval for smaller transactions. The sign-off should confirm that the benchmark was obtained and that the terms are at least as favorable as the comparison.

The bank should retain its own documentation. Affiliate-provided files are useful but insufficient. The bank's file should contain the benchmark, the comparison analysis, the approver's rationale, and the date of execution. The file should be retrievable without relying on the affiliate's systems.

The bank should test its program at least annually and report results to the board. Testing should sample across transaction types, not just loans. Findings should be tracked to remediation, and repeat findings should escalate.

The bank should reconcile its internal "bank chain entity" language to the statutory framework. Policies that name the holding company as accountable should be revised to name the member bank. Vendor and affiliate questionnaires should ask the bank's counterparties for the data the bank needs, not for assurances that the affiliate has its own controls.

Limitations: what this framework cannot resolve

The framework cannot resolve whether a particular transaction is on market terms without the underlying data. The statute sets the standard, and the regulation defines the method, but the conclusion depends on the benchmark the bank obtains. Two banks with similar transactions may reach different conclusions if their nonaffiliate comparables differ.

The framework also cannot substitute for legal analysis of charter-specific questions. Whether a particular foreign office or subsidiary is a member bank, and whether a particular transaction is covered, depends on facts and charter status. The general allocation described here should be confirmed against the specific institution's legal structure.

The framework cannot eliminate the dependency on affiliates for data. The bank can contract for data access and can build its own benchmarks, but some transactions will require information the affiliate controls. The bank's protection is contractual and operational, not statutory.

This article is general educational information about the regulatory allocation of the market-terms duty. It is not a legal opinion, a compliance determination, or a substitute for advice from qualified counsel or a regulatory professional familiar with the institution's specific facts. Readers should consult a qualified local professional before relying on this discussion for any transaction or examination matter.