Tax Records Archives - LadyChain

Accounting for Staking Rewards

Tue, 27 Oct 2026 16:02:49 +0000

Staking rewards accounting begins with an awkward fact: value arrived in your wallet without a sale, a trade, or an invoice. Nothing was bought, yet something was earned, and the earned thing needs a number attached to it before it can be reported.

For most individual filers, staking rewards accounting means keeping two linked records — ordinary income at the moment the reward becomes controllable, valued in your functional currency at that moment, and a cost basis carried forward from that same value. The first number is the one people get wrong, and it is the one that cannot be reconstructed a year later.

Income and basis are the same number. What you report at receipt becomes what you subtract at disposal; if one is fudged, the other is wrong too.
Frequency matters, not just the total. Twelve small receipts at different prices produce a different result from one annual receipt of identical size.
Rewards paid in a second token are a separate asset. Track quantity, price and basis per asset, not per wallet.
Auto-compounding still creates receipts. Value received and immediately redeployed is value received, whether or not it ever sat still in your balance.

Why staking rewards accounting is harder than dividend reporting

A dividend arrives as cash in a currency with one price, on a published date, in a round number. A staking reward arrives as a protocol token, often every epoch, sometimes in a token you did not choose, at a price that moved while you slept.

Three properties do the damage. Receipt is continuous rather than discrete, so there is no single date to point at. The asset received is usually the same asset you staked, so the wallet balance barely appears to change. And the value is denominated in something you never transacted in, which means every receipt requires a price lookup from a source you should be able to defend later.

The three events that create an entry

Almost every entry in a staking ledger traces back to one of three events: receipt, disposal, or penalty.

Receipt

Receipt is the moment the reward becomes yours to move. For most networks that means it lands in an address you control, not the moment a validator was assigned the work. Record quantity, asset, timestamp, and the price in your functional currency at that timestamp.

The price source matters. A single exchange’s last trade at 03:00 on a low-volume pair is a weaker number than a volume-weighted average across several venues, so pick one reference and stick to it.

Disposal

Disposal is any moment the asset leaves your control in exchange for something else — a sale, a swap, a payment, or a conversion to another token. Here you realise gain or loss equal to proceeds minus the basis accumulated at receipt.

Swaps are the trap. Trading token A for token B is a disposal of A in most jurisdictions, even though no fiat ever touched the transaction. The gain is measured in your functional currency, not in the token you received.

Penalty and slashing

A slashing event reduces your staked balance without a disposal, and treatment varies. Some frameworks treat the loss as a capital loss on the underlying, others as a reduction of previously recognised income, and some are silent. Rules differ by jurisdiction, so this is a question for a local adviser rather than a general article.

Choosing a staking rewards accounting method

The method you pick determines which basis gets consumed first, and therefore how much gain lands in a given year. It is a choice worth making deliberately rather than by default.

FIFO, LIFO and specific identification

First-in-first-out consumes your oldest basis first and is the default in many frameworks. Last-in-first-out is permitted in fewer places and often needs explicit election.

Specific identification lets you point at particular lots, which is the most flexible and the most demanding. It requires lot-level records from the beginning — you cannot reconstruct lot identity after the fact from an aggregated balance.

Pooled or per-wallet tracking

Pooling treats all units of one asset across all your addresses as a single balance. It is simpler and usually adequate for a personal portfolio. Per-wallet tracking is more precise and becomes necessary if you run separate entities, keep business and personal funds apart, or need to explain a transfer between your own addresses.

Transfers between addresses you control are not disposals in most frameworks, but they are the single most common cause of a broken cost basis — because the receiving wallet’s software often treats the arrival as a zero-cost acquisition.

