Preparing for Your Next NCUA Exam: What Your GL Should (and Shouldn’t) Look Like

Every credit union accounting team knows the rhythm of exam season. The request list arrives, the general ledger gets a fresh look, and the questions start. Will the suspense accounts hold up. Are the reconciliations current. Can we explain that one adjusting entry from March. The exam itself rarely turns on a single number. It turns on whether your records tell a consistent, defensible story when an examiner pulls the thread.

NCUA examinations are risk-focused, and that has a practical consequence for your GL. When accounting controls are sound and records follow GAAP, examiners are not required to verify every general ledger account, and the scope of the review can stay narrow. When they find weaknesses in accounting routines or controls, the examiner in charge can expand the review and start verifying accounts. So the condition of your GL does not just affect findings. It shapes how deep the exam goes.

Strong NCUA exam preparation is less about the weeks before the request list and more about the general ledger you keep all year. An examiner reads that ledger as a record of how the institution actually runs: what gets recorded, whether it reconciles, and whether anyone can stand behind it. A clean chart of accounts, documentation that lives with the entry, and an audit trail no one can quietly rewrite are what hold up under that kind of scrutiny.

What does an NCUA examiner actually look for in your general ledger?

An examiner is testing three things: that entries are proper and supported, that subsidiary ledgers reconcile to the GL, and that the numbers feeding your Call Report trace back to source.

The General Ledger chapter of the NCUA Examiner’s Guide frames the review around internal controls, the propriety of entries, and out-of-balance conditions. Examiners verify that staff balance each general ledger account against its supporting subsidiary ledger. When a material out-of-balance condition exists between a subsidiary ledger and the GL, the examiner records adjusting entries so that examination trends and ratios are not distorted. That is the part worth sitting with. An unreconciled difference does not just create a finding. It changes the numbers the examiner uses to rate you.

Call Report accuracy sits on the same foundation. Examiners trace the statement of financial condition and the income statement to source documentation, and they reconcile loans and shares to the share and loan download. If your GL is the clean source those numbers come from, the review is short. If it is not, the questions multiply.

What should a clean credit union chart of accounts look like?

A clean chart maps cleanly to the 5300 Call Report account structure, groups related accounts in logical sequence, captures detail through segments rather than account sprawl, and ties one-to-one with your core.

Mapped to the regulatory framework. Your natural accounts should map cleanly to the 5300 Call Report account structure, so the figures that feed it trace without manual gymnastics. Teams that prepare the Call Report by hand on the NCUA site know the cost of a chart that does not align. Every cycle becomes a reconstruction. A chart built to match that structure turns the work into a mapping you set once.

Granularity through structure, not sprawl. The instinct to add an account every time you need to see something differently is how a 400-line chart becomes a 4,000-line chart. The better pattern is a segmented account structure: a natural account that ties to the regulatory framework, plus segments for product, collateral type, secured versus unsecured, and branch where it matters operationally. Picture interest income on a single loan type, broken out by new versus used, secured versus unsecured, and direct versus indirect, without creating dozens of standalone GL accounts. You get the reporting dimensions without the maintenance burden.

Logical, contiguous grouping. Clearing and suspense accounts are where this shows up fastest. When related accounts, say your card settlement and overnight cash clearing accounts, drift out of sequence over the years, month-end reconciliation gets slower and more error-prone. Keeping related accounts contiguous under a shared prefix is unglamorous and pays off every close.

One-to-one with the core. Whatever structure you choose, it should map directly to the accounts your core already feeds. A chart that requires splitting or reclassifying transactions on import is a chart that will eventually break a feed. Preserve the one-to-one mapping and let a lookup translate core codes into your reporting structure.

Names a stranger can read. Concatenated, descriptive account names that combine product, loan type, and income or expense category make manual validation faster and make misclassifications easier to catch before they reach a report. An examiner should not need a decoder ring, and neither should a new hire.

What should your chart of accounts not look like?

