Crypto Expense Management: Policy, Substantiation, and the Month-End Problem

An engineer runs nineteen transfers out of the company wallet in a month and the network fees come with them. A contractor is reimbursed 200 USDT for a conference ticket she bought on a card. Someone tops up an operations wallet with 0.4 ETH so payouts do not stall. At month end the ledger has one line called “crypto expenses” with a number in it, and nobody can break it down.

Nineteen USDT transfers at Ethereum’s rate on 27 August 2026, with base gas at 0.039 gwei and ETH at $2,044, cost under a dollar in network fees in total. The same nineteen on Tron, at $2.15 to $4.50 a transfer, cost $41 to $86. Neither number is large. What is large is the tail — a category with no policy behind it grows quietly, and the first person to look closely at it is usually an auditor.

Crypto spend inside a company splits into three genuinely different things that get merged into one account. Untangling them is most of the work, and it is worth doing before the volume makes it expensive.

Three categories that behave differently

Spend in crypto. The company buys something and pays in tokens. This is a purchase and a disposition of an asset at the same time. Both legs need recording.

Network fees. Gas paid to move tokens. An operating cost incurred to execute a transaction, denominated in a native token you also hold as an asset.

Reimbursement paid in crypto. An employee or contractor spent their own money and is repaid in tokens. The expense is whatever they bought; the token is the settlement method. Whether the reimbursement is wages depends on a test that has nothing to do with crypto.

A single “crypto expenses” account holding all three produces a number that cannot be explained, cannot be substantiated line by line, and cannot be reconciled against the wallet. Splitting them costs nothing at setup and is close to impossible to retrofit.

Reimbursements: the accountable plan test decides everything

This is the part most crypto expense discussions skip, and it is the part with real money attached.

Treas. Reg. §1.62-2 sets out when amounts paid under a reimbursement arrangement are excluded from wages. Three conditions have to be met together.

Business connection. The arrangement must provide advances, allowances or reimbursements only for deductible business expenses paid or incurred by the employee in connection with performing services for the employer.

Substantiation. The employee must substantiate the expenses to the payer within a reasonable period.

Return of excess. Amounts in excess of substantiated expenses must be returned within a reasonable period.

Meet all three and the reimbursement is not wages. Miss any of them and the arrangement is non-accountable, which means the amounts are treated as wages, reported accordingly, and subject to withholding.

Paying the reimbursement in a token does not change that test. It does change one practical thing: the amount reimbursed is now a token quantity, and the substantiated expense is a fiat amount, so the conversion has to be documented as part of the substantiation rather than assumed.

Substantiation itself has its own rules. Treas. Reg. §1.274-5 governs the records required for travel, entertainment, gifts and listed property, and it is stricter than general recordkeeping. A receipt plus a transaction hash is a better evidentiary package than either alone, because the hash proves the settlement and the receipt proves the expense.

Two documents. That is the standard to hold — what was bought, and what moved on chain to pay for it.

Paying in crypto is a purchase and a disposition at once

When a company pays a supplier in tokens, two things happen in the same moment. A payable is settled, and an asset leaves the balance sheet.

Basis tracking is a hard requirement here, and the citation matters because it is widely misreported. Treas. Reg. §1.1012-1(j) requires basis to be tracked per wallet or account from 1 January 2025. Rev. Proc. 2024-28 is an optional transitional safe harbour for allocating basis unused before that date, not the source of the obligation. Declining to use a safe harbour does not remove a regulation, which is the practical reason to get the pairing the right way round.

Transaction costs are addressed in Treas. Reg. §1.1001-7.

For a stablecoin the disposition gain or loss is usually small, which is why the discipline slips. It is small until the month a token trades meaningfully away from its reference, and by then the records either exist or they do not.

Moving assets between wallets you control is not a disposition, except as to any digital assets used or withheld to pay for the transfer itself. That sounds obvious and it is a frequent source of overstated expense, because an internal top-up from treasury to an operations wallet appears in an export as an outflow. The matching process that catches this is set out in crypto reconciliation.

Gas is an expense category, not a rounding error

Gas has three properties that make it awkward, and each has a straightforward handling.

