Seeing the same transaction twice on your Ledger? Duplicates inflate your income or expenses and keep your accounts from reconciling. Many duplicates have a quick fix you can do yourself. Others are better handled by our team. This article helps you figure out which kind you have.
How duplicates happen
A CSV import overlaps dates your bank connection already covers. For example, you connect your checking account, which pulls in recent history, then import a CSV for the whole year.
The same CSV was imported twice, or two files had overlapping dates.
A manual transaction that later synced from your bank too. For example, a cash entry or one created from a receipt.
A transfer was entered by hand while the other account is also connected. Ambrook adds the matching side of the transfer to the other account, and then your bank brings in the real deposit as well.
The same bank account is connected more than once. This can happen after reconnecting a bank, or when a second team member connects the same account.
Step 1: Find the duplicates
Go to your Ledger and click Filter.
Set a Date range around the problem. Leave Account set to all accounts for now.
Look for pairs with the same date, amount and description.
Step 2: Are they in one account, or two?
This is the most important question, because the fix is different.
Both copies are on the same account. The duplicate came from an import, a manual entry or a transfer. You can usually fix it yourself. Continue to Step 3.
Each copy is on a different account, and the two accounts are really the same bank account (for example, “Farm Checking” and “Farm Checking ••1234,” or two accounts on your Accounts page with matching balances). The account is probably connected/added twice. Skip to When the same account is connected twice below.
Step 3: Check the source of each copy
Open each transaction copy and scroll to the bottom to find the Source of the transaction:
Manual: someone created it in Ambrook
Imported: it came from a CSV import
Plaid or MoneyKit: it synced from your bank connection
Step 4: Fix it based on what you found
What you see | What to do |
One copy Imported, one from Plaid/MoneyKit, and lots of them | Delete the overlapping import (see below) |
Both copies Imported | Delete the extra import (see below) |
One Manual, one from your bank, not a transfer | Delete the manual copy |
One copy is a transfer you entered by hand | Match the two sides (see below) |
Both from Plaid/MoneyKit, just a few | Exclude the extra copy |
Both from Plaid/MoneyKit, many of them or ongoing | Contact support |
Lots of duplicates from an import? Delete the import
If a whole date range is doubled and one copy of each says Imported, you can clear them all at once. You generally don’t need to exclude them one by one.
Go to Settings → Import.
Find the import for that account. To make sure it’s the right one, click the three dots (⋯) next to it and choose Filter transactions. This shows only that import’s transactions on your Ledger.
Click the three dots (⋯) again and choose Delete imported data.
Check the number of transactions in the confirmation, then click Delete [number] Transactions.
Before you delete:
Deleting an import removes every transaction in it, including any tags or attachments on those copies. This can’t be undone. If you tagged the imported copies instead of the bank copies, write down those tags first so you can add them to the bank copies.
Only delete the whole import if your bank connection covers its full date range, or if you are going to re-import the missing date range. If part of the import covers dates the connection doesn’t, deleting it removes those transactions too.
If any imported transaction is tagged as a transfer or matched to an invoice or bill payment, Ambrook asks you to remove those links first. The dialog lists them and links straight to each one. See Unlinking Transfer Tags.
Manual duplicates
Delete the manual copy from its three-dot menu. Manual transactions can’t be excluded. If the manual copy is tagged as a transfer, see the next section instead.
Duplicate transfers between your own accounts
Don’t delete or exclude either copy. The transfer you entered is the record of money leaving the first account, and transfer-tagged transactions can’t be excluded anyway. Link the two sides instead:
Open the deposit your bank brought into the receiving account.
Click Category, then choose Account Transfer.
Select the transfer you entered (same amount, opposite sign).
The transfer now shows up once, and both account balances stay correct.
A few bank-synced duplicates
If your bank occasionally sends the same transaction twice, you can exclude the extra copy. If the duplicates continue to sync on recent transactions, notify support.
Check your bank statement to confirm the transaction happened only once.
Open the three-dot menu on the copy you haven’t tagged or matched, and select Exclude.
Choose Duplicate transaction as the reason, then click Exclude Transaction.
Some transactions can’t be excluded until you change them first: transactions with multiple line items, transactions tagged with a transfer, and payments matched to an invoice. See Excluding & Deleting Transactions.
Excluded something by mistake? Filter your Ledger to Status → Excluded Only, open the three-dot menu, and choose Undo Exclusion.
When the same account is connected twice
If two accounts on your Accounts page are really the same bank account, contact support and ask for an account merge. We’ll combine the two connections into one. That way you keep the tags, matches and reconciliations from both, and every transaction appears once.
Please don’t try to fix this by excluding the transactions on one copy, or by hiding one of the accounts. Excluding takes a long time and still leaves two accounts. Hiding removes that account’s transactions from your Ledger and reports, along with any tagging or reconciliation done on it.
The one case you can handle yourself: you connected the account a second time very recently, and nothing on the new copy has been tagged, matched or reconciled. Click the new account, then Remove Account → Hide. If you’re not sure, contact support.
Preventing duplicates
Before you import a CSV, check which dates your bank connection already covers. Only import dates it doesn’t.
On the import screen, watch for the alert icon next to a date. It means that account already has transactions on that day.
If a connection stops syncing, try using Fix Connection or Update Login from Settings → Connections before connecting the account again.
When you record a transfer between two connected accounts, match it to the existing transaction on the other account instead of creating a new one.
What to send support
If you have any questions or need further assistance with duplicate transactions, message us from the Support button in the app, and include:
Whether the duplicates are in one account or two, and the account names
The date range where you see duplicates
The Source of each copy (Manual, Imported, Plaid or MoneyKit)
One or two example transactions (date and amount)
Anything that changed around that time, like a reconnection, a new team member connecting accounts, or an import
