The OCC’s 2016 contract stay proposal tied old trades to new ones with the same counterparty group

On August 19, 2016, the OCC proposed that large banks write resolution stays into financial contracts. Older contracts had to conform once the bank or a covered affiliate traded again with that counterparty or its affiliates, which, in our reading, made counterparty data the work.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

On August 19, 2016, the OCC proposed that large banks write resolution stays into financial contracts. Older contracts had to conform once the bank or a covered affiliate traded again with that counterparty or its affiliates, which, in our reading, made counterparty data the work.

  1. The week The proposal explained what qualified financial contracts are.
  2. The trigger: a new trade pulled old contracts into scope New covered QFCs entered into after the effective date had to comply. [1] For older contracts, the OCC chose an event, not a date.
  3. The unit: what counted as one contract The proposal adopted the Dodd-Frank Act’s treatment of master agreements.
  4. The entities: which booking entities were covered The OCC explained why subsidiaries were included.
  5. The route: protocol, amendment or approved alternative A protocol amends contracts in bulk among adhering parties.
  6. How the proposal reached different firms The proposal’s core target was the national bank inside a U.S. GSIB, where the OCC said covered QFCs were generally booked. [1] For such a bank, in our reading, the contract population was large and the trigger could fire daily with active counterparties.
  7. Objections, in order It did, in part.
  8. Checks a bank’s data, legal and operations leaders could run Check that each counterparty legal entity links to its immediate and ultimate parent, using a consolidation basis that matches the rule’s definition. [2] Check how changes in ownership are captured.
  9. With hindsight The proposal became a rule.

The week

On August 19, 2016, the Federal Register published a proposed rule from the Office of the Comptroller of the Currency titled Mandatory Contractual Stay Requirements for Qualified Financial Contracts. [1] Comments were due October 18, 2016. [1]

The OCC said the proposal would add a new part to its rules to address the exercise of default rights in certain financial contracts that could interfere with the orderly resolution of systemically important financial firms. [1]

Under the proposal, a covered bank would have to ensure that each covered qualified financial contract met two conditions. [1] It would contain a contractual stay-and-transfer provision analogous to the statutory one in Title II of the Dodd-Frank Act and in the Federal Deposit Insurance Act. [1] And it would limit the exercise of default rights based on the insolvency of an affiliate of the covered bank. [1]

The OCC said its requirements were substantively identical to those in a proposal the Federal Reserve Board had issued on May 3, 2016. [1] The OCC described its rule as a parallel proposal for OCC-regulated institutions that were part of a covered entity under the Board’s proposal, intended to work in tandem with it. [1]

The proposal explained what qualified financial contracts are. It said they include swaps, other derivative contracts, repurchase and reverse repurchase agreements, and securities lending and borrowing agreements. [1] It adopted the definition in section 210(c)(8)(D) of Title II of the Dodd-Frank Act. [1]

The OCC said these contracts play a role in financial intermediation when markets are functioning normally. [1] It also called them a major source of financial interconnectedness that may threaten financial stability in times of stress. [1]

The concern was default rights. By contract, the OCC said, a party to a QFC generally has rights if its counterparty defaults, including rights to suspend performance, terminate or accelerate the contract, set off amounts owed, and seize and liquidate collateral. [1]

The proposal focused on two scenarios. In a direct default, the legal entity that is party to the contract enters a resolution proceeding. [1] In a cross-default, an affiliate of the direct party, such as its parent holding company, enters resolution. [1] The OCC gave the example of a parent that guarantees its subsidiaries’ derivatives, where the contracts contain cross-default rights tied to the parent. [1]

The proposal defined covered banks. They were national banks and federal savings associations that are subsidiaries of global systemically important bank holding companies, and national banks, federal savings associations, and federal branches and agencies tied to global systemically important foreign banking organizations. [1]

The OCC said the list of firms meeting the Board’s proposed methodology was then the same as the Basel Committee’s list of global systemically important banks. [1] A footnote named eight U.S. top-tier bank holding companies then identified on that list. [1]

