Supported institution
Use Wesley with BMO whether the client connects accounts or still sends statements.
BMO can fit two different operating modes. When connected account coverage is available, the firm can sync activity directly into the workflow. When the client still works from monthly PDFs, the statement-review path stays available without forcing the team to wait on connection setup first.
Connected account coverage is the cleanest path when the bank connection is available for the client account.
Statement upload remains the fallback when the team only has BMO PDFs, scans, or exported files.
The same bookkeeping team can keep review, cleanup, and downstream import prep in one operating rhythm.
Workflow
Connected account when possible. Statement fallback when needed.
1. Use the connected account when the client can connect it
If the BMO account is available inside Wesley's connected-account coverage, start there so the team does not wait on document collection for current-period activity.
2. Fall back to statements when the source of truth is still a PDF
If the client only sends a monthly statement, historical feed access is missing, or the reviewer wants the official statement period, start from the statement workflow instead.
3. Keep review and downstream handoff explicit
After activity lands in Wesley, the reviewer can still decide whether the next step is spreadsheet QA, QuickBooks prep, Xero prep, or another controlled handoff.
Use connected accounts when...
The client can authorize the institution and the bookkeeping team wants fresher activity without waiting on documents.
- BMO is part of the live connected-account flow for the client setup.
- The team is working current-period books and wants ongoing transaction sync.
- The goal is to reduce manual statement chasing for routine periods.
Use the statement workflow when...
The statement PDF is still the real source of truth for the work in front of the reviewer.
- Historical periods are missing from the connected path.
- The client only provides monthly statements or scanned copies.
- The reviewer wants the official statement period before import or reconciliation.
What support for BMO actually means
Support does not mean forcing every BMO workflow into one lane. In practice, accounting teams bounce between connected activity and statement-driven cleanup depending on what the client can share, what period they are fixing, and what evidence the reviewer needs.
When the BMO account is available inside the connected-account flow, Wesley can reduce manual collection work for routine periods. When it is not, the team can still keep the file-based workflow inside the same broader operating system.
- Typical account coverage for this institution includes checking, savings, business accounts, credit card accounts.
- Live connected activity and statement-upload review can coexist inside the same client workflow.
- Reviewers still control how the cleaned data moves into the downstream accounting system.
Why firms still need the statement fallback
Many BMO engagements still start from the official statement PDF because the client is onboarding late, historical periods are missing, or the reviewer wants the exact statement period before making import decisions.
That is why Wesley keeps the statement path available even when connected coverage exists. The operational problem is not only connecting the bank. It is keeping the review layer stable when real client conditions vary month to month.
- Catch-up and cleanup work usually needs the statement period, not just current synced activity.
- Monthly reviewer controls stay cleaner when the team can compare against the official statement.
- A fallback path prevents connection issues from stalling the bookkeeping queue.
Related pages
Move from bank coverage into the actual workflow.
Connected-account workflow
See how Wesley handles live connected activity before it reaches the rest of the bookkeeping workflow.
Open page →
BMO statement workflow
Use the statement-review path when the BMO source file is still a PDF or scan.
Open page →
Supported imports
See where the reviewed activity can go after the bank side is under control.
Open page →
FAQ
Frequently asked questions
Does Wesley support BMO?
Yes. Wesley can support BMO through connected account coverage when the institution is available for the client setup, and it also supports the statement-review workflow when the client is still sending PDFs or scanned statements.
Does that mean every BMO account always connects live?
No. Institution coverage can vary by account type, client setup, security requirements, and the current connection status. That is why Wesley keeps the statement workflow available as a fallback instead of assuming the live path is always the answer.
What if the client will not connect BMO?
Use the statement workflow. Wesley is built so the review team can still work from the official BMO statement without blocking on connection setup.
Can I still send the cleaned activity into QuickBooks or Xero afterward?
Yes. After the activity is reviewed in Wesley, the team can choose the downstream handoff that matches the rest of the stack, including generic CSV, QuickBooks-oriented output, or Xero-ready output.
Need one operating system even when client bank setups vary?
Use the connected-account path when it is available, and keep the statement-review workflow ready when it is not.
Free Plan includes up to 1 client total. No credit card required.