CSV export: exported value in SATS will be interpreted as value in BITCOIN when imported to koinly

[patriknc]

in sparrow, configure bitcoin unit to "sats"
export transactions of wallet
import the CSV file in koinly
the value of transactions will be interpreted as Bitcoin, instead of sats, offsetting the value exponentially

this error doesd not ocur, when teh bitcoin unit is configured to bitcoin

[craigraw]

I understand the problem, but is it a Sparrow problem? Sparrow is correctly showing the amount in the user's desired unit.

[patriknc]

Yes, Sparrow shows the correct amount.
The CSV file exported by Sparrow shows different amounts depending on the unit setting in Sparrow

[craigraw]

The CSV file exported by Sparrow shows different amounts depending on the unit setting in Sparrow

Yes, I understand, but this appears to be a Koinly issue - it does not allow the user to configure they prefer working in sats, I assume.

[patriknc]

How does the CSV file exported by Sparrow indicate that the amount is in sats or bitcoins?
This is what I see in Sparrow export files for the same transaction

Sparrow configured to sats:
Date (UTC),Label,Value,Balance,Fee,Value (CHF),Txid
2025-11-27 18:12:49,,200000,200000,,,

Sparrow configured to bitcoin:
Date (UTC),Label,Value,Balance,Fee,Value (CHF),Txid
2025-11-27 18:12:49,,0.00200000,0.00200000,,,

I assume, anyone who exports transactions, then changes the Sparrow configuration and then reimports the CSV will be shown wrong amounts of bitcoin or sats

[craigraw]

How does the CSV file exported by Sparrow indicate that the amount is in sats or bitcoins?

It can't - CSV is a very limited format.

I assume, anyone who exports transactions, then changes the Sparrow configuration and then reimports the CSV will be shown wrong amounts of bitcoin or sats.

Sparrow doesn't import CSVs - it references the blockchain for transaction information.

[craigraw]

I should add that if Koinly supported BIP329 Wallet Labels imports (perhaps it does?) this problem goes away, since the specification of that format is strictly defined, including the unit format.

[patriknc]

Yes, I agree.

Regarding the CSV export: You said, it is very limited --> OK

If there is no general agreement / specification / proposal on the CSV format, it would be nice to let Sparrow users know what happens while exporting to CSV: The resulting file varies depending on the "Bitcoin view" setting under the App's "View" Menu.
... or maybe stick to one unit format in the CSV file regardless of the "Bitcoin view" setting?
It is not a problem for Sparrow, since there is apparently no CVS import feature. But I still find it quite puzzling

[craigraw]

The problem is that the CSV export is not Koinly-specific - it's a general format with very loose specifications. Both of your suggestions make sense in the Koinly use case, but for the general use case they either add potentially confusing UI or restrict the user. I'm not convinced they should be implemented, but I'll keep the issue open for further feedback.

[patriknc]

ok, thanks. I initially thought that the CSV export feature adheres to a common spec.