Method	What it produces	Record burden	Common constraint
FIFO	Oldest basis consumed first	Low — chronological list only	Default in many jurisdictions; little flexibility
LIFO	Newest basis consumed first	Low to moderate	Not permitted everywhere; may need an election
Specific identification	Chosen lots consumed	High — lot-level from day one	Must be documented at the time, not later
Weighted average cost	Single blended basis per asset	Moderate — periodic recalculation	Available for some asset classes only
Pooled across wallets	One basis per asset, all addresses	Moderate	Blurs entity boundaries if you hold more than one

A worked year, and the ledger that produces it

Assume a hypothetical delegation of 10,000 units of a token, paying 50 units monthly for twelve months — 600 units in total — at the prices in the table below. Numbers are illustrative, not a rate forecast.

Receipts: January 50 units at 1.00 = 50.00; February at 1.10 = 55.00; March at 1.20 = 60.00; April at 1.30 = 65.00; May at 1.40 = 70.00; June at 1.20 = 60.00; July at 1.00 = 50.00; August at 0.90 = 45.00; September at 1.10 = 55.00; October at 1.50 = 75.00; November at 1.80 = 90.00; December at 2.00 = 100.00. Total ordinary income recognised: 775.00, against 600 units received, an average basis of 1.2917 per unit.

Now sell 300 units at 2.20 for proceeds of 660.00. Under FIFO the 300 units come from January through June — six receipts of 50 units, costing 50.00 + 55.00 + 60.00 + 65.00 + 70.00 + 60.00 = 360.00. Realised gain: 660.00 − 360.00 = 300.00. Remaining basis for the 300 unsold units: 775.00 − 360.00 = 415.00.

Under a weighted average cost approach the same sale would consume 300 × 1.2917 = 387.51 of basis and realise 272.49 — same receipts, same sale, different reported gain.

Fix one functional currency and one price source before the first receipt, and record both in the file header.
Export every reward payout monthly as a raw list of timestamp, asset and quantity, straight from the address’s transaction history.
Attach a price to each line on its own date; never use a month-end price for a mid-month receipt.
Tag each line with the address and the entity that owns it, so pooled totals can be split later if needed.
Reconcile the reward total against on-chain balance changes quarterly; unexplained differences are usually a missed auto-compound or a fee.
Store the file with the price source URLs alongside the numbers, so a reviewer can reproduce any single line.
Re-run the disposal calculation whenever the method changes, and keep the prior output rather than overwriting it.

The post Accounting for Staking Rewards appeared first on LadyChain.

Reading Your Exchange Statement

Tue, 27 Oct 2026 12:02:14 +0000

An exchange statement is a record of what the venue did with your money, not a record of what your money is worth. Those two things diverge constantly, and most of the confusion around statements comes from reading the second meaning into the first.

A good exchange statement answers three questions: what moved, when it moved, and what was charged for moving it. It does not answer whether you made money, because it does not know your cost basis on assets you transferred in, and it does not know what you did elsewhere. Read it as a record of events, and it becomes useful.

Statements describe flows, not performance. Deposits, withdrawals, trades and fees are events. Profit and loss is a derived figure that depends on assumptions the statement does not contain.
Timestamps are usually in one timezone. Most venues record in UTC. A trade at 23:40 UTC lands on a different calendar day in many local timezones, which matters at period boundaries.
Fees appear in two currencies. Some are charged in the asset bought, some in the quote currency. Summing a column without checking the unit produces nonsense.
Reconciliation is the test. Opening balance plus inflows minus outflows should equal closing balance. If it does not, something in the statement is missing or misread.

What an exchange statement is built from

A statement is a rendering of the venue’s internal records over a period. Each line corresponds to a booked event, and the same event can appear more than once in different sections — once as a trade, once as a fee, once as a balance change.

Double counting is therefore easy. Knowing which section is authoritative for which question is most of the skill.

The four sections you will find

Most exports contain a transaction history, a fee summary, a deposit and withdrawal log, and an opening and closing balance. The first is the detail, the second is a subtotal of the first, and the third records movements that never touched the order book.

For activity, use the transaction history. For charges, check the fee summary against the detail. For anything leaving without your knowledge, use the withdrawal log — the shortest and most important section.

