Feature Compliance Strategy
OCC Published Its MRA Manual for the First Time. The Five Cs Are Now Your Issue-File Spec.
OCC PPM 5400-11 and Bulletin 2026-41 set the MRA evidence standard: Five Cs, legal citations, dates, dollar amounts. How to build the issue file that survives validation.
Table of Contents
TL;DR
- On August 27, 2026, the OCC published PPM 5400-11, its Matters Requiring Attention manual, publicly for the first time — along with a revised enforcement manual and a joint final rule with the FDIC defining “unsafe or unsound practice.”
- The manual builds every MRA around five parts: concern, cause, consequence, corrective action, commitment. For violation-based MRAs it also requires the legal citation and supporting facts, including dates and dollar amounts.
- Most banks will accept the finding and log a one-line summary in the issue tracker. That mismatch — five-part finding, one-paragraph file — is where validation stalls and where the OCC’s new escalation language starts to bite.
For decades, the OCC’s MRA manual was internal. Banks saw the output of it — a paragraph in a report of examination — and reverse-engineered the expectations from that paragraph. On August 27, 2026, the agency published PPM 5400-11, “Matters Requiring Attention”, in full, alongside Bulletin 2026-41, which announced revised enforcement and MRA manuals.
The transparency is real, and it cuts both ways. The OCC now has to draft findings against a published standard. Banks now have a published specification for the file that answers them.
That is the part most issue-management programs are not built for. A tracker that holds “BSA monitoring — High — owner: BSA Officer — due 60 days” and a PDF attachment is not an answer to a five-part finding. It is a to-do list.
What actually changed, and when
Three things moved together on August 27:
- The OCC revised PPM 5310-3, its enforcement manual, replacing the May 25, 2023 version.
- The OCC revised and publicly released PPM 5400-11 — the first public release of that manual — replacing a February 27, 2026 version and superseding PPM 5400-14, “Violations of Laws and Regulations.”
- The OCC and FDIC jointly adopted a final rule defining “unsafe or unsound practice” for section 8 of the Federal Deposit Insurance Act and standardizing when an MRA may issue. It published at 91 Fed. Reg. 56,007 on September 1, 2026 and takes effect November 2, 2026.
The revised manuals took effect on issuance. If you were mid-exam on August 28, your report was drafted under the new standard.
The directional story in the trade press has been relief: fewer MRAs, more tailoring, enforcement only after a remediation opportunity. True as far as it goes. Bulletin 2026-41 says the OCC “will generally not take enforcement action under section 8 of the Federal Deposit Insurance Act without first providing the bank an opportunity to remediate deficiencies through the supervisory process.”
Read the last clause of the bulletin’s own caveat and the relief gets narrower: the OCC “may take any legally supportable enforcement action, at any time, as circumstances warrant.” The remediation opportunity is a step, not a shield. Bank of America found that out on October 13, 2026, when the OCC assessed $750 million — its largest civil money penalty ever — for BSA/AML deficiencies that persisted more than a year into a December 2024 cease-and-desist order. The order was the remediation opportunity. Incomplete work against it was the escalation trigger. The same pattern shows up in the American Express trade-based money laundering order, where the cited gaps were program-design failures — a risk assessment untailored to the business, and monitoring rules calibrated to the wrong exposure.
The five parts of a finding, and the file that answers them
PPM 5400-11 requires each MRA to be drafted in the Five Cs format: concern, cause, consequence, corrective action, commitment. The manual also requires decisions grounded in objective facts and sound reasoning, and for violation-based MRAs it requires the legal citation plus supporting facts — dates or date ranges, dollar amounts, duration.
Here is the same structure turned into an issue-file map. The right-hand column is not cosmetic; it is what a validator has to be able to find without interviewing anyone.
| Finding element | What the OCC puts in the MRA | What your file must hold | Working owner |
|---|---|---|---|
| Concern | The practice or failure to act, described precisely | The finding as issued, verbatim, plus your own restatement of the condition tested | Business line owner |
| Cause | Why it happened — the control or design gap | Root-cause analysis to a system or design level, not a person; change record for the control that failed | First line, second line review |
| Consequence | The harm or expected harm, with dollar figures and duration | Your impacted-population estimate, remediation cost range, and customer-facing exposure, reconciled to the examiner’s numbers | Risk, finance |
| Corrective action | The specific action required | Action plan with dated milestones, interim compensating controls, and the evidence artifact each milestone produces | Program owner |
| Commitment | Due date and reporting commitment | Governance approvals, board or committee minutes, and the dated validation plan | CRO or Compliance lead |
Two fields do most of the work and are usually missing. Interim compensating controls — what caps the risk between acceptance and the permanent fix — and the evidence artifact for each milestone. Without them, month three of an MRA looks like a status update, and status updates do not validate.
Consequence is where banks most often argue. The examiner has a dollar range and a duration; a bank that responds with “immaterial” without a reconciled population count loses the argument on the record. If the examiner says 14 months and 41,000 accounts, your file needs the query, the count, and either agreement or a documented reason for divergence.
Observations, other violations, MRAs: three tracks
Before you design intake, get the tiers right. The manual sets three, and they carry different obligations.
| Tier | Standard | Action plan required? | Where it lands |
|---|---|---|---|
| Supervisory observation | Weakness below the MRA standard | No — examiners cannot require one and do not track response | Report narrative or discussion |
| Other violation | Violation that is not substantive | Generally documented, not escalated | Appendix to the supervisory letter or ROE |
| MRA | Meets the MRA standard, including any substantive violation | Yes, plus supervisory follow-up and OCC system documentation | The report, board-facing |
Two traps. First, substance is defined for violations, and technical violations are supposed to fall out of the MRA tier — an MRA may only issue for a “substantive” violation, meaning systemic or patterned, more than minimally impactful, requiring more than minimal restitution, or involving insider misconduct. If you get an MRA citing a single isolated documentation lapse with no harm path, the manual gives you a reasoned basis to ask. Second, MRAs cannot be issued for future violations — only for conduct that has occurred. A finding framed entirely in the future tense is worth a conversation.
That said, pick your fights. Appeals cost relationship capital, and an MRA you fight and lose now carries a repeat flag later.
Repeat and self-identified: the two attributes with teeth
The manual lets examiners tag an MRA as Repeat or Self-Identified, and both should change how you run the file.
Repeat requires that the same or substantially similar MRA was communicated within three years of the prior MRA’s closure, that it was previously corrected, and that the OCC validated and closed it. Three conditions, all of them. A finding that resembles a 2021 issue never validated as corrected is not a Repeat in the manual’s sense — but it will still read like one in the board deck.
For a true repeat, the corrective action alone is insufficient evidence. The file has to explain why a control that previously validated has lapsed, and what changed in the control design rather than in the training deck. That is the difference between closing a finding and closing a repeat.
Self-Identified, meanwhile, is credit you can only collect if the discovery predates the examiner’s. The manual weighs self-identification favorably in assessing corrective action. It does not change the classification. Practically, time-stamp the discovery: the internal audit report, the monitoring alert, the risk assessment that surfaced it, with the date it was raised to the committee. A self-identified issue with no discovery date is indistinguishable from one found during fieldwork.
Validation is where the file gets read
The revised enforcement manual tells examiners performing validation to substantially rely on applicable internal audit work when that function is rated satisfactory. Two implications.
If internal audit is rated less than satisfactory, your validation timeline is longer and your own evidence burden is higher. Build the file for that scenario.
If internal audit is rated satisfactory, get audit into the validation plan at acceptance — not to sign off on the business, but to design the test. An audit-designed test with a documented sample methodology is the strongest artifact a file can carry, and it is far cheaper than an examiner-designed one.
The manual also sets the closure bar at substantial compliance: the essential requirements satisfied even if minor, isolated items remain. That leniency is conditional on someone being able to show the essential requirement held over a period. A single post-implementation walkthrough does not show a period. A three-month sample with exceptions logged, root-caused, and trended does — and the closeout file structure for order termination is the same discipline applied one level up.
The practitioner failure mode: acceptance without decomposition
The real failure happens in week one, in the room where the exit meeting ends. A finding is read aloud, someone senior says “we’ll take it,” and the tracker gets a row. Nobody decomposes the finding into the five parts. Nobody assigns consequence to finance. The correcting team starts building against the corrective action sentence, blind to the cause the examiner already named, and six weeks later the validation memo answers a question nobody asked.
Fix the intake steps, not the tracker field. The alert disposition evidence file is a useful model here: every disposition carries the query, the reviewer, and the reason, so a third party can re-perform it.
- Read the finding aloud, part by part. Assign an owner to each of the five elements within 24 hours of receipt.
- Reconcile consequence before drafting action. Population count and duration agreement, or a documented divergence, from finance and data.
- Name the interim control on day one. Which existing control caps exposure until the permanent fix lands, who tests it, and how often.
- Log the classification and its flags. MRA versus observation, repeat versus not, self-identified date. The classification drives every downstream deadline.
- Book the validation design session at acceptance. Audit if rated satisfactory, second line if not.
None of that requires a new system. It requires the finding to be treated as a document with a structure instead of a headline with a deadline.
And it requires honesty about the classification. The most common quiet error is treating an observation as an action item — assigning an owner, setting a date, tracking it in the same register — then reporting observation volume as if it were finding volume. Logging observations is defensible. Blurring them with MRAs distorts your board metrics and your repeat analysis. Keep one register, but keep the tier field honest.
So what
The published manual is a gift to anyone who reads it as a specification. It tells you, in advance, exactly what a finding will contain and what an examiner will look for at validation. The banks that build files against those five elements will close findings faster, and the ones that keep filing one-line rows will accumulate aging items into the third and fourth quarter — where the escalation math starts.
Start with the intake checklist: five fields, five owners, twenty-four hours. Our Issues Management Tracker & Template has the regulator-finding tab, the minimum-rating rule for MRA-linked issues, and the closure validation checklist built for exactly this.
FAQ
What is a Matter Requiring Attention under the revised OCC manual?
An MRA is a supervisory communication issued only for a practice, act, or failure to act that is contrary to generally accepted standards of prudent operation and that could reasonably be expected to materially harm the bank’s financial condition or present a material risk of loss to the Deposit Insurance Fund, or has already caused material harm — or for a substantive violation of banking or banking-related law. PPM 5400-11, published August 27, 2026, sets the standard and requires the Five Cs format.
Are supervisory observations tracked like MRAs?
No. The revised PPM states examiners may not require an action plan for a supervisory observation and do not track whether the bank responded. Observations sit below the MRA standard. Whether to log them anyway is your call, but make it a documented decision rather than a default.
When does the new standard take effect?
The joint OCC-FDIC final rule defining unsafe or unsound practice, published at 91 Fed. Reg. 56,007 on September 1, 2026, takes effect November 2, 2026. The revised PPMs took effect on issuance, August 27, 2026.
Does an MRA always precede an enforcement action?
Usually. Bulletin 2026-41 states the OCC will generally not take enforcement action under section 8 without first giving the bank an opportunity to remediate through the supervisory process. The word is generally — the bulletin preserves authority to act at any time, and a bank that sits on an MRA is the likeliest escalation candidate.
What does substantial compliance mean for closure?
The revised enforcement manual says the OCC will terminate an action when the bank has satisfied the essential requirements even if minor, isolated requirements remain open. That makes the validation record more important, not less: the examiner has to see the essential requirement held over a period.
◆ Need the working template?
Start with the source guide.
These answer-first guides summarize the required fields, evidence, and implementation steps behind the templates practitioners search for.
◆ Related template
Issues Management Tracker & Template
End-to-end issues tracking and remediation management for risk and compliance teams.
◆ Immaterial Findings · Weekly
Sharp risk & compliance insights. No fluff.
◆ FAQ
Frequently asked questions.
What is a Matter Requiring Attention under the revised OCC manual?
Are supervisory observations tracked like MRAs?
When does the new standard take effect?
Does an MRA always precede an enforcement action?
What does substantial compliance mean for closure?
Author
Rebecca Leung
Rebecca Leung has 8+ years of risk and compliance experience across first and second line roles at commercial banks, asset managers, and fintechs. Former management consultant advising financial institutions on risk strategy. Founder of RiskTemplates.
◆ Related framework
Issues Management Tracker & Template
End-to-end issues tracking and remediation management for risk and compliance teams.
◆ Keep reading
Related posts.
Compliance Strategy
Sixteen Consent Orders Were Terminated. Don't Archive the Obligation Map.
The CFPB terminated 16 pending orders in FY2026 and waived redress allegations at Navy Federal. Build the closeout file before leadership declares victory.
Nov 19, 2026
Compliance Strategy
Third-Party Risk Board Metrics That Survive a Follow-Up Question
Five third-party risk board reporting metrics with definitions, paired evidence, and gaming vectors — built for a board that asks who signed.
Nov 16, 2026
Compliance Strategy
The Fed Is Restructuring How It Supervises Banks. What Bowman's Five-Region Overhaul Means for Community Banks and Their Exams.
Federal Reserve Vice Chair for Supervision Michelle Bowman announced a five-region supervision restructuring, alongside the Community Bank Leverage Ratio cut to 8% that took effect July 1. Here's what changes, what stays the same, and what community bank compliance teams should actually do.
Oct 13, 2026