The proposal reached subsidiaries too. It said covered banks would include any subsidiary of a covered national bank, federal savings association, or federal branch or agency. [1] The OCC explained that unless all entities in a GSIB were covered, counterparties might have incentives to migrate contracts to uncovered entities. [1]

The proposal excluded QFCs cleared through a central counterparty. [1] It said the OCC continued to consider the treatment of cleared contracts, given differences in contractual arrangements, credit risk, default management and supervision. [1]

On timing, the proposed rule would take effect on the first day of the first calendar quarter beginning at least one year after the final rule was issued. [1] Covered QFCs entered into on or after that date would have to comply. [1]

Older contracts had a different trigger. A covered bank would have to bring a preexisting QFC into compliance no later than the first date on which it, or an affiliate that was itself covered, entered a new covered QFC with the same counterparty or that counterparty’s affiliate. [1]

The OCC said that if a covered bank entered no new QFCs with a counterparty or its affiliates, it would not have to conform the old contracts. [1] It described the trigger as an incentive for banks to fix contracts with their most significant counterparties first. [1]

The proposal also offered an approval route. A covered bank could ask the OCC to approve contract forms with additional creditor protections as compliant. [1] The request would need an analysis against factors in the rule and a written legal opinion that the provisions would be valid and enforceable. [1]

The OCC’s paperwork estimate for that approval process assumed 42 respondents at 40 hours each, a total of 1,680 hours. [1] The proposal also referred to the ISDA 2014 Resolution Stay Protocol and the ISDA 2015 Universal Resolution Stay Protocol, industry documents with related provisions. [1]

The OCC’s August 2016 proposal reads as a rule about contract language. A covered bank’s financial contracts would need two kinds of clauses: one recognizing the U.S. resolution stays, and one giving up default rights triggered by an affiliate’s failure. [1]

Our argument is that the harder demand sat in the transition provision. Older contracts did not have to be fixed on a fixed date. They had to be fixed when the bank, or a covered affiliate, next traded with the same counterparty or any of that counterparty’s affiliates. [1] A bank could only apply that trigger if it could see, across its whole group, every entity belonging to each counterparty’s group. In our reading, that made counterparty hierarchy data the real compliance work.

We take the proposal in four parts:

  1. The trigger: how a new trade pulled old contracts into scope, and what a bank needed to know to apply it.
  2. The unit: what counted as one contract, and why master agreements made the document hunt central.
  3. The entities: which booking entities were covered, and why subsidiaries were included.
  4. The route: how contracts could be brought into compliance, by industry protocol, bilateral amendment or approved alternatives.

The parts do not overlap. The first is about timing, the second about the contract record, the third about the bank’s own structure and the fourth about the means of change. Together they cover what a covered bank had to do with its existing and new contracts. After them we look at how the proposal reached different firms, take the objections in order, and end with checks a bank’s data, legal and operations leaders could run.

The trigger: a new trade pulled old contracts into scope

What the proposal said

New covered QFCs entered into after the effective date had to comply. [1] For older contracts, the OCC chose an event, not a date. A covered bank would have to conform a preexisting covered QFC no later than the first date on which it, or a covered affiliate, entered a new covered QFC with the same counterparty or that counterparty’s affiliate. [1]

The OCC explained the choice. It said the approach balanced continuity in a failure against letting banks and existing counterparties avoid the cost of conforming old contracts if they stopped trading. [1] It said the trigger would give banks an incentive to fix contracts with their most significant counterparties. [1]

Two group structures, not one

The trigger had affiliates on both sides. On the bank’s side, a trade by any affiliate that was itself a covered entity or covered bank counted. [1] On the counterparty’s side, a trade with any affiliate of the counterparty counted. [1]

So a bank needed to answer a two-sided question before each new trade. Does any entity in our group already have an unconformed contract with any entity in this counterparty’s group? The OCC said it expected the decision of how to comply with respect to a given counterparty to be made in close coordination between the covered bank and its affiliated covered entities. [1]

Why the answer depends on data

A trading desk sees the entity it is facing. It may not see that the entity is a subsidiary of a fund manager whose other funds trade with a different part of the bank. The trigger made that relationship matter.

