How to Find, Map, and Review Internal Crypto Transfers

Use this guide when crypto moves between wallets or exchange accounts owned by the same entity. Find the related records, mark the movement as an internal transfer, and check that its cost basis carries across.

An internal transfer moves an asset you already own. It does not create a new purchase or sale. Cryptoworth treats a correctly mapped internal transfer as non-taxable. Network fees remain separate and follow your fee accounting settings.

For example, you bought 50 USDC for $45, then moved the 50 USDC to another wallet you own. The transfer carries the $45 cost basis. It does not reset the cost basis to the asset's current market value.

Cryptoworth can identify transfers during a connection sync or by matching records across connections afterward. Both sides should belong to the same entity and be in the same portfolio.

The matching engine compares the asset, amount, timestamp, transaction reference, and send/receive direction. Wallet-to-wallet matching also uses the from and to addresses. Exchange records may lack reliable addresses, so exchange matching can use the other details.

The internal-transfer marker, classification, and calculation result serve different purposes. The marker identifies the movement. The classification controls its accounting treatment. The calculation shows the cost basis carried between the records. Check all three when you review the result.

Click Settings, then choose Internal Transfers in Entity Settings.

Select Auto-mark internal transfers. Detected transfer movements receive an internal-transfer tag; fee transactions are excluded from this tagging.

Click Save under Auto-mark internal transfers.

Go to Subledger > Reconciliation. Use Sync & Reconcile to update the records, then wait for the work to finish. Review both connections in Data Sanity Check. A balance-only connection does not provide the full transaction history needed for matching.

Connect or import any missing wallet or exchange history before matching a transfer. A Synced status alone does not mean that all reconciliation gaps are resolved.

Open Transactions and stay on Crypto Transactions.

Click All Filters.

Click Select field, search for Internal transfer, and choose Internal Transfer.

Set the operator to Is and the value to True. Click Apply in the value picker to keep that choice.

Click Apply at the bottom of the Filters window.

Review the returned records. If the table says No transactions match your filters, it means this view found no marked records. It does not prove that no transfers took place.

The sample entity has no marked records in this view. The next section explains what to check when an expected transfer is missing.

Compare the source records before changing a tag.

If a swap, bridge, or wrapped asset makes the movement unclear, confirm its treatment with your accounting team before marking it as an internal transfer.

In Settings > Internal Transfers, select Enable internal transfer detection time gap if you need to set the allowed gap.

Enter the approved number of minutes. The screen shows a default of 5 minutes. Use a gap that fits the source records; a wider gap can make unrelated records look similar.

Click Save below the time-gap setting.

Return to Transactions. Click Clear all filters in the empty result, or Clear all beside the filter chips, so you can find the unmarked records.

Use the asset, date, and connection filters to narrow the table to the movement you need to review.

Use Map internal transfer after you have confirmed ownership and the related records.

If the receives already exist as separate records, use the one-to-many mapping. You do not need to split the outgoing record just to select those receives.

Use the row checkboxes to select the outgoing record and its related incoming record or records. The screenshot illustrates a two-record selection.

In the selection toolbar, open Bulk Action, then choose Map internal transfer.

Review the asset, amounts, dates, transaction references, and From → To addresses. Compare Incoming total with Outgoing. A green Match confirms the quantity total; it does not confirm common ownership or prove that the records belong together.

The sample screen illustrates the review controls. Confirm the source evidence for your own records before proceeding. Do not map unrelated records because their quantities happen to match.

When the mapping is correct, select I understand the implications of this change and I accept to make this change.

Click Map internal transfer. The dialog states that mapping marks these records as an internal transfer and not taxable. Return to the records and verify their marker and behaviour, then review a new calculation in section 6.

Other pairing options: Pair as Internal Transfer is the two-record cost-basis pairing option. Use a non-taxable transfer classification for that workflow. Pair as Swap serves a different purpose: regular pairing uses outgoing proceeds as incoming cost.

For more detail, see How to Pair Transactions.

Split a record when one imported line combines amounts that need separate review or classifications. For example, a 2,000-token batch might contain 1,200 tokens sent to your own wallet and 800 tokens paid to a supplier. Only the owned-wallet portion is an internal transfer.

Use the allocation in your source records. The amounts below illustrate the form; they are not an approved allocation for the sample transaction.

Clear the earlier selection and select only the original record you need to split.

Open More in the selection toolbar, then choose Split Transaction.

Set Split Into to the number of parts. Under Split By, choose Amount to enter exact token quantities. You can use Percentage when your source allocation is in percentages.

Enter the first part's quantity. In this form example, entering 1,200 leaves 800 of the original 2,000.

Click Add Remainder to put the remaining quantity in the last part.

Confirm that the parts add to Original Amount and Remaining Amount is 0. For a percentage split, the parts must add to 100%.

Leave Fees as Separate Transaction selected when the original record has a fee that must be retained. The form states that disabling this option ignores the fee.

Open each part's Unclassified menu and choose its approved classification. Use a non-taxable internal-transfer classification for the owned-wallet part. Use the correct expense, payment, or other classification for an external part.

Classification names depend on your entity. If the app says no classifications are mapped to the crypto ledger, complete the setup described under If classifications are unavailable before continuing.

After checking the quantities, classifications, and fee option, click Split Transaction. Review the resulting parts, then map only the internal part to its matching receive using section 4.

Do not create another manual send or receive for a movement already represented by the split records. Keep the source reference with the parts so the allocation can be checked later.

Clear investigation filters and select the intended calculation scope, including the records needed to trace the transfer. Click Calculate in Transactions.

Confirm Calculation Mode and Cost Basis Flow against your reporting policy. Per Asset pools inventory by asset across connections. Per Connection keeps separate inventory pools, so the transfer link is important when tracing the receiving wallet's cost.

Leave Publish the Result unchecked. Leave Use only filtered transactions as inventory unchecked unless you intend to exclude earlier acquisitions outside the filters.

Click Calculate in the form and wait for the run to finish. Open that completed run in Subledger > Calculation.

Open Checks. Review any missing inventory, cost-basis mismatch, or other relevant exception before approving the result. Correct the source problem and recalculate when needed.

The sample run has unresolved exceptions. It illustrates where to review them, not a completed transfer correction.

Open Result > Internal Transfers in the same run. Search by transaction ID or hash when needed. Review Outgoing, Incoming, Amount, Basis Removed, Basis Carried, Status, and Evidence.

Confirm that the expected records are included and that the carried basis reflects the source inventory. Review fees separately. The transfer itself should not create a taxable gain or loss.

The sample view contains no internal-transfer events. If you see this after making a correction, confirm that you opened a new run that includes the corrected records. Use the new run to verify the cost-basis effect of your correction.

Keep the run ID, source transaction references, any split allocation, and your review notes together. Publishing transaction values and running GL Sync are separate steps after approval.

If the app says You have not mapped any classifications to the crypto ledger, close the notice. Ask your entity administrator to complete the crypto-ledger classification mappings, then reopen the classification menu.

See How to Map Cryptoworth's Native General Ledger for the setup workflow. Confirm that the classification you use for internal transfers has Non-taxable behaviour.