Lightyear is another format Pulse parses natively — no column mapping. There is exactly one rule: don't rename the file. Lightyear puts your account code in the filename rather than in the rows, and that's how the import matches the statement to your account.
Step 1 — export the account statement
- In the Lightyear app or web, open your account's Documents / Statements section.
- Export the account statement as CSV for your full date range.
- You'll get a file named like
AccountStatement-LY-XXXXXXX-2026-01-01_2026-07-31_en.csv. Leave that name exactly as is — theLY-XXXXXXXpart is your account code, and it's the only place it appears.
If you have several Lightyear sub-accounts (say EUR and USD), export each — the filenames differ, and each statement finds its own account in Pulse.
Step 2 — drop it into Pulse
Transactions → Import, drop the file (several at once is fine, even mixed with other brokers' exports). The preview shows every row and its classification before anything is written.
What the import does for you
- Buys, sells, dividends and distributions import with fees separated out; cash-sweep interest lands as income, not a phantom deposit.
- USD rows convert to your base currency at the row's own date — a dollar dividend from March converts at March's rate, not today's, and the original native amount is kept alongside.
- Deposits and withdrawals import as cash and move your invested capital; a transfer arriving from another of your own accounts is recognized and kept neutral, so moving money between your own brokers never counts as new investment.
- Re-imports are duplicate-free — every Lightyear row carries its own reference, so overlapping exports are safe.
If something looks off
Nine times out of ten it's the filename: a statement renamed to lightyear.csv still parses, but it can no longer auto-match your account, so the rows land in the wrong place or ask you to pick. Re-download (or restore the original name) and import again — duplicates can't happen, so a corrective re-import is always safe.