Crypto treasury management is the written rule a business applies to the Bitcoin it receives once it starts to accept Bitcoin payments: hold it, convert it on receipt, settle it on a schedule, or split it by percentage. The policy governs exposure, operating cash flow, custody, and the records finance uses to close a month.
This article is not legal, tax, or accounting advice, and it gives no jurisdiction-specific tax guidance.
Crypto Treasury Management for Business Accepting Bitcoin Explained
For a business whose Bitcoin arrives as customer revenue rather than as a purchased reserve, crypto treasury management is the repeatable handling rule for inbound payment flow: what proportion is retained, what is converted, when funds move, and how each receipt is evidenced. It is an operating process, not an investment mandate.
Payments treasury is a different problem from the balance-sheet accumulation most published material describes, because the inflow is continuous, tied to individual invoices, and reconciled against the same ledger as card and bank revenue. It has 3 jobs:
- Control exposure, so the share of revenue held in Bitcoin is a deliberate figure rather than whatever accumulated since the last review.
- Keep operating cash predictable, so payroll, supplier runs, and tax obligations are funded on schedule.
- Produce a defensible record of every receipt, with the amount, reference, rate, and timestamp stored at the point of payment.
If the rule has to be revisited every time the market moves, it is a market call dressed up as a treasury policy.
Holding vs Converting Bitcoin Revenue: How to Set the Policy
There are 4 options, and every business accepting Bitcoin picks one: hold the receipts in BTC, convert on receipt, settle on a fixed schedule, or split the flow by percentage. The choice follows from 2 inputs, not from a forecast.
The first is the share of revenue the business can afford to leave exposed without affecting covenants, reporting, or board comfort. The second is the size and timing of outgoing fiat obligations: payroll, supplier commitments, and fixed licence costs. Where those fall on fixed dates, the exposed share has to be small enough that a valuation movement never threatens a payment run.
A split approach is a common landing point. As an example, a business might convert 70% of receipts and retain 30%, with the retained portion capped so it does not compound indefinitely. The exact proportion is not fixed. Each business defines its own split based on its cash flow, risk tolerance and treasury goals. What matters is that the percentage is agreed in advance, which is what makes it defensible later. For the exposure argument itself, read Overcoming Cryptocurrency Volatility as a Merchant.
The controller or head of finance typically drafts the policy, the CFO approves it, and it is recorded in a treasury policy document referenced in a board minute. Holding is not a return strategy; it is a decision about how much of the operating balance is held in a non-cash asset, and the IFRS Interpretations Committee's agenda decision on holdings of cryptocurrencies explains why that distinction carries reporting consequences.
Bitcoin Payment Settlement Options with a Lightning PSP
Settlement is the point at which funds leave the payment service provider and land under the business's control. If a policy assumes settlement behaviour that the provider cannot deliver, it will fail at the first month-end. Please confirm the configuration in writing during procurement.
ElenPAY confirms the per-sub-merchant settlement configuration for its white-label product. For a platform paying out to multiple onward accounts, that capability maps directly to a treasury policy: each sub-merchant carries its own settlement rule, so a blanket approach is not forced across accounts with different cash-flow profiles. Downstream, the settlement batch identifier ties a group of payments back to a single movement of funds.
The questions worth putting to any provider are these: what settlement timings are available, in what asset funds are delivered, whether thresholds are supported, whether the rule can be set per account, and what record is produced for each settlement event. Regarding the payment itself, ElenPAY states settlement in under 1 second, network fees below $0.01, no chargebacks, and integration via REST API, payment links, a checkout widget, or white-label.
How to Reconcile Lightning Payments Against Invoices
Reconciliation runs along a 4-link chain: the invoice or order reference, the payment record, the exchange rate captured at the time of receipt, and the settlement batch. If any link is missing, the month-end becomes a manual investigation.
A Lightning invoice carries a unique payment hash and a specified amount, defined in the BOLT 11 payment encoding specification, so that a payment can be tied to an order reference rather than inferred from a timestamp. The rate recorded at the moment of receipt is the figure finance books against, and it should be stored with the payment record rather than recalculated later from a price feed, which would produce a number that can't be reproduced in an audit. On how Lightning and on-chain Bitcoin relate as the same underlying asset, see whether the Bitcoin Lightning price is different from Bitcoin.
Webhook notifications and CSV or API exports are the audit trail. A controller should insist on at least 5 fields: timestamp, amount in BTC, amount in the accounting currency, invoice or order reference, and settlement batch ID. Partial payments, overpayments, and expired invoices with customer retries are the 3 edge cases to script before go-live.
Who Holds the Bitcoin, and When Does It Move?
There are 3 custody positions in any Bitcoin payment flow: what the provider holds between receipt and settlement, what the business holds after settlement, and the movement in between. Each has a different owner, control set, and record.
ElenPAY manages nodes, liquidity, and custody, so maintaining channel capacity and holding funds until settlement is handled by the provider rather than the finance team. After settlement, responsibility shifts: funds under business control need named signatories, documented access controls, and an internal approval route for transfers, exactly as a bank account does. If the business has not yet decided whether it needs to hold Bitcoin directly, do you need a Bitcoin merchant wallet to cover that decision?
The custody boundary is also the reporting boundary: the provider's records end where its custody ends, so any movement thereafter must be documented by the business's own systems. Firms with existing obligations under the FCA's cryptoasset regime will recognise that split from their fiat controls.
A Bitcoin Treasury Checklist for Finance Teams
- Write the hold, convert, settle, or split rule down as a percentage with a stated cap, and have it formally approved.
- Name 1 owner who maintains the policy and 1 approver who signs it off.
- Confirm the settlement configuration in writing: asset, timing, thresholds, and per-account rules.
- Specify the fields exported for every payment: timestamp, BTC amount, accounting-currency amount, invoice reference, and settlement batch ID.
- Document the custody boundary and who is authorised to move funds once they sit under business control.
- Set a review cadence, plus trigger events that force an early review: a change in payment volume, a new sub-merchant, or a change in outgoing fiat obligations.
| Quick tip: Agree on the export format with the provider before going live, not at the first month-end. Retrofitting a field into historic records is harder than requesting it on day 1. |
See How Settlement and Reporting Work Before the Policy is Signed Off
A crypto treasury management policy only holds if the provider can settle and report the way the policy assumes. The ElenPAY Bitcoin Lightning payment gateway page sets out how settlement works, the integration routes available via REST API, payment links, checkout widget, or white-label, and the records that a finance team receives for every payment.
Book a Treasury Scoping Call with ElenPAY
A treasury policy is only as reliable as the settlement and reporting behind it. A 30-minute call with the ElenPAY team walks through the settlement configuration available for pay-ins and payouts, the fields exported for every transaction, and how per-sub-merchant settlement works for platforms with multiple onward accounts. Bring the draft policy, or the open questions in it, and the team will confirm what ElenPAY can commit to in writing before it goes to the CFO for sign-off.
To book a treasury scoping call, contact the ElenPAY team, and a specialist will confirm settlement and reporting details against the policy as drafted.
Crypto Treasury Management: FAQs
Who in a business should own the crypto treasury policy?
The controller or head of finance usually drafts and maintains it, with the CFO as approver. Naming both roles prevents the policy from drifting into an informal practice nobody signed. Where a platform operates sub-merchants, the owner also needs the authority to set settlement rules for each account.r answer here.
How often should a Bitcoin treasury policy be reviewed?
Quarterly is a workable default, aligned to existing treasury reporting cycles. Alongside the cadence, define trigger events that force an earlier review: a material change in Bitcoin payment volume, a new sub-merchant, or a change in outgoing fiat obligations.
Can settlement be set differently for each sub-merchant?
Yes. Per-sub-merchant settlement configuration is supported in the ElenPAY white-label product, allowing a platform to apply different rules to each onward account rather than a single blanket setting. That matters where sub-merchants carry different cash-flow profiles and different outgoing obligations.nswer here.
What records should a finance team export for each Lightning payment?
At minimum: timestamp, amount in BTC, amount in the accounting currency, the invoice or order reference, and the settlement batch ID. The rate applied at the moment of receipt should be stored with the record rather than recalculated later. Webhook notifications plus periodic exports give both a real-time and a reconcilable view.
Does the exchange rate used for a Lightning payment differ from Bitcoin's price?
Lightning payments are denominated in the same asset, so the underlying valuation is not a separate market. For how the rate applied at checkout relates to the wider Bitcoin price, see the ElenPAY explainer on Lightning pricing.