CARF, exchanges and wallets: keeping track of your LLC's crypto assets

Follow 25,000 USDC across two exchanges and a company wallet, with complete balances, separate gas fees and a dollar settlement you can check.

CARF turns activity handled by exchanges and other crypto providers into structured information by user, asset and transaction category. A US LLC needs a deeper record: one that can reconstruct each movement, establish who controls every account or wallet, and explain why value was received, transferred, exchanged or retained by the business.

That distinction matters whenever a company uses more than one venue. An exchange export is not the LLC’s complete books, and a blockchain history does not identify the commercial purpose behind every transfer. If the business combines Kraken or another exchange, self-custody, USDC collections, USD settlement and EUR banking, the records must connect those channels without turning one internal transfer into two economic events.

A properly structured LLC gives the activity a stable legal centre. It owns the accounts, signs the provider agreements, invoices clients, holds treasury and authorises transactions. The objective is not to design the company around a reporting file. It is to create a business record that remains intelligible when providers, networks and reporting formats change.

The CARF view and the company view are not the same

The OECD’s Crypto-Asset Reporting Framework identifies three broad families of Relevant Transactions:

• exchanges between Relevant Crypto-Assets and fiat currencies;
• exchanges between one or more Relevant Crypto-Assets;
• transfers of Relevant Crypto-Assets, including certain retail payment transactions.

The 2025 CARF XML Schema translates those families into a defined data structure. For each crypto-asset type, it can carry acquisitions and disposals, inbound and outbound transfers, transaction counts, units, aggregate amounts and valuation currency. It also accommodates categories such as staking, crypto loans, wrapping, collateral, payments for goods or services and transfers to wallets not known to belong to another financial provider.

The LLC’s own record must preserve the economic detail behind those totals:

CARF provides a standardised annual view from the provider’s perspective. The company must be able to move from an aggregate figure back to the transaction that created it.

Why two accurate exports rarely line up immediately

An exchange and a blockchain describe the same movement from different points in time. The exchange may timestamp a withdrawal when it accepts the instruction. The network confirms it later. The receiving wallet records the net amount after the fee, and a second exchange assigns another deposit ID when the assets arrive.

Other differences are equally common:

• one provider labels an asset USDC, while another distinguishes USDC on Ethereum, Solana or Base;
• fees may be charged in the transferred asset, a separate token or fiat;
• a swap can appear as one order in the interface but create two economic legs;
• one recurring order may contain several executions;
• stablecoin settlement may occur slightly above or below one dollar;
• a bridge can burn one token and mint a representation on another network;
• one export uses UTC and another uses the user’s local time zone;
• a provider may enrich or correct a transaction after the first export.

These differences do not make either source unreliable. They mean the business needs a shared set of identifiers and reconciliation rules.

Twelve fields that make the record durable

Each movement should retain at least the following layers:

1. Original identifier. The source trade, order, deposit, withdrawal or movement ID.
2. Source system. Exchange, custodian, wallet, payment processor, bank or protocol.
3. Legal owner. The LLC, its owner or another counterparty. Filename and login email are not enough.
4. Date and time. Original timestamp, time zone and a normalised UTC value.
5. Asset identity. Name, symbol and, where necessary, network and token contract.
6. Gross and net units. Amount sent, amount received and amount withheld as a fee.
7. Event type. Purchase, sale, swap, collection, payment, own transfer, contribution, distribution, reward, loan, collateral or another reviewed category.
8. Fiat value. Amount, currency, price source and exact valuation time.
9. Fee. Asset, units, value and the nature of the charge.
10. Address and transaction hash. Origin, destination and on-chain reference where available.
11. Matched movement. The identifier linking both sides of a transfer owned by the LLC.
12. Business evidence. Invoice, agreement, supplier document, treasury decision or corporate approval.

No single platform will supply every field. Reconciliation brings them together while leaving the original evidence untouched.

A reliable exchange-to-wallet workflow

Build the ownership map first

List every account and address used during the period. Record the legal owner, provider entity, account ID, network, assets and opening or closing date.

A wallet controlled personally by the owner does not become an LLC wallet merely because company funds passed through it. If control or assets are contributed to the company, the effective date and legal basis should be documented.

Preserve raw evidence

Download the most detailed history available and retain it unchanged. Store separate trade, deposit, withdrawal, reward and fee exports when the provider offers them. Work from a normalised copy rather than editing the only source file.

A screenshot can support an explanation, but it cannot replace a transaction history containing IDs, units and timestamps.

Normalise without flattening the facts

Convert dates to a common reference while retaining the original time. Standardise symbols only when they identify the same asset. Keep tokens with the same ticker but different contracts or networks separate. Do not round units before the balance is reconciled.

CARF can report units to six decimal places where relevant. The LLC may need greater precision to explain network fees, high-decimal assets and small variances.

Break transactions into economic legs

Buying ETH with USDC includes an outbound USDC leg, an inbound ETH leg and usually a fee. Converting USDC into USD includes a disposal of the token and a fiat receipt. Receiving USDC from a customer is both a commercial collection and an acquisition of a digital asset.

