Review possible duplicates after connecting a bank

When you connect a bank feed, its transactions may overlap ones you already imported from a PDF or CSV. TALISK_HQ 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_HQ 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.

When the dates are a few days apart

Card statements print the date you paid. A bank feed reports the date the charge settled, which is often two or three days later. So the same charge can appear twice with the same amount but different dates.

TALISK_HQ merges these only when the dates are within a couple of days of each other. Past that it stops guessing and shows you the pair, headed Possible duplicate, a few days apart. Use Adopt this row if it is the same charge, or Keep both if you really were charged the same amount twice that week.

Both transactions stay in your books either way, so nothing is lost while the review is waiting for you. The one thing worth doing promptly is deciding before you categorize them: coding both copies would count the expense twice.

When your bank drops a transaction

A bank feed can also withdraw a transaction it sent earlier. Usually that is routine: a pending charge is replaced by the posted version a day or two later, and TALISK_HQ swaps them over without telling you, because there is nothing to decide.

Sometimes there is no replacement, and the charge really happened. Feeds do drop real transactions. TALISK_HQ keeps the line, and it decides for itself whenever it already holds the evidence:

• If you had matched, categorized or reconciled the line, your own work vouches for it, so the line simply stays. Nothing to answer.
• If the line also came in on a statement you imported, the statement vouches for it, so it stays too.
• TALISK_HQ also asks the bank feed a second time, a different way. If the feed still shows the transaction when asked directly, the withdrawal was a feed error and the line stays.

You only see a card for the one case TALISK_HQ genuinely cannot decide: Your bank dropped a transaction and sent nothing to replace it, on a line nothing in your books had claimed yet. Check it against your online banking. If the charge is real, click Keep it; if it never happened, click Remove it to take the line out of your books.

TALISK_HQ never deletes a dropped line on its own unless the replacement arrived with it. A charge quietly disappearing is much harder to notice than one sitting there waiting for an answer.