Finance operations

Where Seattle and Chicago Banks and Fintechs Should Start With Back-Office AI

Banks and fintechs in Seattle and Chicago should start back-office AI with one verifiable task and plan for state vendor examination and records rules.

In this guide

If you run operations at a bank or fintech lender in Seattle or Chicago, start back-office AI with one bounded preparation task whose output a named team can verify. Good candidates to evaluate include assembling a document-readiness view, preparing an exception packet or gathering records for a report. Choose from observed work and available data; back-office location alone does not make a task valuable or suitable for AI.

State rules then shape where that tool's records live and who can inspect them. Washington's Department of Financial Institutions can examine the outside service provider of a Washington state-chartered bank as if the bank did the work, and requires Consumer Loan Act lenders to keep cloud records on servers in the United States. An Illinois state bank must notify its regulator of each outside service relationship. Put these rules in the vendor plan from the first week.

The first deliverable should be something an operations employee can use in the existing process. “AI for onboarding” is too broad to test. “List the missing documents for this file, show the source of each status and route uncertain items to loan operations” defines a practical boundary.

Explore an illustrative finance exception and review workflow.

Find the handoff that deserves attention

This first-project selection exercise is a proposed planning method, not a report of Clairvance client work.

Review a representative period of completed and delayed cases. Follow the input from its original system to the employee who uses it. Record active preparation time, time waiting for data or approval, rework and the consequences of a wrong output.

Ask the people doing the work to distinguish three kinds of effort: moving structured data, interpreting varied information and making a decision. A supported interface or fixed rule may solve the first. AI may help with the second. The third needs an explicit policy and accountable decision maker; describing it as paperwork does not remove the judgment.

Compare a few specific candidates

CandidateUseful first outputWhat keeps it bounded
Document readinessRequired, received, accepted and missing items with source linksOperations confirms acceptance; the tool does not approve the customer or credit
Reconciliation exception preparationRelevant transactions and a draft explanation of the mismatchFinance owns the match and any adjustment
Internal reporting preparationCollected figures with source date and lineageReporting owner verifies definitions and releases the report
Case routingSuggested owner and urgency based on approved categoriesUncertain cases remain visible; routing does not become a final case decision

Favor a candidate when inputs are accessible through an approved path, errors are observable, reviewers have capacity and the downstream action is clear. Defer it when source records are unreliable, access is unresolved or the only success measure is an assumed headcount reduction.

Before selecting AI, demonstrate the simplest viable alternative. Configure an existing checklist, query or document rule against the same cases. If it produces the required output with less operating burden, it is a valid first improvement.

A proposed document-readiness handoff

Consider a workflow that prepares a commercial file for loan operations review. Its inputs are the approved requirement list, documents in the bank’s repository and the file identifier in the loan-origination system. Its output is a review record, not a lending decision.

The system proposes document type, entity and period, links each result to the original file, and shows which requirement it may satisfy. It flags unreadable scans, duplicates, expired documents and conflicting versions. “Received” remains distinct from “accepted.” A reviewer can correct the classification and record why a document is sufficient or why more information is needed.

For the initial release, the tool writes only to the approved review area. Loan operations retains control of the official requirement status and any borrower request. If extraction fails or the source repository is unavailable, the case remains in the existing queue with a visible failure reason. The employee can complete the checklist manually using the source records.

Test the whole handoff: a correctly classified document is not useful if it attaches to the wrong borrower, disappears from the queue or creates an extra review task every time the file is reopened.

Evaluate the business task, not a generic model score

BCG and OpenAI’s bank-operations analysis emphasizes evaluation on real workflow tasks. For a small first project, make that practical with a defined set of expected outputs and failures.

In the document example, check correct entity and period, visible source support, missed requirements, incorrectly accepted documents and reviewer correction time. Include difficult cases as well as routine files. Keep some reviewed cases out of initial configuration work so the final check is not only a replay of examples used to tune the system.

Compare total preparation and review effort with the existing process. Track downstream rework and waiting time too. A faster document-reading step may not change end-to-end turnaround if the file still waits for a credit decision or borrower response.

Give the operating team a maintainable first release

Name the process owner, data owner, reviewer and technical support contact. Record the permitted data, access roles, retention, known limitations and the way to disable the new step. The bank’s security, risk and compliance functions should determine the review needed for this use and its effect on decisions. Do not assume every use has identical model-risk treatment.

Current guidance makes that choice explicit. The April 2026 interagency model risk guidance that replaced SR 11-7 states that generative AI and agentic AI models are not within its scope and is expected to be most relevant to banking organizations with over $30 billion in total assets. Regulators oversee AI primarily through existing laws, regulations, guidance and risk-based examinations, according to GAO's May 2025 review. A generative back-office tool therefore needs a review path the bank defines on purpose.

Show staff how to correct an output and where to report a repeated error. Preserve those corrections for controlled review; the system should not silently change approved rules from a single user action. Set an evaluation point when policies, documents or upstream systems change.

What Washington and Illinois regulators add to the first release

For a state-chartered bank or state-licensed lender, the regulator's reach over vendors and records decides what the vendor contract must allow, where the review record is stored and how long it is kept.

