Now Hiring: Are you a driven and motivated 1st Line IT Support Engineer?

NCUA Examination Checklist for Documents and Evidence

Blog Articles

NCUA Examination Checklist for Documents and Evidence

11th

TL;DR

  • Use the examiner’s Document Request List to set priorities, assign owners, and track deadlines.
  • Prepare records across governance, finance, lending, risk, information security, vendor oversight, and internal audit.
  • Check that evidence covers the requested period and connects review decisions to completed corrective actions.
  • Submit documents through the agreed secure channel and explain any missing records.
  • After the examination, assign owners and deadlines to required actions and retain evidence that the underlying issues were addressed.

When the Records Exist but the Evidence Is Hard to Trace

An NCUA examiner asks a credit union for evidence of employee access reviews across core banking and lending. IT has the certification reports, compliance has the policies, and individual administrators have the tickets for permissions that were removed.

The credit union still needs to connect each review decision to the change it triggered. A practical NCUA examination checklist helps teams make that connection, assign responsibility, and identify gaps before submitting evidence.

How Does the NCUA Examination Process Work?

NCUA tailors document requests to the scope and risk profile of the examination. Its published procedures generally call for the examiner-in-charge to send the notification and Document Request List (DRL) at least four weeks before the planned start date, unless regional management approves a shorter timeframe. 

Use the actual DRL to plan preparation, submission, and follow-up. This timeline is an internal planning aid. Follow the deadlines and instructions provided by the examiner-in-charge.

Stage Preparation priority
Ongoing Maintain reliable records, current policies, and remediation evidence
Upon notification Review the DRL, assign owners, and confirm deadlines
Before requested submission dates Validate documents and record evidence gaps
During the examination Manage secure submissions and follow-up questions
At conclusion Review formal examination communications
After the examination Track and verify required corrective actions

If notice is shorter, prioritise the items on the DRL and flag likely delays early through the agreed examination channel.

The NCUA Examination Checklist Covers 10 Preparation Areas

Use these areas to organise common records. The actual DRL determines what your credit union needs to submit.

Preparation area Records to have available Suggested owner
Examination coordination Notification, DRL, and management questionnaire Compliance
Governance and oversight Board minutes, approved policies, and oversight reports Executive management
Financial reporting Call reports, financial statements, and reconciliations Finance
Lending operations Lending policies, approval records, and exception reports Lending
Risk management Risk assessments, monitoring reports, and corrective actions Risk management
Information security Security programme, assessments, and testing evidence IT or security
User access governance Account inventories, certifications, and revocation records IAM or IT
Third-party oversight Vendor assessments, contracts, and monitoring records Vendor management
Internal audit Audit reports, findings, and remediation evidence Internal audit
Examination follow-up Request tracker, responses, and formal action items Examination coordinator

Establish One Examination Coordination Process

Assign a coordinator to manage the DRL and communicate with the examiner-in-charge. Give each request a departmental owner and track its status, deadline, and any clarification needed.

Confirm Which Governance Records Apply

Gather relevant board and committee minutes, approved policies, and oversight reports. If a policy changed, identify which version applied during the period under examination.

Reconcile Financial Records Before Submission

Validate financial statements, call reports, and supporting reconciliations. When a material discrepancy is still under investigation, document what remains unresolved and who is responsible for follow-up.

Organise Lending Evidence by Control Objective

Group underwriting standards, delegated approval authorities, selected loan records, and exceptions according to what they demonstrate. Make it clear how lending decisions were authorised and how exceptions were handled.

Check That Risk Assessments Reflect Current Operations

Review material changes to banking applications, payment services, vendors, and operating processes. Confirm that the assessment addresses the risks those changes introduced and the controls used to manage them.

Prepare Information Security Evidence

Gather the written security programme, relevant risk assessments, testing results, and incident response procedures. Include records that show how key controls operated during the requested period.

Reconcile User Access Decisions With Remediation

Connect each required access change to its reviewer, entitlement, and implementation status. Pay particular attention to privileged access, former employees, and permissions retained after transfers.

Validate Third-Party Oversight Records

Gather contracts, risk assessments, monitoring records, and open issues for relevant providers. Clarify which controls the vendor operates and which responsibilities remain with the credit union.

Update the Internal Audit Findings Register

Record the owner, agreed action, current status, and available verification evidence for each material issue. Keep planned actions distinct from implemented and verified changes.

Maintain a Complete Examination Request Tracker

Track original requests, submissions, clarifications, and follow-up requests. Make previously submitted documents easy to locate and explain why any requested record is unavailable.

How to Build a Document Request Tracker

Connect each DRL item to its owner, evidence, and submission history. The entries below are illustrative.

DRL item Requested document Owner Status Next action
01 Information security programme Security lead Ready Confirm applicable version
02 User access certification evidence IAM manager In progress Reconcile revocations
03 Financial reconciliation records Finance manager Ready Submit through the approved channel
04 Vendor risk assessments Vendor manager Under review Confirm current documents
05 Internal audit findings Internal audit Ready Verify latest issue status

Use consistent statuses and record the submission date, examiner reference, and supporting file. NCUA recommends grouping files by DRL risk area, beginning filenames with the relevant index number, and listing any requested documents that could not be supplied with an explanation. NCUA

