Bank Reconciliation Gap Finder (Statements → Mismatches → Fix List)
Pinpoint missing statements, feed breaks, and date/amount mismatches, then produce a step-by-step fix list aligned to platform workflows.
Prompt Overview
Featured AI Partner
Tips For You
- Confirm statement day cutoffs; mismatches often cross months. - Test exclusions on a small subset first. - Screenshot the reconciliation variance at each step.
From Operations TeamNexusAi TechnologyProblem It Solves
Stops endless reconciling attempts by identifying the root cause of mismatches and mapping them to correct system actions.
Root-Cause Library
Maps common mismatch patterns to proven fixes.
Reversible Steps
Prioritizes safe actions with backups before merge/exclude.
Variance Zeroing
Clear verification to confirm reconciliation success.
Client-Ready Output
Explains causes and fixes in plain language.
AI Prompt Instructions
Act as: A reconciliation specialist experienced in diagnosing bank feed and statement mismatches in small-business ledgers.
Why this task matters: Accurate cash positions, audit readiness, and tax filings depend on complete, matched bank data.
Important boundaries: Only use evidence provided; flag missing documents; recommend reversible steps first; align guidance to the named platform.
User inputs:
- Platform (QuickBooks or Xero)
- Bank name(s) and account type(s)
- Reconciliation status per month for last 6 months
- Known manual imports or third-party integrations
- Statement periods available vs. missing
Objectives:
1) Identify gaps and mismatches by month and account.
2) Explain likely cause (feed outage, duplicate import, date format shift, FX rounding).
3) Produce a clear Fix List with system navigation steps and validation tests.
Analysis workflow:
- Compare statement periods to ledger periods.
- Run a 3-way match: beginning balance, transactions, ending balance.
- Detect duplicate imports via identical date/amount/vendor clusters.
- Check for timezone/date parsing inconsistencies.
- Flag FX accounts with rounding variances and propose tolerance tests.
Required output format:
- Gaps Table: Month, Account, Missing Docs, Impact
- Root Cause Notes: Evidence, Hypothesis, Risk
- Fix List: Step, System, Why, Expected Result, Reversal Plan
- Verification: Exact reports to re-run and expected balances
Quality controls: Tie each fix to a specific system menu path; include before/after checkpoints; avoid irreversible merges without backup.
Final instruction: Deliver a platform-specific, client-facing Fix List that can be executed in under 2 hours for most single-account scenarios.
Expected Outcome
Gaps Table: May (Main Checking): Missing bank statement; Impact: cannot reconcile 27 lines. Root Cause: Stripe duplicate import 2024-05; Evidence: identical amounts/dates; Risk: overstated revenue. Fix List: 1) QuickBooks > Banking > For Review: filter Stripe, find duplicates, exclude batch; Expected: -27 lines. 2) Upload May statement PDF; Expected: start/end balances align. Verification: Re-run Reconciliation Report for May: variance = 0.
Implementation Journey
Diagnose with Claude
Paste reconciliation status, available statements, and notes about imports into Claude. Request a Gaps Table, Root Cause Notes, and a Fix List tailored to QuickBooks or Xero.
10-12 minutesExecute fixes in QuickBooks/Xero
Follow the Fix List in your accounting system: exclude duplicate bank lines, upload missing statements, and align opening/ending balances. Keep before/after counts to track progress.
30-40 minutesVerify zero variance
Run the Reconciliation Report for affected months. Compare balances to statement PDFs and ensure variance is zero. Save the report and screenshots in the client workpapers.
10-15 minutes