In Seattle

Washington's Division of Banks, part of the Department of Financial Institutions (DFI), regulates state-chartered commercial banks, savings banks and savings and loan associations (DFI Division of Banks). A company that provides one of those banks a covered service, meaning a service the federal Bank Service Company Act makes subject to examination, can be examined by the DFI director to the same extent as if the bank performed the service itself. Before a state-only examination of the provider, the director must make one of three findings, one of which could fit an AI vendor: that the provider manages a system whose integrity cannot be evaluated without direct examination (RCW 43.320.500 and 43.320.510).

DFI's list of Washington state-chartered banks includes banks headquartered in Seattle and Bellevue, and a provider serving any bank on that list is examinable the same way.

The Washington Consumer Loan Act, which exempts most business-purpose loans, applies to each loan made to a resident of, or a person physically located in, the state, so it follows the borrower rather than the lender's office (RCW 31.04.025). A fintech lender licensed under it must keep its loan records, including all documents used to support the underwriting approval, for at least three years after the final entry (WAC 208-620-520). Electronic records must be displayable to the DFI director on request, and a cloud service used for records must run on servers located in the United States or its territories (WAC 208-620-530).

In Chicago

Under the Illinois Banking Act, when a state bank has bank services performed for it by contract, including clerical, bookkeeping, accounting, statistical or similar functions and related electronic data processing, that performance is subject to examination as if the bank performed it on its own premises. The bank must also notify the regulator, now the Secretary of Financial and Professional Regulation (205 ILCS 5/2), of the service relationship with its next statement of condition, and of each later contract (205 ILCS 5/48(2.5)).

A lender licensed under the Illinois Consumer Installment Loan Act keeps its records in its business or at a location the Director of Financial Institutions approves, preserves each loan's records for at least two years after the final entry, and may use accounting systems kept by electronic data processing only if the Director approves them in writing (205 ILCS 670/11).

First-release questionWashingtonChicago (Illinois)
A state bank's AI vendorThe DFI director may examine the provider of a covered service as if the bank performed itContracted bank services are examinable as if performed by the bank, and the bank notifies the regulator of each service relationship
A licensed lender's loan recordsAt least three years after the final entry, including underwriting supportAt least two years after the final entry, kept in the business or at an approved location
Electronic and cloud storageDisplayable to the director on request; cloud servers in the United States or its territoriesElectronic accounting systems need the Director's written approval

These are proposed design choices, not legal conclusions. Keep the review record, source links and reviewer corrections in a system the institution controls, so an examiner can verify the work from its own records. Write examination access, retention periods and server location into the vendor contract before the pilot starts rather than at renewal. An Illinois state bank should add the service relationship to its next statement of condition. Federal and state requirements overlap, so confirm the specific obligations with your compliance team and examiner.

The next project should follow evidence from the first: useful output, manageable review and a reliable recovery path. For a broader purchase, use the bank build-or-buy comparison. For connected priorities across the team, see finance operations transformation.

Quick answers

Where should a Seattle or Chicago bank start with AI in the back office?

With one bounded preparation task whose output a named team can verify, such as a document-readiness view, an exception packet or a set of records gathered for a report.

Which back-office tasks suit AI in a bank?

Tasks that interpret varied information before a person decides: document readiness, reconciliation exception preparation, internal reporting preparation and case routing. Moving structured data may need only an interface or rule, and decisions need an accountable owner.

Can Washington or Illinois regulators examine a bank's AI vendor?

Washington's DFI director can examine a provider of covered services to any state-chartered bank in Washington as if the bank performed them. In Illinois, contracted bank services are examinable as if the bank performed them, and the state bank must notify the regulator of each service relationship.

How do federal regulators oversee AI use in banks?

Primarily through existing laws, regulations, guidance and risk-based examinations, according to GAO. The April 2026 model risk guidance excludes generative and agentic AI from its scope, so banks define their own review for those tools.

Sources

  1. BCG and OpenAI’s bank-operations analysis · bcg.com
  2. The April 2026 interagency model risk guidance · occ.gov
  3. according to GAO's May 2025 review · gao.gov
  4. DFI Division of Banks · dfi.wa.gov
  5. RCW 43.320.500 and 43.320.510 · app.leg.wa.gov
  6. list of Washington state-chartered banks · dfi.wa.gov
  7. RCW 31.04.025 · app.leg.wa.gov
  8. WAC 208-620-520 · app.leg.wa.gov
  9. WAC 208-620-530 · app.leg.wa.gov
  10. 205 ILCS 5/2 · ilga.gov
  11. 205 ILCS 5/48(2.5) · ilga.gov
  12. 205 ILCS 670/11 · ilga.gov

Revision note · October 5, 2026: Refocused on Seattle; removed the list of other Washington cities where state-chartered banks are based.

How we research and review these guides

AI transformation with Clairvance

Put the ideas to work in your business.

We provide AI consulting and implementation for finance operations teams. Bring us the process that is slowing your team down and the systems involved. We can assess the problem with you and discuss a practical implementation.

Discuss your project →

Still exploring? Explore the Workflow Opportunity Workbook →