← All articles
Regulatory & Compliance

How to evaluate AI lending software for examiner readiness and vendor risk

Vijay Mehra
November 17, 2026

Disclosure. LenderBox publishes this guide and sells AI lending software, so we are one of the vendors this checklist is meant to test. It ranks no products. Regulatory references come from the regulators' own websites, read on November 16, 2026 and listed under Sources. This is a practical checklist, not legal advice. Last reviewed November 16, 2026.

What examiner-ready AI lending software can show you

To judge whether AI lending software is ready for your examiners and your vendor risk committee, ask for evidence in four areas: the vendor's security and operations, how the AI is documented and controlled, what record each loan file keeps, and the contract terms for change and exit. Most of this can be requested in writing before the first demo.

Use the checklists below with your vendor risk, model risk, credit administration and IT reviewers. Each item says what to request and what a complete answer looks like.

Start by rating how critical the tool is

The interagency guidance on third-party relationships, issued by the OCC, Federal Reserve and FDIC in June 2023 (OCC Bulletin 2023-17 and Federal Reserve SR 23-4), describes a risk management life cycle and notes that not every third-party relationship carries the same risk. A tool that prepares every credit decision deserves deeper review than one that formats reports.

Then send the same request list to every vendor on your shortlist, with a deadline. Compare the documents that come back, item by item.

Part 1: security and operations

Your vendor risk team will ask for these first.

  • Attestation report. Request the report itself, under NDA. Check the type (Type II tests controls over a period), the trust services criteria covered, the period, and whether the auditor is an independent firm.
  • Encryption. Ask how data is encrypted at rest and in transit, and who manages the keys.
  • Hosting. Ask where data is stored and processed, including backups and any AI model providers.
  • Isolation. Ask how your data is kept apart from other institutions' data.
  • Training. Ask, in writing, whether your data trains or fine-tunes any model, the vendor's or a provider's.
  • Access. Ask who at the vendor can see your deals, how that access is approved, and whether it is logged.
  • Subprocessors. Get the list and their own reports.
  • Resilience. Request business continuity and incident response procedures and recent penetration test results.

Part 2: model risk and AI controls

In April 2026 the Federal Reserve, OCC and FDIC issued revised model risk management guidance (SR 26-2), which supersedes SR 11-7. The Federal Reserve says it is expected to be most relevant to banking organizations with over $30 billion in total assets and emphasizes a risk-based approach tailored to each organization. Smaller institutions should still be ready to explain how they understand and control an AI tool. Ask for:

  • A plain description. What the software does, what it does not do, and which outputs feed a credit decision.
  • Decision rights. Written confirmation that your staff approve every credit decision, and where in the workflow that happens.
  • Model documentation. The vendor's documentation for your model risk reviewer, including the models used and how outputs are checked.
  • Testing on your files. Results from your own closed loans, compared with what your team approved.
  • Change control. How you are told when models or logic change, and how a change is tested before it reaches your deals.
  • Overrides. How a reviewer corrects an output, and whether the original and the correction are both kept.

Part 3: what the loan file must show an examiner

Examiners read the loan file. Ask each vendor to show a finished file and confirm it contains:

  • Every figure in the analysis traced to the document and page it came from.
  • Each policy exception, the policy section it touches, the reason, and who approved it.
  • Who prepared, reviewed and approved the analysis and memo, with dates.
  • Where documents disagreed and how the reviewer resolved it.
  • A record that can be produced later in the same form, without rebuilding it.

Credit unions should also check that the tool applies the board-approved loan policy. NCUA's examiner's guide says Part 723 of its rules establishes policy and program responsibilities for commercial lending and that every credit union needs a board-approved loan policy.

Part 4: contract, change and exit

  • Data on exit. In what format you can export deals, documents and records, at what cost, and what the vendor deletes afterward.
  • Notice of change. How you are told about new subprocessors, hosting changes or material product changes.
  • Incident notice. How quickly and how you are told about a security incident.
  • Pilot and guarantee terms. What happens if the tool does not work for you, written into the agreement.

The evidence pack at a glance

