Crypto treasury management: how a finance team runs it in 2026

The short answer: Crypto treasury management is how a finance team controls, spends, accounts for and reports on the crypto a company holds. It covers custody and signer rules, stablecoin liquidity, vendor and contractor payments, the monthly close and board reporting. Custody platforms hold the keys. Breezing is the accounting and payments layer that posts the results to Xero, QuickBooks or Bexio.

Updated September 2026. Every source used is listed at the end of this post.

Most guides on this topic come from custody vendors, so they stop at the wallet. This one is written from the finance side. It gives you the policy a board can approve, the checklist that closes the month, and the workflow for paying real vendors and contractors from a crypto treasury.

What crypto treasury management covers

Treasury management for crypto is five workstreams. Each has an owner, a control and a tool category. The mistake we see most often is buying a custody platform and assuming the other four come with it.

Workstream	What it includes	Typical owner	Tool category
Custody and access control	Where keys live, who can sign, thresholds by amount, address whitelists, key recovery	CFO or head of security	Custody platform or multisig such as Safe
Liquidity and stablecoin reserves	Months of spend held in stablecoins or fiat, which stablecoins are allowed, when to rebalance	Treasurer or CFO	Exchange or OTC desk, bank
Payments and expenses	Vendor bills, contractor invoices, payroll top-ups, reimbursements, gas	Finance ops	Payment tool, address book, subledger
Accounting and close	Transaction import, categorization, cost basis, invoice closure, journal entries, roll-forwards	Controller or outsourced accountant	Crypto subledger connected to the GL
Reporting and policy	Monthly treasury report, board pack, policy review, audit support	CFO	Subledger and GL reports

Custody products cover the first row. Accounting products cover rows three and four. Nobody sells rows two and five. Those are decisions, and they belong in a policy.

The crypto treasury policy template

A treasury policy turns "we hold crypto" into a document a board, an auditor and a new hire can test. Here is the structure we recommend, with example wording. The numbers are illustrations. Replace them with yours, but keep a number in every section, because a policy without numbers cannot be tested.

1. Purpose and scope. Example: "This policy governs all digital assets held by Acme Inc. and its subsidiaries, in any wallet, exchange account or custody arrangement, and binds everyone with signing or administrative rights over them."

2. Roles and approval thresholds. Name roles, not people. Example: "Payments up to $10,000 need one finance ops approver and one signer. Above $10,000, two of three named signers. Above $100,000, or to any address outside the approved address book, three of five signers plus written CFO approval before signing."

3. Custody and access control. Example: "Treasury wallets are three-of-five multisigs. Hardware keys are held by five named officers in at least two countries. The operating wallet is capped at the lower of $50,000 or two weeks of budgeted spend. Exchange balances are for conversion only and are swept within two business days." A Safe account lets you "define a list of owner accounts and a threshold number of accounts required to confirm a transaction", per Safe's developer documentation, so this section is enforced in code rather than on paper.

4. Approved assets and concentration limits. Example: "Approved assets are BTC, ETH, USDC and the company's own token. No single exchange or custodian holds more than 25% of treasury value. No stablecoin issuer exceeds 60% of stablecoin reserves. New assets need board approval." For stablecoin selection, borrow the tests US law now applies to issuers. Under the GENIUS Act, signed on 18 July 2025, each payment stablecoin must be "backed on a one-to-one basis with reserves such as U.S. dollars, Treasury securities, money received under repurchase agreements, or similarly liquid assets approved by regulators", and issuers "must file monthly certifications confirming the adequacy of reserves", per Covington's summary of 25 July 2025. Circle, for example, says USDC is redeemable "1:1 for US dollars", that it "publishes monthly reserve attestations by a Big Four accounting firm", and reports $73.3 billion in circulation as of 31 August 2026, per circle.com. A workable policy line is "only stablecoins whose issuer publishes monthly reserve attestations and offers 1:1 redemption".

5. Liquidity and stablecoin reserves. Example: "The company holds at least six months of budgeted operating spend in stablecoins or fiat. Below four months, the treasurer converts within five business days. Above nine months, the excess moves to treasury wallets."

6. Payments and expenses. The section most policies skip. Example: "Every outgoing payment references an approved bill, invoice or expense claim in the accounting system. A second person verifies new payee addresses over a separate channel, and each gets a test transfer first. Payments run twice a week. Crypto reimbursements are paid and expensed at fair value on the payment date."

