Correct a bank-feed journal entry
Fix a journal entry that came from a posted bank row by going back to the row, not the entry.
Why Not At The Entry
A journal entry created by posting a bank row is owned by that row. Correct it at the row, not at the entry.
The bank row and its entry have to stay consistent. Voiding the entry on its own would leave the row marked as posted with nothing behind it in the ledger, so the feed and the books would disagree.
Manual journal entries your firm created by hand are different — those are voided from the entry itself, with a reason recorded. That path does not apply here.
Correct It At The Source
- Note the entry's date, amount, and account.
- Open the company's Bank Feeds and select Posted.
- Find the matching bank row and open it.
- Use Undo.
The posting is removed from balances and the row returns to Ready with its coding intact. Recode it and post it again. See Undo a posted bank transaction.
Fix The Cause Too
If the original posting came from a bank rule, undoing the entry does not stop it happening again — the rule is still active and still posts matching rows. Check the row's source label first. See Review what posted and who posted it and Stop an overbroad bank rule.
Transfers And Pairs
An entry created by recording a transfer covers both sides. Correcting it affects both bank rows — check both registers afterwards. See Code an internal transfer.
When Undo Is Blocked
Undo can be unavailable when the period is locked or the transaction has been reconciled. Do not work around it with an offsetting journal entry — that leaves two wrong records instead of one.
Create a support ticket with the company, bank account, entry number, transaction date, amount, and what the correct treatment should be.
For a wide accidental set, see Reverse an accidental posting batch.