For example, a file could be named 07_User_Access_Review_2026_Q3.pdf. If you submit related evidence for an unavailable item, keep the original request marked as unavailable and explain what the alternative evidence covers.

What Information Security Evidence Shows That Access Controls Worked?

An access policy describes the expected process. Entitlement reports, review decisions, and source-system records show how that process operated across core banking, lending, directories, and reporting applications.

Evidence Question it helps answer
Access policy What process was expected?
User and entitlement report Which identities held access?
Certification decisions Who evaluated the permissions?
Approval records Why was access retained?
Exception records Which issues required investigation?
Remediation tickets What corrective action was requested?
Source-system verification Did the required change take effect?

Check that the records cover the requested period. A current account listing shows access today. Historical reports and timestamps help establish what access existed when the control was tested.

How a Credit Union Can Handle Missing Revocation Evidence

A hypothetical credit union retrieves completed access certifications for its core banking and loan origination systems. During its quality check, the IAM team finds several permissions marked for revocation with no clear confirmation that the changes took effect.

  1. Establish what the records show. Identify which items have documented decisions, which removals were verified, and which actions remain unresolved.
  2. Investigate missing confirmations. Ask application administrators to check current permissions and available historical records. If access is still active, assess the risk and follow the approved remediation procedure.
  3. Document the timing of the evidence. If later testing confirms that access is gone, record when that check happened and whether the original removal date can be established.
  4. Prepare the response. Submit available certification records, verified changes, and open exceptions, with a brief explanation of evidence gaps and the owners of outstanding actions.

How to Respond During the Examination

When an examiner asks for clarification or additional documents, confirm the request and examination period. Assign it to the appropriate subject-matter owner, retrieve evidence from the authoritative source, and record what was submitted and when. If a request duplicates an earlier one, reference the previous submission and coordinate through the examiner-in-charge where appropriate. 

Use the official report and formal examination communications to identify findings and required actions. Track clarification requests in the DRL so the team can distinguish open questions from actions management needs to address.

How to Verify Corrective Actions After the Examination

Review the official report and record each required action, accountable owner, deadline, and evidence needed for closure. If a deadline is at risk, use the established supervisory channel to communicate the issue. MERIT can support examination report delivery, status updates, and follow-up on action items. 

Verify that the action addresses the examination concern. For example, removing one employee’s unnecessary access resolves the individual exception. If the transfer procedure omitted a shared repository, update and test the procedure as well.

Where Access Governance Automation Supports Examination Preparation

When access is spread across banking applications and directories, user access review automation can help connect entitlement records, reviewer decisions, exceptions, and remediation evidence throughout the year.

SecurEnds supports these workflows across connected applications. Check which integrations provide the entitlement detail and historical evidence your credit union needs. The identity governance solution for credit unions provides additional context for coordinating access oversight across banking systems.

Best Practices for Checking Evidence Before Submission

  • Check completeness. Confirm that the evidence covers the requested systems, population, and examination period.
  • Reconcile records with the source. Check that reports, approvals, and remediation records reflect what happened in the affected system.
  • Make each item traceable. Record the DRL reference, source, owner, relevant dates, and submission history.
  • Explain evidence gaps directly. Identify what is missing, what can be substantiated, and who owns the next action.
  • Use the agreed secure channel. Follow the examination team’s submission instructions. NCUA supports secure file transfer and MERIT document request surveys. 

Frequently Asked Questions

What documents are typically included in an NCUA examination checklist?

Common records include financial statements, board minutes, lending policies, risk assessments, information security documentation, internal audit findings, and corrective action evidence. Use the examiner’s DRL to confirm which records apply to your examination. 

How far in advance does NCUA notify a credit union of an examination?

NCUA’s published procedures generally call for the notification and DRL to be sent at least four weeks before the planned start date. Regional management can approve a shorter timeframe. Confirm submission deadlines with the examiner-in-charge. 

Does every credit union receive the same NCUA examination document request list?

No. NCUA tailors requests to the scope and risk profile of the examination. Different lending activities, technology environments, and risk profiles can lead to different requests.

Can credit unions use MERIT to submit examination documents?

Yes. Authorised credit union users can respond to MERIT document request surveys and attach supporting documents. Follow the secure submission instructions provided by the examination team. 

What should a credit union do if requested examination evidence is missing?

Check whether the record exists in another authoritative system. If it remains unavailable, explain why and document any later testing with its actual date. If the gap reveals a control weakness, assign an owner and track corrective action. 

Are outstanding access review revocations automatically NCUA examination findings?

An outstanding revocation is an open access issue. Document the permission, associated risk, current status, and owner. Use formal examination communications to determine whether the issue was recorded as a finding or requires a supervisory response.

How should credit unions manage corrective actions after an NCUA examination?

Review the official report, assign owners and deadlines, and retain evidence that each corrective action addressed the concern. Where applicable, use MERIT to provide updates and coordinate follow-up. 

Make Examination Readiness Part of Routine Work

Keep policies, financial records, access reviews, and corrective action evidence current throughout the year. When the DRL arrives, teams can focus on validating the requested information and explaining open issues. After the examination, keep each required action visible until there is evidence that it addressed the underlying concern.