Answering the question needs three linked records. The first is a counterparty hierarchy that maps legal entities to their parents. The second is a contract inventory showing which entities in the bank’s group are party to which agreements. The third is a status flag showing whether each agreement has been conformed. In our reading, a bank missing any of the three could not apply the trigger reliably.

What “affiliate” meant

The proposal tied the counterparty’s affiliates to the Bank Holding Company Act, as the final rule later described it. [2] The final rule changed that. It defined consolidated affiliate by reference to financial consolidation principles, as reflected by U.S. GAAP or IFRS, instead of the Bank Holding Company Act. [2]

The OCC gave the reason. It said commenters pointed out that counterparties already track and monitor financially consolidated affiliates under U.S. GAAP or IFRS. [2] It also said exposures to a non-consolidated affiliate may be captured as a separate counterparty. [2]

That change is a data decision. The agencies moved the definition toward a hierarchy firms already maintained. In our reading, it confirms that the trigger’s workability depended on the data available to apply it.

The effective date and the quarter rule

The proposal tied its effective date to the calendar. The rule would take effect on the first day of the first calendar quarter beginning at least one year after the final rule was issued. [1] The OCC cited section 302(b) of the Riegle Community Development and Regulatory Improvement Act of 1994. [1]

The OCC described that law as generally requiring new regulations imposing requirements on insured depository institutions to take effect on the first day of a calendar quarter. [1] So the one-year runway ended on a quarter date, and the trigger for older contracts began from it.

Banks that become covered later

The proposal planned for change in the covered population. A bank that became a covered bank after the final rule was issued would have to comply by the first day of the first calendar quarter beginning at least one year after it became covered. [1]

For data, that means a bank’s own status is a field that can change. A national bank inside a group newly identified as a GSIB would inherit the whole program on a delay. The counterparty hierarchy and contract inventory would need to exist before that clock started, or the year would go to building them.

A trigger that changes with trading

A date-based deadline is the same for everyone. An event-based trigger moves with each counterparty relationship. A counterparty that trades daily would hit the trigger at once. One that traded infrequently could leave old contracts unconformed for longer.

That creates an operational control requirement. Before a new trade books, something must check the counterparty group’s conformance status. If the check fails, the trade either waits or the old contracts must be fixed first. In our reading, that check belongs in the onboarding or pre-trade workflow, not in a periodic legal review.

The OCC’s preference for significant counterparties

The OCC said the trigger would encourage banks to fix contracts with their most significant counterparties. [1] Those are the counterparties with active trading. A firm with large but dormant positions would not trip the trigger.

The proposal accepted that trade-off openly. It said a covered bank would not have to conform a preexisting QFC if it entered no new QFCs with that counterparty or its affiliates. [1] The policy aim was continuity for the contracts that matter in a failure, and active relationships were the proxy.

The unit: what counted as one contract

Master agreements

The proposal adopted the Dodd-Frank Act’s treatment of master agreements. It said master agreements for QFCs, together with all supplements and underlying transactions, would be treated as a single QFC. [1] The OCC described a master agreement as a contract with general terms the parties apply to multiple transactions between them. [1]

That rule shaped the work. A bank would conform a master agreement once, and the change would carry to the trades under it. But it had to find the right master agreement first, and know which trades sat under it.

The document hunt

A large bank’s contract population can include master agreements of different vintages, governed by different laws and signed by different entities. Some may sit in systems with structured data. Others may exist only as scanned files with limited metadata.

Conforming a master agreement means knowing its parties, its governing law, its existing default and cross-default provisions and any credit support documents tied to it. The proposal’s cross-default restrictions reached credit enhancements, such as an affiliate’s guarantee of the bank’s obligations. [1] So the hunt covered guarantees as well as the master agreements themselves.

Credit enhancements as contracts

The proposal noted that credit enhancements on QFCs are themselves QFCs under the Dodd-Frank definition. [1] It defined terms such as direct QFC, direct party, affiliate credit enhancement, covered affiliate credit enhancement and supported party to describe the relationships. [1]

