Exporting your transactions as CSV

The transaction-history CSV is your portable copy of every buy and sell you've recorded in Gold Silver Ledger.

It's the file to reach for when you need your activity in a spreadsheet, in a backup folder, or in someone else's hands — an accountant, a partner, a tax preparer, or a future version of you who wants the raw data without opening the app.

Transaction CSV export is available on Pro and Premium plans. Starter accounts can export holdings but not transactions — for that, see Exporting your holdings as CSV, and to unlock transaction exports as well, see Upgrading your subscription.

The button lives on the Transactions History page, alongside the import, sale, and purchase controls.

The browser downloads the file to your default Downloads folder. There's no preview or confirmation step — the file generates and saves in one click.

One row per transaction line — meaning one row per product within a transaction. A buy of 35 American Gold Buffalos in a single purchase is a single row with quantity 35; a buy of one silver bar and one palladium bar on the same day is two rows sharing the same date and dealer.

The header row carries thirteen columns:

There's no separate "transaction ID" column and no totals row — this is a flat per-line ledger, suitable for sorting, filtering, or pivoting in whatever tool you bring it into.

The flat-line structure matters most when you're trying to read a single transaction that contained multiple products.

Sales follow the same pattern: a sale of three coins from a single sell transaction is one row with Quantity = 3 if the price per unit was uniform.

Each row is independent — the linkage between a sold item and the buy that originally created it isn't surfaced in this export. For that linkage, look at the Annual Report's per-item record instead. See How the Annual Report autofills your data.

The file downloads with a date-stamped name: transactions-{YYYY-MM-DD}.csv — for example, transactions-2026-05-20.csv. The date is the day you generated the export, not anything to do with the transactions inside it.

If you run multiple exports on the same day, your browser will append a numeric suffix (transactions-2026-05-20 (1).csv, (2).csv, and so on) so nothing gets overwritten.

Monetary values in the transaction CSV are always in USD, regardless of the display currency you have set on the app. The column headers say so explicitly — Price Per Unit (USD), Spot at Time (USD), and so on.

This is a deliberate exception to the rest of the app, where everything renders in your selected display currency. Transaction exports stay in USD so that:

If you need the values in another currency for a downstream tool, the conversion is one column-formula away in your spreadsheet of choice — but the file itself ships USD-only.

CSV is plain text, so it opens in any spreadsheet or text editor.

If a date column lands as plain text in your spreadsheet of choice, format the column as a date and the values resolve. If a numeric column comes in without a $ sign, that's the CSV standard — the numbers themselves are correct.

The transaction CSV captures activity, not inventory. It tells you what you bought and sold; it doesn't tell you what's currently sitting in your stack at the item level, with nicknames and references and per-item annotations.

It also doesn't carry tax classifications — short-term, long-term, gain or loss against each sell. The Annual Report is the right place for that view. See Generating your Annual Report.