Last checked: November 2026
General information only. Not tax, legal or accounting advice. Treatment and valuation decisions belong with your accountant. Written by the team behind Flash.
Short answer
A pool balance is what the pool has credited to you; a payout is bitcoin that reached your wallet. At month end, keep the unpaid balance as a visible pool-side figure, record received payouts at their value when received, and agree with your accountant whether and how an unpaid balance is recognised.
Why balances and payouts differ
Pools credit rewards to an account or balance and pay out on a schedule or once a threshold is met. Thresholds, schedules, payout fees and queued or failed payouts mean credited rewards and received payouts can differ in any month. A dashboard balance describes the pool side of the record; a wallet receipt describes what arrived.
Keep those two records distinct, and keep the cut-off evidence, so your accountant can decide when mining income is recognised.
Payout thresholds by pool (as published)
| Pool | Published payout settings |
|---|---|
| Braiins Pool | Payouts are created daily at 9.00 UTC. Rules apply per Financial Account: scheduled daily, weekly or monthly, or when the balance reaches a threshold you set. The on-chain minimum payout is 0.0002 BTC. On-chain payouts under 0.005 BTC carry a 0.0001 BTC payout fee; payouts are free from 0.005 BTC. Lightning payouts from 1 satoshi up to 0.005 BTC are free. [2] |
| Luxor | Daily, weekly on a chosen day, or monthly on the first day of the month. A subaccount is paid only when its balance exceeds the minimum withdrawal threshold plus the withdrawal fee: for BTC, 0.001 and 0.000075, so the balance must be greater than 0.001075 BTC. Payments are processed shortly after 04:00 UTC. With wallet splits, the smallest split must reach 0.0002 BTC. [3] |
| OCEAN | TIDES has no minimum itself. OCEAN's on-chain payout threshold is currently 0.01048576 BTC per its Lightning page. Its terms describe amounts credited to your TIDES balance below the on-chain threshold as a contingent entitlement to future payouts; the bitcoin remains OCEAN's until a payout is made. [4] [5] |
| NiceHash | Its help documents miner payment timing, including every-four-hours and daily payout options, and a service charge on mining payments. Mining payments land in the NiceHash wallet. Confirm the schedule and thresholds in your own settings. [6] |
Foreman is not a pool: its Pool Report shows actual earnings as reported by your pool while its Profit Report is an estimate. [7]
Pools change these settings; check each pool's page before closing a month.
Month-end steps
- Export or note each pool's balance at your cut-off and the time zone it uses. Luxor exports are UTC, as described in the Braiins and Luxor guide; Braiins creates payouts at 9.00 UTC. Keep the original export or dated balance evidence. [2]
- List payouts received in the month from wallet or exchange records. Keep the receiving address and receipt time with each entry so the period boundary can be reviewed.
- Match each payout to its pool record by transaction ID and amount. Do not count the same bitcoin twice: a balance paid out next month is the same bitcoin, not new revenue. Keep pending or failed payouts visible until receipt is confirmed.
- Value each received payout when received. Retain its reporting-currency value and valuation source with the BTC amount, using the approach agreed with your accountant.
- Keep unpaid balances in a month-end schedule by pool and site. Agree with your accountant whether they are recognised and how. OCEAN's contingent-entitlement wording is one input to that decision, not a general rule for every pool. [5]
- Assign payouts and balances to sites using separate payout addresses, Braiins Financial Accounts or Luxor subaccounts per site. Keep the allocation basis when a shared address needs a site split. [2] [3]
- Record in QuickBooks with your accountant: debit a Bitcoin asset account and credit mining revenue for received payouts. Any treatment of unpaid balances is as your accountant decides. Retain the schedule with the reviewed entries.
Multi-pool sites
One site mining to two pools has two balances, two thresholds and two payout times. Keep a per-pool line in the month-end schedule. Payout fees reduce what arrives, so preserve the pool record alongside the receipt. A single site total can hide an unpaid balance at one pool behind a received payout from another.
Worked example
Illustrative only. Invented amounts. One site uses Pool A and Pool B. Pool A paid 0.020 BTC and 0.015 BTC during the month and shows 0.004 BTC credited but unpaid at month end. Pool B paid nothing because its balance of 0.0008 BTC is below its threshold. Receipt-time values of the two payouts total an invented $3,150.
Record the two received payouts, totalling 0.035 BTC and $3,150: debit Bitcoin asset and credit mining revenue. List 0.004 BTC and 0.0008 BTC in the month-end schedule as unpaid pool balances, with treatment per accountant. Next month, when Pool A pays the 0.004 BTC, match it to that schedule line so it is not counted twice.
How Flash fits
Flash is the CFO layer for compute operators. Braiins Pool connects directly with a read-only API token. OCEAN Pool connects read-only through your public Bitcoin mining address. NiceHash connects mining earnings and wallet activity, including deposits, trades and withdrawals. [1]
Luxor and Foreman are CSV import only: CSV import wizard with saved definitions and reusable rules. Kraken, Coinbase, Coinbase Prime and Gemini connect directly. Map payout addresses to sites and keep unmatched activity visible for review. [1]
Each payout is valued when it was received, matched to the site that earned it. Pool earnings, payouts and the balance still at the pool, checked at close. Lock a month before sharing it. Later changes are recorded as corrections. [1]
Honest limitations
Pool settings and thresholds change, so check each pool. Luxor and Foreman are CSV import only. Income recognition for unpaid balances is your accountant's decision; Flash does not make it. NiceHash figures follow NiceHash's own help; check your settings. A balance shown on a pool dashboard is not bitcoin in your wallet.
Questions
Should I record an unpaid mining pool balance as income?
This is general information; it is your accountant's decision. Many operators record received payouts and keep unpaid balances on a month-end schedule. OCEAN's terms describe balances below threshold as a contingent entitlement.
What is a mining pool payout threshold?
It is the balance condition a pool uses before issuing a payout. Schedules, fees and pending payments also affect when bitcoin reaches your wallet. Check your own pool settings.
What are Braiins Pool's payout limits?
The on-chain minimum is 0.0002 BTC. On-chain payouts under 0.005 BTC carry a 0.0001 BTC fee; payouts from 0.005 BTC are free. Lightning payouts from 1 satoshi up to 0.005 BTC are free.
When does Luxor pay out?
Luxor offers daily, weekly on a chosen day, or monthly on the first day of the month. Payments are processed shortly after 04:00 UTC, subject to the balance exceeding the withdrawal threshold plus fee.
How do I avoid counting the same bitcoin twice?
Match received payouts to pool records by transaction ID and amount. When a scheduled unpaid balance is paid next month, match it to that schedule line and follow the treatment your accountant agreed.
How should a site with two pools be handled at month end?
Keep a separate schedule line for each pool and site. Each pool has its own balance, threshold and payout timing. Keep payout fees visible alongside the amounts received.
Is this tax advice?
No. This is general information, not tax, legal or accounting advice. Income recognition, classification and valuation decisions belong with your accountant.
Check operating assumptions with Flash's mining calculator.
Sources
Checked 17 November 2026.
- Flash for miners
- Braiins rewards and payouts
- Luxor revenue and payments
- OCEAN Lightning payouts
- OCEAN terms
- NiceHash earnings and payments
- Foreman: How To Audit Pool Payouts