For data, that means the record of a contract is incomplete without its support structure. A swap between a bank subsidiary and a client, guaranteed by the parent, is two linked QFCs. The cross-default restrictions addressed the link. [1]

Contracts where the bank acts as agent

The proposal said a party to a QFC included a party acting as agent under it. [1] That would have pulled in agreements where the bank acted for clients, such as securities lending arrangements run on their behalf.

The final rule changed course. It said a covered bank does not become a party to a QFC solely by acting as agent. [2] The OCC gave the example of a master securities lending arrangement where the bank’s only obligations are as agent for one or more principals. [2]

For the inventory, that distinction needs a field. A contract record that does not say whether the bank is principal or agent cannot tell which agreements are in scope. The change narrowed the population, but only for a bank whose records could show the role.

What the record for each agreement should hold

Putting the pieces together, a usable record for each agreement would carry several items. They include the parties and their parent entities, the booking entities on the bank’s side, the governing law, whether the bank is principal or agent, whether positions are cleared, the linked credit support and guarantees, and the conformance status and route.

These fields are ordinary. Each one answers a question the rule made relevant. The difficulty is having all of them in one place, for every agreement, kept current as trades and counterparties change. In our reading, that consolidation was the core of the program.

The receiver’s view of the same contracts

Another rule, from Treasury, asked for overlapping data for a different reason. On October 31, 2016, Treasury published final rules on QFC recordkeeping under the Orderly Liquidation Authority, effective December 30, 2016. [6]

Treasury said those rules require records on positions, counterparties, legal documentation and collateral. [6] It said the information would help the FDIC as receiver decide whether to transfer QFCs and assess the consequences of transfer, repudiation or termination. [6]

The two rules looked at the same contracts from different sides. The stay rules changed the contract terms. The recordkeeping rule asked for data the receiver would need if a firm failed. In our reading, a bank that built one contract and counterparty data set could serve both.

Governing law and why it mattered

The stay-and-transfer requirement addressed a specific risk. The OCC said a court in a foreign jurisdiction might decline to enforce the U.S. statutory stay in some cases, such as a contract with a non-U.S. entity, governed by non-U.S. law and secured by collateral outside the United States. [1]

By requiring the stay’s effect in the contract itself, the rule aimed to make it enforceable as a matter of contract law. [1] For the data inventory, governing law and counterparty jurisdiction became fields that mattered. A contract under U.S. law with a U.S. counterparty carried less of this risk than one under foreign law.

Cleared contracts excluded

The proposal excluded QFCs cleared through a central counterparty. [1] So the inventory needed a way to separate cleared from uncleared positions and the agreements governing each. Clearing changes the counterparty to the clearinghouse, so the trade records should already carry that distinction. The proposal relied on it being accurate.

Default rights that were not covered

The proposal did not touch every default right. It said the restrictions would leave many creditor protections commonly included in QFCs unaffected. [1] It excluded from the cross-default definition rights to terminate without cause, such as termination on demand or at set intervals. [1]

That meant legal review had to read each relevant provision, rather than flag every termination clause. A data model that tagged default rights by type would let lawyers focus on the provisions in scope.

The entities: which booking entities were covered

Covered banks and their subsidiaries

The proposal applied to national banks, federal savings associations and federal branches and agencies that were part of a GSIB, and to their subsidiaries. [1] The OCC said that in the United States, covered QFCs were generally entered into at the subsidiary level rather than through intermediate holding companies. [1]

The OCC explained why subsidiaries were included. Unless all entities in a GSIB were covered, it said, counterparties might have incentives to migrate contracts to uncovered entities. [1] It asked whether a subsidiary with only a de minimis level of covered QFCs could be excluded. [1]

Subsidiaries with another supervisor

The OCC asked about overlap. It noted that some subsidiaries of covered banks could be supervised by another U.S. agency, such as a broker-dealer subsidiary of a national bank. [1] It asked whether conflicting jurisdiction needed to be addressed, for example by carving out subsidiaries subject to comparable requirements elsewhere. [1]

For a bank’s data team, the question shows that entity type matters as well as ownership. A broker-dealer subsidiary books contracts under its own regulatory regime. Its contracts still counted for the group’s trigger under the proposal. [1]