It is paid in a different asset from the payment. A USDT transfer costs ETH or TRX. The expense is denominated in the native token, so the fiat amount depends on a rate at a moment, and that rate needs the same policy as every other conversion.

It is volatile in a way the payment is not. Ethereum base gas read 0.77 gwei on 26 August 2026 and 0.039 gwei on 27 August 2026. Twenty times, overnight. A gas budget set from last quarter’s average is a budget set from noise. The network trade-offs are in ERC-20 vs TRC-20.

It is sometimes spent on nothing. A reverted transaction consumes gas and moves no tokens. In most wallet exports this appears as a native-token balance that dropped with no transfer to explain it, which is why an unexplained ETH shortfall is usually reverted transactions rather than theft.

On the treatment of gas spent on a failed transaction, we found no ruling, regulation or notice addressing it directly as at 27 August 2026, so any confident answer is an extrapolation. Capture the item anyway: hash, status, gas consumed, date, and the payment it was attempting. That gives an adviser something to work from and turns a mystery balance movement into a number you can manage.

Spend controls, which are the actual product

A crypto expense policy that exists as a document and not as a permission set is only a document — the controls live in the permissions.

Four controls do most of the work.

Separate wallets by purpose. Treasury, operations, payouts. A single wallet that does everything makes every control a matter of trust, and it makes the reconciliation harder in exactly the same proportion.

Per-person permissions rather than a shared key. A seed phrase three people know has no controls, whatever the policy says. Named access with distinct rights is the precondition for everything else on this list.

Separation between the person who initiates and the person who releases. The control that does most of the work, and the one that defeats both the inserted payee and the edited address.

Limits by role and by period. A threshold above which a second approver is required costs nothing on ordinary spend and catches the unusual item on the day it happens rather than at month end.

Where those live in one place, the expense record is a by-product rather than a reconstruction. VaultNow is built that way: a single dashboard with custodial wallets plus external wallets for tracking, team access with flexible custom permissions, invoicing, address screening and bulk payouts of up to 100 transactions, at $0.50 per transaction plus gas.

Cards, wallets and what a company can actually hand someone

Companies reach for a card because a card carries controls the wallet does not: a merchant category, a per-transaction limit, a decline. A wallet hands someone the ability to send anything anywhere, once.

Three arrangements, with their honest trade-offs.

A funded operations wallet with named access and limits. Works for on-chain spend, which is what most crypto expense actually is. Gives you the hash on every item. Does not work for buying a laptop.

Reimbursement in tokens after the fact. The employee pays with their own card, substantiates, and is repaid in tokens under an accountable plan. Simplest structure, and the one that keeps the §1.62-2 analysis clean, because there is no advance to return excess from.

An advance in tokens against expected spend. Attractive operationally and it is where accountable plans most often break, because the return-of-excess condition becomes a live obligation somebody has to police. If you use advances, the return process has to be as real as the advance process.

There is a fourth thing companies ask about, which is paying part of salary in crypto and calling it an expense arrangement. That is a different question with different law behind it, and the American position starts at 29 CFR 531.27(a), which reads in part: “Standing alone, sections 6 and 7 of the Act require payments of the prescribed wages… in cash or negotiable instrument payable at par.” The regulation then continues: “Section 3(m) provides, however, for the inclusion in the ‘wage’ paid to any employee, under the conditions which it prescribes of the ‘reasonable cost,’ or ‘fair value’ as determined by the Secretary, of furnishing such employee with board, lodging, or other facilities.” Quoting only the first sentence makes the rule look absolute, and it is not. The full treatment is in paying employees in cryptocurrency.

The treasury edge of the same question

Expense management and treasury meet at one decision: how much to hold in the settlement asset.

Two constraints shape it, and one of them is new.

A payment stablecoin is not a yield instrument, at least not from its issuer. Section 4(a)(11) of the GENIUS Act, at 12 USC 5903(a)(11), bars a permitted or foreign payment stablecoin issuer from paying a holder interest or yield solely for holding, using or retaining the stablecoin. The Act was not yet in force as at 27 August 2026, and the effective-date mechanism and its current status are set out in B2B crypto payments.

