# Bank technology contracts under the Bank Service Company Act: the 30-day notice, examiner access and contract terms, explained

A bank that has a technology provider perform covered services must notify its federal banking agency within 30 days, and the provider’s work becomes examinable. The information security guidelines add contract duties, and part 304 adds the provider’s own incident notice.

Explainer · Financial Services · Economics & Procurement. Published November 14, 2026. Last reviewed November 14, 2026.

## At a glance

- 12 U.S.C. 1867(c): services a depository institution has performed for it, by contract or otherwise, are examinable as if the institution performed them itself.
- The institution must notify each such agency within 30 days after the contract is made or the service is performed, whichever occurs first.
- Covered services include check and deposit posting, statements and other clerical, bookkeeping, accounting, statistical or similar functions; the FDIC includes data processing, internet and mobile banking.
- FDIC form 6120/06 is optional; notices go to the FDIC regional office (FIL-19-2019).
- 12 CFR part 364, appendix B: institutions must require service providers by contract to implement appropriate security measures.
- 12 CFR 304.24: a bank service provider must notify the bank as soon as possible of an incident that has materially disrupted or degraded, or is reasonably likely to, covered services for four or more hours.
- Proposed replacement third-party guidance: comments now due December 16, 2026 (as checked November 14, 2026).

## Three duties, one relationship

When a bank hands a core banking, data processing or digital banking function to an outside technology company, three separate sets of rules attach to the same contract. The Bank Service Company Act brings the provider within the reach of the bank’s federal examiner and requires the bank to tell that examiner the relationship exists [1]. The Interagency Guidelines Establishing Information Security Standards require the bank to bind the provider by contract to protect customer information [5]. The computer-security incident notification rule puts a direct duty on the provider to warn the bank when an incident disrupts the service [6]. Supervisory guidance on third-party risk then describes how the agencies expect the contract to be negotiated and the relationship overseen, without having the force of law [4].

## What the Bank Service Company Act says

Section 7(c) of the Act, 12 U.S.C. 1867(c), applies whenever a depository institution that is regularly examined by an appropriate federal banking agency, or a subsidiary or affiliate the agency examines, causes services authorized under the Act to be performed for itself, “by contract or otherwise”, on or off its premises [1]. Two consequences follow. First, the performance of those services is subject to regulation and examination by the agency “to the same extent as if such services were being performed by the depository institution itself on its own premises” [1]. Second, the institution must notify each such agency of the existence of the service relationship within thirty days after the making of the service contract or the performance of the service, whichever occurs first [1]. Both the thirty-day period and the “whichever occurs first” wording are in the statute, so a service that begins before the contract is signed runs the period from the earlier event.

Section 1867(d) authorizes the Federal Reserve Board and the appropriate federal banking agencies to issue regulations and orders to administer the Act and prevent evasions [1]. Separately, a bank service company itself is subject to examination by the agency of its principal investor and to the enforcement provisions of 12 U.S.C. 1818 as if it were an insured depository institution [1].

## Which services count

The notice and examination provision turns on “services authorized under this chapter”. Section 3 of the Act, 12 U.S.C. 1863, lists check and deposit sorting and posting, computation and posting of interest and other credits and charges, preparation and mailing of checks, statements, notices and similar items, and any other clerical, bookkeeping, accounting, statistical or similar functions performed for a depository institution [2]. The FDIC reads that list to include data processing, internet banking and mobile banking services [3]. The statute does not use the phrase “technology service provider”; the FDIC’s letter uses it.

## How the notice is given

The FDIC’s letter FIL-19-2019, issued April 2, 2019, reminds FDIC-supervised institutions that section 7 requires written notice to their federal banking agency of contracts or relationships with technology service providers that provide covered services [3]. The FDIC offers form FDIC 6120/06 for the purpose, says the form is optional and that the information may be submitted in any format, and asks that notices go to the institution’s FDIC regional office [3]. The letter applies to all FDIC-supervised institutions, including those under $1 billion in total assets [3]. This page relies on the FDIC’s letter; institutions supervised by the OCC or the Federal Reserve should confirm the channel their own agency uses.

## What contracts must and should say

### The requirement

Appendix B to 12 CFR part 364, the FDIC’s version of the interagency information security guidelines, requires each institution to exercise appropriate due diligence in selecting service providers, to require its service providers by contract to implement appropriate measures designed to meet the guidelines’ objectives, and, where its risk assessment indicates, to monitor them to confirm they have satisfied those obligations, including by reviewing audits, summaries of test results or equivalent evaluations [5]. The appendix defines a service provider as any person or entity that maintains, processes or is otherwise permitted access to customer information or consumer information through services provided directly to the institution [5]. FIL-19-2019 states that institutions must account for these requirements in contracts with technology service providers [3].

### The guidance

The 2023 Interagency Guidance on Third-Party Relationships, issued by the Federal Reserve, the FDIC and the OCC and published at 88 FR 37920 on June 9, 2023, lists considerations for contract negotiation from the nature and scope of the arrangement through performance measures, the right to audit, costs, ownership and license, confidentiality and integrity, operational resilience and business continuity, indemnification, insurance, subcontracting, foreign-based third parties and default and termination [4]. Its last item, regulatory supervision, says it is important for contracts in relevant relationships to stipulate that the third party’s performance of activities is subject to regulatory examination and oversight, including retention of and access to relevant documentation; the footnote cites 12 U.S.C. 1464(d)(7)(D) and 1867(c)(1) [4]. The guidance states that it does not have the force and effect of law and imposes no new requirements [4].

