Help › Bookkeeping

Review possible duplicates after connecting a bank

Open this in Talisk HQ

When you connect a bank feed, its transactions may overlap ones you already imported from a PDF or CSV. Talisk merges the clear-cut overlaps for you and puts anything it isn't sure about into a review queue:

  1. A banner on Ledger › Banking reads N possible duplicate transactions need review — click Review now (or go to Banking › Review).
  2. For each one, either click Adopt this row on the existing transaction it matches (Talisk merges the feed onto your row), or Keep both if they're genuinely different transactions.

Merging keeps a single, correct copy so a bank event is never counted twice. Reach for Keep both only when the two really are separate. The queue is empty until a connected feed overlaps your imported statements: most of the time you'll never see it.

Good to know: This queue only fills when an automatic bank feed overlaps statements you'd already imported and Talisk can't safely auto-merge: a fresh book shows nothing. Choosing "Keep both" is right only when they really are two separate transactions.