The qualified financial contract stay rules adopted by the Federal Reserve, the Office of the Comptroller of the Currency and the Federal Deposit Insurance Corporation require covered entities to ensure that their qualified financial contracts contain provisions limiting a counterparty’s ability to exercise default rights based on the entity’s affiliate entering resolution. The regulatory intent is to prevent a disorderly unwinding of contracts during a resolution event. The operational consequence for the firms subject to them is a contract remediation exercise of unusual breadth.
Most firms handled the initial wave through the industry resolution stay protocol, which delivered coverage efficiently for adhering counterparties. What tends to remain afterwards is a tail: counterparties that did not adhere, agreement types that sit outside the protocol’s reach, newly onboarded relationships, and legacy documents whose in-scope status was never definitively established. That tail is where remediation programs stall.
This guide treats the problem as a contract data exercise rather than a documentation exercise. The amendment language is largely settled. What is not settled, in many institutions, is a defensible answer to the question of which agreements are in scope, what their current compliance state is, and how that state is maintained as the estate changes.
Why scoping is the hard part
Qualified financial contracts are defined by product characteristics rather than by document title, which means scope cannot be determined from a contract type field alone. Five factors make identification harder than it first appears.
- Breadth of the definition, covering securities contracts, commodity contracts, forward contracts, repurchase agreements, swap agreements and related credit enhancements.
- Credit enhancements travel with the contract, so guarantees and collateral arrangements supporting an in-scope agreement fall into scope themselves.
- Document titles are unreliable, because a master agreement may cover both in-scope and out-of-scope activity depending on the annexes executed under it.
- Entity structure matters, since the rules apply by covered entity, and the same counterparty relationship may be in scope for one legal entity and not another.
- Legacy documentation gaps, where older agreements lack the metadata needed to classify them without a document-level review.
The practical consequence is that scoping cannot be completed from a counterparty list. It requires a document-level classification pass across the agreement estate, with the classification recorded as durable data rather than as the output of a one-off project spreadsheet that ages out within a year. Institutions that approach this as a legal review rather than as a data exercise tend to produce an answer that is correct on the day it is delivered and stale within months, because nothing in the process keeps it current as new agreements are executed.
Protocol adherence typically resolves the majority of counterparties quickly, which makes the remaining bilateral population look small. It is also the population with the weakest documentation, the least standard agreements and the counterparties least inclined to sign an amendment, which is why the tail consumes most of the program timeline.
What has to be maintained after remediation
Remediation is a project. Compliance is a standing state. These are the controls that keep the two from diverging once the project team disbands.
- Recordkeeping capability. The ability to produce qualified financial contract records in the required form and timeframe is an ongoing obligation, not a project deliverable, and it degrades when the underlying data is not maintained.
- A gate on new agreements. Every new in-scope agreement must carry compliant language at execution. Without a gate in the onboarding path, the remediated population erodes with each new relationship.
- Amendment monitoring. An amendment to an in-scope agreement can affect its compliance status, so amendments need the same classification and check as originals.
- Entity and affiliate changes. Reorganizations, acquisitions and new legal entities change which agreements sit with which covered entity, and therefore which are in scope.
- Evidence of coverage. Adherence letters, executed amendments and classification decisions retained and retrievable, because the question will be asked long after the people who answered it first have moved on.
Five steps to a defensible compliance position
Step 1, classify the estate at document level
Run a classification pass across master agreements, annexes, guarantees and collateral documents, recording in-scope status, covered entity, counterparty and current compliance state as structured fields. Treating this as a durable data model rather than a project extract is what allows the answer to be reproduced later, and the same discipline underpins broader third-party contract automation work.
Step 2, reconcile protocol coverage against the population
Match adherence records to the classified population to produce a precise remaining set. Most firms find discrepancies here, usually because adherence was recorded at counterparty group level while agreements sit with specific legal entities.
Step 3, work the bilateral tail with a tracked outreach
Each remaining counterparty becomes a tracked item with an owner, a status and a next action. The value of tracking is less about speed than about being able to demonstrate a reasoned, documented effort on the relationships that remain unresolved. Where the discrepancy runs the other way, and adherence is recorded for an entity with no in-scope agreements, that is worth understanding too, since it usually indicates a classification gap rather than surplus coverage.
Step 4, install the execution gate
Add a compliance check to the agreement approval path so that an in-scope agreement cannot be executed without compliant stay and cross-default override language. This is the control that prevents the population from decaying after the project closes.
Step 5, rehearse the recordkeeping request
Periodically produce the qualified financial contract records as if responding to a request, and measure how long it takes and what is missing. A capability that has never been exercised is an assumption rather than a control.
See in-scope classification maintained as live data
Aavenir keeps agreement classification, compliance state and evidence linked to the executed documents, so scope questions have a current answer.
Where this connects to the wider contract program
Stay clause remediation is one of several regimes that ask the same underlying question of a financial institution: can you tell us, with evidence, which of your agreements have a particular characteristic and what their current state is. Vendor oversight expectations ask it about service providers. Resolution planning asks it about critical services and their contractual continuity. Each program that answers the question separately builds a separate dataset that ages separately. Firms that instead maintain one classified agreement estate, with regime-specific attributes layered on top, find that the second and third programs cost a fraction of the first. The obligation register that results also serves ongoing obligation management rather than sitting idle between examinations. There is also a practical argument for doing the classification well rather than adequately. A classification recorded as structured data supports queries nobody anticipated when it was built, which is exactly what the next regulatory request tends to require. A classification recorded as a project spreadsheet supports only the question it was built to answer, and usually not for very long.
Agreement types and scoping considerations
An orientation table for the classification pass. Scope determination should follow the regulatory definitions and legal advice rather than this summary, which is intended to show where classification effort concentrates.
| Agreement family | Scoping difficulty | Common gap | Classification approach |
|---|---|---|---|
| Derivatives master agreements | Low | Entity-level adherence mismatch | Match adherence to executing entity |
| Repurchase and reverse repo | Moderate | Assumed covered by protocol | Confirm annex-level coverage |
| Securities lending | Moderate | Legacy documents lacking metadata | Document-level review |
| Guarantees and credit support | High | Not recognized as in scope | Trace to the supported agreement |
| Custody and related services | High | Classified as service agreements | Assess against product characteristics |
The stay rules have been in force long enough that the initial remediation wave is history in most institutions. What remains is the steadier discipline of keeping the classification current, gating new agreements, and being able to produce records on request without a scramble. That is contract data work rather than legal drafting work, and it rewards a single maintained estate over a series of project datasets. Firms that have built it report that the next regime to ask a similar question, and there is always a next one, lands as a configuration exercise rather than a program. The institutions that struggle are those where the answer lives with the people who produced it rather than in a system, because those people move on and the question does not.
For related guidance, see DORA Article 28, what your ICT contracts must carry, Finding embedded leases in your contracts under ASC 842 and The bank’s guide to DORA ICT third-party contract terms.