Questions about scope in both directions

The OCC asked whether the rule should be wider. Its second question raised whether banks outside the GSIB groups but with material QFC activity should be covered, and how material levels could be defined and measured. [1]

It also asked whether the rule was too broad. Its third question asked whether subsidiaries with only de minimis covered QFCs could be excluded, and whether scope could be narrowed while meeting the rule’s goals. [1] Both questions turn on measurement. A bank that could not count its QFCs by entity could not answer either one.

Entities excluded by the current text

As checked on November 16, 2026, the current text of 12 CFR 47.3 lists subsidiaries that are not covered banks. [5] They include subsidiaries held in satisfaction of debt previously contracted, certain portfolio concerns of small business investment companies, and subsidiaries held to promote the public welfare. [5]

Each exclusion depends on why the bank holds the entity. That is another field the entity register needs, beyond ownership percentage.

Intermediate holding companies

The OCC explained why the proposal did not focus on intermediate holding companies. It said covered QFCs were generally entered into at the subsidiary level, through the national bank, federal savings association or federal branch or agency. [1]

It pointed to the Board’s 2015 total loss-absorbing capacity proposal. [1] Under its clean holding company component, the OCC said, the U.S. intermediate holding companies of foreign GSIBs would be prohibited from entering QFCs with third parties. [1]

That cross-reference shows how one rule shaped another’s data. If holding companies were not to face third parties, the contract population would sit in operating subsidiaries. A bank’s entity register needed to show which entities could face third parties and which could not, and the contract inventory needed to agree with it.

Three agencies, one group

The OCC proposal covered OCC-regulated entities. The Board’s proposal covered other parts of the same groups. [1] The FDIC later adopted a parallel rule for state non-member banks and state savings associations. [4] The final rules were substantively identical. [2]

For a GSIB, that meant one contract population governed by three agencies’ rules, depending on the booking entity. The trigger counted trades by any covered affiliate under any of the three. [2] A compliance program that tracked only one legal entity’s contracts could not apply the rule.

Booking entity as a data field

The booking entity on a trade decides which rule applies and which affiliates count for the trigger. A bank with several entities able to face clients needs that field to be accurate and consistent across systems.

Migration risk runs the other way too. The OCC worried counterparties might move trades to uncovered entities. [1] A bank’s data would need to show whether new trades were moving between entities in ways that avoided the rule.

Foreign banks’ U.S. operations

The proposal covered federal branches and agencies of foreign GSIBs and their subsidiaries. [1] Their contracts can sit under master agreements that span several branches in different countries.

The proposal addressed that case, and the final rule narrowed it. Under the proposal, such a multi-branch master agreement was covered only for transactions booked at, or payable or deliverable at, a U.S. federal branch or agency. [2] The final rule covered it only for the transactions booked at those branches. [2] That required booking data at the transaction level as well as the agreement level. A branch that recorded only which agreement a trade sat under, without where it was booked, could not separate the covered trades from the rest.

The route: protocol, amendment or approved alternative

Industry protocols

The proposal referred to the ISDA 2014 Resolution Stay Protocol and the ISDA 2015 Universal Resolution Stay Protocol. [1] It noted that an exception in the proposal was substantially similar to one in those protocols, added to address concerns from asset managers. [1]

The proposal itself allowed a covered bank to comply by amending covered QFCs through adherence to the ISDA 2015 Universal Resolution Stay Protocol. [1] The final rule kept that route and added a U.S. Protocol, and said its phased compliance dates would give time for the U.S. Protocol to be developed. [2]

A protocol amends contracts in bulk among adhering parties. For data, the question becomes which counterparties have adhered, as of what date, and which of their agreements the adherence reaches.

Bilateral amendment

Where a counterparty did not adhere to a protocol, the bank would need to amend the agreement directly. Each bilateral amendment is a negotiation, a signature and a record. Multiplied across a client base, that is a program with its own tracking system.

Approved enhanced creditor protections

The proposal let a covered bank ask the OCC to approve contract forms with creditor protections that would otherwise be impermissible. [1] The request would explain how the terms were consistent with the rule’s purposes, analyzed against factors in the rule, with a written legal opinion on enforceability. [1]