Why the statement will not match your screen

Your portfolio view marks holdings to current prices. The statement records historical events at their historical prices. Between the two sits every price change since the event, which the statement has no reason to know about.

Recent activity commonly lags by a day or more, and pending withdrawals can appear in one section before another. Neither is an error; both make same-day comparison misleading.

The numbers people misread on an exchange statement

Three line items cause most of the arguments, and each has a specific reading error behind it.

Realised versus unrealised

Realised amounts come from closed positions and are fixed at the moment of the closing trade. Unrealised amounts move with price and are an estimate at the timestamp on the report. A statement that shows a large unrealised figure is describing a moment, not a result.

A statement run at a different hour of the same day can show a materially different total with no trade in between. Note the generation time when comparing periods.

Fees quoted in the asset, not the currency

Many venues charge a fee in the asset you receive. Buy a small amount of a token and the fee arrives as a slightly smaller amount of that token, not as a separate currency charge. On the statement it may appear as a reduced quantity rather than an explicit cost.

This is the most common source of “where did my fee go” questions. The cost is real, just denominated in what you bought; its currency value at the time of the trade is the figure you need.

Transfers in versus trades

An asset arriving from an external wallet is not a purchase. It has no price on the statement, because the venue never saw the price you paid. Treating an inbound transfer as a buy at the day’s market price will overstate or understate your position by however far your original entry price sits from today.

Reconciling an exchange statement

Reconciliation means proving the closing balance from the opening balance and the events in between. Worked through on a small illustrative account, the method is straightforward.

Start with 10,000 USDC and no other holdings. During the period you buy 2 units at 2,500 each with a 5 USDC fee, sell 1 unit at 3,000 with a 3 USDC fee, and withdraw 500 USDC. Every figure is illustrative.

Opening balance: 10,000.00 USDC, 0 units.
Buy: −5,000.00 for the two units, −5.00 fee. Cash is now 4,995.00, holdings are 2 units.
Sell: +3,000.00 for one unit, −3.00 fee. Cash is now 7,992.00, holdings are 1 unit.
Withdraw: −500.00. Cash closes at 7,492.00.
Closing balance should be 1 unit and 7,492.00 USDC. If the statement says otherwise, find the discrepancy before drawing any conclusion from the period.
Total fees for the period are 5.00 + 3.00 = 8.00, or about 16 basis points on the 5,000.00 of buying and 3,000.00 of selling combined.
Repeat the check against the venue’s own closing balance field; a mismatch there usually means a pending item or a timezone boundary, not a missing trade.

A statement you cannot reconcile is not evidence of a problem, but it is a reason to stop reading the summary and start reading the detail.

Line item	What it records	What people assume it records
Trade history	Fills with price, size and time	Their profit on the position
Fee summary	Charges, sometimes in mixed units	A single currency total
Deposit log	Assets arriving from outside	A purchase at market price
Withdrawal log	Assets leaving, with destination	Only the amounts they remember sending
Closing balance	Holdings at the cut-off timestamp	Value at today’s prices

Using an exchange statement beyond bookkeeping

The statement is also the input to any tax or audit process, and that is where its limits bite hardest. Cost basis methods differ — some jurisdictions use first-in-first-out, others allow average cost, and the treatment of transfers between your own accounts varies.

A venue only sees its own side, so one statement cannot describe assets held elsewhere. Consolidating across accounts is your job, and it is easier monthly than annually.

What to keep and for how long

Keep the full transaction-level export, not the PDF summary. Summaries drop the identifiers you need to match trades across accounts, and retention periods differ by jurisdiction. Check local rules for how long records must be kept; the safe habit is to keep everything and archive it offline.

Name exports with their generation date and keep a copy that does not depend on continued access to the venue. If an account is closed or restricted, the export is all you will have.

The post Reading Your Exchange Statement appeared first on LadyChain.