The words two rows in large serif type, the unpaired withdrawal and deposit Koinly shows for a single transfer
Explainerone question answered

Merging two rows in Koinly turns a sale and a purchase back into one transfer. How to merge, split and edit

Fahad Zar, photographed against a plain background, head and shoulders
Fahad ZarCrypto tax accountant, licensed and regulated by the AAT. MSc Accounting and Finance, BPP University London. Six years reconciling wallet and exchange histories for UK filings.

Published 13 November 2026 Reviewed against gov.uk 13 November 2026 11 min readTools and records

The words two rows in large serif type, the unpaired withdrawal and deposit Koinly shows for a single transfer

Merging in Koinly takes a withdrawal from one of your wallets and a deposit to another, of the same coin, and makes them one transfer with no gain or loss. Left as two rows, the withdrawal is taxed. Koinly’s help page says that by default all withdrawals are treated as payment to a third party, the same as selling, and a profit or loss is calculated for them. So two rows for a move between your own wallets put a disposal on your report that never happened. Select both, press Merge, and it is gone. The video below shows the clicks.

The rest of this page is about judgement, which the buttons do not supply. Which rows belong together, which merge in the video should be read with care, how to undo a merge Koinly made on its own, what editing a row changes in the tax, and when a row should be marked as spam rather than deleted.

Merging a withdrawal and a deposit of the same coin makes one transfer with no gain, which is what HMRC’s rule on moving between your own wallets requires. Merging two different coins makes an Exchange, and the gain on the coin given up stays, because a swap is a disposal. Split from the Ledger tab undoes any merge, and every edit gets a note.

Why Koinly shows two rows for one move

Koinly records every action twice, which its transfers page calls a double ledger. A move from Coinbase to a hardware wallet is a withdrawal from Coinbase and a deposit to the wallet. If the pair passes six checks, same asset, within twelve hours, withdrawal first, deposit no larger than the withdrawal, no more than twenty per cent apart, and the same transaction hash or none, Koinly merges them into a transfer and you never see the two rows.

When a check fails, the rows stay apart, and the page on transfers counted as sales works through the six reasons. The commonest in our files are a wallet that was never added, so one side of the move is invisible, and a CSV imported in the wrong timezone, so the deposit appears to land before the withdrawal and the chronology check fails. Then the withdrawal is a sale at that day’s market price, with a gain or loss against your pooled cost, and the deposit is a fresh acquisition with a new date and a cost taken from the market price rather than what you paid.

HMRC’s position is the opposite. CRYPTO22100 says moving tokens between public addresses you control, keeping beneficial ownership throughout, is not a disposal. The only taxable piece of a transfer is the network fee paid in tokens, which CRYPTO22280 treats as a disposal of those tokens at market value. The guide to moving crypto between wallets covers the rule in full.

Which rows belong together

Koinly’s merge and split page allows three kinds of merge, and the tax result differs for each.

A withdrawal and a deposit of the same coin become a transfer. No gain, no loss, and the coins keep their pooled cost and their acquisition date. The difference between the amount sent and the amount received becomes the transfer fee. This is the merge that fixes a transfer counted as a sale.

A withdrawal of one coin and a deposit of another become an Exchange, with an optional third row for the fee tagged Cost. Koinly then calculates a gain on the coin you gave up, valued from the coin you received. That is right. CRYPTO22100 says exchanging tokens for a different type of token is a disposal, and the sterling value of what changed hands is both the proceeds of the old coin and the cost of the new one. Merging here does not remove the tax. It makes the trade one row with one price instead of two rows priced separately, which is tidier and usually more accurate, and it clears a missing price warning on the received coin because Koinly values the trade from the coin it knows.

Several deposits, or several withdrawals, on the same day become one row. Up to fifty at a time, all in the same wallet, on the same day, with the same tag or none, and in the same direction. Hourly staking payouts are the usual case. The sterling value is the sum of the parts, so the income figure does not change, and the staking rewards guide covers how that figure is taxed.

Now the example in the video. It merges a withdrawal of wrapped ether and a deposit of ether and says the result will not be counted as taxable. Read that line carefully. Koinly’s transfers page says a merge of two different tokens appears as an Exchange and gains are calculated as if the first was sold for the second. In law, wrapping is contested ground. Exchanging one token for a different token is a disposal under CRYPTO22100, and the wrapping and bridging guide sets out where the argument for no disposal is stronger, which is a same asset relocation with beneficial ownership unchanged. Our practice treats a wrap as a disposal unless the client has taken a reasoned position the other way and written it down. Because wrapped ether and ether trade at the same price, the Exchange row usually shows a gain or loss near nil on the swap itself, and the real effect is that the pooled cost moves from one asset to the other. Merge the rows by all means. Do not edit the result into a transfer to make the disposal vanish.

How to merge, step by step

Koinly's transactions page with two rows selected and the Merge button showing, the opening frame of the video
Our walkthrough of merging, splitting and editing, recorded in Koinly. The player loads from YouTube’s cookie free domain only when you press play.

