Preventing duplicates
Spendle blocks duplicate transactions automatically during import. In specific situations they can still occur.
How can duplicates occur?
Section titled “How can duplicates occur?”- Different formats combined. When the same account is imported both via CSV and via PSD2, the same transaction may arrive in a slightly different form or with a different booking date.
- Two PSD2 connections with the same account number. Check in the Import tab which accounts are linked to which connection. Does an account appear more than once? Uncheck it in one of the connections, or remove the duplicate connection.
- Incorrect counter account. Duplicate transactions with a reversed amount (positive ↔ negative) usually point to an incorrectly configured counter account — often caused by an action rule. Check the action rule and correct it.
- Changed transaction ID. Spendle uses the transaction ID from the bank or from GoCardless to recognise duplicates. If that ID changes at the source, an existing transaction is treated as new.
Tips to prevent duplicates
Section titled “Tips to prevent duplicates”- Use one format per account where possible.
- Avoid overlapping periods between different formats for the same account.
- Make sure an account appears only once across your PSD2 connections.
Finding duplicates after the fact
Section titled “Finding duplicates after the fact”Two filters are available on the Transactions tab to track down duplicates:
- Duplicates — a list of transactions that resemble each other.
- Source duplicates — a list of potential duplicates showing the source (CSV, Klarna or GoCardless) per row. Accessible via Filter in the top-right corner of the Transactions tab.
Click the logo circle to the left of a transaction to show the checkbox column, check the duplicates and choose Delete in the action menu. See also Remove duplicate transactions.