DAC8 in 2026: crypto records for the first 2027 exchange
Prepare the LLC identity, exchanges, wallets, transfers and valuations that explain its real crypto activity throughout the first DAC8 reporting year.
The first DAC8 reporting period is no longer a future milestone. It began on 1 January 2026. Providers within scope are now collecting customer and transaction data for the 2026 calendar year. They will report that information under the applicable domestic timetable during 2027, and EU Member States must complete the first exchange by 30 September 2027.
DAC8 does not turn a US LLC into a European company, prevent it from using digital assets or determine the tax due on a transaction. It standardises an information trail. For a business, the practical objective is to make that trail readable: one legal account holder, clearly owned wallets, complete exchange records and a documented reason for every movement.
That is where an LLC can be particularly effective. It can invoice in stablecoins, hold digital-asset treasury, invest surplus capital, pay suppliers and convert between crypto, USD and EUR. The structure works best when company property remains distinct from the owner’s personal assets and the books can follow each unit without recreating the year from screenshots.
The dates that matter in the first DAC8 cycle
The text of Directive (EU) 2023/2226 and the European Commission’s DAC8 overview establish a sequence rather than one universal filing date:
| Milestone | What happens | Business response |
|---|---|---|
| 1 January 2026 | The first covered reporting period begins | Preserve complete data from the first transaction of the year |
| Throughout 2026 | Providers perform due diligence and collect reportable activity | Keep the entity profile, residence, TIN and account ownership current |
| 1 January 2027 | Deadline in the Directive for completing due diligence on specified pre-existing users | Replace stale self-certifications and resolve contradictory KYC data |
| During 2027 | Providers submit 2026 information under domestic rules | Close the year with raw exports, wallets, valuations and books aligned |
| By 30 September 2027 | Member States complete the first exchange for 2026 | Retain the supporting file that explains the reported aggregates |
The provider’s domestic submission date can fall before 30 September. The September date governs the exchange between tax authorities; it should not be presented as a single provider deadline in every EU country.
The provider reports; the company preserves context
DAC8 places the reporting obligation on a Reporting Crypto-Asset Service Provider, or RCASP. A customer does not prepare the authority-to-authority XML message. The customer does, however, provide reliable due-diligence information and remains responsible for any separate tax, accounting or information return required where it operates or is tax resident.
An LLC account is an Entity Crypto-Asset User. Depending on the facts, the provider may need to establish:
- the LLC’s legal name, address and tax identification number;
- the entity’s tax residence or residences;
- whether it is an Active Entity, another entity category or an Excluded Person;
- the identity, tax residence and TIN of relevant Controlling Persons;
- the role through which each natural person exercises control;
- whether a later change makes an earlier self-certification unreliable.
Formation in Wyoming, New Mexico, Delaware or Florida is not an automatic DAC8 conclusion. A US LLC is not reportable in Europe merely because it exists, and it is not automatically outside the data set merely because it was organised in the United States. The provider’s reporting nexus, the entity’s self-certified residence and classification, and in applicable cases its Controlling Persons all matter. Our separate guide to entity self-certification for a US LLC explains why copying the federal tax classification is not enough.
What the DAC8 transaction record actually contains
The Directive organises reportable information by type of Reportable Crypto-Asset. Where relevant, the provider reports:
- identifying and tax-residence data for the Reportable User;
- entity and Reportable Controlling Person data where the due-diligence outcome requires it;
- the full name of each reportable crypto-asset;
- aggregate gross consideration, units and transaction counts for fiat acquisitions;
- aggregate gross proceeds, units and transaction counts for fiat disposals;
- aggregate fair market value, units and counts for crypto-to-crypto acquisitions and disposals;
- Reportable Retail Payment Transactions;
- inbound and outbound transfers, subdivided by transfer type where known;
- transfers to distributed-ledger addresses not known by the provider to belong to another virtual-asset service provider or financial institution.
Fiat acquisitions and disposals are reported in the currency paid or received, or converted consistently where several currencies are involved. Crypto-to-crypto activity and transfers are valued in one fiat currency at the time of each transaction using a consistently applied method.
It is not a tax return or a conventional account statement
The crypto reporting fields in DAC8 do not include a universal 31 December balance field. They also do not, by themselves, provide the customer’s complete cost basis, net profit, deductible fees or the commercial purpose behind a transfer.
The reporting payload and the LLC’s own books therefore answer different questions:
| Provider reporting layer | LLC recordkeeping layer |
|---|---|
| Aggregate acquisitions and disposals | Individual trades, timestamps, price, fees and supporting records |
| Outbound transfer | Destination wallet and the person or entity that owns it |
| Inbound transfer | Source, counterparty and business purpose |
| Aggregate fair market value | Valuation method used in the accounting and tax analysis |
| Identity and tax residence | Current corporate documents and signed self-certification |
| Transaction count | Full history capable of exposing duplicates or missing periods |
Gross disposal proceeds are not taxable profit. A transfer is not necessarily a disposal. An owner contribution is not trading revenue. The provider’s aggregate data must be interpreted through the company’s actual transactions.
Eight records worth maintaining from day one
1. A versioned entity profile
Keep the exact legal name, EIN, formation jurisdiction, principal address, current Operating Agreement, members, managers and authorised persons. Record the effective date of every change rather than overwriting the former structure.
2. A provider register
For every exchange or custodian, identify the contracting legal entity, jurisdiction, account ID, opening date, verified account holder, entity classification and assigned deposit addresses. The brand on the app does not always identify the legal provider behind a particular product.
3. Complete raw exports
Retain CSV, statement or API output showing original timestamps, asset, network, units, price, fiat currency, fee, transaction type and provider reference. A provider's summary total is not a substitute for transaction-level history.
4. A corporate wallet register
Record each address, blockchain, purpose, custodian, activation date and key-control policy. Distinguish an LLC wallet from a personal wallet, provider deposit address and customer or supplier address.
5. Transfer matching
Pair the exchange withdrawal with the corresponding wallet receipt using transaction hash, date, units and network fee. A movement between two wallets owned by the LLC remains an internal movement even where a provider includes it in transfer aggregates.
6. Valuation and tax lots
Store the fiat value assigned at transaction time and the cost method required for the books or relevant tax residence. A provider’s DAC8 valuation does not necessarily supply every figure needed for a local tax calculation.
7. Commercial evidence
Connect customer receipts to invoices, supplier payments to bills and investment transactions to treasury decisions. The blockchain proves that value moved; the commercial file explains why the company moved it.
8. A period-end inventory
Reconcile units by asset and wallet. Although the DAC8 transaction payload has no universal year-end balance field, opening holdings plus inflows, acquisitions and rewards less outflows, disposals and fees should explain the closing inventory.
A monthly close that remains manageable
Reliable records do not require a complicated internal platform. They require a repeatable sequence:
- Freeze the period. Export the same date range from every exchange, custodian and corporate wallet.
- Preserve original timestamps. Keep the source time zone while creating one normalised accounting view.
- Match own-wallet transfers. Link both legs so the movement is not counted twice as income, expense or disposal.
- Classify external activity. Separate customer receipts, supplier payments, trades, swaps, rewards, owner funding and distributions.
- Reconcile units. Opening units plus additions less reductions and network fees must lead to the closing position.
- Resolve exceptions. Investigate unmatched movements, missing assets and differences between provider and blockchain data.
- Archive evidence. Keep the original export, the working file and supporting contracts without replacing the source data.
This discipline remains useful even where a provider is outside DAC8. It gives the LLC controlled digital treasury rather than a compliance file assembled solely for one European reporting rule.
Four common movements with different meanings
A customer settles an invoice in USDC
The LLC issues the invoice, receives USDC into a corporate wallet and later converts part of it to USD. The sale, token receipt, conversion and bank payout are connected but distinct events. Invoice, transaction hash, exchange trade and bank credit establish the full chain.
The LLC moves BTC into self-custody
Changing wallets does not, by itself, change ownership. The exchange may report a transfer to an address not known to belong to a service provider. A wallet register and matched transaction hash show that the asset remained company property.
The owner contributes digital assets
An owner’s transfer of BTC or USDC should not be treated automatically as business revenue. Date, value, source address, company acceptance and legal character should establish whether it is a contribution, loan or another properly documented transaction. A later payment back to the owner is a separate event.
The company executes a crypto-to-crypto swap
DAC8 includes aggregate acquisitions and disposals against other reportable crypto-assets. The books still need both asset legs, units, timestamp, fee and the tax treatment applicable to the company. The absence of fiat does not make the event disappear.
Why the LLC remains a valuable operating structure
An LLC is more than access to an exchange or bank account. It is a legal account holder that can contract, invoice, own assets, receive investment, pay suppliers and maintain business capital separately from its owners.
Crypto operations become easier to explain when that separation is respected:
- provider accounts are opened in the LLC’s exact name;
- corporate wallets have documented ownership and purpose;
- personal funds enter as evidenced capital or financing;
- owner withdrawals are recorded according to their real legal and accounting character;
- fiat banking, payment processors and digital assets use one coherent business identity;
- the annual tax file starts from the company’s activity rather than an isolated exchange balance.
DAC8 does not remove those advantages. It increases the value of operating through a company capable of explaining its own transactions.
A practical 2026 year-end review
Before the first reporting cycle closes, verify that:
- the LLC name and EIN match across every provider;
- tax residence, TINs and Controlling Persons are current;
- the legal entity providing each account is known;
- exports cover the full year or the period since account opening;
- every corporate wallet has been identified;
- own-wallet transfers are matched;
- contributions and distributions are not mixed with sales;
- crypto receipts are supported by invoices or contracts;
- fees, swaps and rewards are included;
- the closing inventory reconciles to the transaction history.
Recover missing data while provider access and transaction exports remain available. The objective is not to manufacture paperwork. It is to preserve the evidence that already describes a real business.
How Exentax supports a crypto-operating LLC
Exentax designs the complete operating structure: LLC, entity classification, banking, exchanges, wallets, payment processors, currencies and tax documentation. We identify the legal account holder, where the activity is performed, how revenue enters and how value moves before reaching a bank or remaining in digital assets.
We do not treat the LLC as a device for opening one account. It is the legal and operating centre of an architecture that can collect in USD, EUR or digital assets, invest, reinvest and work with international providers under one coherent identity.
For the wider framework, read DAC8, crypto and European reporting. The guide to CARF, exchanges, wallets and stablecoins develops unit-level records and matching between the LLC's own wallets. If the model also uses payment processors, continue with payment processors, stablecoins and LLC records.
Questions about the 2026 DAC8 reporting year
Does an LLC owner file a DAC8 return?
DAC8 reporting is performed by the provider within scope. The LLC and its owners provide accurate due-diligence information and separately comply with the tax, accounting and information obligations that apply to them.
Does DAC8 report a wallet balance on 31 December?
The Directive’s crypto data set focuses on transaction aggregates, units, values and transfers by asset. It does not create a universal year-end balance field. A closing inventory remains essential for the LLC’s own books.
Is a transfer to the LLC’s own wallet a sale?
Not merely because value moved. It may be included in the provider’s transfer reporting, while its economic nature remains an internal movement. Address ownership and transaction matching establish the distinction.
Is every US LLC automatically within DAC8?
No. The provider’s reporting nexus, the entity user’s residence and classification, and where applicable its Controlling Persons must be considered. State formation alone does not decide the outcome.
Does the DAC8 report calculate taxable gain?
No. It communicates aggregate amounts and units. Cost basis, fees, lots, business context and the rules of the relevant tax jurisdiction are still needed.
Can a US LLC continue to collect and invest in crypto?
Yes, where its providers support the activity and the transactions are properly documented. DAC8 is an information-reporting framework, not a prohibition on business use of digital assets.
Better records create more operating freedom
The strongest first-cycle DAC8 file is built through ordinary company discipline: correct account ownership, controlled wallets, complete exports and a clear commercial explanation for each movement.
That discipline does not narrow what an LLC can do. It allows digital assets to function as real business infrastructure with stronger control and more room to grow.