What Matters
A funding charge cannot be checked against today’s displayed rate alone. Rebuild each settlement using the applicable rate, position value, side, time and settlement currency, then compare the result with the account ledger. Rate displays, payment intervals and notional formulas differ by product. A mismatch is a reason to investigate the inputs before concluding that a charge is wrong.
DN Evidence Block
Last verified: 29 October 2026. Scope: official Bybit, OKX and Hyperliquid funding documentation and Hyperliquid’s funding-history API reference. Original DN tool: Funding Bill Reconciler, a manual settlement worksheet and a synthetic three-event ledger.
Decisive distinction: Bybit and OKX describe mark-price-based position valuation for the contracts covered by their examples. Hyperliquid’s funding documentation instead specifies oracle-price valuation and an eight-hour formula with hourly payments. [1] [2] [3]
Method: documentation review and arithmetic validation. DN did not access accounts, submit trades or test billing systems. The 2027 edition uses evidence reviewed in October 2026. Current contract and account rules take precedence.
Start with the settled transaction, not an annualized headline
Find the actual funding entry for the contract and account. Preserve its timestamp, currency, amount, position side and reference. A website’s current rate can describe the next settlement or a normalized period. It is not necessarily the rate that produced yesterday’s ledger entry.
Do not start by dividing a displayed APY by a fixed number of events. Annualization may use assumptions that do not match the contract’s settlement interval, historical rates or your holding period. Funding can change sign. An annualized illustration is not a promised return or a substitute for the event record.
This guide audits an existing funding bill. For comparing venue mechanics before trading, see the DN Perpetual Funding Stability Index.
DN Funding Bill Reconciler
Use one row for every settlement event and every relevant position leg. Copy the following worksheet into a spreadsheet or your notes. It is a manual audit tool and sends no account data to DN.
| Input | Evidence to capture | Common mismatch |
|---|---|---|
| Contract and account | Exact instrument, product, subaccount and long/short leg | Combining different contracts or accounts |
| Settlement event | Timestamp, source timezone, ledger reference | Comparing the wrong interval |
| Applied rate | Historical settled rate and its period/unit | Using a current estimate or an annualized display |
| Position quantity | Eligible quantity at the event, with contract units | Using current size after a partial close |
| Valuation basis | Required price, contract size and multiplier | Using entry price, margin or the wrong price index |
| Expected signed funding | Rebuilt payment or receipt in settlement currency | Percentage or sign conversion error |
| Recorded signed funding | Normalized ledger debit/credit and precision | Assuming every export uses the same sign convention |
| Residual | Recorded minus rebuilt amount, with explanation | Unexplained rounding or missing events |
The calculation and sign convention
For a product where positive rates mean longs pay shorts, define rebuilt signed funding = direction × position value × applied decimal rate, using direction +1 for a long and −1 for a short. In this DN worksheet, positive funding means an expense; negative means a receipt. The position value and rate must already be expressed in compatible units for that settlement.
Convert percentages correctly: 0.01% is 0.0001 as a decimal. Normalize your ledger’s sign convention before comparison. The worksheet convention does not claim that every platform or API exports debits and credits this way.
Residual = recorded signed funding − rebuilt signed funding. Keep unresolved rows separate. A nonzero residual is a discrepancy to explain, not automatic proof of an overcharge.
Check the product’s position-value formula
Funding is commonly based on position value rather than the collateral deposited. The same margin balance can support different notional positions, while the same notional can be maintained with different collateral balances. Multiplying the rate by initial margin can therefore badly understate the expected charge.
OKX’s calculation guide explicitly includes contract count, contract size and multiplier. Its USDT-margined example multiplies by mark price; its crypto-margined example divides by mark price and produces a coin-denominated value. [2] Do not paste a linear formula into an inverse contract without checking the specification.
Hyperliquid’s documentation uses oracle price for its stated funding-payment valuation, and describes hourly application of one eighth of the computed eight-hour rate. It also distinguishes HIP-3 funding-formula behavior. [3] For a specific market or API field, confirm whether the returned rate is already normalized to the payment period. Dividing a rate twice creates another error.
Audit question: can you explain every multiplier, price and currency in your reconstructed amount? If not, retain the row as unknown rather than filling a missing input with an assumption.
Worked reconstruction: three events, changing size and sign
Synthetic linear-contract example, not a real exchange bill. Assume the trader is long at all three settlement events and the values shown are already the correct settlement notionals and per-event rates. A partial close before event B changes the position value. Event C’s rate changes sign.
| Event | Eligible position value | Applied rate | Rebuilt funding |
|---|---|---|---|
| A | 100,000 USDT | +0.010% | +10 USDT expense |
| B | 60,000 USDT | +0.030% | +18 USDT expense |
| C | 60,000 USDT | −0.005% | −3 USDT receipt |
| Net | Not a sum of position values | Not an average rate | +25 USDT expense |
The arithmetic is 100,000 × 0.0001 + 60,000 × 0.0003 − 60,000 × 0.00005 = 25 USDT. If the normalized ledger also records a net 25 USDT expense with matching event amounts, the example reconciles. A net total alone does not prove every row is correct: offsetting mistakes can cancel each other.
A trader using only the final 60,000 USDT position and the first +0.010% rate for all three events would estimate 18 USDT and see a false 7 USDT discrepancy. The error comes from mismatched inputs rather than the bill. This example assumes exact values and excludes rounding, collateral conversion and other charges.
Reconstruct the settlement schedule that actually applied
Do not assume every perpetual settles three times per day. OKX’s funding FAQ describes different intervals for different contracts and tells users to inspect the contract schedule. It also identifies account funding-history records. [4] A daily total can differ because the number of eligible events differs.
Bybit’s calculation guide notes that intervals and limits can vary and describes an automatic switch to hourly settlement when a contract reaches its preset funding limit. It also warns that opening or closing within five seconds either side of funding time does not guarantee inclusion or exclusion. [1] This is a provider-specific boundary warning, not a universal safe timing rule.
Preserve actual position changes and execution times. An order submitted before settlement may fill afterward; an accepted close is not the same as a completed close. For uncertain execution, use the DN Order Timeout Guide.
Keep funding separate from the rest of the account ledger
Separate funding from trading fees, realized P&L, borrow interest, liquidation charges, transfers and collateral conversions. Some interfaces display cumulative metrics, while individual transaction logs show separate entries. Summing both can count the same charge twice.
Reconcile in the native settlement currency first. If you later convert to USD or another reporting currency, record the conversion price and time as a separate step. A changing coin price can change the reporting-currency value even when the coin-denominated funding amount is unchanged.
For developers, Hyperliquid’s API reference distinguishes user funding history, historical market funding rates and non-funding ledger updates. [5] These answer different questions: the public rate history alone does not establish the exact quantity held in a particular account.
Use the DN Balance Reconciliation Guide to connect funding entries to the broader balance movement. For a hedged trade, reconcile each leg separately before netting amounts. Offsetting direction does not guarantee equal funding, equal value or matching settlement times.
If a residual remains, send an answerable support case
First check incomplete history exports, duplicate rows, timezone conversion, currency, precision and account scope. Where the contract publishes a rounding rule, apply that rule; do not dismiss an unexplained difference as rounding merely because it looks small.
Copyable funding audit request
Account/subaccount and exact contract: [details]
Settlement timestamp and timezone: [time]
Position side and eligible quantity: [evidence]
Applied settled rate and source: [rate, period, URL/export]
Valuation formula and settlement price used: [inputs]
Rebuilt amount and currency: [amount]
Recorded amount, sign convention and transaction reference: [details]
Residual after applicable rounding: [difference]
Please confirm the applied quantity, rate, valuation price, rounding rule and any adjustment associated with this event.
Use the authenticated official support channel. Do not disclose passwords, API secrets or wallet recovery phrases. Keep the original export and your calculations so that a later correction can be traced.
Use the audit before comparing venues
A lower displayed rate is not enough to justify a move. Compare compatible periods and include execution fees, slippage, transfers and custody exposure. Start with the DN Venue Switching Cost Calculator or DN Pathfinder after your current ledger is understood.
Affiliate disclosure: linked DN tools and reviews may contain affiliate links. They are optional research pathways; no signup is required to use this worksheet. This article does not rank venues or recommend a funding-capture trade.
Methodology, limitations and corrections
DN reviewed five official pages and validated the synthetic arithmetic with decimal calculations. This is a manual reconciliation framework, not an account-connected calculator, live billing test or guarantee of a support outcome. The example does not model liquidation, funding collection shortfalls, every contract type or future returns. Missing account evidence cannot be replaced by a public rate chart. Version 1.0, 29 October 2026. Send corrections with a source URL through DN’s contact page.
Frequently Asked Questions
Why is my funding fee different from the displayed rate?
The screen may show an estimate, a different period or a later rate. Compare the actual settlement rate with the eligible position value and account entry.
Is funding charged on margin or position value?
Check the contract rules. The products discussed here use a position-value calculation; collateral deposited is not automatically the funding base.
Can I multiply the current funding rate by three for a daily cost?
Only as an explicitly assumed scenario with compatible periods and constant inputs. It is not a reconstruction of actual settled charges.
Does an opposite position cancel my funding cost?
Not necessarily. Values, rates, currencies and settlement schedules can differ. Reconcile each leg before netting.
Does a mismatch prove I was overcharged?
No. Resolve missing events, units, timing, price basis, currency and rounding first. Preserve unexplained residuals for a documented investigation.
Primary sources
- Bybit: Funding Fee Calculation, updated 12 May 2026.
- OKX: How to calculate futures funding fees, updated 11 August 2026.
- Hyperliquid: Funding.
- OKX: Perpetual Futures Funding Fee FAQ.
- Hyperliquid: Perpetuals info endpoint.
All sources reviewed 29 October 2026. Product availability and terms vary. General operational education, not individualized investment advice.