Wave uses Plaid to connect eligible bank and credit-card accounts in the United States and Canada. Automatic bank transaction imports are currently part of Wave’s Pro plan, and Wave says transactions generally update every 24 hours but may take as long as seven days depending on the financial institution.
The most important distinction is this:
bank connection imports transaction data;
reconciliation verifies the books against the bank statement.
Those are related but separate accounting jobs.
Supported Account Types
Wave currently lists several supported account categories for Plaid connections:
checking;
savings;
certificates of deposit;
prepaid debit cards;
money-market savings accounts;
credit cards.
Support still depends on the specific institution.
A bank can fall into a supported account category without being available through Plaid.
Automatic Imports Require Pro
Automatic transaction imports are currently a Pro feature.
Starter users can still maintain books by manually entering transactions or uploading statement files.
That makes bank automation one of the strongest differences between Starter and Pro.
Wave Uses Plaid
Wave relies on Plaid as its secure bank-data connection provider.
Wave’s accounting documentation describes the bookkeeping bank feed as read-only.
That connection can retrieve transaction information but is not itself a mechanism for moving money into or out of the account.
Online payment and payroll funding connections may involve separate functionality.
How Far Back Can Imports Go?
When connecting an account, Wave currently allows users to select the transaction-import starting date.
Depending on the bank, the initial connection can import up to 18 months of transaction history.
Older records can be added using statement uploads or Wave Connect.
This is particularly important when moving historical bookkeeping into Wave.
Unlimited Connected Accounts
Wave currently says there is no limit to the number of bank accounts that can be connected for transaction importing.
A business can therefore connect several:
checking accounts;
credit cards;
savings accounts.
Each connected banking account should map to the appropriate account in Wave’s chart of accounts.
Import Delays Are Not Always Wave Problems
Bank connections can stop working for several reasons.
Wave’s current troubleshooting documentation identifies issues such as:
bank maintenance;
bank security changes;
unsupported MFA;
unread notifications on the bank website;
credential changes;
a bank ending third-party access;
Plaid compatibility issues.
This matters because Wave cannot fix every connection issue directly.
The failure may be inside the bank-Plaid relationship.
Reconnecting Can Restore Imports
If Wave shows a Reconnect option, users can reauthorize the bank connection.
Current guidance also recommends checking the bank itself, acknowledging blocking notifications and updating credentials where appropriate.
However, reconnecting needs care because choosing an import start date that overlaps existing transactions can create duplicates.
Duplicate Connections
A user can also accidentally connect the same bank account more than once.
Wave has a specific workflow for resolving duplicate bank connections.
This is different from duplicate transactions.
A duplicate connection is an infrastructure problem.
Duplicate transactions are an accounting-data problem that can result from overlapping imports or multiple data sources.
Duplicate Transactions
Wave says duplicates can occur when:
a bank is reconnected with an overlapping start date;
the same account has multiple connections;
manual invoice, bill or receipt transactions also appear through the bank feed.
The correction depends on the cause.
Some duplicates should be deleted.
Others should be merged.
Statement Uploads Provide a Fallback
If Plaid does not support the bank or the connection remains broken, Wave supports manual statement imports.
The platform accepts formats including OFX, QBO, QFX and ASO, with CSV available as another option.
Wave explicitly recommends several of the structured bank formats over CSV when available because they are easier to import reliably.
Wave Connect Is Another Import Route
Wave Connect, the official Google Sheets add-on, can also upload bank transactions.
This can be useful for businesses that need more structured batch control or already prepare transaction data in spreadsheets.
It is not the same thing as the live Plaid bank feed.
Reconciliation Comes After Importing
Wave’s Reconciliation page compares the transactions in Wave with the actual bank statement.
The goal is to find:
missing transactions;
duplicates;
incorrect amounts;
other differences.
A perfectly functioning Plaid connection does not eliminate this accounting control.
Reconciliation Is Web-Only
Current Wave documentation says reconciliation is available only in the web version of Wave.
That makes reconciliation a desktop/web bookkeeping workflow even though other accounting tasks may be available through the mobile app.
Chase Has Special Limitations
Wave currently documents some Chase-specific behavior.
For example, Chase may use masked account numbers in third-party applications, and a Chase account can be limited in how automatic imports interact with multiple third-party applications or Wave business profiles.
This is a good example of why “Wave bank connections” cannot be explained solely from Wave’s side.
Bank-specific security policies can change the experience.
Bank Connections Are Not the Same as Payroll Funding
Wave may use connected bank relationships for more than one product, including payroll funding or customer payments, but the automatic bookkeeping import is a specific Pro feature.
A business can therefore encounter a bank connection in one Wave context without automatically having all transaction-import functionality.
The Best Troubleshooting Order
When imports stop:
- Check whether the business has Pro.
- Review the Connected Accounts status.
- Check whether the bank itself is available.
- Look for a Reconnect prompt.
- Verify credentials or MFA changes.
- Avoid reconnecting with an unnecessarily old import date.
- Use statement uploads or Wave Connect if live importing is unavailable.
- Reconcile afterward to verify the books.
That sequence focuses on the failing layer before editing accounting data.