Bank feed posts the same transactions twice in the package.
Duplicate transactions usually come from a feed reconnect after an incident, a manual import that overlaps, or two links on the same account. The fix is deduplication on transaction reference.
Try this first
- 1Sort the bank journal by date and amount, duplicate pairs usually jump out.
- 2Compare the transaction reference or end-to-end id, two entries with the same reference are duplicates.
- 3Remove duplicates in a staging step, not directly on already-matched rows, or your reconciliation breaks.
- 4Check whether two active bank links exist on the same IBAN (for example an old Klippa feed plus a new direct link) and disable the old one.
- 5Turn on import checks for batch uploads so the package warns on overlap.
When to bring us in
For hundreds of duplicates across a long period we can write a dedup script against the transaction id.
See also
- Switching from Exact Online to Yuki, open items and history do not matchPackage migrations stumble on ledger mapping and open AR/AP. Without a mapping table you lose context.
- Twinfield to Exact, dimensions and cost centres go missingTwinfield uses dimensions, Exact uses cost centres and projects. The mapping is not one-to-one.
- Accountant asks for RGS mapping, your ledger does not follow RGSRGS is the Dutch standard chart that SBR filings and accountant software expect. Without mapping, every year-end is manual.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.