crypto and taxation.

For Romanian users, terms such as FIFO, CASS, DAC-8 and code 1023 can quickly turn a simple question into a confusing one.

Here are eight concepts worth understanding.

1. Cost basis

Your cost basis is essentially the acquisition cost associated with an asset.

It matters because calculating a gain generally requires comparing what you received when disposing of an asset with the relevant acquisition cost behind it.

Without reliable acquisition records, calculating the result becomes much harder.

2. FIFO

FIFO means First In, First Out.

It is a method of determining which units are treated as disposed of first when someone has acquired the same asset at different times.

For example:

Buy BTC at price A
Buy more BTC at price B
Later sell part of the BTC

FIFO starts with the earliest acquired units.

The current TCS glossary notes that Romanian legislation does not explicitly mandate FIFO as the only permissible method, but describes it as a practical method commonly used for documented transaction-level calculations.

3. Taxable event

Not every crypto action is economically identical.

Buying crypto, holding it, moving it between your own wallets, selling it and paying for something with crypto are different types of activity.

The idea of a taxable event helps distinguish which actions may create a tax calculation from those that primarily change where the assets are stored.

4. Declarația Unică

Declarația Unică, also known as Form 212 or D212, is the Romanian individual tax declaration used for several categories of income.

The current TCS guide identifies it as the form through which Romanian individuals report relevant crypto income.

5. Code 1023

Code 1023 is the income code identified in the current TCS guidance for "transferul de monedă virtuală" when completing Declarația Unică.

It is a small detail, but a useful one to recognize before opening the form.

6. CASS

CASS is Romania's health-insurance contribution.

For crypto users, it is separate from the basic income-tax calculation and can become relevant depending on the applicable income thresholds and personal situation.

That is why two taxpayers with similar crypto activity can still need to look beyond the headline income-tax rate.

7. DAC-8

DAC-8 is the European framework extending automatic tax-information reporting to crypto-assets.

The TCS glossary explains that Romania implemented this reporting framework for crypto platforms, increasing the importance of maintaining records that are consistent with the activity reported by service providers.

For users, the practical lesson is simple:

your own transaction history should be complete.

8. BNR exchange rate

BNR is the National Bank of Romania.

For transactions denominated in foreign currencies, Romanian calculations may require consistent conversion into RON using the relevant historical exchange-rate information.

With a few transactions, this can be done manually.

With hundreds of transactions across many dates, it becomes another reason automation can be useful.

Why these terms matter

Knowing the vocabulary does not turn someone into a tax expert.

It does make the process easier to understand.

Instead of seeing:

FIFO + cost basis + RON valuation + D212 + code 1023

as five unrelated technical terms, you can start seeing one workflow:

Track the acquisition → Track the transaction → Calculate consistently → Convert where necessary → Prepare the Romanian reporting information.

That is the workflow The Crypto Support is trying to simplify for crypto users in Romania.

Full Romanian glossary:

https://thecrypto.support/en/ghid/termeni-fiscali-crypto

This article is educational and does not constitute personalized tax, legal or financial advice.

"I didn't withdraw the money."

"I lost money on other trades."

"My profit was small."

"I already know roughly how much I made."

Those assumptions can become a problem when they replace an actual transaction-level calculation.

Here are five areas Romanian crypto users should check carefully.

1. Looking only at bank withdrawals

One common mistake is assuming that nothing matters until money reaches a Romanian bank account.

But your transaction history can contain relevant disposals before any bank withdrawal happens.

For example, selling crypto for fiat on an exchange and keeping that fiat on the platform does not make the underlying transaction disappear.

The important thing is what happened to the asset, not simply where the cash eventually went.

2. Assuming losses automatically cancel gains

The current TCS guide notes an important peculiarity of Romanian crypto reporting: crypto losses are not entered as a separate deductible category in Declarația Unică and are not treated as a general offset against positive crypto gains in the way some users expect.

That means importing the complete transaction history matters.

Looking only at the final portfolio performance can produce a very different picture from calculating transactions under the Romanian reporting framework.

3. Misunderstanding the small-gain exemption

Romania has a specific small-gain exemption described in the current TCS guide.

The guide states that both conditions need to be met:

• the gain from each transaction is below 200 RON

• total gains for the year remain below 600 RON

The important word is both.