FIL-19-2019 records what FDIC examiners had found: some contracts did not require the provider to maintain a business continuity plan, set recovery standards or define remedies for missing them; others did not detail the provider’s duties to notify the institution, regulators or law enforcement of security incidents; and some left key terms undefined [3]. The letter says long-term and automatically renewing contracts may be at higher risk of coverage gaps, and that where a contract leaves gaps it is prudent for the institution to assess the risk and put compensating controls in place, such as obtaining supplementary business continuity documentation or adjusting its own plan [3].

## The provider’s own incident duty

The FDIC’s computer-security incident notification rule, 12 CFR part 304, subpart C, defines covered services as services subject to the Bank Service Company Act and a bank service provider as a bank service company or other person that performs them, excluding designated financial market utilities [6]. Section 304.24 requires a bank service provider to notify at least one bank-designated point of contact at each affected banking organization customer as soon as possible when it determines it has had a computer-security incident that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, covered services for four or more hours [6]. If the bank has not given a point of contact, notice goes to the chief executive officer and chief information officer, or two individuals of comparable responsibilities [6]. Scheduled maintenance, testing or software updates communicated in advance are excluded [6]. The duty comes from the regulation, not the contract, so the bank’s practical lever is making sure the provider holds a current contact.

## One conflict to know about

FIL-19-2019, still posted by the FDIC, refers institutions to the FDIC’s Guidance for Managing Third-Party Risk, FIL-44-2008, for contract structure and provider oversight [3]. The 2023 interagency guidance states that it rescinds and replaces the FDIC’s 2008 guidance [4]. The two documents therefore point in different directions on that cross-reference. As checked on November 14, 2026, the agencies say they plan to rescind their existing third-party guidance when the proposed replacement is finalized [8], and the statutory notice duty described in the 2019 letter reads the same in the 2024 edition of the U.S. Code, whose amendment notes list no change after 2010 [1].

## Where the guidance stands in November 2026

On September 15, 2026 the OCC, the Federal Reserve, the FDIC and the NCUA proposed new third-party risk management guidance (91 FR 58536) that would discuss the potential benefits of aligning a bank’s third-party risk management practices with the assessed risk of each relationship, and said they plan to rescind and replace the existing guidance [7]. On November 13, 2026 the agencies extended the comment period from November 16 to December 16, 2026 [8]. The proposal is supervisory guidance and, as the agencies say, non-binding [8]. It does not change the statute: the thirty-day notice in section 1867(c)(2), the contract requirement in the information security guidelines and the provider’s incident duty in part 304 stay as they are whatever the final guidance says [1] [5] [6].

## What we would check in a contract file

These are our suggestions, not requirements. For each technology provider that performs a covered service: the date the service started or the contract was signed, whichever came first, and the date the agency notice went out; a clause acknowledging examiner access to the provider’s performance of the service and its records; the security measures the provider is bound to and the evidence the bank will review; a named point of contact the provider holds for incident notices; and the business continuity and recovery terms the FDIC found missing in 2019. Counsel should confirm how these apply to a particular institution and charter. This page explains the rules; it is not legal advice.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## Sources

1. U.S. Government Publishing Office (GovInfo). 12 U.S.C. 1867, Regulation and examination of bank service companies (United States Code, 2024 edition). <https://www.govinfo.gov/content/pkg/USCODE-2024-title12/html/USCODE-2024-title12-chap18-sec1867.htm> Checked November 14, 2026.
2. U.S. Government Publishing Office (GovInfo). 12 U.S.C. 1863, Permissible bank service company activities for depository institutions (United States Code, 2024 edition). <https://www.govinfo.gov/content/pkg/USCODE-2024-title12/html/USCODE-2024-title12-chap18-sec1863.htm> Checked November 14, 2026.
3. Federal Deposit Insurance Corporation. FIL-19-2019, Technology Service Provider Contracts (April 2, 2019). <https://www.fdic.gov/news/financial-institution-letters/2019/technology-service-provider-contracts> Checked November 14, 2026.
4. Federal Reserve, FDIC and OCC, Federal Register (via GovInfo). Interagency Guidance on Third-Party Relationships: Risk Management (88 FR 37920, June 9, 2023). <https://www.govinfo.gov/content/pkg/FR-2023-06-09/html/2023-12340.htm> Checked November 14, 2026.
5. Federal Deposit Insurance Corporation, Electronic Code of Federal Regulations. 12 CFR part 364, appendix B, Interagency Guidelines Establishing Information Security Standards (eCFR current to November 12, 2026). <https://www.ecfr.gov/current/title-12/part-364> Checked November 14, 2026.
6. Federal Deposit Insurance Corporation, Electronic Code of Federal Regulations. 12 CFR part 304, subpart C, Computer-Security Incident Notification (eCFR current to November 12, 2026). <https://www.ecfr.gov/current/title-12/part-304/subpart-C> Checked November 14, 2026.
7. OCC, Federal Reserve, FDIC and NCUA, Federal Register. Proposed Third-Party Risk Management Guidance (91 FR 58536, September 15, 2026): document details. <https://www.federalregister.gov/documents/2026/09/15/2026-18859/proposed-third-party-risk-management-guidance> Checked November 14, 2026.
8. Federal Deposit Insurance Corporation. Agencies Extend Comment Period for Proposed Third-Party Risk Management Guidance (joint release, November 13, 2026). <https://www.fdic.gov/news/press-releases/2026/agencies-extend-comment-period-proposed-third-party-risk-management> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/bank-service-company-act-provider-notice-and-contracts-explained>
Publisher: Moraph Insights
