Examiner-Ready Credit File Documentation Checklist

An examiner-ready commercial credit file holds 34 items across ten categories, each with a named owner, a specific piece of evidence and a date that proves it is still current. Twenty-two are blocking — the file is not complete without them. Twelve are advisory: a written reason and a cure date will do.

Key facts

• In YuSight, 100% of the figures in a memo are cited back to the source document and page, and the workflow audit trail records who reviewed what and when — the two artifacts an examiner asks for first.
• The federal standard is functional, not a list. Loan documentation practices must enable an informed lending decision, identify the purpose and source of repayment, ensure any claim against the borrower is legally enforceable, demonstrate administration and monitoring, and take account of the loan's size and complexity (12 CFR Part 30, Appendix A, II.C).
• The rating lives in the file, not in the system. "The rating assigned to a credit should be well supported and documented in the credit file," and "all credits should receive a formal review at least annually to ensure that risk ratings are accurate and up-to-date" (OCC, *Rating Credit Risk*, Comptroller's Handbook).
• Currency is a filing requirement too. A UCC-1 financing statement "is effective for a period of five years after the date of filing," and a continuation "may be filed only within six months before the expiration" (UCC § 9-515).

This is the checklist for the file. The separate question of what an examiner requires from an AI-drafted memo is answered in examiner review of an AI-drafted credit memo; what the memo itself must contain is in what a commercial credit memo must contain.

How to read the checklist

Owner is the role accountable for the item being in the file. Evidence is what satisfies it — an assertion in the memo never does. Currency is the age limit past which the item stops counting; those limits come from your own policy rather than regulation, so the column shows common practice. A Blocking gap stops the file; an Advisory gap needs a written reason and a cure date. A blank field is not a reason.

The 34-item checklist

The FDIC states the expectation behind all of it in one line: lending policies should provide for the "maintenance and review of complete and current credit files on each borrower" (FDIC RMS Manual of Examination Policies, Section 3.2).

Worked example: scoring one file

Alder Creek Properties LLC, a $2,400,000 owner-occupied CRE term loan, twenty months after closing. Items 18 and 31 are marked N/A with written reasons. Denominator: 32.

Applicable items 32 Present, current, evidenced 28 Gaps 4 Gap 1 Appraisal dated 41 months ago; policy limit 36 Blocking Gap 2 UCC-1 lapses in 4 months, no tickler entry Blocking Gap 3 Hazard certificate expired 30 Nov 2025 Blocking Gap 4 Guarantor PFS 14 months old; policy 12 Advisory Completeness = 28 / 32 = 87.5% Blocking gaps = 3 → file is NOT examiner-ready

Eighty-seven and a half per cent looks respectable and is irrelevant. Gap 2 is the expensive one: a lapse date nobody diarised converts a secured exposure into an unsecured one without anybody deciding to. Completeness is a management metric; the blocking count is the pass/fail.

How do examiners test completeness?

They sample — typically weighting larger exposures, adversely rated credits and recent originations — and read each file against the bank's own policy, not an external checklist. Three findings follow:

• A missing item on one file is a documentation exception, cured and closed.
• The same item missing across the sample is a credit administration finding, because it means the control is not operating.
• Exceptions that exist but were never reported is the worst of the three, because it says the exception process itself is not working — an effective policy "describes types of acceptable exceptions and includes guidelines for identifying, justifying, approving, and reporting exceptions" (OCC, *Lending and Loan Portfolio Risk Management*, June 2026).

Rating support is tested the same way: the examiner reads the rationale and asks whether the file evidences it. The questions asked when AI is in the workflow are in what examiners ask about AI underwriting; the covenant side of the file is in covenant monitoring.

Key takeaways

• Count blocking gaps, not completeness percentages. One unperfected lien outweighs thirty tidy items.
• Every item needs a date, an owner and a piece of evidence. An assertion in the memo is not evidence of the document.
• Appraisals, insurance certificates and UCC continuations all expire. Diarise them at closing, not at the annual review.
• Rating rationale and its refresh date are file items, not system fields.

Frequently asked questions

What documents must a commercial credit file contain?

The approval record, three years of financials with their preparation level and dates, tax returns with matching IRS transcripts, dated collateral valuations, current insurance, evidence of lien perfection, guarantor documentation, the covenant compliance record, the rating rationale and its refresh date, and the exception log. Thirty-four items in the checklist above.

How do examiners test credit file completeness?

By sampling loans and reading each file against the bank's own written policy. One missing item is an exception. The same item missing across the sample is a credit administration finding, because it shows the control is not working.

Can documentation gaps be detected automatically?

Yes, for the mechanical part. A system can tell you the appraisal is 41 months old, the certificate expired, the continuation window opens in four months and no transcript was ever ordered. It cannot judge whether the rating rationale is any good.

What is the difference between a blocking and an advisory gap?

A blocking gap stops the file — there is no compensating strength that substitutes for a missing guaranty or an unperfected lien. An advisory gap can be carried with a written reason and a cure date, logged as an exception with an owner.

How current does a financial statement have to be?

Set by your own policy, not by regulation. Common practice is an interim statement within 90 days at approval and annual statements within 120 days of fiscal year end, with the preparation level — audit, review, compilation or company-prepared — recorded as a field rather than a footnote.

How long do we have to keep the file?

Life of loan plus your retention policy period, and long enough to reproduce the file as it stood on the approval date. If a memo cited its sources, that reproduction is straightforward; if it did not, it is archaeology.

See the audit trail an examiner would see

YuSight keeps the record an exam sample tests: every figure cited to its source document and page, a named reviewer and timestamp on each step, full version history, and an exception log with owners and dates. 100% of figures are cited. Book a live demo.