Troubleshooting Bank Reconciliation
Bank, credit card, deposit, and reconciliation troubleshooting calls, including prior-period breaks, missing/duplicate transactions, wrong-account postings, reversals, and file research.
🔎 Keyword Search
📚 Converted Guide Sections
1How to Use This Guide
How to Use This Guide
This guide is designed as an internal playbook for bank reconciliation troubleshooting calls. It is meant to give reps a repeatable way to separate a current-month mismatch from a prior-period problem, trace deposits and reversals correctly, test safely, and know when file research or escalation is required.
| Core principle | Do not jump straight to a journal entry. Most bank rec cases come from a prior reconciliation already being off, a wrong-account posting, a deposit still in Undeposited Funds or duplicated, a closed-year reversal, or a transaction that was changed, deleted, or recreated. |
|---|
| What this guide covers | Why it matters for bank rec cases |
|---|---|
| Bank rec discovery and call control | Most cases sound like “the numbers don’t match,” but the real issue could be the dates, transaction history, or the wrong account. |
| Question phase and evidence gathering | The rep needs the exact statement date, ending balance, account name, and missing or duplicate transaction examples before testing anything. |
| Troubleshooting/testing workflow | Every bank rec case needs isolation: current period or prior period, missing or duplicate item, wrong account, reversal timing, or file-specific behavior. |
| Real CRM case patterns | The case section shows how reps resolved duplicate deposits, wrong-account deposits, prior-year reversals, and report/window mismatches. |
2Table of Contents
3Support Mindset for Bank Reconciliation Calls
1. Support Mindset for Bank Reconciliation Calls
Bank reconciliation support is different from general how-to support because customers are often looking at the symptom instead of the break point. The goal is not to prove the customer wrong; the goal is to prove which transaction trail AccountEdge is actually reading from. Remember, that we cannot look at every single transaction to see where they went wrong, its our role to give the customer the tools to understand how to search for their issue. Sometimes you may find the issue during your call but other times, you may need to cut the call after a certain amount of time has been spent trying to find the issue – when ending such calls, it is important to not abruptly disconnect, but to leave the customer with some knowledge and an FAQ for reference.
What reps must assume at the start
| Assumption | What the rep should do |
|---|---|
| The customer may be right that the balance is wrong. | Ask for the exact account, statement date, ending balance, and sample transactions before testing. |
| The cause may be in a prior month. | First prove whether the previous reconciliation was already out of balance. |
| A “missing” item may be in the wrong bank account or still in Undeposited Funds. | Trace the source transaction path: Receive Payment, Prepare Bank Deposit, Spend Money, check, or GJ. |
Few things that reps should not do during applicable scenarios
Do not suggest a General Journal just because the reconciliation is out of balance.
Do not tell the customer to delete a deposit or check blindly before checking downstream links.
Do not promise that a reversal can be dated back into a closed fiscal year.
Do not assume a transaction is missing when it may be sitting in Prepare Bank Deposit or another bank account.
Rep coaching point
“Let’s first prove whether the break started this month or earlier, then we’ll trace the transaction path before we decide whether this is a wrong-account issue, a reversal issue, a duplicate deposit, or something file-specific.”
4The Four-Phase Bank Reconciliation Investigation Framework
2. The Four-Phase Bank Reconciliation Investigation Framework
All bank reconciliation cases should move in this order: Discovery, Question Phase, Troubleshooting/Testing, and Implement Solution.
| Phase | Goal | Rep actions | Exit criteria |
|---|---|---|---|
| 1. Discovery | Understand exactly what the customer sees. | Get the account, statement date, statement balance, out-of-balance amount, and one or two example transactions. | Rep can restate the issue in one sentence. |
| 2. Question | Narrow the likely causes. | Ask whether the current month looks right, whether prior months were reconciled, and whether transactions were reversed, changed, deleted, or deposited elsewhere. | Rep has a short list of likely causes. |
| 3. Test | Prove the break point. | Use Reconcile Accounts, Bank Register, Prepare Bank Deposit, and the Reconciliation Report. Test one variable at a time. | Rep can show why the item is missing, duplicated, or unreconciled. |
| 4. Implement | Apply the confirmed fix. | Undo/redo reconciliation, reverse or redeposit correctly, re-enter a deleted item, or escalate with evidence. | Customer sees the corrected result or next step. |
5Bank Reconciliation Baseline Discovery Checklist
3. Bank Reconciliation Baseline Discovery Checklist
Use this checklist before changing anything in a live file.
| Checklist area | Rep should verify | Red flag |
|---|---|---|
| Account | Exact bank or credit card account. | The customer is reconciling the wrong account or a clearing account. |
| Statement date / balance | Closing date and ending balance from the statement. | Wrong date, wrong balance, or future-dated entries causing confusion. |
| Prior successful reconciliation | Whether the immediately prior statement is truly in balance. | The customer is troubleshooting this month while an earlier month was already broken. |
| Transaction source path | Whether the item came from Receive Payment, Prepare Bank Deposit, Spend Money, a check, or a GJ. | The customer is searching in the wrong window. |
| Repair / conversion history | Whether the file was repaired, converted, or transactions were recreated manually. | Duplicate or recreated entries may exist. |
6Fast Triage Matrix: Symptoms, Causes, and First Checks
4. Fast Triage Matrix: Symptoms, Causes, and First Checks
| Customer symptom | Likely causes | First checks |
|---|---|---|
| Out of balance, but current month seems correct | Previous reconciliation already out of balance. | Enter the last successful statement date and balance, mark nothing, and see if the account is already out. |
| Transactions appear on the report but not in Reconcile Accounts | Changed/deleted transaction history or clear-state issue. | Run the Reconciliation Report by recorded statement date and consider undo/redo. |
| Payments are missing in the reconcile window | Deposited to the wrong bank account or still in Undeposited Funds. | Trace the payment to Prepare Bank Deposit and verify the target account. |
| Same payment seems deposited twice | Duplicate deposit or manual re-entry after repair. | Trace the original receipt and each deposit before using a GJ. |
| Prior-year reversal is behaving differently than expected | Closed fiscal year restrictions. | Explain that the reversal belongs in the current fiscal year by design. |
7Deep-Dive Modules: How to Troubleshoot Bank Reconciliation Issues
5. Deep-Dive Modules: How to Troubleshoot Bank Reconciliation Issues
Module A – Standard Bank Reconciliation Flow and Key Windows
Banking > Reconcile Accounts: use this for the live match process and to test whether the previous reconciliation is already out of balance.
Banking > Bank Register: use this to see whether the transaction exists, what date it uses, and which account it hit.
Banking > Prepare Bank Deposit: use this when a payment was grouped with Undeposited Funds before being deposited.
Reports > Index to Reports > Banking > Reconciliation Report: use this to find the month where the issue started.
Module B – Out of Balance: Prove Previous vs Current
Open Banking > Reconcile Accounts.
Enter the ending balance from the last successfully reconciled statement and enter that statement date.
Do not check off any transactions.
If the account is already out of balance, the issue began before the current month.
Then run the Reconciliation Report for prior recorded statement dates and review where the break started.
Module C – Missing Transactions, Wrong Bank Account, and Prepare Bank Deposit
If a payment was received into Undeposited Funds, it will not appear in the target bank account until a bank deposit is recorded.
If it was deposited to the wrong account, delete or reverse that deposit first so the receipt returns to Prepare Bank Deposit, then redeposit it to the correct account.
This is what resolved the Angelic Templeton case: the payments were not missing; they were in the wrong bank account.
Module D – Reversals, Closed Fiscal Years, and Undo Reconciliation
Do not promise that a prior-year check or deposit can be deleted or reversed inside the closed fiscal year.
If a reversal is needed, it must be recorded in the current fiscal year by design.
If the customer reconciled the wrong month or wrong items, create a backup and use Banking > Reconcile Accounts > Undo Reconciliation.
Module E – Duplicate Deposits, Repairs, and File Research
Trace the path: original Receive Payment or Receive Money, each Bank Deposit entry, and the bank account(s) affected.
If the file was repaired or activity was recreated manually, compare the returned file history against the recreated activity.
In the Krista Ales case, the fix was to reverse the manually created deposit, then deposit that reversal into Undeposited Funds so the negative could clear the positive in reconciliation.
8Real-World Case Library and Coaching Notes
6. Real-World Case Library and Coaching Notes
| Case | Issue | Resolution / outcome | Coaching note |
|---|---|---|---|
| SCA2606073 | Same payment appeared in two deposits after repair and manual re-entry. | Reverse the manually created deposit, then deposit the reversal into Undeposited Funds so the negative clears the positive. | Trace the source payment and deposit trail first. |
| SCA2601269 | Customer reconciled the wrong items and wanted to undo. | Create a backup and use Banking > Reconcile Accounts > Undo Reconciliation. | Earlier months must be unreconciled sequentially. |
| SCA2514302 | Payments from the statement were missing. | They had been deposited to the investors account instead of the operations account. | Missing does not always mean absent. |
| SCA2514396 | Items showed on the report but not in Reconcile Accounts. | Support advised undoing and redoing the reconciliation and using the clearing-transactions FAQ. | Report history and current-window state can drift. |
| SCA2602809 | Customer reversed a 2023 transaction while reconciling FY2025. | Explained that closed-year items cannot be changed and the reversal belongs in the current fiscal year. | Do not promise same-period cleanup in a closed year. |
9Escalation Standards and Supervisor Hand-Off Format
7. Escalation Standards and Supervisor Hand-Off Format
A good escalation lets a senior reproduce the issue quickly.
| Hand-off field | Required detail |
|---|---|
| Customer / case | Customer name, case ID, product/build, account, statement date, and statement balance. |
| Issue statement | One sentence describing the exact mismatch. |
| Expected vs actual | What should clear and what AccountEdge is actually showing. |
| What was checked | Previous reconciliation test, bank register, source transaction type, target bank account, and any repair/conversion history. |
| Requested help | Confirm deposit trail, verify prior-period break point, approve workaround, or request file research. |
Escalate when the rep cannot safely explain the mismatch after proving previous vs current reconciliation and tracing the transaction path.
10Customer Communication Scripts
8. Customer Communication Scripts
Opening a bank rec troubleshooting call
“Let’s first prove whether the break started this month or earlier, then we’ll trace the transaction path before we force a fix.”
When the customer wants a quick journal entry
“A journal entry may clear the month, but before we do that I want to make sure we are not hiding a duplicate deposit or wrong-account posting.”
When the issue is a wrong-account deposit
“The payment is not missing from AccountEdge; it was deposited to a different bank account.”
11Source Notes and KB Reference Links
9. Source Notes and KB Reference Links
This guide was created using CRM case data, public AccountEdge Knowledge Base resources, and established internal support knowledge.
Bank Reconciliation Process: https://accountedge.helpjuice.com/en_US/banking_2/bank-reconciliation-process
Bank Reconciliation Out of Balance: https://accountedge.helpjuice.com/en_US/banking_2/bank-reconciliation-out-of-balance
Undo Bank Reconciliation: https://accountedge.helpjuice.com/en_US/banking_2/undo-bank-reconciliation
Clearing Transactions from the Reconcile Accounts Window: https://accountedge.helpjuice.com/en_US/banking_2/clearing-transactions-from-the-reconcile-accounts-window
Prepare Bank Deposit: https://accountedge.helpjuice.com/en_US/how-to/prepare-bank-deposit
Initial Bank Reconciliation: https://accountedge.helpjuice.com/en_US/getting-started/initial-bank-reconciliation
Calculated Statement Balance & Balance Sheet Don’t Match: https://accountedge.helpjuice.com/en_US/banking_2/calculated-statement-balance-balance-sheet-dont-match
AccountEdge Knowledge Base: https://accountedge.helpjuice.com
AccountEdge Help Viewer: https://help.accountedge.com/us/help/helpviewer.html
🧭 Best Path / Rep Call Flow
- Discovery: identify exactly what the customer sees, where they see it, and the date/report/window involved.
- Question phase: narrow whether this is setup, transaction history, workflow, reporting, or file-specific behavior.
- Troubleshooting/testing: test one variable at a time, use safe non-posting evidence first, and avoid irreversible changes.
- Implement or escalate: apply the confirmed fix, verify the result, or hand off with clear evidence.