Skip to main content

Importing CSVs into Custom Accounts

How to import Deposits, Withdrawals, Trades, Income, Mining, Gifts, Gambling, Purchases, Staking and Donations from any exchange.

S
Written by Scott

Recap aims to support all exchanges with Connected Accounts. These import all of your transaction history automatically through read-only connections to your accounts. See here for our connected account support.
​
If we don't currently support your exchange via our Connected Accounts, Recap allows you to import CSV transactions into a Custom Account with support for a wide range of transaction types.
​

In a rush? See an example in our Google Sheet or download the CSV template.
​

Before you start

Each import replaces the account's CSV data

Every time you import a file into a custom account, Recap replaces all the transactions from the account's previous import with the contents of the new file. This stops duplicates building up across uploads. You can think of the CSV file as the master record, always overriding data in an account.
​

  • To add new transactions, add them to your existing file and import the whole file again. A file that holds only the new rows replaces everything imported before it.
    ​

  • For one or two extra transactions, you can use Add transaction in the Activity screen instead. Transactions added this way aren't part of the CSV, so they're kept when you re-import.
    ​

  • Unchanged rows keep any changes you made to them in Recap, such as a new transaction type. Editing a row in the file makes it a new transaction, so changes you made to that row in Recap are lost. It's best to make corrections in the CSV itself.
    ​

  • If some rows have problems, the file shows as Failed with the problem rows listed, but the other rows are still imported and replace the previous data. Fix the listed rows and import the whole file again. If no rows can be imported, nothing is replaced.
    ​

Fees

