If your finance team is in the middle of an ERP implementation and your bank reconciliation is no longer tying, the problem is rarely just the bank reconciliation itself.
After go-live, cash that used to reconcile cleanly can suddenly develop differences between the bank and general ledger. AP warrant clearing may not zero out. Utility billing activity may lag behind bank deposits. Cashiering activity may post to the general ledger differently than it did in the legacy system.
Those symptoms usually point to something upstream: conversion, configuration, change posting behavior, timing differences, or workflow changes. The key is to stop treating the issues as one large unexplained variance and start isolating where the break is occurring.
Common Warning Signs After Go-Live
A post-implementation bank reconciliation issue may be bigger than a normal monthly timing difference when:
- Different variances roll forward month to month
- Cash ties in total but does not tie by fund
- Outstanding checks, ACH items, or deposits in transit do not agree to the converted reconciliation detail
- AP warrant clearing, payroll clearing, or merchant settlement accounts carry unexplained balances
- Utility billing, permits, licenses, or cashiering receipts no longer tie cleanly to treasury deposits
- Staff are posting journal entries or suspense items just to get through the close
These issues are common during ERP stabilization. They are also fixable when the team follows a structured process.
Step 1: Rebuild the Cutover Baseline
Before reconciling the first month in the new system, have a solid starting point. The final reconciled cash – one that is fully, completely reconciled – from the legacy system should tie to the to the opening cash balance in the new system.
From this reconciled position you will have:
- Final legacy bank reconciliation support
- Converted general ledger cash balances
- Fund-level pooled cash balance or due to/from pooled cash balances
- Listings of outstanding checks, ACH items, wires, and deposits in transit at cutover
There are numerous strategies and planning activities to ease into the cutover, but with a focus on bank reconciliation, a common issue is that total cash converts correctly, but the reconciling items do not. When that happens, the reconciliation will continue to show unexplained variances month after month.
Step 2: Separate Timing Differences from True Errors
Not every reconciling item requires a journal entry. Classify each variance before correcting it:
- Timing difference clear in future periods.
- Conversion items created during migration or cutover and should be documented separately.
- Posting errors to the wrong fund, account, or source.
- Configuration issue with the ERP is consistently routing activity incorrectly.
- Workflow issues with departments or users are entering transactions inconsistently.
This distinction prevents the team from using cash plugs to solve issues that actually need configuration, training, or workflow correction.
Step 3: Reconcile by Source, Not All at Once
Instead of trying to reconcile entire bank account in one pass, break activity into major sources and tie each stream separately to the bank and general ledger.
The most useful streams to review are:
- AP warrant runs, voids, reissues, and warrant clearing
- Payroll direct deposits, retirement payments, and payroll liabilities
- Utility billing receipts, cashiering batches, merchant settlements, and bank deposits
- Permit, licenses, and fee deposits, particularly if they originate from separate systems
- ACH activity, wires, transfers, and investment activity
- Manual journal entries affective cash accounts, especially in more modern systems where only operational entries impact bank reconciliation processes
Most differences are concentrated in specific streams and once the variance is assigned to a source then the team can identify the corrective action quicker.
Step 4: Track Variances
On a related note, as part of post-go-live stabilization, variances should be tracked and updated with their resolution. This creates accountability and prevents the team from re-reviewing the same items each month, and also creates an audit trail for conversion cleanup decisions, configuration fixes, and temporary workarounds.
Step 5: Clean Up Clearing Accounts Before They Become Permanent
Clearing accounts are often where ERP implementation issues begin to accumulate first. Review them early and separately from the bank reconciliation itself.
Look for:
- Old conversion items that should have been cleared at go-live
- Transactions sitting in clearing accounts across multiple periods
- Duplicate or offsetting entries created during conversion
- Voids, reversals, or corrections that did not fully clear
- Temporary suspense accounts or manual workarounds that have become routine
If clearing accounts are not addressed early, the bank reconciliation may tie while the underlying cash process remains unreliable.
Step 6: Increase Visibility During Stabilization
During the first few months after go-live, a monthly review cycle is usually not enough. Temporary weekly review procedures can help identify issues before they build into larger monthly-end variances.
Weekly stabilization reviews should focus on high-risk and high-volume areas:
- Payroll and retirement disbursements
- Utility billing cash receipts and bank deposits
- Cashiering, permits, licenses, and merchant settlement activity and other deposits
- AP warrants, voids, stale checks, wires, ACH, and interfund transfers
The temporary review does not need to become a permanent activity. Its purpose is to stabilize the process, identify causes, and then return the team to a manageable monthly close.
Do Note Force the Reconciliation
One of the biggest mistakes a team can make is adjusting cash simply to make the reconciliation tie. A plug may close the month, but it does not close the issue.
Forced entries often create larger problems. If something does not reconcile, it is usually pointing to a real issue upstream. The correction should address the source of variance and issues with the conversion or configuration.
Getting Back on Track
When reconciliations stall after ERP go-live, the fastest path forward is usually a structured reset. That reset should result in an audit-ready workpaper package, a documented variance tracker, and clear ownership over any remaining cleanup items.
A practical reset usually includes:
- Checking the cutover cash in total and by fund to the previously reconciled balance
- Validating converted outstanding checks, deposits in transit, and other reconciling items
- Tying current-period bank activity to GL cash activity by source
- Isolate timing items from conversion issues, posting errors, and configuration problems
- Cleaning up clearing accounts and addressing any workflow causation
- Standardizing posting procedures across departments and systems
An experienced advisory team can help by bringing structure, outside perspective, and ERP and accounting experience to a process that often becomes difficult for internal staff to untangle while they are also trying to keep daily operations moving.
The Bottom Line
A struggling bank reconciliation after ERP go-live does not necessarily mean the implementation failed. More often, it means conversion, posting configuration, or workflow needs closer attention.
Once the issue is isolated and corrected at the source, the reconciliation process can stabilize and confidence in cash balances and monthly close can be restored.
If your finance team is spending more time explaining reconciliation differences than resolving them, it may be time to step back and rest the process. We help finance teams rebuild cash reconciliation baseline, isolate conversion and posting issues, and create a practical path back to a repeatable monthly close.
If your bank reconciliation has become harder after go-live, reach out. We can help you determine whether the issue is conversion, posting configuration, timing, or workflow, and map out the next steps to get the process back under control. Contact us today!