7. Accounting and valuation. Example: "In-scope crypto assets are measured at fair value at each month end using [named price source] at 23:59 UTC. Cost basis is FIFO per wallet and does not change within a fiscal year." Under US GAAP, crypto assets in the scope of ASC 350-60 are measured "at fair value in accordance with ASC 820" with gains and losses "in net income", effective "for fiscal years beginning after Dec. 15, 2024", per Grant Thornton's summary of ASU 2023-08, dated 21 December 2023. Under IFRS, the June 2019 IFRIC agenda decision holds that "a cryptocurrency is not cash" and not a financial asset, applying IAS 2 when held for sale in the ordinary course of business and IAS 38 otherwise, per the IFRIC Update of June 2019.

8. Reporting and review. Example: "The treasurer sends a monthly treasury report to the CFO within ten business days of month end covering holdings, runway, realized and unrealized results, policy exceptions and open items. The board gets a quarterly summary. The policy is reviewed annually and after any security incident."

Eight sections, a page each at most. If your current policy is a Notion page that says "use the multisig", this is the upgrade.

Crypto expense management: paying people and vendors from a crypto treasury

Expense management is where a crypto treasury touches ordinary business every week. A company paying contractors and SaaS vendors in USDC has an accounts payable process like any other. The bank feed is a wallet, the currency is a token, and the payment itself has a tax treatment.

Paying contractors and vendors in stablecoins. The vendor invoices in dollars or euros with a wallet address on it. Finance records the bill, gets the approval from section 2 of the policy, and pays USDC from the operating wallet. Stablecoins are the right rail because invoice and payment amounts match, which ends the exchange rate argument before it starts. Networks and payment terms are covered in our guide to stablecoin invoicing.

Closing the bill in Xero or QuickBooks. This is where most teams still keep a spreadsheet. The usual workaround posts the payment to a clearing account, applies it to the bill by hand, then reconciles the clearing account at month end. Breezing does it natively. In Xero, you "pick the open invoice or bill, set the amount, submit", as the breezing.io home page puts it, and the on-chain payment is matched to the open receivable or payable and marked paid. In QuickBooks Online, the payment posts to A/R or A/P against the customer or vendor, and Breezing "handles any minor exchange rate variances instantly", per the two integration pages. No clearing account, nothing to reconcile.

Categorizing expenses. Every outgoing transfer needs a category, a counterparty and, where your GL uses them, a cost center or class. Subledger rules do most of it. A known vendor address maps to that vendor's expense account every time, gas on the operating wallet maps to a fee account, and new payees get flagged for a human. Mirror your existing chart of accounts. A crypto-specific taxonomy only makes year-end mapping harder.

Reimbursements. Staff reimbursed in crypto are paid at fair value on the payment date, and the expense is booked that day with the receipt attached, like a card expense. A stablecoin keeps the amount clean. ETH creates a disposal on the company's side, which brings us to the entry.

The accounting entry for a USDC vendor payment. A $5,000 design bill recorded in April, paid on 3 May with 5,000 USDC on Ethereum, gas paid in ETH worth $3.40 at the time.

Line	Debit	Credit
Accounts payable, vendor	5,000.00
Digital assets, USDC		5,000.00
Transaction fees expense	3.40
Digital assets, ETH, at carrying amount		3.40

If the ETH used for gas has a carrying amount different from its fair value that day, the difference is a small realized gain or loss. The USDC line is clean because Circle redeems USDC "1:1 for US dollars", per circle.com, so the amount paid is the amount that leaves the balance sheet, but its classification depends on that redemption right. PwC's crypto assets guide, dated 31 May 2025, notes that a stablecoin may be a financial asset when it includes "a right to receive cash from the issuer", per PwC Viewpoint. Whether it is a cash equivalent is unsettled under current US GAAP, with "diversity in practice related to determining whether these assets meet the definition of a cash equivalent", and the FASB's 18 August 2026 proposal to add examples of when a digital asset could qualify is open for comment until 19 November 2026, per Deloitte's Heads Up of 19 August 2026. Until that settles, write the classification of stablecoin balances into the policy, however much they behave like cash in operations. The entries for purchases, sales, staking and payments received are in our post on crypto accounting journal entries.

The tax reporting angle. For US taxpayers, digital assets are "property, not currency", and the IRS names stablecoins as a type of digital asset, per irs.gov. Paying a contractor in crypto has two sides. For the payer, settling a service with a digital asset held as a capital asset means "you have exchanged a capital asset for that service and will have a capital gain or loss", per Q14 of the IRS virtual currency FAQ, updated 30 June 2026. For a stablecoin paid at one dollar that gain is usually nil. For ETH it is not. For the payee, the same FAQ says the fair market value an independent contractor receives, "measured in U.S. dollars as of the date of receipt, constitutes self-employment income", and wages paid in virtual currency are subject to withholding, FICA and FUTA and "must be reported on Form W-2". Broker reporting on Form 1099-DA applies from 1 January 2025, with basis reporting from 1 January 2026, per the same IRS digital assets page. Either way, the fair value at the moment of each payment has to be captured, and that is a subledger job, not a spreadsheet job.