Separate legs keep a broad platform label from obscuring what actually happened.

Match own transfers

A transaction hash is the strongest common reference when it exists, but a robust match should also compare:

• network and asset;
• sending and receiving addresses;
• gross and net units;
• network fee;
• time window;
• withdrawal and deposit IDs;
• ownership of both endpoints.

If both accounts belong to the LLC, record one internal transfer with two sides. Do not create two items of income and do not assume a sale.

For US federal tax purposes, the IRS digital asset FAQs state that moving assets between wallets or accounts owned or controlled by the same taxpayer is not itself taxable. Digital assets used or withheld to pay transaction services require separate treatment.

Reconcile units before valuation

Opening units plus acquisitions and inbound movements, less disposals, outbound movements and fees, should explain the closing units of each asset at each location. Only then should fiat values be reconciled.

Unit-first reconciliation catches missing rewards, fee deductions, bridge movements, pending deposits and wrong-network transfers that an amount-only review can miss.

Keep exceptions visible

Do not force a category when evidence is missing. Maintain a short exception list with a precise reason: unknown wallet owner, missing hash, unit difference, unidentified token, deposit without a counterparty or transaction without a reliable valuation.

An exception is resolved by obtaining evidence, not by assigning a generic code that happens to make the totals balance.

Worked example: tracking 25,000 USDC across two exchanges and a wallet

This is an illustrative example, not a client case or a provider quote. All prices and fees are assumed to make the calculation explicit. The LLC owns both exchange accounts and the wallet. It uses USDC on Ethereum and already holds 0.010 ETH in the wallet for gas. There are no other movements during the example.

Four steps, three separate charges

1. Purchase. The LLC spends 25,000 USD to acquire 25,000 USDC on exchange A. Assume execution at 1 USD per USDC with no purchase fee.
2. Withdrawal. Exchange A debits 20,000 USDC: it sends 19,998 USDC to the wallet and retains 2 USDC as its withdrawal fee. The LLC pays no additional charge for that withdrawal. This is an exchange fee, not a claim that Ethereum gas is paid in USDC.
3. Own-account transfer. The wallet sends exactly 8,000 USDC to exchange B, which credits the full amount without a deposit fee. The wallet pays 0.001 ETH in gas from its separate reserve. The Ethereum gas documentation identifies ETH as the currency used for network fees.
4. Sale for dollars. Exchange B sells 5,000 USDC at 1 USD each. Gross proceeds are 5,000 USD; it deducts a 5 USD trading fee and credits 4,995 USD. The 1:1 price is an assumption for this example, not a guaranteed conversion rate.

Where every USDC ends up

These are balances after each step, not transaction amounts to add down the table. Every number in the table is denominated in USDC.

The closing position reconciles separately for each asset:

• USDC: 25,000 - 2 - 5,000 = 19,998 USDC. This equals 5,000 + 11,998 + 3,000 across the three locations.
• USD at exchange B: 5,000 - 5 = 4,995 USD available. The original 25,000 USD was spent on the purchase and is no longer a cash balance.
• ETH in the wallet: 0.010 - 0.001 = 0.009 ETH. Gas is not deducted again from the USDC balance.

The two own-account transfers change where the assets sit, not who owns them. The sale converts 5,000 USDC into dollars; the 4,995 USD received is not automatically profit. The result depends on the acquisition cost and the applicable treatment of each charge.

Connecting the example to CARF records

Where a provider is subject to CARF, its categories distinguish acquisitions, disposals and transfers. Adding them all together will not produce a sales figure or an asset balance. Nor should an interface's gross withdrawal amount be copied unexamined into a reporting field: retain the actual units transferred and the separate fee.

The evidence needed here is specific: the purchase execution, the withdrawal receipt showing 2 USDC retained, each transfer hash, the 8,000 USDC deposit and the sale settlement showing the 5 USD fee. The gas transaction has its own ETH amount. Together these records explain the entire movement of funds without duplicate income or missing costs.

Stablecoins still need an asset record

USDC, USDT and other stablecoins can support collections, supplier payments, international treasury and access to digital markets. They are highly useful financial tools for an LLC, but they are not simply a bank cash line.

The record should identify:

• issuer and specific token;
• blockchain and contract;
• units received or transferred;
• market value used at that time;
• fee and the asset used to pay it;
• the commercial, financial or internal reason for the movement;
• any later conversion into USD, EUR or another asset.

CARF carries aggregate values and permits alternative valuation methods where a direct market value is not used, including book value, a third-party value, a recent provider valuation or a reasonable provider estimate. The LLC must maintain its own valuation policy and apply it consistently for the accounting and tax rules that govern it.

A dollar reference does not eliminate small differences between the invoice, the tokens received and the eventual settlement. Price, spread and fees should explain those differences rather than being rounded away at 1:1.

Self-custody with corporate evidence

CARF specifically contemplates transfers to wallet addresses that the provider does not know to be associated with another virtual asset service provider or financial institution. The schema carries aggregate units and value sent to those wallets. That reporting category does not make the transfer a sale and does not, by itself, establish who economically owns the destination.

