In Planning → Spending → Transactions, compare suspected duplicates with source records before excluding either entry. Hide a confirmed extra entry to remove it from Spending summaries while preserving its transaction record. Similar dates, merchants, and amounts alone don't prove duplication.
Why do duplicate Spending transactions appear?
Spending can contain overlapping activity when a statement covers dates already received from a linked account, or when the same file is approved in separate import proposals. Don't assume those sources automatically merge into one entry.
Two entries can also represent different transactions: repeated purchases for the same amount, the two sides of a transfer, or a card payment alongside the purchases it paid. Those need different treatment from an accidental second import.
Start with the account and source period. Check the original statement or export and the Dora import conversation where relevant. A connection issue belongs in Troubleshooting Linked Accounts; creating another connection or account isn't a duplicate-transaction cleanup step.
How do I review a suspected duplicate?
In Spending's Transactions tab, narrow the review to the relevant account and dates, then compare each suspect entry with its source.
Open the sliders icon with the Filter transactions tooltip and choose Account and Date range.
Open each transaction and compare its account, displayed date, amount and sign, merchant, and Statement description.
Check the statement, export, or import conversation for the account ending and source period. Don't assume every source detail is displayed in transaction details.
Establish whether both entries represent the same real activity or separate movements.
A debit and credit across different accounts may be transfer counterparts. If the source history doesn't make the answer clear, contact Kerdora Support with both examples before hiding one. Retain source files so the decision can be checked later.
How do I exclude a confirmed duplicate?
In Spending transaction details, the eye control can hide a confirmed extra entry from Spending’s Cash flow and Analyze tabs, the Actual cash flow statement in Financials, and a Guide’s Income Statement. Advisors and clients use the same household transaction record.
An advisor opens the confirmed duplicate in Planning → Spending → Transactions; a client uses Spending → Transactions.
Select the eye control whose tooltip says “Visible in spending — tap to hide.”
Check for Hidden from spending, then review the affected Cash flow total.
Hiding saves immediately. It doesn't delete the source transaction, disconnect an institution, or change an account balance. It also doesn't automatically change the household spending assumption in Profile.
Hidden entries stay in the default Transactions list, marked Hidden, for advisors and clients. Use hiding to correct Spending inclusion, not to make an entry private.
Kerdora has no Delete or Undo control for imported transactions. For an entire overlapping file import, contact Kerdora Support with the household, account ending, dates, and filenames; don’t assume bulk removal is available.
How do I find or restore a hidden transaction?
Spending’s Transactions tab includes hidden entries by default; use Visibility to narrow the list to hidden entries. Restoring a manually hidden transaction clears that manual choice; a matching hiding rule can still keep it hidden.
Open the sliders filter button.
Choose Visibility → Hidden only to list excluded entries. The default, Visible and hidden, shows both.
Open the transaction and select the eye control whose tooltip says “Hidden from spending — tap to show.”
Check whether the hidden indicator disappears and the appropriate Cash flow total changes.
If the entry stays hidden, inspect Spending Rules rather than repeatedly pressing the eye. Spending Rules: Automatically Categorize Transactions in Bulk explains how to edit or delete the rule. Deleting a rule can affect other matching entries, so check its scope first.
Can a rule safely hide every duplicate?
Spending rules can hide transactions matching supported conditions, but they don't determine which of two matching copies is the duplicate. The editor has no source-file or import-batch condition.
If both copies have the same account, description, amount, and date, a rule based on those fields can hide both. A broad merchant rule can also hide legitimate future purchases.
Use individual hiding for isolated confirmed duplicates; ask Support to investigate a whole overlapping import. Kerdora has no bulk import-removal control.
When unwanted activity has a distinct, verifiable pattern, see Spending Rules: Automatically Categorize Transactions in Bulk for creating and previewing a rule. Its preview reports matches, not proof that they are duplicate entries. Check actual Spending totals after any rule change.
Is a transfer or credit-card payment a duplicate?
In Spending, movement between household accounts can produce a withdrawal from one account and a deposit into another. A card payment can appear separately from the purchases it pays. Those entries can all be valid source records.
Use a category in a Transfer group for internal movement that should stay separate from inflows and outflows. Keep the underlying card purchases in their appropriate spending categories; counting both purchases and their payment as outflows can overstate spending.
Categorizing and Filtering Transactions explains category corrections. Check the actual purpose of debt-related activity before classifying it: an interest charge, fee, loan payment, and movement between accounts aren't automatically the same thing.
Profile debt payments remain a separate planning input. Changing a transaction category doesn't remove that debt record or its payment from Profile.
How do I prevent overlapping imports?
Before approving a Dora transaction import, compare its account and dates with existing Spending history. Keep a record of imported filenames and periods so you can identify overlap later.
Check Planning → Spending → Transactions for the account and period you intend to import.
Compare the proposed count and totals with the source file before selecting Import.
Wait for the existing import's result and reconcile it before submitting another portion.
Use non-overlapping periods when splitting a long history.
Importing Transactions from a Bank or Credit Card Statement covers proposal review and processing failures. If duplication keeps recurring, send Support the household, account ending, dates, filenames, and example amounts/descriptions. Don't send passwords or full account numbers. Leave uncertain records in place while their source is investigated.