Treasury operations: the monthly checklist

Treasury operations are the tasks that repeat. Here is the month-end sequence in the order that avoids rework. The accounting steps are expanded in our crypto month-end close checklist.

1. Freeze the wallet inventory. Every address, exchange account and multisig in the register has an owner and a purpose, and nothing was created during the month without being registered.
2. Sync every source into the subledger and check the last synced block or date per wallet. A wallet that stopped syncing on the 19th is a silent hole in the books.
3. Verify balances against the source. Compare the subledger balance per asset per wallet with the explorer or exchange statement, and chase every difference before categorizing anything.
4. Run the wallet roll-forward for every wallet and asset. Opening plus inflows minus outflows minus fees equals closing. Your auditor will ask for this schedule.
5. Match internal transfers. Movements between your own wallets are neither income nor expense, and the ones you miss inflate both.
6. Categorize the rest. Rules first, then the exceptions queue by hand. Ask for missing invoices now, not in January.
7. Close paid invoices and bills against their on-chain payments so receivables and payables in the GL reflect what settled.
8. Check liquidity against policy. Months of runway versus the floor in section 5, with a conversion order raised if you are under.
9. Post fair value marks for in-scope assets using the price source and time named in the policy.
10. Post journal entries and reconcile each GL crypto account back to the subledger. Any difference is a timing item you can name or an error you must fix. Our guide on how to reconcile crypto transactions covers the usual causes.
11. Test policy compliance. Exchange concentration, approved asset list, operating wallet cap, and an unchanged signer set on each multisig.
12. Write the monthly treasury report. Holdings by asset and wallet, runway, realized and unrealized results, exceptions and open items.
13. Lock the period in the subledger so nobody's later recategorization moves a closed month.

Teams that do this monthly spend a few hours on it. Teams that do it annually spend a few weeks, usually the weeks before the audit.

Treasury management for protocols and foundations

Protocols, DAOs and foundations run the same five workstreams with three differences.

Signing lives in a multisig. Safe accounts execute a transaction only after "a threshold of owners" confirms it, per Safe's documentation, so the policy thresholds are enforced on chain. The risk moves to the owner set: who holds keys, where they are, and what happens when one of them leaves.

Spending is grants and vesting as much as payroll. A grant becomes an expense when the milestone is met and the tokens are released, so the treasury needs a schedule of committed but unreleased grants alongside the wallet balances. Contributor vesting is the same problem in the other direction. Both belong in the monthly report, or the runway number is wrong.

Most of the treasury is the entity's own token. The ASC 350-60 fair value model applies only to assets meeting six criteria, one being that the asset "is not created or issued by the reporting entity or its related parties", per the Grant Thornton summary. The native token is out of scope and needs its own answer before the first close. Our ASC 350-60 post covers the scope test and the annual per-asset reconciliation that comes with it. Breezing's customer list on breezing.io includes Safe, The Graph and ENS, which is the best evidence we can offer that this accounting layer works at protocol scale.

Crypto treasury management software: what to look for

The category name misleads. "Crypto treasury management software" is at least three products, and the first vendor you speak to will define the category as whatever they sell. Use these criteria and note which layer each belongs to.

Criterion	Why it matters	What to check	Layer
Custody model and signer policy	The control an auditor tests first	Multisig or MPC, threshold by amount, whitelists, recovery	Custody
Wallet and exchange coverage	A wallet the tool cannot read is one you reconcile by hand	Count your chains and exchanges, check each is supported	Accounting
Balance verification against the source	Imported data is only useful if it matches the chain	Per-wallet balance check at a point in time	Accounting
Native invoice and bill closure	Clearing accounts are where crypto payments go to be forgotten	Can a payment close an open Xero or QuickBooks bill directly?	Accounting
Cost basis options	Your policy fixes one method, the tool must support it	FIFO, LIFO, HIFO, weighted average, per wallet or universal	Accounting
Behaviour on correction	A recategorized transaction should update the entry, not duplicate it	Does a resync update the GL entry or post a new one?	Accounting
Pricing basis	Per-wallet and per-seat pricing punish good wallet hygiene	Priced by transaction volume, unlimited wallets and users	Any
Security attestation	Your treasury data is a map of your treasury	SOC 2 report on request	Any
Payment batching and address book	Weekly payment runs need approvals and a verified payee list	Address verification steps, batch approvals	Payments