One. Find the pair. Open the Transactions tab. An unpaired transfer shows as a Send in one wallet and a Receive in another, minutes apart, for the same coin. The Warnings filter does not list these, so sort by date and look for the pair, or filter by the coin.

Two. Select both. Hover over the wallet icon at the left of each row and a checkbox appears. Tick both. The toolbar at the bottom of the page shows Merge.

Three. Merge. Press it. Koinly combines the two rows into one. Open the new row and the Ledger tab shows both legs, the coin leaving one wallet and arriving in the other. A same coin merge is labelled a transfer. A different coin merge is labelled an Exchange, with the gain on the coin given up shown on the row.

Four. Check the balance and the gain. After a merge the running balance of the coin in each wallet should match what you actually hold, and the disposal that used to sit on the withdrawal should be gone from the gains report for that year. If the balance in the receiving wallet now shows a negative figure, the merge joined the wrong pair.

How to split a wrong merge

Koinly merges on its own during every recalculation, and it sometimes joins the wrong pair, two transfers of the same amount on the same day being the usual case. Open the merged row, go to the Ledger tab, and press Split entries at the bottom left. A transfer splits into its withdrawal and its deposit. A trade splits into the withdrawal, the deposit and a third row for the fee tagged Cost. Then select the right pair and merge again.

The reason to care is that a wrong merge can hide a real disposal. If a withdrawal to an exchange where you sold was merged with an unrelated deposit, the sale has disappeared from the report. Koinly’s help page warns that manually merging transactions that should not be merged may cause issues with the calculations, and that only uninterrupted blocks of trades in the same direction should be merged, so a buy, a sell and a buy on the same day cannot be merged into one.

Editing a transaction, and what each field changes

The three dots at the right of any row open Edit. You can change the date and time, the asset and the amount, the fee, and the tag. Each one moves a tax figure.

The date and time decide which tax year a disposal falls in and which acquisitions it is matched against. Section 106A of the Taxation of Chargeable Gains Act 1992 matches a disposal first against acquisitions on the same day and then against acquisitions in the following thirty days, before the pool, so moving a trade across midnight can change its cost. Koinly shows every time in UTC, which the transactions page says at its foot, so a trade stamped 23:30 on 5 April is on the last day of the UK tax year whatever your clock said.

The amount and the asset feed the section 104 pool that CRYPTO22200 describes, one pool per token, so a corrected quantity on one acquisition changes the pooled cost of every later disposal of that token. The fee is an allowable cost when paid to have the transaction included on the ledger, and a disposal in its own right when paid in tokens. The tag decides whether a deposit is income, a gift, an airdrop or a transfer, and the next page in this set covers the tags one by one.

Keep a note of every edit, with the reason and the evidence. CRYPTO10400 says the onus for records sits with you, and a report whose rows have been changed by hand without a note is hard to defend.

Mark as spam, or delete

The same menu offers Mark as spam and Delete, and they are for different rows. Spam is for a token that arrived unasked, the dusting and address poisoning deposits that mimic real coins. Marking it as spam crosses the row out and removes it from the reports while leaving it visible on the page, and it can be unmarked. Delete is permanent and is for a duplicate, the same transaction imported twice from an API and a CSV, which doubles a sale and is one of the causes of a negative balance. Delete nothing that is merely confusing. A row that is real and wrong is edited, and a row that is real and unpaired is merged.

A worked example with figures

Suppose you move 1 ether from Coinbase to a hardware wallet on 3 March 2026, when ether is £2,400. You bought it in 2023 for £1,500. The wallet was never added to Koinly, so the move is a withdrawal on its own, and Koinly treats it as a sale. Gain £900 in the year to 5 April 2026. In May 2026 you add the wallet and sell the ether from it for £2,600, and because the deposit came in as a fresh acquisition at £2,400, Koinly shows a gain of £200 in the year to 5 April 2027.

The true position is one disposal, in May 2026, with a gain of £1,100 in the later year. The unpaired transfer has invented a £900 gain in 2025 to 2026 instead. If your other gains that year already used the £3,000 annual exempt amount, that is £162 or £216 of tax at the published rates of 18% and 24%, due with the return by 11.59pm on 31 January 2027, on a sale that never happened. Add the wallet, merge the two rows, and the £900 moves to the year it belongs in. The 0.0005 ether network fee, about £1.20, is the only disposal on 3 March.

When it needs an accountant

A few unpaired transfers between wallets you can name are an evening’s work, and you should do them yourself. It becomes a job when the unpaired rows run into the hundreds across exchanges and chains, when an exchange that held one side of the transfers has closed, when wraps, bridges and liquidity positions are mixed in with the transfers, or when a wrong merge has hidden a real disposal somewhere in several years of history. Then every pool has to be rebuilt from the chain before the report means anything, and the fees below cover that.