Examiners notice the same handful of patterns: accounts that never clear, accounts no one owns, duplicates, dead accounts left active, and catch-alls hiding activity.

• Suspense and clearing accounts that age indefinitely. A suspense account is a temporary home, not a parking lot. Items that sit for months, or an ACH clearing account that eats hours of daily reconciliation and still does not zero out, are exactly what an expanded review looks for.
• Dormant accounts left active. Old depreciation accounts, retired marketing GLs, accounts tied to a product you sunset two years ago. If it has no current activity and no purpose, deactivate it. Active dead accounts invite questions and clutter every report.
• Duplicates and near-duplicates. Two accounts that mean almost the same thing guarantee inconsistent coding. Pick one, map the other, move on.
• “Miscellaneous” and “Other” as a habit. A catch-all that grows month over month is where examiners expect to find misclassified activity. Use it sparingly and clear it deliberately.
• Sign and classification confusion. Accounts reclassified between asset and liability categories, or sign conventions applied inconsistently, create reconciliation noise. A well-built ledger stores transaction values by the nature of the transaction, so debits and credits keep their natural signs and a whole class of cleanup disappears.
• Accounts without an owner. Every account should have someone who can explain what it is for and who reconciles it. “I’m not sure who handles that one” is not an answer you want to give on site.

What documentation standards do examiners expect?

Every nonroutine entry needs support and an approver, every subsidiary ledger needs a current reconciliation, and the close itself needs a repeatable, evidenced process.

Adjusting and nonroutine entries. These draw the most attention because they are where judgment lives. Each should carry its supporting documentation, the rationale, and the approver. Arbitrary adjustments and out-of-balance ledgers are concerns the Examiner’s Guide specifically addresses, and they are easy to avoid with a habit of attaching support at the time of entry rather than reconstructing it later.

Subsidiary reconciliations. Examiners verify that each GL account balances to its supporting subledger. The reconciliation should be current, documented, and reviewed by someone other than the preparer. The same applies to bank reconcilements. An unreconciled difference there is a common reason an examiner expands scope into the broader GL.

The close as a documented process. A close checklist, with sign-offs and dates, turns “we know what we do” into “here is what we did.” It also makes the soft close versus hard close distinction real. You want the ability to make corrections in an open period and then lock the period so prior numbers cannot quietly change.

Fixed assets and accruals. Board-approved policy for fixed asset purchases, depreciation schedules set up at acquisition, and accrued dividends recorded in the right liability account are all specific items the Examiner’s Guide calls out. Documentation here is mostly about showing the policy exists and was followed.

Why does audit trail integrity matter more than anything else?

Because it is the one thing you cannot reconstruct after the fact. A chart can be tidied and a reconciliation can be caught up, but a missing or editable history cannot be recreated honestly.

An audit trail answers four questions for every transaction: who entered it, when, who approved it, and what supported it. The integrity of that record is what lets an examiner trust the rest of your books without testing every line. A few principles hold up under scrutiny.

• Posted entries get reversed, not deleted. Once an entry posts, the correct fix is a reversing entry, not an edit or a delete. The original stays visible, the correction stays visible, and the story stays complete. A ledger that lets you quietly delete posted activity is a ledger an examiner cannot fully trust.
• No back doors. When something breaks, the temptation is to bypass the workflow and force a fix. The disciplined approach is to correct through the normal path, even when that means re-entering work, so the audit trail stays intact. A bypass saves an hour and costs you the one thing the exam depends on.
• Segregation of duties, enforced by the system. The person who creates an entry should not be the only person who approves it. Multi-level approval workflows, with access scoped to a person’s function, turn segregation of duties from a policy on paper into something the system can enforce on every transaction.
• Access tied to role. Account-level and function-level security means people touch only what their job requires, which is both a control and a smaller surface for error.

A pre-exam GL checklist

Run this before the request list arrives, not after.