Balance sizing is a working-capital decision. Hold enough to cover the payment cycle plus gas, and hold the rest where your treasury policy says to hold it. The broader framing is in crypto treasury management.

Measurement is the other half, and it turns on whether the token falls inside ASC 350-60, added by ASU 2023-08. Fiat-backed stablecoins carrying a claim on the issuer are widely read as falling outside that scope, which is a prevailing reading rather than a settled answer, and worth confirming with your auditor for the instrument you actually hold. Record-keeping mechanics sit in crypto bookkeeping and crypto accounting for businesses.

A month-end sequence for the expense side

Six steps, in this order, because each removes noise from the next.

1. Pull the full transaction list per wallet, not the balance. Every wallet, including ones with small balances.

2. Tag internal transfers first. Anything where both sides are your own addresses is not an expense.

3. Split native-token movements from token movements. Gas top-ups, gas spend and reverted transactions live in the native-token ledger.

4. Match spend against receipts. Every outbound transfer that is not a payout or an internal move needs a document behind it. Ones that do not have one go on a list with a named owner.

5. Apply the rate policy. One source, one moment, consistently.

6. Check the reimbursement file separately. Substantiation received, excess returned where advances were made, and conversion documented.

The measure of whether this works is step 4. Where nearly all spend arrives with its document already attached, the close is short. Where receipts are chased after the fact, the same chase repeats every month.

The nine things a crypto expense policy has to state

Most policies are two pages of principle and no decisions. These are the decisions.

1. Which wallets exist and what each is for. Named, with a purpose, and a rule against using one for another’s job.

2. Who may initiate, who may release, and above what amount a second approver is required.

3. Which assets and which networks are permitted. Naming them prevents a payment to a network your systems do not track.

4. The rate source and the rate moment. One of each, written down, applied to every conversion including gas.

5. How gas is recorded and budgeted. Which account, which currency, how often the budget is re-based.

6. What substantiation is required, and by when. Receipt plus hash, within a stated number of days.

7. Whether advances are permitted, and the return-of-excess mechanism if they are.

8. The address change procedure. Out-of-band confirmation, and who is allowed to clear it.

9. What happens when screening flags a destination. Held, escalated to whom, and on what timeline. Blocking and rejecting are different actions with different consequences, and the procedural obligation for blocked property sits at 31 CFR 501.603: report within 10 business days, with an annual report by 30 September covering property blocked as at 30 June. The screening mechanics are in cryptocurrency address screening.

A policy that answers those nine is shorter than most and does more — because every line of it is a decision somebody would otherwise have to make under pressure.

What a defensible record actually contains

Different categories need different fields, and a single expense form that tries to cover all three collects the wrong things.

Two rows deserve emphasis. The rate moment has to be the same rule everywhere, including for gas, because a company that values payments at the block timestamp and gas at month-end close has built a difference into its own books. And basis released on disposal is the row that gets skipped, because on a stablecoin the number is usually near zero, right up until the month it is not.

Contractors are not employees, and the paperwork differs

Reimbursing a contractor is not the same exercise as reimbursing an employee, and the difference shows up on a form.

The accountable plan rules in Treas. Reg. §1.62-2 are framed around employees and wages. For a contractor, the question is instead what goes on the information return. The instructions for Form 1099-NEC put fees and commissions for services performed by a non-employee in box 1a, at $2,000 or more for returns covering 2026 and indexed for later calendar years, due 31 January under IRC §6071(c). Where a payer reimburses a contractor without a substantiation process in place, the reimbursement generally travels with the compensation onto that form rather than sitting outside it.

The practical fix is the same either way: require the receipt, require it within a stated period, and keep the reimbursement in a separate payment from the fee so that the two are distinguishable in the ledger and on the chain. Two transfers cost about six cents on Ethereum at the 27 August 2026 rate and remove an argument at year end.

For a contractor outside the United States performing services abroad, the analysis usually stops earlier, because services income is sourced to the place of performance under IRC §861(a)(3) and §862(a)(3), which puts work done abroad outside the reporting regime. Documentation is Form W-8BEN for an individual and W-8BEN-E for an entity, and the sourcing rule with its narrow exception is set out in 1099 for foreign contractors.

