Connecting a bank account to Wave does not mean Wave becomes another online bank.
For accounting transaction imports, Wave uses Plaid to establish a data connection to supported financial institutions. The connection used for transaction importing is read-only: its purpose is to bring financial activity into the accounting system, not to let someone move money through the bookkeeping connection.
For new Wave businesses, automatic transaction imports are part of Wave Pro.
Once the transactions arrive, however, another job remains: making sure the records in Wave actually match the business’s bank and credit-card statements.
That job is reconciliation.
What a Bank Connection Actually Does
A connected financial institution can automatically send supported transaction information into Wave.
Instead of manually creating every coffee purchase, software subscription, customer deposit and card charge, the transaction feed populates the accounting Transactions page.
Wave can then categorize or merge certain transactions automatically under Pro.
This reduces data entry, but a bank feed should not be mistaken for completed bookkeeping.
The imported transaction tells Wave that money moved.
It does not necessarily understand the full business reason the money moved.
Bank Imports Are Not Real-Time
Wave explicitly states that bank transaction imports are not instantaneous.
They generally update around once every 24 hours, while some financial institutions may take as long as seven days to provide updated transactions. Users cannot select a particular import time or frequency.
This explains a common source of confusion.
A user may open online banking, see yesterday’s purchase, then open Wave and assume the bank connection is broken because that purchase is missing.
The two systems are not necessarily expected to match minute by minute.
When the feed has not updated for more than seven days, Wave says there may be a connection issue requiring troubleshooting.
Why Some Banks Cannot Be Connected
Wave’s accounting bank connections depend on Plaid support.
Not every bank, credit union, financial institution or individual account type available in the United States and Canada is necessarily supported. Certain MFA implementations can also interfere with the connection.
Another restriction is product eligibility.
Wave’s current Help Center states that bank connectivity can depend on the business being active on Pro, online payments or payroll, depending on the specific banking purpose.
If a bank cannot be connected for automatic accounting imports, the business can still get transaction information into Wave using other methods.
Manual Bank Details Do Not Create an Accounting Feed
Wave allows some businesses to manually supply routing and account information for purposes such as online-payment payouts or payroll funding.
That is different from connecting a bank for accounting transaction imports.
Wave explicitly says a bank account cannot be manually added using routing and account numbers to create an automatic transaction feed.
This distinction prevents two completely different workflows from being confused:
Payments/payroll bank connection: used to send or receive money.
Accounting transaction connection: used to import financial records.
Both involve a bank account, but they solve different problems.
What If Automatic Import Is Not Available?
Wave supports transaction imports from bank statement files.
Its documentation describes uploading formats including OFX, QBO, QFX and CSV, among others depending on the financial institution’s export options.
Wave Connect provides another import route for certain workflows.
This also means Starter users are not prevented from doing accounting simply because automatic imports belong to Pro. They can use more manual methods to populate the books.
The tradeoff is administrative effort.
Why Duplicates Happen
Bank automation creates another bookkeeping problem: the same economic event can reach Wave in more than one way.
Imagine a business owner receives a client payment and records it manually.
Later, the bank feed imports the deposit.
If Wave does not recognize and merge those two records correctly, the books can appear to show twice as much money.
A similar problem can occur when a receipt creates an expense transaction before the related card transaction is imported. Wave provides tools for identifying and merging duplicates.
This is why reviewing transactions remains important even when automation is enabled.
Reconciliation Is the Accuracy Check
Reconciliation compares the bookkeeping records in Wave with an external source: the actual bank or credit-card statement.
Wave’s reconciliation process asks the user to establish a period with an ending date and closing statement balance. Transactions are then matched until Wave’s matched balance agrees with the statement’s closing balance.
When everything matches, the difference reaches zero.
That zero is more meaningful than a dashboard that simply “looks right.”
It provides evidence that the accounting records for the period correspond to the financial institution’s records.
What Can Cause an Unreconciled Period?
Wave documents several common causes.
There may be:
missing transactions, duplicate transactions, an incorrect closing statement balance, pending transactions, transactions entered in error, or earlier reconciled items that were later edited.
Balances can also differ because bank imports are delayed or because money is still in transit—for example, when a check has been recorded in the books but has not yet cleared the bank.
The useful troubleshooting question is therefore not simply:
“Why is Wave wrong?”
It is:
“At which layer did the difference arise?”
Was the transaction missing from Wave?
Was it duplicated?
Was it dated differently?
Was the opening balance incorrect?
Has the bank not posted it yet?
That diagnostic approach is much faster than randomly editing transactions until the balance changes.
Reconciliation Is a Web Workflow
Wave’s current reconciliation functionality is available through the web version rather than the mobile reconciliation interface.
The mobile app can handle several accounting tasks, but full bookkeeping still has web-only components.
That matters for businesses hoping to run the entire accounting process exclusively from a phone.
A Better Monthly Workflow
For a small business, a sensible Wave workflow looks like this:
allow transactions to import or upload them manually; review and categorize them; resolve duplicated records; attach or scan supporting receipts; then reconcile each bank and credit-card account against its statement.
Only after those steps do reports such as profit and loss become much more trustworthy.
A report can calculate perfectly from inaccurate transactions.
Reconciliation is what helps verify the underlying records before those calculations are relied upon.