Coverage
Supported imports, destinations, and review-first handoffs.
Wesley is strongest at the prep layer before import. That means extracting the statement, letting the reviewer clean it up, and then sending the right output into the destination system that actually runs the ledger.
QuickBooks Online, QuickBooks Desktop, Xero, and QIF-style legacy workflows are all supported as downstream destinations.
Generic CSV stays available when the team wants spreadsheet review before committing to a system-specific file.
The same upload can usually switch output format without forcing the reviewer to start over.
Primary accounting destinations
Use these workflows when you already know where the cleaned statement data has to go next.
Destination
QuickBooks Online imports
Start with the QuickBooks Online import workflow when the destination is QBO.
Open page
Destination
QuickBooks Desktop prep
Use a Desktop-oriented CSV when the downstream stack still depends on QuickBooks Desktop.
Open page
Destination
Xero imports
Use the Xero-first workflow when the cleaned statement is headed into Xero.
Open page
Destination
QIF and legacy workflows
Use QIF when the downstream system still depends on a legacy import format.
Open page
Review-first handoffs
Use these when the team wants to keep cleanup outside the accounting system before choosing the final import path.
Review-first
Generic CSV review
Keep the statement in a general CSV for spreadsheet QA, transformation, or reviewer handoff.
Open page
Card workflow
QuickBooks card imports
Use the card-specific QuickBooks flow when the source is a credit card statement.
Open page
Card workflow
Xero card imports
Use the Xero-ready card flow when monthly statement cleanup still happens before import.
Open page
Product
Document upload workspace
Use the product page when the broader workflow includes Excel, JSON, or workspace exports before downstream posting.
Open page
Notes
What import support means here
Wesley is the prep layer before import, not a replacement for the destination system's own upload UI or reconciliation workflow.
Import support is strongest when the source file is still a PDF statement, a scan, or another messy document that needs review before handoff.
If the destination is not listed, start with generic CSV and shape the final import file in your existing downstream process.
Explore next
Keep going deeper from here.
FAQ
Frequently asked questions
Can the same upload switch from generic CSV to a system-specific file?
Yes. That is one of the main reasons teams use Wesley. They can review first, then choose the final output format once the statement is clean enough.
What if my destination system is not listed?
Use the generic CSV workflow as the handoff layer, then shape the final import file inside your existing destination-specific process.
Does import support mean native sync?
No. On this page, import support means Wesley can prepare the reviewed file before the destination system's import step.
Need a workflow that matches your client mix?
Start with one statement, one client, and the output format your team already needs downstream.
Free Plan includes up to 1 client total. No credit card required.