For a side-by-side of the accounting layer, see our list of the best crypto accounting software.

Where Breezing fits

Breezing is our product, and it is the accounting and payments layer, not custody. The facts below come from breezing.io, its pricing page and its integrations page, checked on 4 September 2026.

Breezing imports every wallet and exchange, verifies balances against the source and posts journal entries to Xero, QuickBooks Online or Bexio. The home page lists 58 blockchains and 17 exchanges, and the integrations page adds wallets including Safe, Ledger, MetaMask and Trezor, plus Abacus, Banana and Odoo on the accounting side. Invoices and bills close without a clearing account. Cost basis runs as FIFO, LIFO, HIFO or weighted average, per wallet or universal. Change a category or a rule and a resync updates the existing journal entry instead of posting a new one. Breezing has completed an independent SOC 2 audit and is a Swiss Made Software member.

Every plan includes unlimited wallets and users with no per-seat fees. Pricing starts at $29 a month for 600 transactions and runs to $2,917 a month for 1.5 million transactions, with custom enterprise plans above that. Customers include BDO, Safe, Dune, The Graph and ENS.

What Breezing does not do is hold your keys. Pair it with a multisig or a custody platform for the first row of the workstream table, and use Breezing for rows three, four and five.

Quick answers

What is crypto treasury management?

Crypto treasury management is the finance function for a company's digital assets. It decides who can move funds and under what approvals, how much sits in stablecoins for operating spend, how vendors and staff get paid, how every movement reaches the general ledger, and what the board sees each month.

What is crypto expense management?

Crypto expense management is paying vendors, contractors and staff from company wallets, then recording each payment with its category, its fair value in the reporting currency, the network fee and its tax treatment. Done well, a USDC bill payment closes the bill in Xero or QuickBooks directly, with no clearing account.

How do you manage business expenses as a crypto business?

Pay from a dedicated operating wallet with a spend cap and an approved address book. Attach the invoice or receipt to every payment before it goes out. Sync the wallet into a subledger that categorizes each payment and posts it to the accounting system, so the expense record exists the day the money moves.

What is the best crypto treasury management software for enterprise?

No single product covers it. Enterprises pair a custody platform for keys and signer policy with an accounting layer for the close. For the accounting and payments layer, Breezing syncs 58 blockchains and 17 exchanges into Xero, QuickBooks Online and Bexio, closes bills without a clearing account and has completed a SOC 2 audit.

What are best practices for corporate crypto treasury?

Write a board-approved policy with named signer roles and thresholds. Separate cold treasury from a capped operating wallet. Hold a stated number of months of spend in stablecoins. Pay only to a verified address book. Fix one cost basis method and one price source for the year. Close monthly. Report to the board quarterly.

What are crypto treasury operations?

Crypto treasury operations are the repeating tasks that keep the treasury controlled and the books current. Keeping the wallet inventory, funding the operating wallet, running payments, syncing and categorizing transactions, verifying balances, rolling wallets forward, posting fair value marks, reconciling the ledger and writing the monthly report. This post lists thirteen steps.

What should a crypto treasury policy include?

Eight sections. Purpose and scope, roles and approval thresholds, custody and access control, approved assets and concentration limits, liquidity and stablecoin reserves, payment and expense rules, accounting and valuation choices, and reporting and review cadence. Each needs a number a reviewer can test, such as two-of-three signers above $10,000.

How do you pay a vendor invoice in USDC and close it in Xero or QuickBooks?

Record the bill in Xero or QuickBooks as usual and pay the USDC from the operating wallet. In Breezing, pick the open bill, set the amount and submit. The payment posts against accounts payable for that vendor and marks the bill paid, with small rate variances handled in the same step. No clearing account.

How is a crypto treasury measured on the balance sheet?

Under US GAAP, crypto assets in the scope of ASC 350-60 are measured at fair value with changes in net income, for fiscal years beginning after December 15, 2024. Under IFRS, the June 2019 IFRIC agenda decision treats holdings as intangible assets under IAS 38, or inventory under IAS 2 when held for sale.

What crypto treasury management software fits protocols and foundations?

A multisig such as Safe for signing, and an accounting layer that reads the multisig, tracks grants and vesting, and posts to the general ledger. Breezing's customers include Safe, The Graph and ENS. The entity's own token sits outside ASC 350-60, so agree its measurement before the first close.

Bottom line

Crypto treasury management is a finance job with a security prerequisite. Get custody right once, then run the treasury the way you run cash. A written policy with numbers in it, an operating wallet that pays bills against real invoices, a monthly close that starts with a balance check and ends with a locked period, and a report the board can read.