The OCC said it expected to consult with the FDIC and the Board on such requests. [1] It said creditor protections that could apply industry-wide may help ensure impediments to resolution are addressed uniformly. [1]

Tracking the route

Each conformed contract arrives there by one of these routes. A complete record would show which route applied, when and with what evidence. In our reading, that record is what an examiner would ask to see.

Compliance dates sorted by counterparty type

The proposal had one compliance date for new contracts. [1] The final rule replaced it with three, sorted by who was on the other side. [2] As the current text reads, contracts where each party is a covered entity, covered bank or covered FSI had to conform by January 1, 2019. [5]

Contracts where each other party is a financial counterparty that is not covered had until July 1, 2019. [5] Contracts with any other party, or with a small financial institution, had until January 1, 2020. [5] The OCC said the phase-in responded to commenters who wanted time for outreach to counterparties unfamiliar with the protocol. [2]

That schedule added a field to the counterparty record: its class under the rule. A bank had to know whether each counterparty was a covered entity, a financial counterparty, a small financial institution or something else. The final rule defined small financial institutions by type and by assets of $10 billion or less. [2] A counterparty’s asset size is data the bank must hold and refresh.

The approval route required a written legal opinion that the proposed provisions would be valid and enforceable under the law of the relevant jurisdictions. [1] Where the request covered amendments, the opinion had to address the validity of the amendment process too. [1]

An opinion is a document tied to specific contract forms and jurisdictions. It is evidence in its own right, and it ages. A bank that cannot find the opinion behind a contract form cannot show why that form was approved. Keeping it linked to the contracts it supports lets a bank show, later, which agreements rest on which opinion. If the law in a jurisdiction changes, that link shows which contracts to revisit.

What an examiner could ask for

An examiner reviewing compliance would want to see the population of covered QFCs, the status of each, the route by which each was conformed and the evidence. The trigger adds one more item: proof that no new trade was booked with a counterparty group while an old contract stayed unconformed. [1]

That last item is the hardest to show after the fact. It needs trade data joined to the counterparty hierarchy and the contract status as of each trade date. In our reading, a bank that kept only a current status flag, without history, would struggle to prove the control worked on a past date.

How the proposal reached different firms

A U.S. GSIB’s national bank

The proposal’s core target was the national bank inside a U.S. GSIB, where the OCC said covered QFCs were generally booked. [1] For such a bank, in our reading, the contract population was large and the trigger could fire daily with active counterparties.

A foreign bank’s federal branch

A federal branch of a foreign GSIB faced the multi-branch issue. Its agreements might be shared with branches elsewhere, and only some trades booked in the United States. [2] Transaction-level booking data was essential.

An asset manager facing a covered bank

Asset managers were counterparties, not covered banks. But they would receive the amendment requests. A manager with several funds, each a separate legal entity, would see each fund’s agreements touched when any fund traded with any covered entity in the bank’s group.

The final rule gave financial counterparties other than covered entities until July 1, 2019 to conform, later than the first compliance date. [5] Commenters had sought more time for outreach to counterparties unfamiliar with the protocol. [2]

A community bank facing a covered bank

Community banks that traded swaps or repos with a GSIB’s bank were counterparties too. The final rule gave contracts with small financial institutions, defined as banks, savings associations, farm credit institutions or credit unions with assets of $10 billion or less, until January 1, 2020. [2] [5]

For a community bank, the request arrives from the larger bank. The work is a review of one or a few agreements, with counsel, before signing.

A broker-dealer inside a covered group

A broker-dealer subsidiary of a covered national bank was itself covered under the OCC’s proposal, as a subsidiary. [1] A broker-dealer elsewhere in the group fell under the Board’s rule. [3] Either way, its repo and securities lending agreements were part of the population.

For a broker-dealer, the agent distinction matters. Securities lending run on behalf of clients may involve the firm as agent, which the final rule excluded from being a party on that basis alone. [2]

A state-chartered bank in a GSIB group

