Before you start
Whether you see the Export button on Transactions depends on your role. Owners always see it. Custom-role users need the Export Transactions permission assigned — without it, the button won’t appear, and your organization’s admin can grant it from the Permissions screen. Viewer-role users never see the button, even if the permission were somehow assigned to them; that requires a role change, not a permission grant. Exporting from a reconciliation run’s detail page has no permission requirement.Export transactions
- Go to Transactions under Operations in the left nav.
- Click Export in the page header, next to Filters.

- In the Export transactions modal, set any filters you want. All of them are optional:
These are the only filters the export modal offers. The on-page Filters drawer also supports benchmark status, reconciliation status, country, currency, and asset filters (depending on your organization’s settings), but none of those carry over to export — there’s no way to export, say, only unreconciled transactions or only flagged transactions directly. Use the export modal’s date range, type, provider, status, and account filters to narrow things as far as they’ll go.
- Click Export.

transactions.csv. Filters change the filename too — for example, a date range alone produces transactions_2026-06-01_2026-07-17.csv, and adding a provider and status filter appends those to the name (lowercased), so you can tell what’s in a file without opening it.
The Export button only appears on the main Transactions page — it’s not available if you’ve drilled into a single account’s transaction list.
Export a reconciliation run
Each reconciliation run has its own export, separate from the Transactions export above, and it isn’t filtered the same way.- Go to Reconciliation under Operations in the left nav.
- In the Runs tab, click a row to open that run’s detail page.
- Click Export at the top of the Run detail page.

{runId}-transactions.csv containing every transaction in that run. It always exports the Transactions tab’s data, even if you have the Exceptions or Orphaned tab open when you click — there’s no way to export exceptions or orphaned rows separately.
For a large run, this can take a while: the export gathers the full result set (up to 20,000 transactions) before building the file, and the only feedback while it works is a loading spinner on the button. If a run has more than 20,000 transactions, the export stops there with no warning — the file downloads normally and looks complete, but the rows beyond 20,000 are silently missing.