Exclude a bank transaction

When Excluding Is Correct

Excluding takes a bank row out of the coding queue without creating any ledger activity. The row stays visible and can be restored.

• The transaction is already in the books from an import or manual entry, and the feed row duplicates it.
• The row belongs to a period before the company's LedgerHQ cutoff.
• The bank reversed the transaction and both sides are noise.
• The activity belongs to a different entity and never will be this company's.

When Excluding Is Wrong

Never exclude a row because you are unsure how to code it, because it has a warning, or to make the queue look finished. Excluding is a statement that the transaction does not belong in these books. If you cannot explain it, leave it and ask.

Exclude The Row

1. Open the company, select Bank Feeds, and open the account.
2. Open the row's menu and choose Exclude.

To exclude several at once, check the rows and use Exclude selected in the selection bar. LedgerHQ reports Excluded n of m.

Verify And Restore

Excluded rows move to the Excluded bucket. They are skipped by every posting action, are not reconciliation candidates, and are not treated as evidence by Tally.

If you excluded the wrong row, open it in the Excluded bucket and choose Restore. It returns to the normal queue with its coding intact.

Effect On Reconciliation

An excluded row will not clear on a bank statement, because it never became ledger activity. If a statement line has no matching transaction, check the Excluded bucket before booking a discrepancy. See Investigate a reconciliation difference.

Excluding is also how you resolve a genuine duplicate flagged by a warning — see Resolve a bank-feed warning.