The FDIC adopted its own rule for state non-member banks and state savings associations in these groups. [4] It required those institutions and their subsidiaries to ensure covered QFCs limit default rights and transfer restrictions to the same extent as under the Dodd-Frank Act and the Federal Deposit Insurance Act. [4]

For a group with both national and state-chartered banks, the same counterparty might face entities under the OCC and the FDIC. The trigger counted trades across them. [2] The group’s data needed to treat them as one population.

A corporate end user

Non-financial counterparties, such as a company hedging interest rates, had the same later date as small institutions. [5] Their concern is narrower: what rights they give up if their bank’s parent fails.

Objections, in order

1. The trigger let banks avoid fixing old contracts

It did, in part. The OCC said a covered bank would not have to conform old contracts if it stopped trading with that counterparty group. [1]

But dormant contracts are the ones least likely to drive a disorderly unwind of new positions. The OCC chose to spend the industry’s effort on active relationships. [1] In our reading, that was a defensible priority, at the cost of leaving some legacy contracts unconformed.

The required clauses are legal text. Lawyers draft and negotiate them.

But applying the trigger requires knowing which contracts exist, who is party to them and whether they are conformed. [1] The final rule changed the affiliate definition because of what data counterparties already kept. [2] The legal work could not start until the data said where to look.

3. The protocol made the work trivial

Adherence to the Universal Protocol could amend contracts in bulk, and the final rule recognized it. [2] The OCC said many covered firms had already adhered. [2]

Adherence still needed tracking. A bank had to know which counterparties had adhered and which agreements it reached. Counterparties that did not adhere still needed bilateral amendments. The protocol reduced the work; it did not remove the record.

4. The burden estimate was small

The OCC estimated 1,680 hours for the approval request collection. [1] That estimate covered requests for approval of enhanced creditor protections, not the remediation program. [1] It did not measure the cost of building counterparty hierarchies or contract inventories, and the proposal did not claim it did.

5. Only the largest banks were affected

The covered banks were few; in our view, their counterparties were far more numerous. Asset managers, community banks and corporates would receive amendment requests because the rule worked through contracts, and the final rule set later compliance dates for them. [5] The data work fell mainly on covered banks, but counterparties needed their own records to respond.

6. Resolution planning already required this information

Large banks already prepared resolution plans. Those plans discussed financial contracts and their treatment in a failure. In our reading, though, a resolution plan describes a strategy. The stay rule required each covered contract to carry specific terms, and the trigger required a conformance check for each new trade with a counterparty group. [1]

Treasury’s recordkeeping rules, published later in 2016, asked for position-level and counterparty data for a receiver’s use. [6] The two demands overlapped in data but differed in purpose. Neither one replaced the other.

Counterparty hierarchy

Check that each counterparty legal entity links to its immediate and ultimate parent, using a consolidation basis that matches the rule’s definition. [2] Check how changes in ownership are captured.

Contract inventory

Check that each master agreement, credit support document and guarantee is in an inventory with parties, governing law, booking entities and conformance status. The rules treated a master agreement and its transactions as one contract. [1]

Pre-trade control

Check whether booking a new QFC with a counterparty group triggers a conformance check across the group’s agreements. The trigger in the 2016 proposal and the final rule depends on it. [1] [5]

Status history

Check that conformance status is stored with dates, so the firm can show the status of any agreement on any past trade date. A current flag alone cannot prove that the trigger was applied when a trade booked. [1]

Counterparty class

Check that each counterparty carries its class under the final rule’s phased dates: covered entity, financial counterparty, small financial institution or other. [5] Check how the asset size used for the small institution test is sourced and refreshed. [2]

Protocol adherence records

Check that protocol adherence is recorded by counterparty entity and date, and linked to the agreements it amends. [2]

Alignment with recordkeeping

Check whether the contract data used for stay compliance matches the data kept for Treasury’s QFC recordkeeping rule, which requires records on positions, counterparties, legal documentation and collateral. [6] One data set serving both reduces reconciliation work.

These checks are good practice that follows from the rules’ structure, not requirements stated in this form. Each firm’s obligations depend on its status under the rules and should be confirmed with counsel.

With hindsight