Three fixed fees, quoted in writing before any work starts

One taxpayer, one tax year unless the line says otherwise. Written position within 15 working days of software access.

Review and file
For an exchange-only history under about 5,000 trades where the software report is already built.
£499
Computation
For several platforms, wallet transfers read as sales, duplicates, and one or two back years.
£950
Reconciliation
For DeFi, derivatives, high volume, or balances that do not tie.
£1,750
Multi-year rebuild, staged. Several years, an HMRC letter, an exchange data notice, or a return that was never filed. From £3,450 in two stages, half at signing, with the second stage priced once the first is done.

Send your software report to zar@certifiedcryptoaccountant.com for a written fee the same working day, or start with the free review. Licensed and regulated by the AAT, licence 1010475.

Questions about merging, splitting and editing in Koinly

Does merging two transactions in Koinly remove the tax?

Only when the two rows are a withdrawal and a deposit of the same coin, which merge into a transfer with no gain. That matches HMRC's manual, which says moving tokens between addresses you control while keeping beneficial ownership is not a disposal. Merging a withdrawal of one coin with a deposit of another makes an Exchange, and Koinly calculates a gain on the coin given up, because a swap is a disposal.

What is the difference between a transfer and an Exchange in Koinly?

A transfer is a withdrawal and a deposit of the same coin merged into one, with the coins keeping their cost and acquisition date and no gain. An Exchange is a withdrawal of one coin merged with a deposit of a different coin, a trade, with a gain or loss on the coin given up. Koinly decides which by whether the two rows are the same asset.

Koinly merged the wrong transactions. How do I undo it?

Open the merged row, go to the Ledger tab and press Split entries at the bottom left. A transfer splits back into its withdrawal and deposit, and a trade into the withdrawal, the deposit and a fee row tagged Cost. Then select the right pair and merge again. Check the running balance of the coin afterwards, because a wrong merge can hide a real disposal.

Should I merge a wrap of ether to wrapped ether?

You can merge the two rows, and Koinly will record the result as an Exchange with a gain or loss on the ether given up, usually near nil because the two trade at the same price. Exchanging one token for a different token is a disposal under HMRC's manual, and wrapping is contested, so merge for tidiness but do not edit the result into a transfer unless you have taken a reasoned position that a wrap is not a disposal and written it down.

When should I delete a transaction rather than mark it as spam?

Delete only a duplicate, the same transaction imported twice, which doubles a sale. Deletion is permanent. Mark as spam is for unsolicited tokens that mimic real coins, and it crosses the row out while keeping it visible, so it can be reversed. A row that is real and wrong should be edited, and a row that is real and unpaired should be merged.

Sources

Every figure on this page was checked against the source below on 13 November 2026.

  1. How to merge and split transactions manually. Koinly help centre, checked 13 November 2026
  2. How Koinly handles transfers between your own wallets. Koinly help centre, checked 13 November 2026
  3. What are transactions in Koinly. Koinly help centre, checked 13 November 2026
  4. CRYPTO22100, Capital Gains Tax, what is a disposal. HM Revenue and Customs, checked 13 November 2026
  5. CRYPTO22280, Capital Gains Tax, fees satisfied in tokens. HM Revenue and Customs, checked 13 November 2026
  6. CRYPTO22200, Capital Gains Tax, pooling. HM Revenue and Customs, checked 13 November 2026
  7. CRYPTO10400, record keeping. HM Revenue and Customs, checked 13 November 2026
  8. Capital Gains Tax rates and annual tax-free allowances. HM Revenue and Customs, checked 13 November 2026
  9. Self Assessment tax returns, deadlines. GOV.UK, checked 13 November 2026
  10. Taxation of Chargeable Gains Act 1992, section 106A. legislation.gov.uk, checked 13 November 2026
Fahad Zar, photographed against a plain background, head and shoulders

Fahad Zar

Crypto tax accountantAAT licensed 1010475

  • AAT Licensed Accountant and MAAT, licence 1010475
  • MSc Accounting and Finance, BPP University London
  • Six years inside digital asset accounting, across several crypto tax firms
  • Practises through Zar Enterprises Ltd, ICO registration ZC225094
  • Supervised for anti-money laundering by the AAT

What matters to me is that the number on the return is true, whatever it turns out to be.

Whether this is worth a conversation

Where this stops being a reading job and starts being a hiring one.

  • Unpaired transfers run into the hundreds across exchanges and chains, or one side of them sits on an exchange that has closed
  • Wraps, bridges and liquidity positions are mixed in with the transfers and you are not sure which merges are disposals
  • A merge somewhere in several years of history may have hidden a real sale and the return is due by 31 January 2027

If the unpaired rows are between wallets you can name, the merges give transfers with the balances you expect, and no Exchange row surprises you, you have fixed it yourself. Note each merge and edit with its reason and file.

If one of these is you, the first look costs nothing.

Claim the free health check

Read next

Similar Posts