Common issues
- "Bank not listed in Plaid." Plaid covers most US/Canada banks but not 100%. If yours isn't supported, you can still upload statements as CSV imports — see Documents.
- "Transactions stopped syncing." Plaid tokens occasionally need refreshing. Open Settings → Bank Feed and reconnect. Some banks throttle Plaid; wait a few hours and try again.
- "Tally matched the wrong document." Unmatch and pick the right one. Tally absorbs the correction.
- "A pending transaction won't match an invoice." Tally only matches against posted transactions. Wait for the bank to post; matches usually resolve within 1–2 days.
- "I'm a bookkeeper and I can't see my client's bank feed." Check your access level — bank feed views typically require "review" or "full" access on that client.
Confirming or unmatching
- Confirm a suggested match — one click, and Tally remembers the alias for the future.
- Pick a different document — if Tally's suggestion is close but wrong, search for the right document and assign manually.
- Unmatch — if a previously-confirmed match was wrong, unmatch and Tally adjusts the alias memory.
If you're a bookkeeper helping a client
The connection lives on the client's workspace. Either:
- The client connects their bank themselves through their portal — recommended, because the credentials and audit trail belong to the client.
- You walk them through it on a call.
Once connected, the bookkeeper (with the right access level) can use the feed on the client's behalf — review transactions, confirm matches, etc.
If you're a small business owner
- Open Settings → Bank Feed → Connect.
- Search for your bank in Plaid's list.
- Sign in with your bank credentials inside Plaid's secure flow. Tally never sees your password — Plaid issues Tally a scoped read-only token.
- Choose which accounts to share (checking, savings, credit cards). You can update this later.
- After authorization, your transactions start syncing.
Importing unmatched transactions as expenses
Sometimes a transaction has no corresponding invoice — a card swipe at a coffee shop, a recurring subscription where no PDF arrives, etc. From the Bank Feed view, you can import an unmatched transaction directly as an expense document. Tally adds a lightweight expense record with the merchant, amount, date, and category (suggested from your history). You review it like any other document.
This is the most common workflow for SMBs that don't track every receipt — bank transactions become the source of truth, and Tally categorizes them for you.
Multi-bank and multi-account
You can connect multiple banks or credit cards. The Bank Feed view shows all of them in one timeline by default, or filter by connection or account. Tally's matching works globally — a transaction from any account can match a document, as long as the amount and timing fit.
What's next
- Documents — handling matched and unmatched transactions
- Connect QuickBooks — push reconciled transactions to QBO
- How Tally learns — alias learning details
- Troubleshooting
What you'll do
- Connect a bank or credit card via Plaid.
- See transactions appear in your Bank Feed view.
- Match transactions to invoices and receipts you've uploaded.
- Confirm or unmatch when Tally is uncertain.
- Optionally treat unmatched transactions as standalone expense documents.
What you see in the Bank Feed
Each transaction has:
- Date, merchant, amount, account.
- Match status — already matched to an invoice, suggested match, no match yet.
- Confidence score for suggested matches (so you can sort or filter).
Tally tries to auto-match transactions to documents you've already uploaded by combining vendor name (with fuzzy matching), amount, and date proximity. The more matches you confirm, the better future matches get — Tally learns aliases like "AMZN MKTP" = "Amazon" so the next charge auto-matches.