Wealthsimple transaction export
Download a CSV from the Wealthsimple website. The owner signs in.
Parent: canadian-banks.
Request URL
Official: Request a custom statement, Find your monthly statements, trading account documents.
Submit
Activities CSV (Trade, managed, Crypto):
- Sign in. Stop. The owner completes 2FA.
- Activities tab (clock icon) → Download activities.
- Time period → Next → tick accounts → Download CSV.
Official: this export omits chequing, crypto staking, and swaps.
Monthly statements (PDF or CSV, including chequing):
- Profile (bottom left) → Documents → Statements.
- Filter by account. Click PDF or CSV on a row.
- Bulk: Generate document → Bulk download monthly statements → CSV or PDF → dates → accounts → ZIP.
Holdings CSV is as-of today only. You cannot pick a past date.
Chequing CSV is web only. Official: not in the app. Business chequing: Documents → Performance statements → Download CSV (help).
Formats
Official: CSV (machine-readable) and PDF (not). Official help does not list OFX, QFX, or QBO.
History
Activities: owner picks the period. Official help publishes no maximum. Monthly CSVs: one month per file, or a range in the bulk ZIP. Official: chequing statements from September 2023.
Categories and automation
Official pages do not list a budget-category column. Treat as uncategorized. No personal-export API. Interactive login plus 2FA. Business chequing can link accounting software through Plaid — read canadian-banks first.
Gotchas
- Use Download activities for trades. Use Statements for chequing.
- Do not type the password or 2FA code into an agent session.
- The documents list lazy-loads. A first pass counted 179 download controls. Scrolling until the count stopped changing gave 443. An export that trusts the first count gets about 40 percent of the history, and reports success. Scroll until the control count is stable before you count or download.
- A fast download loop triggers a security interstitial. The page then reads "Wealthsimple is using a security service to protect itself" and shows a Ray ID. Every download control disappears. The login session stays valid, so the page looks empty rather than blocked. That makes the failure read as "no documents exist". Detect it by testing the page text for that wording, not by counting controls. Add a delay between downloads. Re-check for the interstitial as you go. Before you record that something is absent, prove the instrument could have seen it. A blocked page and an empty account are indistinguishable if you only count controls.