Wave duplicate connections: check every included account

When a bank account appears under two Wave connections, compare all accounts inside each connection before removing anything. Wave permits deleting a duplicate connection only when every account within it is duplicated. For a partially duplicated connection, its documentation provides an account-level import toggle instead.

This is a Wave US connection-scope investigation, not duplicate removal inside a CSV. LocalExtract prepares PDF transaction CSV locally; it cannot inspect or change Wave connections.

Map connections to bookkeeping accounts

Open Banking → Connected Accounts and identify the bank accounts inside each connection, their destination bookkeeping accounts and the coverage already imported. Wave’s duplicate-connection instructions distinguish a connection containing several accounts from one individual account.

The same guide warns that a connection cannot be restored to a past date or time. Do not treat removing and reconnecting it as an undoable experiment. If an account is used for online-payment payouts or payroll funding, its responsible owner must address that dependency before any connection deletion. This guide does not walk through payment or payroll changes.

Automatic imports have their own Wave plan requirements. The relevant question here is whether the authorized account has the import control, not whether another CSV format can remove a connection.

Choose the scope of the proposed change

For C2, deleting the whole connection would affect card C as well. Wave documents toggling Automatically import transactions into account for an individual account; it does not support deleting just one account from inside the connection.

For C3, matching scope is only one condition. Verify actual destination accounts, imported history and payout/payroll dependencies before an authorized owner considers deletion. The synthetic connection-scope worksheet checks set overlap and those review flags, not a live Wave connection.

Review historical transactions separately

Stopping future duplicate imports does not establish which existing ledger rows are duplicates. Wave’s next documented stages use Accounting → Chart of Accounts to rename the duplicate bookkeeping account, then Accounting → Transactions and an account filter to inspect its records. A duplicate label helps avoid future misuse; it does not prove every transaction in that account is disposable.

Preserve the supported records and review any move, merge or deletion individually. Archiving a duplicate account later removes it from the transaction dropdown; it is not a substitute for resolving its history. For repeated observations in source files, use the separate CSV overlap guide.

LocalExtract processes one PDF at a time to date,description,amount CSV. It does not disable imports, delete connections or repair ledger duplicates. Download for PDF-only source records.

Official Wave instructions checked October 16, 2026.