Reg W Applicability Guide: Covered Transactions & Services

If you're working in banking compliance, legal, or treasury, you've probably hit a wall trying to figure out if a deal with a sister company is allowed. That's Regulation W territory. It's not just another rule; it's a core firewall meant to prevent banks from recklessly funneling resources to their affiliates and endangering depositor funds. But its applicability isn't always black and white. I've spent over a decade untangling these rules, and the most common mistake I see is assuming a transaction is "internal" and therefore low-risk. That assumption can lead to six-figure penalties.

Let's cut through the legalese. Regulation W (12 CFR Part 223) implements Sections 23A and 23B of the Federal Reserve Act. Its primary goal is to limit the risks a bank faces from transactions with its "affiliates." An affiliate isn't just a subsidiary you own. It can be a company under common control, a sister company, or even a sponsored investment fund. The definition is broad, and that's where the first trap lies.

What Exactly is Regulation W?

Think of Reg W as a set of speed limits and guardrails for the financial highway between a bank and its corporate family. It doesn't ban travel; it regulates it heavily to prevent crashes that could wipe out the bank. The rule applies to all "member banks" (those that are part of the Federal Reserve System) and their affiliates. The applicability hinges on two main questions: Is the counterparty an "affiliate"? and Is the activity a "covered transaction" or service?

You can't just rely on a standard org chart. For example, a bank holding company's portfolio company that the bank doesn't technically own can still be an affiliate under the "acting in concert" or control tests. I've seen examiners flag relationships with fintech partners where the bank had significant operational influence, even with a minority stake.

Key Transactions Under Regulation W's Microscope

This is the heart of the matter. The term "covered transaction" is specifically defined. If your deal fits one of these categories, Reg W applies. Let's break them down with real-world scenarios.

1. Credit Extensions (The Big One)

Any loan, line of credit, or extension of credit. This is obvious. But it also includes less obvious forms:

• Overdrafts: An affiliate's account overdrawn beyond a de minimis threshold and time period.
• Repurchase Agreements (Repos): The bank buying securities from an affiliate with an agreement to sell them back. This is treated as a loan collateralized by those securities.
• Issuing a Guarantee or Letter of Credit: If your bank guarantees an affiliate's obligation to a third party, that's a credit extension to the affiliate. I audited a case where a bank standby letter of credit for an affiliate's real estate development loan triggered a major limit violation.

2. Purchasing Assets

Buying securities, loans, or other assets from an affiliate. This includes:

• Buying a bundle of mortgages originated by an affiliate mortgage company.
• Purchasing commercial paper or bonds issued by an affiliate.
• Acquiring real estate from an affiliate. The key here is that the purchase price is considered the amount of the covered transaction.

3. Investments in Affiliate Securities

This means your bank buying the stock, capital notes, or debentures of an affiliate. There's a strict prohibition against buying low-quality assets from an affiliate, which includes securities that are not investment grade.

4. Derivative Transactions

Entering into any derivative contract (swap, forward, option) that exposes the bank to credit risk from the affiliate. The credit exposure, calculated periodically, is the covered transaction amount. This area is a compliance minefield because the exposure can fluctuate wildly.

5. Intraday Credit and Federal Funds

Even a Federal Funds loan to an affiliate for one day is fully subject to the limits and collateral requirements. There's no materiality exception for short-term loans.

Service Arrangements and Reg W

Here's where many banks get tripped up. Reg W isn't just about money moving around. Section 23B applies to any transaction with an affiliate, including the provision of services. The core mandate: it must be on terms at least as favorable to the bank as those prevailing for comparable transactions with non-affiliates.

You need to document this. A handshake deal won't cut it during an exam.

• Shared Services: The bank paying an affiliate for IT support, marketing, or HR services. You need a contract and benchmarking to prove market rates.
• The Reverse: The bank providing services to an affiliate (e.g., custody, cash management). The fees charged must be at market rate. Underselling services is a common 23B violation.
• Cross-Marketing: An affiliate referring clients to the bank for a fee. The fee structure must be justifiable compared to third-party referral agreements.
• Use of Premises/Equipment: Renting office space or equipment to/from an affiliate. This is a classic area for non-compliance—leases are often set informally and not reviewed for market terms.

Common Pitfalls and How to Avoid Them

Based on my experience and regulatory enforcement actions, here are the top mistakes.

Pitfall 1: Misidentifying Affiliates. The biggest error is having an incomplete affiliate list. You must regularly review ownership, control, and investment fund sponsorship. A private equity fund sponsored by your holding company? Its portfolio companies are likely affiliates.

Pitfall 2: Ignoring the "Aggregate" Limit. Everyone tracks the 10% per-affiliate limit. The 20% of capital aggregate limit for all covered transactions is often an afterthought until it's breached by a combination of loans, securities purchases, and derivative exposures.

Pitfall 3: Inadequate Collateral Documentation. The rule requires specific, perfected security interests in collateral. A general pledge agreement or an unperfected interest is insufficient. I've seen banks accept affiliate stock as collateral, which is often legally problematic and sometimes prohibited.

Pitfall 4: Assuming Internal Transfers Are Exempt. Transfers of funds between a bank and its operating subsidiary (like a loan production office) are generally exempt. But transfers to a non-operating subsidiary (like a securities broker) are not. Knowing the difference is critical.

A Practical Reg W Compliance Checklist

Before you engage in any transaction with a related entity, run through this list.

• ✅ Affiliate Test: Is the counterparty definitively on our approved and updated affiliate list? If unsure, get legal confirmation.
• ✅ Transaction Classification: Does the activity fit the definition of a "covered transaction" (credit, purchase, investment, derivative)?
• ✅ Limit Check: For covered transactions: Does this stay within the 10% (per affiliate) and 20% (aggregate) limits of the bank's capital?
• ✅ Collateral Requirement: If it's a credit transaction, do we have a legally enforceable security interest in eligible collateral valued at 100-130% of the transaction amount?
• ✅ Market Terms (Section 23B): For ALL transactions (including services), do we have documentation (contracts, fee comparisons, bids from third parties) proving terms are as good as or better than arm's-length terms?
• ✅ Board Approval: Are transactions exceeding certain thresholds properly approved by the bank's board as required?

This isn't a one-time exercise. You need a monitoring system, often part of your larger compliance management system, to track limits and exposures in real-time.

Your Reg W Questions Answered