Bank reconciliation is the monthly close process that ties your GL cash balance to your bank statement. Bank Match is the tool that gets you there faster: matching rules and Bank Match AI pair bank feed transactions to GL entries so you spend your time on exceptions instead of every line.
How Bank Match runs depends on how your bank data arrives. With an aggregator-backed connection, matching happens continuously in the background. If you upload statements manually, you kick off Bank Match yourself after each upload, since there’s no live feed to trigger it automatically.
Where to start
Editing matched and reconciled transactions
You can edit non-financial fields on a bank-matched or reconciled transaction, such as its classifications or custom fields, without undoing the match or the reconciliation first. On a reconciled transaction, this requires the Allow modifications to paid or reconciled records setting, which is off by default, and your role must be one of the setting’s authorized roles. See General Preferences for how to turn it on.
On a reconciled transaction, fields with financial impact, such as accounts and amounts, stay locked. If you change one, DualEntry rejects the save, lists it after Fields that cannot be changed:, and tells you what to undo first. On a matched journal entry or intercompany journal entry that hasn’t been reconciled, changing the amount, date, or bank account unmatches it automatically. The save goes through, and the bank-feed transaction goes back to unmatched in Bank Match so you can match it again.
Period locks still apply. Once a transaction’s accounting period is locked, DualEntry blocks edits to it as usual. See Period locking for how locks work.
Last modified on October 8, 2026
