◈ Mail → Excel

Excel export for Crypto opss

By the Mail → Excel team · Updated 2026-10-20

Exchange support threads and withdrawal confirmations are the only evidence when a transfer is disputed. This page lists the exact columns, an example row and the command that produces it.

Columns to keep

ColumnWhy it matters
exchangeWhich exchange or wallet provider sent the message.
txidFull transaction id — truncated ids cannot be verified on-chain.
assetTicker of the asset moved.
amountStore as a number with a separate currency column; never sum mixed currencies.
dateMessage date in ISO 8601; sortable and unambiguous across time zones.

Example row

One real-shaped row from this role’s export:

exchangetxidassetamountdate
Binance0x8f3a…c21dUSDT500.002026-10-15

Export it in one command

python mail_to_excel.py \
  --host imap.example.com --user you@example.com \
  --days 31 --fields exchange,txid,asset,amount,date \
  --out crypto-ops.xlsx

The --fields option is what turns a raw dump into a report your role can use.

Provider notes

Proton Mail requires Proton Bridge for IMAP — without it there is no standard IMAP access.

Two pitfalls that ruin the file

Next step

Step-by-step: export crypto ops email to Excel · all roles · ready script ($3)

FAQ

Can this be used for tax reporting?

It gives you the raw rows; tax calculation is a separate step and jurisdiction-specific.

Is it safe to keep txids in a spreadsheet?

Txids are public, but the mapping to your accounts is sensitive — store the file encrypted.

Is there a ready script for this?

Yes — the Python script exports any IMAP mailbox with the fields listed above; it costs $3 and runs locally.

Related guides