Crypto conditional orders do not follow one universal fund-reservation rule. Some reserve assets when submitted; others check and commit funds only after a trigger. A successfully accepted pending order therefore does not always prove it can be funded later. Identify the venue, product and exact order subtype, then budget every commitment that could become active against the same spendable assets.
Read the reservation rule beside the trigger rule
A pending instruction contains at least two questions: what makes it activate, and where will its funds come from? An accepted trigger answers neither the later balance check nor the eventual fill price.
Bybit's V5 documentation gives a useful, narrowly scoped comparison. For Spot, its orderFilter distinguishes these two subtypes:
| Bybit Spot subtype | Before the trigger | After the trigger |
|---|---|---|
tpslOrder | Required assets are occupied | Execution still depends on the resulting order |
StopOrder | Required assets are not occupied | Required assets are occupied when triggered |
The same placement documentation says conditional derivatives orders do not occupy margin before activation and can be cancelled if margin is insufficient afterward. These are Bybit's documented order-placement rules, not a definition for every exchange or every order called “stop.” Record the product and subtype instead of inferring reservation behavior from a familiar interface label.
Even a funded instruction can remain unfilled. A triggered limit order needs an acceptable match; a market instruction faces its execution rules. The stop-market versus stop-limit guide separates that execution question from the funding question here.
Keep two views of the same money
The exchange's reservation and a trader's intended budget serve different purposes:
- Provider-held funds are already unavailable under the venue's rules.
- Locally budgeted commitments are money assigned to pending plans that the provider has not held.
A local budget can stop cooperating strategies from promising the same funds twice. It does not lock those funds at the exchange. A manual trade, withdrawal or another application can still consume them.
Start with the provider's usable amount for the intended action, account and asset. Do not subtract exchange-held funds again if that amount already excludes them. Bybit's wallet-balance schema defines locked as funds held by Spot open orders and separately defines account-wide available margin in USD; those account-wide fields do not apply to isolated margin. A USD margin valuation is not automatically the same amount of spendable USDT.
The available-versus-total balance worksheet covers field mapping and snapshot timing. Here the additional question is what future claims remain invisible to that available amount.
Two pending buys share the same 750 USDT
This is an original hypothetical spot-cash example, not a venue fee schedule. Assume one account holds 1,000 USDT. An existing active order already holds 250 USDT, leaving 750 USDT provider-available. The trader also wants to keep a 50-USDT policy buffer.
Two independent conditional buys are accepted without reserving assets. Plan A's maximum purchase amount is 450 USDT plus an assumed 5-USDT fee allowance. Plan B's is 350 plus 5. Assume both can trigger, neither cancels the other, and these allowances fully cover the example's cash costs. There is no margin borrowing, other activity or price change in the worked states.
| Cash claim | Amount | Already excluded from provider-available cash? |
|---|---|---|
| Existing active order | 250 USDT | Yes |
| Conditional Plan A | 455 USDT | No |
| Conditional Plan B | 355 USDT | No |
| Policy buffer | 50 USDT | No |
| Total intended use | 1,110 USDT | — |
The two conditional plans promise 455 + 355 = 810 USDT. Against the 750 available, they are 60 short even before the buffer. Including that buffer, the unassigned planning balance is 750 − 455 − 355 − 50 = −110 USDT.
The example's headline commitment excluding the optional buffer is 250 + 455 + 355 = 1,060 USDT. Accepted pending orders have allowed the planner to promise more cash than the account holds. The provider did not promise to fund both later.
Now assume A triggers and fully spends exactly 455 USDT, including its fee. The existing 250-USDT hold remains. A leaves the future-commitment bucket because its cash has been spent; keeping it there would subtract it twice.
| Reconciled state | Provider-available USDT | Unheld conditional commitments | Buffer | Unassigned planning balance |
|---|---|---|---|---|
| Before either triggers | 750 | 810 | 50 | −110 |
| A fully executed | 295 | 355 | 50 | −110 |
After A, total USDT is 1,000 − 455 = 545; subtracting the unchanged 250 hold leaves 295 available. B requires 355, so the cash shortfall is still 60. A's successful execution did not repair the original overcommitment.
A coherent plan would resolve that deficit before accepting both commitments locally: for example, defer one plan, reduce a permitted amount or document a tested cancellation relationship. Two different trigger prices alone do not make plans mutually exclusive. A market path can reach both at different times.
Move commitments between states
Use the following worksheet whenever an order changes state. It is a planning method, not an exchange accounting formula.
| Event | Treatment of the future commitment | Evidence needed |
|---|---|---|
| Unreserved conditional accepted | Keep the intended cash claim locally | Confirmed subtype, size and reservation rule |
| Triggered into a resting funded order | Move the occupied amount out of the unheld bucket | Active-order and balance evidence showing the hold |
| Partially filled | Separate spent cash, provider-held remainder and any unheld remainder | Confirmed fills, fees and remaining quantity |
| Definitively rejected or cancelled | Release only the confirmed unused commitment | Terminal state plus reconciled fills |
| Response lost or cancellation pending | Preserve the unresolved claim | Authoritative outcome before reusing cash |
The difficult case is a trigger followed by an ambiguous response. The instruction might have become an active order, filled partially or been rejected. Neither “triggered” nor “cancel sent” establishes released funds. Use the order-timeout reconciliation process before spending that capacity again.
Recalculate costs when size, limit price or fee assumptions change. A budget based on a price from submission time may no longer cover an instruction activated much later. A fixed purchase cap also needs a clearly stated treatment for fees outside that cap.
Derivatives add collateral and debit timing
The spot worksheet cannot be copied directly into a leveraged account. Bybit's perpetual and expiry contract order-cost explanation includes initial margin plus opening and estimated closing fees. The applicable margin model and current account conditions affect what can support another order; notional divided by leverage alone is an incomplete cash estimate.
Keep anticipated debits in their correct currencies. A funding payment between submission and activation can change available capacity. The funding settlement-currency guide explains why the asset debited matters alongside a valuation. Likewise, liquidation fees versus trading fees distinguishes forced-close charges from ordinary execution costs; budgeting an entry does not establish that a position can survive a later margin shortfall.
For a protective close, establish whether the instruction reduces an existing position and what the venue requires for that order subtype. Do not assume it behaves like a new entry merely because both use triggers; the reduce-only order guide covers the position constraint.
Before relying on a conditional instruction, the useful record is specific: assets held now, assets merely promised, the other plans sharing them, and the evidence required to release each claim. That record makes a later rejection explainable without treating a pending order as a cash reservation.
Method and limits
Prepared with AI assistance from primary Bybit documentation reviewed on 23 October 2026. The cash ledger and state worksheet are original educational examples. No live account was queried; these venue rules do not establish a dedicated conditional-order reservation feature in KLINEO.