Accounting for Staking Rewards

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.

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.

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