A yearly total below one threshold does not automatically mean every situation qualifies.

4. Keeping only the final number

Imagine your spreadsheet says:

Annual crypto gain: 24,850 RON

Where did that number come from?

Which transactions?

Which acquisition prices?

Which dates?

Which exchange rates?

If you cannot answer those questions, debugging the calculation becomes very difficult.

A better system keeps a path from the final result back to the individual transactions and the original source records.

5. Forgetting that income tax may not be the only calculation

Romanian crypto users may also need to consider CASS depending on the applicable income situation and thresholds.

The TCS guides treat CASS separately from the crypto income-tax calculation and explain it as a threshold-based health contribution rather than simply another percentage applied to every crypto gain.

This is one reason a quick calculation of "profit × tax rate" may not tell the whole story.

Good data prevents most problems

Most of these mistakes share the same underlying issue:

incomplete or misunderstood data.

Keeping complete records throughout the year makes the eventual Romanian tax calculation much easier to verify.

At The Crypto Support, that's exactly the problem we're trying to make simpler for Romanian crypto users.

Read the complete guide:

https://thecrypto.support/ghid/en/greseli-declarare-crypto

This article is educational and does not constitute personalized tax, legal or financial advice.

It starts much earlier, with your transaction history.

For someone who has used several exchanges, wallets or crypto cards during the year, the most difficult part can be reconstructing an accurate picture of what actually happened.

What should you prepare?

Before working on your Romanian tax declaration, it helps to gather:

• transaction exports from every exchange

• deposits and withdrawals

• wallet transfers

• fiat purchases and sales

• crypto card payments

• acquisition records

• supporting bank or exchange statements

The important part is completeness.

Using only the exchange you currently trade on may leave gaps if assets were previously bought or transferred somewhere else.

Why the transaction history comes first

The Romanian Declarația Unică does not reconstruct your crypto activity for you.

You first need to determine the relevant annual figures from the underlying transactions, then use those figures when completing the declaration.

That becomes harder when you have:

• several exchanges

• different CSV formats

• transactions in EUR or USD

• multiple wallets

• swaps

• fees

• missing acquisition information

A few trades can be manageable manually.

Hundreds of transactions are a different problem.

Crypto and RON

For Romanian reporting, transactions ultimately need to be understood in Romanian lei.

That means dates matter.

A transaction that happened months ago may need a historical currency conversion rather than today's exchange rate.

This is why financial data should preserve both the original transaction and the valuation used later in the calculation.

Where does crypto go in Declarația Unică?

The Crypto Support's current guide identifies income code 1023 as the category used for the transfer of virtual currency in Declarația Unică.

For income realized during 2026, the guide currently lists 25 May 2027 as the filing and payment deadline.

This is also why waiting until the last week to collect your transaction history is not ideal.

The calculation should already be ready before you start completing the form.

Keep the records behind the result

A final number is useful.

A final number that you can explain is much better.

Your calculation should ideally remain connected to:

the original transaction,
the acquisition information,
the date,
the valuation,
and the calculation that produced the final result.

That makes mistakes easier to find and corrections easier to make.

What we're trying to simplify

At The Crypto Support, we focus specifically on crypto tax reporting for Romania.

The goal is to make the workflow closer to:

Import transactions → Verify data → Calculate → Prepare the reporting figures

instead of rebuilding an entire year of crypto activity manually in a spreadsheet.

Read the complete Romanian guide:

https://thecrypto.support/en/ghid/declaratia-unica-crypto

This article is educational and does not constitute personalized tax, legal or financial advice.

Before calculating anything, keep records of:

• exchange trade history

• deposits and withdrawals

• wallet transfers

• fees

• fiat purchases and sales

• transaction dates and values

The key point is simple: your current wallet balance is not enough. Tax calculations depend on the history behind it.

For Romanian users, this matters when preparing the information needed for Declarația Unică and other tax reporting requirements.

At The Crypto Support, we are building tools specifically for crypto tax reporting in Romania.

Full guide:
https://thecrypto.support/en/ghid/taxe-crypto-romania

Import your transactions, calculate the result, generate a report.

In practice, the difficult part often starts before the tax calculation itself.

At The Crypto Support, we are building tools for crypto tax reporting in Romania, and one of the biggest technical challenges is turning transaction data from different exchanges into one consistent format.