ItemWho asksWhat a complete answer looks like
Attestation reportVendor riskType II report, period and criteria stated, delivered under NDA
Data handling statementVendor risk, ITHosting location, encryption, isolation and no-training terms in writing
Subprocessor listVendor riskNamed providers with their own reports
Continuity and incident proceduresVendor risk, ITCurrent documents and recent penetration test results
Model documentationModel riskWhat it does, what it does not do, how outputs are checked
Results on your closed filesCredit administrationSide-by-side comparison with your approved analysis
Sample finished fileLoan review, complianceCited figures, recorded exceptions and approvals
Exit termsLegal, procurementExport format, fees and deletion in the contract

How LenderBox answers this checklist

We are a vendor, so here are our answers in the same format. LenderBox is SOC 2 Type II attested by an independent auditor, and the report is available under NDA. Data is hosted on Amazon Web Services in United States data centers, encrypted at rest and in transit, and kept under zero data sharing: isolated per institution and never used to train or improve any model. Access to production data requires explicit authorization and is logged. On request we provide model documentation for your model risk team. LenderBox drafts the credit memo and recommendation, every figure is cited to the document and page it came from, exceptions are kept on the record with the reason, and your underwriter approves at every stage. Results write back to your loan system. You can export your deals, documents and records in standard formats with no export fees. There are no long-term contracts, and you get a full refund of subscription fees within 90 days of go-live, on one written request. More detail is on our security page and our page for vendor risk teams.

Questions to ask any vendor, including us

  1. Can we read your attestation report this week, and what period and criteria does it cover?
  2. Where is our data stored and processed, including by AI model providers?
  3. Is our data used to train or fine-tune any model?
  4. Who at your company can see our deals, and is that access logged?
  5. What model documentation can our model risk reviewer read?
  6. Can the software approve a loan, or change a figure without a person seeing it?
  7. Show us a finished loan file. Where are the sources, exceptions and approvals?
  8. How will you tell us when the models or logic change?
  9. What do we get back, and what do you delete, if we leave?

Frequently asked questions

What do examiners look for when a lender uses AI in underwriting?

Expect questions about how you chose and oversee the vendor, how you understand and control the tool, and whether each loan file shows where its figures came from and who made the decision.

Is a SOC 2 report enough for vendor due diligence?

It covers the vendor's controls. A complete due diligence file also includes the data handling terms, subprocessor list, continuity procedures, model documentation and results on your own loans.

What is the difference between SOC 2 Type I and Type II?

A Type I report describes controls at a point in time. A Type II report tests whether controls operated over a period, which is why vendor risk teams usually ask for Type II.

Does the model risk guidance apply to a community bank?

The Federal Reserve says SR 26-2 is expected to be most relevant to banking organizations with over $30 billion in total assets. Community banks should still be able to explain how they understand and control any AI tool they use.

Which guidance covers vendor risk for banks?

The interagency guidance on third-party relationships, issued in June 2023 as OCC Bulletin 2023-17 and Federal Reserve SR 23-4, applies to banks' third-party relationships.

Is this checklist written for credit unions too?

Yes. The security, AI and file checks apply equally. Credit unions should also confirm that the tool applies their board-approved loan policy under NCUA's commercial lending rules.

Sources

  • OCC Bulletin 2023-17, Third-Party Relationships: Interagency Guidance on Risk Management: occ.gov, read November 16, 2026.
  • Federal Reserve SR 23-4: federalreserve.gov, read November 16, 2026.
  • Federal Reserve SR 26-2, Revised Guidance on Model Risk Management: federalreserve.gov, read November 16, 2026.
  • NCUA Examiner's Guide, Commercial and Member Business Loans: ncua.gov, read November 16, 2026.
  • LenderBox: security, trust center.

Want our diligence package? Request the SOC 2 report through the trust center. Want to see a finished loan file built from your own documents? Talk to our team.

Related reading

See it work on one of your own deals.

A 30-minute demo can run on documents you bring. Every figure comes back tied to its source page, and your team still makes every credit decision.

See it in action
30 MINUTES. NO COMMITMENT. 90-DAY MONEY-BACK GUARANTEE.