When two Spending transactions appear to represent the same activity, compare their account, source, date, amount, description, and import range before excluding either one. Kerdora does not automatically merge suspected duplicates; use Hide from spending to remove a confirmed duplicate from Spending analysis without deleting the source ledger record.
Why do duplicate Spending transactions appear?
Common causes include:
a statement import covering dates already received through account aggregation;
the same statement period being imported more than once;
an institution resending or changing a posted transaction;
two connected accounts representing different sides of a transfer; or
a credit-card payment appearing alongside the card purchases it paid.
Similar merchant names, dates, and amounts are evidence, but they do not prove two entries are duplicates.
How do I review a suspected duplicate?
Open the client and go to Spending → Transactions. Compare the two rows:
confirm the source account and account mask;
compare transaction and posting dates;
confirm amount and sign;
compare merchant and original description;
check the linked source or statement import period; and
decide whether one row is a transfer counterpart or card payment.
Use one authoritative source for each account and date range. If an imported statement overlaps a linked feed, keep the source that best supports an ongoing workflow and hide only the confirmed overlap.
How do I hide a duplicate from Spending?
On the transaction row, select Hide from spending. The row becomes muted and stops contributing to effective Spending analysis, cash-flow totals, and category results.
Hiding does not delete the transaction, change the institution, or stop future syncs. It preserves the source record so the decision can be reviewed.
To restore it, find the hidden row and select Show in spending.
How do I find hidden transactions?
Open the Spending transaction filters and use Visibility:
Visible only shows transactions included in Spending;
Hidden only shows excluded transactions; and
Visible and hidden shows both.
Use Hidden only when reviewing prior duplicate decisions or restoring a transaction.
Can I hide repeated duplicate patterns in bulk?
Yes, when the pattern can be described safely. Create a Spending rule with conditions that identify the source, account, merchant, description, or other available criteria, then set the rule's hidden action.
Preview which transactions the rule matches before saving. A broad rule can hide legitimate future activity. Rules change the effective category, merchant, hidden state, or tags without rewriting the underlying ledger transaction.
Is a transfer or credit-card payment a duplicate?
Usually not. Movement between household accounts can create a debit in one account and a credit in another. A credit-card payment can also appear beside the purchases it pays.
Classify internal movement as Transfer and use the purchase transactions for spending categories. Counting the card payment and the purchases as spending double-counts household outflow.
How do I prevent duplicate statement imports?
Record each import's account and start and end dates.
Check whether account aggregation already covers that range.
Import each statement period once.
Reconcile large totals against the statement after import.
Review overlaps before hiding anything.
If a repeatable duplicate pattern cannot be resolved, contact Kerdora Support with the household, source, account mask, date range, import filename, and example transactions. Do not send credentials or full account numbers.