For the accounting and payments layer, we recommend Breezing. It reads the wallets and exchanges you already have, closes invoices and bills in Xero, QuickBooks Online or Bexio without a clearing account, updates entries in place when you correct them, and prices by transaction volume with unlimited wallets and users. Custody is a separate product category, and it should be. Keys and books are different controls, and your auditor tests them separately.

Sources

• Breezing home page, Breezing, checked 2026-09-04: supports the product description, 58 blockchains and 17 exchanges, sync to Xero, QuickBooks and Bexio, invoice and bill closure without a clearing account including the "pick the open invoice or bill, set the amount, submit" wording for Xero, journal entries updating on resync, FIFO, LIFO, HIFO and WAC per wallet or universal, unlimited wallets and users with no per-seat fees, the completed SOC 2 audit, Swiss Made Software membership, and the customer names BDO, Safe, Dune, The Graph and ENS.
• Pricing, Breezing, checked 2026-09-04: supports the $29 a month Basic plan at 600 transactions, the $2,917 a month Scale plan at 1.5 million transactions, custom enterprise pricing, and unlimited wallets and users on every plan.
• Integrations, Breezing, checked 2026-09-04: supports the accounting systems listed, namely Abacus, Banana, Bexio, Odoo, QuickBooks and Xero, and the wallets listed, Safe, Ledger, MetaMask and Trezor among them.
• Xero integration, Breezing, checked 2026-09-04: supports matching an on-chain payment to the open accounts receivable or payable item in Xero, marking it paid, and updating a journal entry in Xero when a category or rule changes in Breezing.
• QuickBooks integration, Breezing, checked 2026-09-04: supports posting the payment against the customer or vendor in QuickBooks Online, handling minor exchange rate variances, and updating entries in place.
• Clarifies accounting for certain crypto assets (ASU 2023-08), Grant Thornton, dated 21 December 2023, checked 2026-09-04: supports fair value measurement under ASC 820 with gains and losses in net income, the effective date for fiscal years beginning after 15 December 2024, the six scope criteria including the exclusion of assets issued by the reporting entity or its related parties, and the annual reconciliation of opening and closing balances per crypto asset.
• IFRIC Update June 2019, IFRS Foundation, dated June 2019, checked 2026-09-04: supports the agenda decision that a cryptocurrency is not cash and not a financial asset, with IAS 2 applying when held for sale in the ordinary course of business and IAS 38 otherwise.
• The GENIUS Act becomes law: key provisions from the federal stablecoin regulatory framework, Covington & Burling, dated 25 July 2025, checked 2026-09-04: supports the 18 July 2025 signing, the one-to-one reserve requirement and permitted reserve assets, and the monthly reserve certifications.
• Stablecoins and the GENIUS Act: an overview, Federal Reserve Bank of Richmond, dated 18 November 2025, checked 2026-09-04: corroborates the 1:1 reserve backing and the monthly attestations of reserve composition with CEO and CFO certifications, and gives the public law number 119-27.
• USDC, Circle, undated page with figures as of 31 August 2026, checked 2026-09-04: supports 1:1 redemption for US dollars, monthly reserve attestations by a Big Four accounting firm, and $73.3 billion USDC in circulation as of 31 August 2026.
• Safe Smart Account overview, Safe, undated, checked 2026-09-04: supports the owner list and threshold mechanism, where a threshold of owners must confirm a transaction before it executes.
• Digital assets, IRS, checked 2026-09-04: supports digital assets being treated as property rather than currency, stablecoins being named as a type of digital asset, exchanging digital assets for goods or services being a reportable event, Form 1099-DA reporting from 1 January 2025 and basis reporting from 1 January 2026.
• Frequently asked questions on virtual currency transactions, IRS, page updated 30 June 2026, checked 2026-09-04: supports Q10 on contractor receipts being self-employment income at fair market value on the date of receipt, Q11 on wages paid in virtual currency being subject to withholding, FICA and FUTA and reported on Form W-2, and Q14 on paying for a service with a capital asset producing a capital gain or loss.
• 2.1 Initial recognition and measurement of crypto assets not in scope of ASC 350-60, PwC Viewpoint, dated 31 May 2025, checked 2026-09-04: supports a stablecoin qualifying as a financial asset when it carries a right to receive cash from the issuer.
• FASB proposes enhancements to disclosures about cash equivalents and clarifications to the evaluation of certain digital assets, Deloitte Heads Up, dated 19 August 2026, checked 2026-09-04: supports the diversity in practice on whether stablecoins meet the definition of a cash equivalent under current US GAAP, the 18 August 2026 FASB proposal and its 19 November 2026 comment deadline.