Why exchange data is messy

Every crypto exchange exports data differently.

One platform may call an operation a “Trade”, another may call it a “Convert”, while another may represent the same activity using several separate rows.

The column names can also be completely different.

One exchange might provide:

Date
Type
Asset
Amount
Price

Another might provide:

Timestamp
Operation
Currency
Quantity
Total
Fee

Even when both files describe the same kind of transaction, a program cannot safely treat them as identical.

Before Romanian tax rules can be applied, the raw exchange data first needs to be understood and normalized.

What normalization means

Normalization means converting different exchange formats into one internal structure that the application can understand consistently.

For example, regardless of which exchange produced the original CSV, the application may need to identify the same basic information:

• when the transaction happened

• which asset left the account

• which asset entered the account

• the amount involved

• any fees

• the source exchange

• the original transaction identifier

• the value of the transaction in RON

Once the data follows one structure, the rest of the system becomes much easier to reason about.

The pipeline can then look something like this:

Raw exchange data → Normalization → Transaction classification → RON valuation → Tax calculation → Report

This separation is important.

The tax calculation should not need to know whether the original transaction came from Binance, Kraken or another exchange.

It should receive a clean, predictable transaction format.

Why dates and currencies matter

Dates look simple until financial calculations depend on them.

Some exchanges use UTC. Others use local time. Some exports include a timezone, while others only provide a date and time.

That matters because the value of a crypto transaction can depend on when it happened.

For Romanian tax reporting, transactions also need to be interpreted consistently in RON.

If a transaction originally happened in EUR or USD, the application needs enough information to determine the relevant value in RON.

When there are hundreds of transactions, doing this manually becomes tedious and error-prone.

Swaps make things more complicated

A crypto swap looks simple to the user.

For example:

BTC → ETH

But software needs to preserve much more information.

It needs to know how much BTC left the account, how much ETH arrived, whether a fee was paid, when the swap happened and how both sides of the transaction relate to each other.

Now imagine a longer sequence:

BTC → ETH → SOL → EUR

The software needs to preserve the history of those operations so that later calculations remain understandable and traceable.

This is one of the reasons crypto tax calculations can become difficult very quickly once users start trading across multiple assets and platforms.

Why the final number is not enough

A financial application should not behave like a black box.

Simply showing:

“Taxable amount: X RON”

is useful, but it is not enough.

Ideally, the user should also be able to understand where that number came from.

A good system should make it possible to trace the result back through the calculation.

Final result → Calculation step → Classified transaction → Normalized transaction → Original exchange record

This becomes especially important when users want to verify a result or when something looks wrong.

If a transaction was classified incorrectly, the application should make it possible to identify it.

If an exchange export contained incorrect or incomplete information, that should also be visible.

Validation matters

Financial software should not blindly accept every row in a CSV.

The system should detect suspicious or incomplete data before it reaches the final calculation.

Examples include duplicate transactions, missing timestamps, unsupported transaction types, missing values or inconsistent swap records.

Sometimes the safest result is not to calculate automatically.

It is to tell the user that a transaction needs to be reviewed.

Global crypto data, Romanian tax reporting

Crypto exchanges are global.

Romanian tax reporting is local.

An exchange does not export a special CSV designed specifically for Romania.

The blockchain also does not know what ANAF or Declarația Unică are.

That local interpretation happens later in the process.

This is why we think it is useful to separate the system into two main questions.

First:

What actually happened in the transaction?

Then:

How should that transaction be handled for Romanian tax reporting?

Keeping these responsibilities separate makes the application easier to maintain and easier to update when requirements change.

What we are building at The Crypto Support

The experience we want for the user is much simpler than the system behind it.

Import.

Verify.

Calculate.

Report.

The user should not need to manually reconcile several incompatible CSV files or build complicated spreadsheet formulas just to understand their own transaction history.

The complexity should be handled by the software while the result stays transparent and traceable.

That is one of the main technical problems we are working on at The Crypto Support: turning messy crypto transaction data into structured information that can be used for tax reporting in Romania.

You can read more about the problem here:

https://thecrypto.support/en/ghid/de-ce-calculator-taxe-crypto

The Crypto Support provides educational information and tooling for crypto users in Romania. This article does not constitute personalized tax, legal or financial advice.