The Office of the Comptroller of the Currency (OCC) sets supervisory expectations for how national banks and federal savings associations manage risk from third-party relationships. The 2023 interagency guidance — issued jointly by the OCC, FDIC, and Federal Reserve — replaced OCC Bulletin 2013-29 with a single, principles-based framework that applies across all OCC-regulated institutions regardless of size.
Every OCC-regulated institution is subject to the guidance. Community banks with simpler vendor portfolios face proportionally lighter scrutiny than large multi-charter institutions, but no bank is exempt. Examination intensity scales with the complexity and criticality of a bank's third-party relationships.
A critical activity is a third-party relationship that could significantly impact a bank's operations, expose it to material risk, or affect a large number of customers if the relationship fails. Core banking platforms, payment processors, and cloud infrastructure providers typically fall into this category and attract the closest supervisory attention.
OCC Bulletin 2013-29 was an OCC-specific document. The 2023 guidance harmonises standards across the OCC, FDIC, and Federal Reserve under one framework, giving banks operating under multiple charters or holding structures a single consistent standard. The principles-based approach gives institutions flexibility on implementation while maintaining clear expectations around risk management outcomes.
Crest Perspective
Banking regulators globally have moved from principles-based guidance to prescriptive expectations on third-party risk. DORA, OSFI B-10, the 2023 US Interagency Guidance, and the RBI Master Directions each specify what a board-level third-party risk programme must contain. For regulated institutions, the question is no longer whether to have a TPRM programme but whether the programme’s documentation is sufficient to withstand a regulatory examination.
It applies to every OCC-regulated institution regardless of size, though examination intensity scales with the complexity and criticality of a bank's third-party relationships. Community banks with simpler vendor portfolios face proportionally lighter scrutiny than large, multi-charter institutions with numerous critical activities.
A critical activity is a third-party relationship that could have a significant impact on a bank's operations, expose it to significant risk, or affect a large number of customers if the relationship fails. Core banking platforms, payment processors, and cloud infrastructure providers typically fall into this category.
Reassessment frequency should be risk-based: critical activity vendors warrant at least annual formal reassessment alongside continuous monitoring, while lower-risk vendors can be reviewed less frequently. Regulators increasingly expect continuous, evidence-based monitoring for the most critical relationships.
OCC Bulletin 2013-29 was an OCC-specific document; the 2023 interagency guidance replaced it with a single, principles-based framework issued jointly by the OCC, FDIC, and Federal Reserve. This harmonisation gives banks operating under multiple charters or holding structures one consistent standard.
No. A SOC 2 report is useful supporting evidence, but examiners expect the bank to perform its own independent risk assessment. The bank remains responsible for corroborating the report's scope against its own risk exposure.
When OCC examiners assess a bank’s third-party risk programme, they look for evidence of ongoing management, not a one-time compliance exercise. Examination teams start by requesting the bank’s third-party inventory and risk ratings, then test whether documentation reflects independent analysis or simply acceptance of vendor-supplied materials.
The most common finding is a gap between stated policy and actual practice. A bank may have a policy requiring annual reassessment of critical vendors, but examination evidence reveals the policy is not being executed consistently. Examiners document this as a deficiency in programme effectiveness.
Key areas that attract closest scrutiny:
The interagency nature of the 2023 guidance has direct examination implications. Under OCC Bulletin 2013-29, OCC-supervised banks were examined against one standard, while Fed-supervised bank holding companies faced a slightly different framework. The 2023 guidance creates a single examination baseline across all three agencies, which matters most for large banking organizations operating under multiple regulatory charters.
The principles-based approach shifts examination methodology. Rather than checking a list of required programme elements, examiners now assess whether a bank’s third-party risk management activities are proportionate to the risk and complexity of its third-party relationships. A community bank with three critical vendor relationships and a large regional bank with 200 are both expected to have effective programmes — but what an effective programme looks like differs substantially.
Examiners are also placing greater emphasis on concentration risk. Banks with material concentration in a single cloud provider, core banking platform vendor, or payment network are expected to understand and document that concentration at the board level.
The FFIEC IT Examination Handbook provides supplemental guidance that examination teams use alongside the 2023 interagency guidance. The Outsourcing Technology Services booklet specifies supervisory expectations for technology service provider (TSP) risk management directly relevant to how banks should structure their critical vendor oversight programmes.
Banks that have aligned their third-party risk frameworks to both the FFIEC IT Handbook and the 2023 interagency guidance are better positioned for technology-focused examinations. The FFIEC handbook covers areas the interagency guidance leaves to institutional discretion, including specific requirements for service level agreements with TSPs and requirements around on-site examinations of TSPs.
The 2023 guidance explicitly addresses relationships with fintech companies, marketplace lenders, and other non-bank entities that have become significant partners for regulated banks. These relationships present distinct challenges because fintechs often lack the compliance infrastructure of traditional enterprise software vendors — they may not have SOC 2 reports, may not have undergone regulatory examination, and may operate in jurisdictions with different data protection requirements.
OCC guidance expects banks to apply the same lifecycle management framework to fintech partnerships as to any other critical third-party relationship. For banks entering Banking-as-a-Service (BaaS) arrangements, the guidance is particularly relevant: the OCC has made clear that regulated banks bear full responsibility for their fintech partners’ compliance with federal consumer protection laws and anti-money laundering requirements.
Banks building or remediating their third-party risk programmes to align with OCC expectations should address five structural areas:
The 2023 guidance aligns OCC third-party risk expectations with broader operational resilience frameworks that US and international banking regulators have been developing since 2019. The Basel Committee’s Principles for Operational Resilience (2021) and the FFIEC’s Business Continuity Management booklet both treat third-party relationships as a material operational resilience risk requiring active board-level oversight.
For US banks with international operations, aligning third-party risk programmes to both the 2023 interagency guidance and international frameworks — including DORA for EU operations, OSFI B-10 for Canadian operations, and the MAS TRM guidelines for Singapore — reduces the compliance overhead of maintaining separate programmes for each jurisdiction and demonstrates regulatory maturity to all supervisors.
AI-powered TPRM, compliance automation and GRC intelligence for enterprise teams.
Request a Demo →Ready to get started?
Bring structure, automation, and continuous intelligence to your GRC Process — without adding headcount.
★ Schedule a Demo