The cost of getting the information return wrong is a figure rather than a warning. For returns due in 2027: $60 if corrected within 30 days, $130 if corrected by 1 August, $340 if later or not filed, and for intentional disregard, the greater of $690 or 10% of the aggregate amount required to be reported correctly, with no cap. §6721 covers the return and §6722 covers the payee copy, so one omission can attract both.

Five ways this goes wrong in practice

Internal transfers booked as spend. A top-up from treasury to the operations wallet appears as an outflow in every export. Left untagged, it inflates the expense account by the full amount, and the error compounds every month.

Gas recorded in fiat only. The USDT ledger looks tidy and the ETH wallet stops reconciling, because there is no native-token amount to tie the balance movement to.

A rate applied at whatever moment was convenient. Payments valued at the block timestamp, gas at month end, reimbursements at the receipt date. Three policies is the same as none.

Advances with no return-of-excess process. The condition in §1.62-2 is not satisfied by intending to collect the excess. Somebody has to run it, on a schedule, with a consequence.

Receipts chased after the fact. How much of the close is spent chasing paper is decided by what proportion of spend arrives with its document already attached. That proportion is set by policy and enforcement, not by tooling.

Frequently asked questions

What is crypto expense management?

Controlling, recording and substantiating company spending that settles in digital assets. It covers three separate things: purchases paid in tokens, network fees, and reimbursements paid in tokens, each of which is recorded differently.

Are crypto reimbursements taxable to the employee?

Not where the arrangement meets the accountable plan conditions in Treas. Reg. §1.62-2: a business connection, substantiation within a reasonable period, and return of any excess within a reasonable period. Fail any of the three and the arrangement is non-accountable, and the amounts are treated as wages.

How do you record gas fees in accounting?

On a separate expense line from the payable being settled, in the native token amount, with a fiat conversion taken at the same moment as the transfer it belongs to. Recording gas in fiat only moves the problem into the ETH or TRX wallet reconciliation.

Is paying a supplier in stablecoin a taxable disposition?

Paying in tokens settles a payable and disposes of an asset in the same moment, so both legs are recorded. Basis has to be tracked per wallet or account under Treas. Reg. §1.1012-1(j) from 1 January 2025.

Do I need receipts for crypto expenses?

Yes, and a transaction hash does not replace one. The hash evidences settlement; the receipt evidences what was bought. Treas. Reg. §1.274-5 sets stricter substantiation rules for travel, entertainment, gifts and listed property.

Can a company earn interest on stablecoin held for expenses?

Not from the issuer. Section 4(a)(11) of the GENIUS Act, at 12 USC 5903(a)(11), bars a permitted or foreign payment stablecoin issuer from paying a holder yield solely for holding the stablecoin. Whether an intermediary may is a separate question, and the Act’s effective-date position is set out in the B2B settlement guide.

Is a wallet top-up an expense?

Not as to the assets moved. The IRS digital asset guidance treats a transfer between wallets you own as not a disposition, except as to any digital assets used or withheld to pay for the transfer itself, which is the gas leg. It appears in every wallet export as an outflow, so it has to be tagged as internal before matching runs, or the expense account will be overstated by the full amount.

What should a crypto expense policy include?

Named wallets and their purposes; who initiates and who releases, with a second-approver threshold; permitted assets and networks; the rate source and moment; gas recording and budgeting; substantiation requirements and deadlines; whether advances are allowed and how excess is returned; the address change procedure; and what happens when screening flags a destination.

Open your chart of accounts and see whether gas has its own line. If it is sitting inside a general crypto expenses account with purchases and reimbursements, split it this week, before the next month closes. That one change makes the wallet reconcilable and makes the gas number visible enough to manage. If your wallets, permissions, invoicing and screening already sit in one dashboard, as they do in VaultNow, the split is a reporting change rather than a migration.

This article is general information, not legal, tax or accounting advice. Positions and fees are stated as at 27 August 2026 and change. Check your own facts with your own adviser.