1. Reconcile every subsidiary ledger to the GL, and confirm a reviewer other than the preparer signed off.
2. Reconcile loans and shares to the most recent share and loan download.
3. Age your suspense and clearing accounts. Clear or explain anything outstanding.
4. Confirm the Call Report figures trace to GL source, with charge-offs, recoveries, and provision expense documented.
5. Deactivate dormant accounts and resolve duplicates.
6. Pull the adjusting entries for the period and confirm each has support, rationale, and an approver.
7. Verify the close checklist is complete with dates and sign-offs, and that closed periods are locked.
8. Confirm account ownership. Every account has someone who can explain and reconcile it.
9. Spot-check the audit trail. Pick a few entries and confirm you can see who posted, who approved, and what supported them.

Where the system earns its keep

Good discipline carries most of the load, but the right ledger makes the clean path the easy path.

Most of what we have described is process. A general ledger built for credit unions does not replace that process, but it can make exam readiness the default rather than a project. The features that matter here are not exotic.

• Dynamic account groupings that update across every report at once, so a chart change does not mean editing twenty report definitions by hand.
• A report audit that flags missing or duplicated GL accounts before a report goes out, catching the gaps examiners otherwise find.
• Journal entry templates with automatic numbering and balance validation, so entries are consistent and self-checking.
• Multi-level approval workflows with access scoped by function, so segregation of duties can be enforced on every entry.
• Posted entries that reverse rather than delete, preserving the audit trail by design.
• A soft and hard close, so you can correct an open period and lock a closed one.
• Drill-through from a report figure to the underlying transactions, plus ad hoc analysis directly on live GL data, so answering an examiner’s question takes a click, not an export.
• A scheduled data feed from your core, so the GL stays the reconciled source the Call Report draws from.

This is the work Flexi has done alongside credit unions for years. The kind of ledger structure, controls, and reporting that hold up when an examiner pulls the thread. None of it replaces a disciplined close. It just means the discipline lives in the tools instead of in a binder.

Frequently asked questions

How far back do NCUA examiners review general ledger activity?

It depends on risk and scope. Under a low-risk assessment with adequate controls, examiners are not required to verify every GL account. If they identify weaknesses in accounting routines or controls, the examiner in charge can expand the review and verify accounts where warranted.

How long can items stay in a suspense or clearing account?

There is no single rule, but the expectation is that suspense and clearing accounts are temporary. Items that age for months without resolution, or clearing accounts that never zero out, are common triggers for a closer look. Age and clear them as part of every close.

What is the most common GL issue that affects Call Report accuracy?

Misstating charge-offs, recoveries, or provision expense is a frequent one. Tracing each Call Report figure back to documented GL source is the fix.

Should we correct a posted journal entry by editing it?

No. Once an entry is posted, correct it with a reversing entry so both the original and the correction stay visible. Editing or deleting posted activity breaks the audit trail and undermines the integrity examiners rely on.

Does aligning our chart of accounts to the NCUA framework automate the 5300 Call Report?

It does not file the report for you, but it removes most of the manual reconstruction. When your natural accounts map to the 5300 Call Report account structure, the figures that feed it trace cleanly from the GL, which is where both accuracy and speed come from.

The real test is the other 51 weeks

A clean general ledger is not really about the exam. The exam is just the week someone outside your institution checks the thing your team should be able to vouch for on any given day: that the numbers are real, that they reconcile, and that every entry traces to a person and a reason. Get that right and the rest follows. The chart maps to the framework, the support sits with the entry, and the audit trail cannot be quietly rewritten, so the examiner ends up confirming what you already know rather than discovering what you missed.

The credit unions that find exams uneventful are not the ones with the most elaborate chart of accounts. They are the ones whose books tell the same honest story in March that they tell during exam week. That consistency is also what your board, your auditors, and your members are trusting every time they read a number you produced. Build the ledger that holds up to a stranger’s scrutiny, and the exam stops being something you brace for. It becomes a snapshot of how you already work.