For each corporate self-custody wallet, retain:

• address and network;
• activation date;
• business purpose;
• authorised operators;
• approval and recovery policy;
• evidence that the LLC controls the wallet;
• links to exchange accounts and company records.

Private keys and recovery phrases should never be placed in an accounting file. Control can be evidenced through corporate records, verification transactions, operating policies and consistent transaction history without weakening key security.

Swaps, wrapping, staking and collateral deserve separate treatment

The CARF schema provides additional types for staking, crypto loans, wrapping and collateral. Those distinctions reflect genuine economic differences. An outward movement may be:

• a final exchange into another token;
• a temporary collateral deposit;
• assets committed to earn rewards;
• a wrapped representation of value on another network;
• a loan advanced or repaid;
• a fee or service payment.

The provider’s label is useful evidence, but not the whole conclusion. Agreements, protocol terms, economic rights and return movements allow the LLC to determine the correct accounting and tax treatment in the relevant jurisdiction.

Receiving a business payment in USDC

Suppose a customer pays a 4,000 USDC service invoice. The company should connect:

1. engagement or order;
2. invoice issued by the LLC;
3. payment address supplied to the customer;
4. transaction hash and receipt time;
5. fiat value on receipt;
6. subsequent movement of the asset;
7. conversion or retention as treasury.

If the USDC is later sent to an exchange and converted into USD, the collection and the conversion are separate events. If it remains in the wallet, it remains an LLC asset. If it pays a supplier, the expense needs its own invoice or evidence.

This chain makes stablecoin collections a professional business process rather than a parallel flow disconnected from the company.

Why an LLC strengthens international crypto operations

An LLC provides a durable legal identity around financial tools that change quickly. It can hold corporate exchange accounts, self-custody wallets, contracts, payment channels, USD banking, EUR access and digital-asset treasury within one business structure.

The arrangement is strongest when:

• exchanges and wallets are expressly assigned to the LLC;
• owner funding enters as a documented contribution or financing event;
• withdrawals are recorded according to their real nature;
• the company keeps its own exports and is not permanently dependent on one platform;
• each movement has a business purpose;
• investing, collections and working capital remain analytically distinct;
• activity and tax residence are reviewed professionally.

CARF does not remove the legal privacy, asset separation or operating range of an LLC. It requires a clear view of which provider reports, which user it identifies and which transaction aggregates it carries. A well-run structure has more options because it can explain how those options are used.

How Exentax helps

Exentax goes far beyond forming an LLC. We design the complete operating architecture so that the entity, banks, processors, exchanges, wallets, USD, EUR and stablecoins all belong to the same commercial reality.

We review account ownership, provider entities, residence, corporate evidence and flow of funds. We help determine which accounts the company needs, how treasury differs from investment and which records allow collections, transfers, swaps and conversions to be understood precisely.

Our work combines international structuring, tax, banking and operations. The client receives an LLC prepared to use serious financial tools, not an isolated company with no connection to the way it collects, invests or pays.

For the first-cycle timeline, read DAC8 records for 2026 and the 2027 exchange. To separate provider, transfer and reporting, continue with MiCA, DAC8 and the Travel Rule. For collections and settlement, see payment gateways, stablecoins and a US LLC.

Questions about reconciling crypto records for CARF

Does CARF report every individual transaction?

The standard exchanges aggregate information by user, asset and transaction category. Providers retain underlying records under the applicable rules. The LLC needs transaction-level detail to explain those aggregates and prepare its own accounts.

Is an own-wallet transfer counted twice?

It should not become two economic transactions. It can appear as an outbound movement in one source and an inbound movement in another, but hash, units, timing and ownership allow both sides to be matched. Record the network fee separately.

Does CARF treat a self-custody withdrawal as a sale?

No. CARF includes a reporting category for aggregate transfers to wallets not known as another provider. The economic nature still depends on who controls the destination and what happened to the asset.

Is a stablecoin always recorded at exactly one dollar?

That should not be assumed. Retain the actual valuation, spread and fees. CARF also recognises alternative valuation methods where relevant.

Is a year-end exchange export enough?

Not always. The exchange may not know who owns every wallet, which invoice a payment satisfies or whether an inbound movement is a contribution. Periodic reconciliation preserves context while it is still available.

Does a US LLC automatically fall within CARF?

Not because it was formed in the United States. The provider’s reporting nexus, the entity user’s identity, residence and classification, and where relevant its Controlling Persons must be assessed.

Can an LLC use exchanges, self-custody and stablecoins coherently?

Yes. The combination can be highly effective when ownership, authority, wallet security, valuation and business evidence are aligned from the start.

From crypto movements to a readable financial structure

Crypto reconciliation is not about producing a perfect file for an authority. It is about ensuring that the LLC knows what it owns and can follow value across customers, exchanges, wallets, banks and suppliers without losing ownership or context.

That discipline supports stablecoin collections, treasury diversification, investment and international operations with stronger control. CARF provides a reporting language; professional structuring turns it into clear business decisions.

Organise my LLC crypto operations