A treasury wallet can hold the asset it needs to pay and still lack the fee balance required to submit the payment. The shortfall is operationally different from insufficient cash. A blockchain fee budget should connect expected activity, available fee assets and the actions the institution might need during stress.
The relevant unit is the wallet and network, not just the firm's monthly expense total. A central treasury reserve does little for an isolated account if replenishment requires approvals or transfers that cannot be completed before a deadline. Budgeting must therefore include where fee assets sit and how they get there.
Separate maximum authorisation from actual expenditure
EIP-1559 distinguishes the base fee, priority fee and maximum fee settings for its transaction format. A maximum fee is a cap in the submitted instruction, not an invoice showing what was spent. The operating ledger should preserve both the authorised ceiling and the actual transaction cost.
A reviewer deciding whether to approve a payment needs the ceiling and its basis. Finance reconciling costs needs the realised amount and the relevant fee asset. The institution should not book every submitted cap as actual expenditure or evaluate overspending solely by comparing an estimate with a cap selected for urgency.
A hypothetical transaction with a 100,000-unit gas limit and a 40-gwei maximum fee per gas has a 0.004-ETH execution-fee ceiling under that simple calculation. It may consume less. The example demonstrates the units, not a forecast of current network prices or a complete fee model for every blockchain.
Forecast activity by transaction family
List the workflows that generate transactions: transfers, approvals, revocations, deposits, withdrawals, collateral changes and account administration. Several transactions may support one economic action. A forecast built from payment count alone can omit the approval and cleanup work required for the payments.
Use the institution's own completed activity to estimate the range for each family. Retain unusual observations separately. An average can be useful for normal operations but should not become the only basis for an urgent withdrawal budget. The stress case should reflect the actions the institution actually plans to take.
Ethereum's gas and fee documentation explains that execution consumes gas and that a failed transaction can still incur fees. The budget should therefore distinguish successful business outcomes from chargeable execution attempts. Paying a fee does not establish that the intended asset movement occurred.
Record the number of attempts as well as the completed actions. If a workflow becomes costly because of repeated failure, identify the execution cause instead of treating the spending variance as only a pricing problem. Changing a fee limit may not fix a transaction that is failing for another reason.
Keep a reserve for risk-reducing operations
A normal operating budget can exclude activity that becomes necessary only during disruption. Examples include cancelling or replacing pending instructions through the supported process, revoking spending permissions and moving assets out of an affected account. The institution should identify these actions before allocating its fee reserve.
A reserve should have a purpose, access rule and replenishment trigger. Calling it emergency gas without specifying the authorised operations leaves signers to invent the policy during an incident. The amount should follow the network and expected transaction sequence, with a stated stress assumption.
Stress funding should also account for simultaneous demand across wallets. If every account depends on one replenishment wallet, test whether the source can fund them all under the same stressed conditions. A reserve visible on a consolidated balance report may be operationally concentrated.
This fits the wider treasury payment exception process. A fee shortfall needs a named owner and an approved route for replenishment. It should not force a payment operator to bypass the treasury's destination or signing controls.
Do not substitute a new network casually
A cheaper network may require a different supported asset, destination route or intermediary. The fee comparison should include the full workflow and the receiver's ability to accept it. A lower quoted network fee does not justify changing the settlement route without checking the original payment requirements.
For networks with additional fee components, obtain the relevant model and capture the components separately. This article's Ethereum execution example should not be copied into every rollup or alternative chain. The treasury's catalogue should state which asset pays each charge and which service invoices fees outside the chain.
A cost-saving proposal should describe what changes operationally: who receives the payment, which chain holds it, whether another transfer is needed and which party bears that transfer cost. The institution can then compare like-for-like delivered outcomes. A transaction-level saving may disappear when the entire route is included.
Replenishment is a controlled payment
Define a minimum operating balance per active wallet, with a trigger based on the expected upcoming workload. A fixed native-token threshold may be easy to implement but should be reviewed against the actual fee range and scheduled activity. The same quantity can cover very different numbers of transactions under different conditions.
Set a replenishment ceiling as well. Excessive fee balances create another asset exposure and another reconciliation obligation. Treasury should approve how the fee asset is acquired, where it is held and how unused amounts return to the appropriate account. Funds should not drift between client or entity wallets merely because they are labelled operating gas.
Separate the asset-acquisition approval from the wallet-funding instruction where required by the institution's process. Record the source account, destination, entity and cost allocation. The payment is small relative to a large treasury transfer, but it still changes the assets controlled by each wallet.
The wider discussion of stablecoin payments in corporate treasury considers payment execution. Fee budgeting supplies a supporting resource that a stablecoin balance alone may not provide.
Use estimates without turning them into guarantees
Ethereum's JSON-RPC reference describes eth_estimateGas as an estimate and notes that it can differ from actual use. Save the estimate with its inputs and observation context. Treat it as evidence for the proposed ceiling, not proof of the eventual cost.
A policy can permit routine transactions below one fee threshold and require escalation for urgent actions above it. The exception request should explain the business deadline, current estimate and available alternatives. A signer should not be left choosing between an arbitrary ceiling and a missed obligation without an escalation route.
For delayed transactions, the approval record should state when a changed fee instruction needs renewed review. The fee asset, economic destination and amount can remain the same while the authorised maximum increases. The institution should decide whether that increase is within the original mandate before the operator submits it.
Where a service provider sponsors transactions or charges fees through a commercial arrangement, treasury should obtain the charging rules and failure treatment. A wallet may show little native-token expenditure while the institution receives a separate invoice. Include that obligation in the budget and reconciliation without assuming the sponsored route removes execution cost.
The institution should also plan for the provider being unavailable or declining sponsorship. If the fallback requires a funded wallet, test its balance, access and approval route before relying on it. A fee model that works only while an external party pays can create a hidden dependency in the emergency plan.
Keep the fallback cost assumption distinct from routine prices. Its purpose is continuity, and its use should produce an identifiable exception.
Reconcile costs to actions and accounts
After execution, retain the transaction evidence needed to calculate the realised fee using the network's model. Reconcile the wallet's fee-asset movements, replenishments and closing balance. Attribute costs to the workflow or entity under the institution's policy, with failed attempts visible rather than quietly netted into successful payments.
A useful variance report separates transaction volume, execution complexity, fee price, retries and fee-asset price changes. Otherwise a month with fewer payments but more expensive emergency activity can look like an unexplained failure of the budget. The categories should help the owner change a specific process or assumption.
The fee reserve also deserves a continuity drill. Start with one underfunded wallet, a busy source wallet and an urgent risk-reducing operation. The team should obtain authority, replenish the account and execute within its planned response window. Merely pointing to a sufficient consolidated balance does not complete the exercise.
The result should be a fee plan tied to real action: normal volume, stressed volume, wallet-level availability, approved ceilings and replenishment evidence. Fees are an operating resource as well as an expense. Treasury needs to manage both dimensions if the assets it holds are to remain usable.