The proposal became a rule. On September 12, 2017, the Federal Reserve Board published its final rule restricting the QFCs of systemically important U.S. banking organizations and the U.S. operations of foreign ones. [3] It required covered entities to ensure their QFCs limit default rights and transfer restrictions to the same extent as under the Dodd-Frank Act and the Federal Deposit Insurance Act. [3]

The FDIC followed on October 30, 2017, for state non-member banks and state savings associations in the same groups. [4] The OCC published its final rule on November 29, 2017, effective January 1, 2018. [2] The OCC said its requirements were substantively identical to the Board’s and the FDIC’s. [2]

One small detail in the OCC’s final rule shows why dates should be copied, not assumed. Its introduction says the OCC issued its proposal on August 19, 2017. [2] The Federal Register shows the proposal published on August 19, 2016. [1]

The final rule kept the trigger for older contracts. As the current text reads, a QFC entered before January 1, 2019 is a covered QFC if the covered bank, or an affiliate that is a covered entity, covered bank or covered FSI, enters a QFC with the same person or a consolidated affiliate of that person on or after that date. [5]

The affiliate definition changed in the way the data argument predicts. The final rule defined consolidated affiliate by financial consolidation principles under U.S. GAAP or IFRS, which the OCC said counterparties already track. [2]

The compliance dates were phased by counterparty type. The current text sets January 1, 2019 for contracts among covered entities, covered banks and covered FSIs. [5] It sets July 1, 2019 for other financial counterparties and January 1, 2020 for small financial institutions and all others. [5]

The OCC recognized industry protocols. As the proposal had, the final rule allowed a covered bank to bring covered QFCs into compliance by adhering to the ISDA 2015 Universal Resolution Stay Protocol, and referred to a U.S. Protocol then being developed. [2] The OCC said many covered firms had already adhered to the Universal Protocol. [2]

The agent question was resolved in favor of commenters. The final rule said a covered bank does not become a party to a QFC solely by acting as agent. [2] The OCC’s paperwork estimate for approval requests rose to 44 respondents at 40 hours each, 1,760 hours in total. [2]

The rule is still in force. As checked on November 16, 2026, the eCFR text of 12 CFR 47.3 defines covered banks to include national banks and federal savings associations that are subsidiaries of GSIBs, and federal branches and agencies of foreign GSIBs. [5] The current text also includes a national bank or federal savings association with more than $700 billion in total assets on its most recent Call Report. [5]

The receiver’s data rule took its own path. Treasury’s QFC recordkeeping rules, published October 31, 2016, became effective December 30, 2016. [6] [7] Treasury said the final version cut burden in several ways. It replaced the requirement for organizational charts of counterparties with certain information on each counterparty, such as its immediate and ultimate parent entities. [6]

In our reading, that change mirrors the stay rule’s shift to consolidated affiliates. Both agencies moved toward a counterparty hierarchy firms could maintain: a legal entity and its parents. [2] [6]

As checked on November 16, 2026, the current text of 31 CFR 148.1 sets compliance dates for records entities by size. [7] It names March 31, 2019 for records entities with total assets of $1 trillion or more and their corporate groups, and June 30, 2019 for those of $500 billion or more. [7]

It names June 30, 2020 for those of $250 billion or more, and June 30, 2021 for remaining records entities. [7] Treasury’s 2016 rule also set a de minimis exemption from most recordkeeping, other than keeping governing documents, for entities party to 50 or fewer open QFC positions. [6]

So the 2016 proposal’s structure lasted. Contract terms changed through protocols and amendments, on dates sorted by counterparty type, with a trigger that ran through counterparty groups. [5] The data needed to apply it, entity hierarchies and contract inventories, is the same data Treasury’s rule asked records entities to keep for a receiver. [6] [7]

We have not reviewed examination findings on how well banks applied the trigger, and none appear in the sources we checked. Firms should confirm their current obligations under both rules with counsel.

Spotted an error? Tell us and we will check it and correct the article where needed.

  • qualified financial contracts
  • resolution planning
  • OCC
  • counterparty data
  • contract remediation
  • Dodd-Frank