Overview
DoorLoop pulls your bank transactions through Plaid, a third-party bank connection service. When Plaid refreshes or re-initializes a bank connection — such as after you repair a broken link, re-authenticate, or reconnect an account — it can re-send historical transaction data that DoorLoop has already imported. DoorLoop then receives these as new transactions, and they appear again in your register.
This is expected behavior on Plaid's side, not a DoorLoop bug. The transactions themselves are accurate — they simply got imported twice. Excluding them doesn't affect your actual bank account or your reconciled records.
Why This Happens
The most common triggers for old transactions reappearing:
You repaired or reconnected a bank account — Plaid resets its sync position and re-sends recent transaction history.
Your bank pushed a data refresh — Some institutions proactively push updated transaction data to Plaid, which DoorLoop then receives as new entries.
A transaction changed state — A pending transaction that posted, or a transaction your bank retroactively modified, can reappear as Plaid sends an updated version. See Exclude Transactions from Bank Transactions for more on why this happens.
You added the same account twice — If the same bank account was connected more than once under different names, its transactions appear duplicated. Check Accounting > Transactions for duplicate account entries.
Note: Old transactions from a specific date range (commonly 2–3 months prior) reappearing all at once is almost always caused by a Plaid connection repair — this is the most common pattern DoorLoop users report. To identify duplicates, go to Accounting > Transactions, apply the filter, and set the status to Categorized. This helps locate potential duplicates during reconciliation.
How to Exclude Reappearing Transactions
If the same transaction has been imported twice, exclude the duplicate — don't delete it. Excluding keeps it out of your reports and reconciliation without permanently removing it from your transaction history.
To exclude a single transaction or multiple transactions at once, see Exclude Transactions from Bank Transactions.
Handling Specific Duplicate Scenarios
If duplicates are auto-matched, match one bank transaction to the corresponding DoorLoop transaction and exclude the others.
For duplicate rent payments, confirm the actual payment via your bank statement, then delete the extra payment and its associated deposit.
For vendor ledger duplicates, record the bank deposit to the same account as the original expense and include "Void Check" in the memo to avoid confusion later.
Can This Be Prevented?
Not entirely — Plaid's refresh behavior is controlled at the bank and Plaid level, not within DoorLoop. However, you can reduce how often it happens:
Avoid unnecessary reconnections. Only use Repair Connection when DoorLoop or Plaid specifically prompts you to. Reconnecting proactively can trigger a fresh backfill.
Don't disconnect and reconnect the same account as a troubleshooting step unless support recommends it.
Review transactions regularly to identify and exclude duplicates promptly.
Verify before excluding — make sure a transaction is truly a duplicate by comparing details like date, amount, and payee.
When to Contact DoorLoop Support
Reach out if:
Transactions continue reappearing after you've excluded them.
You see duplicates but can't identify which one is the original.
The reappearing transactions are matched to the wrong property or account.
You suspect the same bank account was connected twice and need help identifying and merging the duplicates.
You need guidance on preventing duplicates or stabilizing your bank feed.