Importing your own files
CSV and statement imports for banks without a connection, with column mapping you configure once per asset.
Not every account can be connected, and some you would rather not connect. Import instead.
CSV
Upload the file on the asset, then tell Walletguide how to read it. The mapping is per asset and remembered, so the second import of the same bank's export is upload-and-confirm.
| Setting | What it does |
|---|---|
| Date column | Which column holds the transaction date, and its format |
| Amount columns | One, or several that get summed — banks that split debit and credit into two columns are the reason this is plural |
| From/To columns | The counterparty, used to resolve a merchant |
| Description columns | What lands on the transaction as its text |
| Start / end date | Optional bounds, for importing only part of a file |
Nothing is written until you confirm the preview.
Statements and receipts
A file uploaded to the wallet can be parsed into transactions when it is in a recognised format. Same principle: parse, review, confirm. A file that could not be parsed says so rather than failing quietly.
Duplicates
Re-importing an overlapping range is the normal way to get this wrong. Use the start and end dates to bound what you bring in, and check the preview — it is the last point at which nothing has happened yet.
Exporting
The export view takes your data back out. Everything here is also reachable from the API and the CLI, which is the better route for anything you want to do more than once:
walletguide transactions list --from 2026-01-01 --to 2026-12-31 --limit 1000 --json > transactions.json