Enter every amount before any fee, and record the fee on its own in FeeAmount and FeeCurrency. Recap always deducts the fee separately, on top of the amounts, so a fee that is also included in an amount gets counted twice.
​

  • Trades with the fee paid in the currency you spent. You bought 0.02 BTC for £1,000 and paid a £5 fee, £1,005 in total. Enter InOrBuyAmount 0.02 (BTC), OutOrSellAmount 1000 (GBP) and FeeAmount 5 (GBP). Recap deducts £1,005 from your GBP balance.
    ​

  • Trades with the fee taken from what you received. You spent £1,000 on BTC and 0.0198 BTC arrived after a 0.0002 BTC fee. Enter InOrBuyAmount 0.02, the amount before the fee, with OutOrSellAmount 1000 (GBP) and FeeAmount 0.0002 (BTC). Recap adds 0.0198 BTC to your balance.
    ​

  • Withdrawals (you're sending) - fee is exclusive. Enter the amount that arrived at the other end as OutOrSellAmount, and the network fee as FeeAmount. As the sender, you pay the fee on top.
    ​
    Example: if 1 ETH arrived and the fee was 0.01 ETH, enter OutOrSellAmount 1 and FeeAmount 0.01. Recap then deducts 1.01 ETH from your balance. If your exchange only shows the total that left your account, subtract the fee from it first.
    ​

  • Deposits (you're receiving) - fee is inclusive. The fee was already deducted before the funds reached you, and the sender covered it. Record the amount that landed in your account and leave FeeAmount blank.
    ​

Don't leave trade fees out to make a balance match. They are allowable costs, so leaving them out overstates your gains. If a balance is out by the fee, check whether the fee is also included in one of the amounts.
​

If you want to see how fees have been applied to a transaction, use the 'changed balances' section in the 'details' tab for any transaction.
​

How transfer fees are treated for tax

When you pay a fee in crypto to move funds between your own wallets or accounts, Recap treats that fee as a small disposal in its own right: you have parted with those tokens to pay for the transfer, so the fee reduces your holding and can realise a small gain or loss.
​

These transfer fees are not included as allowable costs (the costs deducted when calculating a gain), because they are not attributable to a specific acquisition or disposal. Fees paid as part of a trade or an on-chain swap are included as allowable costs.
​

CSV file details

Your file needs all eight column headers, even when a column has no values: Type, Date, InOrBuyAmount, InOrBuyCurrency, OutOrSellAmount, OutOrSellCurrency, FeeAmount and FeeCurrency. Which values you fill in depends on the transaction type.
​

Required in every row

  • Type - Airdrop, Deposit, Withdrawal, Trade, Income, Mining, Gift (gifts to or from), Spouse (gifts to or from your spouse or civil partner), Gambling (in or out), Purchase, Stake, Unstake, StakingReward, Donation, Fork, MarginGain, MarginLoss, LendingFee, Fee, FeeRebate, LoanPrincipal (loan acquisition), LoanPrincipalPayment (loan repayment), LoanCollateral (’Locking’ of loan collateral), LoanCollateralUnlocked and LoanInterest
    ​

    We've got a more detailed A-Z guide for each transaction type here.
    ​

  • Date - The Date of the transaction. We support multiple different date formats, but to avoid ambiguity, we recommend using yyyy-mm-dd hh:mm:ss, e.g. 2021-01-01 23:42:20. When uploaded into Recap, this date will represent a date according to the timezone of your web browser. To eliminate any confusion regarding time zones, consider using an ISO standard date and time format like 2021-01-01T23:42:20Z, where the time zone is explicit.


    ​Supported date formats:
    ​
    ​ISO8601 standards where the timezone is explicit:

    Full UTC: 2020-10-06T17:41:28Z

    With Offset: 2020-10-06T17:41:28-09:00


    ​Local date and time formats reflect the timezone settings of your web browser.

    Local Date Only: 2011-12-03

    Local DateTime: 2011-12-03T10:15:30

    YYYY-MM-DD HH:mm:ss: 2016-03-11 08:24:43

    DD-MM-YYYY HH:mm: 06-10-2020 17:41

    DD/MM/YYYY HH:mm: 06/10/2020 17:41

    YYYY/MM/DD HH:mm:ss: 2020/10/06 17:41:28

    Month DD, YYYY HH:mm AM/PM: January 15, 2021 12:53 AM

    Day Mon DD YYYY HH:mm:ss: Mon Oct 31 2017 14:53:18
    ​

Required for some transaction types

Depending on the activity type, there will be a few conditionally-required fields. To give a simple example - if you’re buying an asset or receiving an airdrop, you’ll need the InOrBuy pairs (InOrBuyAmount and InOrBuyCurrency). If you’re selling an asset or withdrawing some bitcoin to another wallet, you’ll need the OutOrSell fields (OutOrSellAmount + OutOrSellCurrency). More details about the specific conditionally-required fields per activity type can be found in the detailed sections for that type.

  • InOrBuyAmount - In or buy amount as a positive number or 0 [Required for Airdrop, Deposit, Trade, Income, Mining, Gift (from someone), Gambling (proceeds), Unstake, StakingReward, Fork (origin currency amount), FeeRebate, MarginGain, LoanPrincipal and LoanCollateral types]
    ​
    Note: for a trade, InOrBuyAmount is the amount before any fee was taken. See Fees above.
    ​

  • InOrBuyCurrency - In or Buy currency, e.g. BTC [Required where InOrBuyAmount is specified]
    ​

  • OutOrSellAmount - Out or Sell amount as a positive number or 0 [Required for Withdrawal, Trade, Gift (to someone), Gambling (placement), Purchase, Stake, Fork (new currency amount) types, MarginLoss, LendingFee, LoanCollateralUnlocked and LoanPrincipalPayment]
    ​

  • OutOrSellCurrency - Out or sell currency, e.g. GBP [Required where OutOrSellAmount is specified]
    ​

Optional / Specialised fields

  • ValueAmount/ValueCurrency - Only used for receiving a Spouse gift, this is the amount and currency of the value of the gift. For example, if your spouse gifts you 1 BTC they bought for 5,000 GBP, you would use 5000 in the ValueAmount column and GBP in the ValueCurrency column
    ​

  • FeeAmount - Fee amount as a positive number, where a fee is applicable. Leave it blank if there was no fee, but keep the column.
    ​

  • FeeCurrency - Fee currency, e.g. GBP, BTC

Manually priced assets

Users can choose to override Recap's pricing engine with a manually entered asset price, this is useful when we are unable to price an asset or you'd like to use a manual price instead of ours. Special Note: Imported prices cannot be edited in Recap once imported. Users should re-import their CSV files if they wish to make adjustments to these prices.

  • PriceAmount - A manual price, for one unit of the asset [Required wherever PriceBaseCurrency and PriceQuoteCurrency are specified]
    ​

  • PriceBaseCurrency - The asset you wish to manually price (i.e BTC) [Required wherever PriceAmount and PriceQuoteCurrency are specified]
    ​

  • PriceQuoteCurrency - The currency you wish to use to price the base asset. This should always be the same as your tax currency - (i.e. GBP for HMRC, USD for IRS and ZAR for SARS). [Required wherever PriceBaseCurrency and PriceQuoteCurrency are specified]


We maintain this Google Sheet and regularly add notes as we get feedback and make improvements to our example dataset. You can download this as a sample CSV by clicking the button below:
​


​

Importing your CSV files

Once your file is ready, create a custom account in Recap and import it:

  1. Go to the Accounts screen and click Add account.

  2. Choose Custom and click Next.

  3. Give the account a name (you can change this later) and click Next.

  4. Drag your file into the upload box, or click the box to choose it. Recap accepts .csv and .xlsx files, and the import starts straight away.

  5. Check the Import results, then click Done.


​To import an updated file later, click the file icon on the account, or open the account's ⋯ menu and choose Import CSV. You can also click Done at step 4 and add the file later.

Did this answer your question?