A Bitcoin mining pool can show rewards earned, a payout sent and a balance still waiting for payment at the same time. These figures describe different stages. To reconcile them, choose one account and reporting period, preserve the original exports, then match completed payouts to the receiving wallet. Comparing a dashboard's lifetime revenue with today's wallet balance will rarely answer the question you actually need to resolve.
This guide proposes an operational recordkeeping workflow for existing miners. It uses public pool documentation checked on November 18, 2026, and an explicitly fictional arithmetic example. It does not use customer transactions, predict earnings or establish tax treatment. Pool interfaces and account-specific restrictions can change; retain the documentation applicable to the records you are checking.
1. Separate rewards, payouts and wallet receipts
Start with three record sets: rewards credited by the pool, payouts initiated or completed by the pool, and receipts recorded by the destination wallet. Add the pool's opening and closing unpaid balances. Your first objective is to identify what each field measures before adding anything together.

F2Pool's revenue documentation distinguishes total income, paid revenue, unpaid balance and estimated current-day revenue. It also explains that a daily revenue row can describe the preceding day's activity. Consequently, a row label and the time money reaches a wallet need not represent the same interval. Do not treat an unfinished daily estimate as a settled credit.
Create a short scope note above your worksheet: pool, account or subaccount, coin, payout method, start and end times, time zone, and export time. Keep the original timestamp alongside any converted local time. A month ending at midnight UTC differs from a month ending at midnight in Shanghai. Either reporting convention can be documented; switching between them inside one calculation creates avoidable differences.
| Record | Question it answers | Keep beside the amount |
|---|---|---|
| Reward entry | What did the pool credit for this period? | Account, reward date, status and unit |
| Pool balance | What remains unpaid at the cutoff? | Snapshot time and any pending adjustments |
| Payout entry | What payment did the pool process? | Method, status, destination and reference |
| Wallet receipt | What arrived at the intended destination? | Amount, confirmation or credit status, reference |
Braiins documents history exports with a selected date range, record type and format. Preserve each downloaded original, then work from a copy. Record the selected filters and account, particularly when an export contains multiple financial accounts. An empty result needs investigation; it is not automatically evidence of zero earnings.
Hardware identity belongs in a separate asset record. Our worker naming and asset-register guide helps connect a machine to its pool account. For example, the catalog item below identifies a specific ASIC model; its photograph and specifications cannot establish which account received its work or which wallet received a payout.
Antminer S21 XP 270 TH/s

Air-cooled Bitcoin ASIC. Match your own unit and worker to the correct account; the model does not identify a payment destination.
2. Match each payout to its actual destination
Work from an individual payout row to the corresponding receipt. Check the coin and payment method first, then the destination, amount and payment reference. Preserve the pool's status verbatim in your working record rather than translating every state into “received.”

Braiins' payout API documentation separates on-chain and Lightning records and exposes fields for status, amount in satoshis, fees, destination and timing. Its transaction ID field is for on-chain payouts. These fields are useful examples, not a universal column schema: map the exact export you receive, and read its definitions before deciding whether a displayed amount includes a fee.
For an on-chain payment, open the transaction reference and locate the output corresponding to your intended destination. A transaction's total output value may include other recipients or change. The Bitcoin developer guide explains that transactions contain outputs with their own amounts and positions. Match the relevant output, rather than copying the transaction total into your receipt column.
Keep one unit throughout the worksheet. One BTC equals 100,000,000 satoshis. If the pool exports satoshis and the wallet displays BTC, retain both the original value and a clearly labelled conversion. Do not round intermediate BTC values to two decimal places. Also separate coin reconciliation from any later fiat valuation; a change in exchange rate does not explain a missing quantity of BTC.
A transaction reference is not sufficient by itself to prove that a custodial account credited the intended user. Match the receiving service's deposit record too. Conversely, a Lightning payout should be checked with the provider's Lightning payment record; do not invent an on-chain TXID for it. Treat an unavailable reference as a documented gap and use the relevant service's support process.
When investigating an unpaid amount, begin with the account's displayed reason and applicable payout rules. F2Pool's official support guide describes where to inspect revenue and TXIDs and notes that BTC payout thresholds can be configured. A balance below a threshold is a different situation from a completed payment missing at the destination. Neither observation alone justifies changing the machine's firmware.
If the destination recently changed, use our payout-address verification checklist alongside this worksheet. Preserve the old and new effective periods privately. Do not change an address merely to make two screenshots look consistent; first establish which address applied to the payout under review.
3. Explain differences and preserve the closing record
After matching individual payments, compare the period's balance movements. A useful reconciliation starts with opening unpaid balance, adds credits and documented adjustments, then subtracts recorded balance debits. Classify each fee once according to the source records. If a fee is already included in a debit, subtracting it again creates a false shortfall.

The following fictional example defines its own accounting convention solely to demonstrate arithmetic. Assume a pool records a payout debit that includes both the recipient amount and a separately disclosed payout fee. This is not a claim about any particular pool's export semantics or expected mining return.
| Illustrative movement | Satoshis |
|---|---|
| Opening unpaid balance | 120,000 |
| New credited rewards | 80,000 |
| Total balance debit for one payout | 150,000 |
| Closing unpaid balance: 120,000 + 80,000 − 150,000 | 50,000 |
| Disclosed fee within that payout debit | 1,000 |
| Recipient amount: 150,000 − 1,000 | 149,000 |
In this example, the wallet receipt is smaller than the pool's total debit without any missing payment. In a different export, the payout amount might already be net of the fee. Read the definitions and reconstruct the movement before reusing the formula. Add separate rows for genuine reversals, internal transfers or other adjustments only when the source records support them.
Keep unresolved items in an exception list with the original reference, amount, observation, evidence needed, owner and next review date. Useful categories include a period-boundary mismatch, a pending payment, a fee-definition question, a destination mismatch and an unavailable export. Avoid hiding an unresolved difference in a generic “other” line just to force the totals to agree.
Close the record by saving original exports, your mapping of fields, the calculation sheet and a dated explanation of each exception. Mark whether the closing balance agrees with the source snapshot. Carry that same closing balance into the next period's opening balance, with an explicit adjustment if later evidence changes it. Keep a revision trail instead of replacing the earlier file silently.
For a support request, provide the account reference, coin, relevant interval and time zone, payout reference, destination evidence and a concise description of the mismatch through the service's official channel. Do not attach passwords, API tokens, private keys or recovery phrases. Retain complete originals privately and redact only the copy you share.
Frequently asked questions
Should daily pool rewards equal daily wallet receipts?
Not necessarily. Unpaid balances, thresholds, processing and reporting cutoffs can separate the earning period from the receipt date. Compare like-for-like records and explain the balance movement.
Does a matching payout prove the miner is profitable?
No. This workflow checks payment records. Electricity, equipment, hosting, maintenance and other costs require a separate operating assessment. A receipt is not a net-profit figure.
Can I use a hashrate screenshot instead of a payout export?
No. Hashrate describes work over a measurement interval, while payout records describe payments. See our miner-versus-pool hashrate guide for that separate comparison.
What should I do if records still disagree?
Keep the item open, preserve the original evidence and ask the responsible service to clarify the specific field or payment. Do not invent a balancing entry or assume a hardware fault without supporting evidence.
Planning an ASIC purchase or a deployment change? Review LeedMiner's miner catalog and send the exact model, quantity, location and operating requirements with your inquiry. Keep equipment selection separate from the private pool and wallet records used to reconcile your existing operation.





