Accountable publisher
Published under the RTX5 Editorial Team byline. It identifies the responsible publishing organization; it does not imply that a named lawyer, regulator, financial adviser, or licensed expert approved this page.
Data guideInformationalPublished reference
Balance, Equity, Drawdown, and Daily-Loss Calculations for Prop Firms
Evidence-led data guide: Balance, Equity, Drawdown, and Daily-Loss Calculations for Prop Firms. Review decision criteria, limitations and next steps.
Trust and methodology
How this research was prepared
We want you to be able to identify who owns the page, inspect the evidence, understand how tools were used, and challenge anything that looks wrong or out of date.
Evidence you can inspect
2 primary references are listed on this page with context about what each one supports. The source set was checked on . The page also includes an original working artifact: Daily-loss and trailing-drawdown example.
Assistance is disclosed
Automation and AI may help organize research, outline a page, or edit language. They are not treated as sources, are not presented as human experts, and do not remove the publisher's responsibility for the final page.
Corrections are welcome
If a statement is incomplete, unsupported, or outdated, send the exact URL, sentence, and supporting evidence through our contact route. Read the full editorial and corrections policy.
Direct answer
What the evidence supports
Balance is the account ledger value after booked transactions. Equity is balance adjusted by current unrealized profit or loss and any other platform-defined items. Drawdown is a decline from a reference value, but the reference and timing vary: initial balance, start-of-day balance or equity, trailing high-water mark, static threshold, intraday equity, end-of-day snapshot, or closed balance. Daily-loss limits can include realized loss, unrealized loss, commissions, swaps, fees, deposits, withdrawals, or reset-time adjustments depending on the written rulebook.
A prop firm must translate every rule into an unambiguous calculation contract before selling an evaluation. Define data source, currency conversion, timezone and reset, reference value, included cash flows, open-position treatment, threshold comparison, rounding, late corrections, disconnections, symbol closure, breach timing, and appeal evidence. If the dashboard, risk engine, support team, and customer terms compute different values, disputes are inevitable.
Original worked calculation
Daily-loss and trailing-drawdown example
The result changes when a rule uses equity instead of balance, includes open P/L, or moves a high-water mark. Publish the equation and the event timestamps.
Daily-loss rule
Start-of-day reference $100,000; maximum daily loss 5% = $5,000. Closed P/L is −$1,200 and open P/L is −$3,900, so equity loss is $5,100 and breaches the limit by $100 if open P/L is included.
Trailing rule
High-water equity $105,000; trailing allowance 10% = $10,500; current floor $94,500. Current equity $94,400 breaches the floor by $100.
Required rule fields
State timezone, reset event, balance or equity, fees, swaps, currency conversion, open-position treatment, price source, threshold equality, high-water movement, corrections, and outage behavior.
This is an illustrative test vector, not a recommended prop-firm rule. Give the same timestamped events to the risk engine, dashboard, statement, and support tooling and require the same result.
Inputs that define a prop-risk calculation
The formula is only the beginning. State, time, cash flow, currency, and data-quality rules determine the number users actually see.
Reference baseline
Specify initial, day-start, prior close, trailing peak, or fixed monetary baseline and whether it uses balance or equity. Define when a peak updates and whether it can move downward after withdrawal or correction.
Included economic components
List realized P&L, unrealized P&L, commission, swap, financing, platform fee, adjustment, credit, rebate, deposit, withdrawal, payout, conversion, and tax treatment. Use examples with positive and negative values.
Time and reset
Choose authoritative timezone, daylight-saving handling, trading-day calendar, holiday behavior, rollover, reset event, positions held across reset, delayed fills, backdated corrections, and service outage treatment.
Prices and currencies
Define bid, ask, mid, mark, last, provider, stale-price, market-closed, and conversion-rate policy. State precision and rounding at instrument, account, and display levels.
Breach semantics
State strict greater-than versus greater-than-or-equal, momentary versus confirmed breach, grace or no-grace policy, action on open orders and positions, account state, notification, evidence retention, and appeal process.
Turn a marketing rule into a testable specification
- 01
Write equations and state tables
Represent each rule with named variables, units, sign conventions, data sources, update triggers, states, and precedence. Avoid phrases such as “up to” or “during the day” without definitions.
- 02
Create worked examples
Include wins, losses, open positions, commissions, swaps, deposits, withdrawals, reset boundaries, multiple currencies, partial fills, stale quotes, and exact-threshold cases.
- 03
Run deterministic test vectors
Give the same timestamped events to risk engine, dashboard, back office, statements, and support tooling. Every component should produce the same threshold, value, and account state.
- 04
Test live-state failures
Delay quotes and fills, disconnect services, cross reset time, change conversion rates, correct trades, and restart systems. Define whether calculation pauses, uses a fallback, or blocks activity.
- 05
Publish and version the rule
Show the effective rule, examples, timezone, version, change notice, grandfathering policy, support route, and appeal evidence. Keep the applied version with each account.
Evidence for a breach or payout decision
A reviewer should be able to reconstruct the calculation from immutable events rather than relying on a screenshot of one displayed number.
Versioned rule contract
Retain the exact terms, formula, thresholds, included components, timezone, price policy, effective period, and account assignment.
Timestamped event ledger
Keep orders, executions, corrections, balance entries, fees, prices, conversion rates, resets, system states, and identifiers needed to replay the result.
Calculation trace
For each material update, store inputs, intermediate values, reference peak or baseline, output, threshold comparison, rule version, and decision.
Data-quality record
Flag stale, missing, corrected, disputed, or fallback data and record how the policy treated it.
Case and appeal history
Preserve notifications, support evidence, reviewer actions, override authority, decision rationale, correction, payout impact, and final communication.
Boundaries and limitations
- There is no universal prop-firm drawdown formula; the firm’s disclosed rulebook and applicable law define the commercial rule.
- A dashboard estimate should not be represented as authoritative if the contract uses another price source, clock, or ledger.
- Risk controls can enforce rules but do not prove the fairness, legality, financial condition, or payout reliability of a prop firm.
- RTX5 configuration must be tested against the signed rule specification for the exact deployment and account program.
Primary references
Sources were checked on 21 September 2026 and support the stated context; they do not certify RTX5, replace product testing, or provide individual legal or financial advice.
Questions readers ask
Is daily drawdown based on balance or equity?
It can be either, both, or a more specific defined value. The firm must state the authoritative formula, open-position treatment, data source, and reset.
What happens to drawdown after a payout?
That depends on whether the baseline is fixed, trailing, balance-based, or adjusted for withdrawals. The rule and examples must state the behavior before purchase.
Can a momentary price spike cause a breach?
Only the written rule and data policy can answer. Define authoritative prices, stale or erroneous-quote handling, confirmation logic, and dispute evidence.
Continue through the evidence map
Review the planning cluster, follow another published reference, or discuss the exact product and deployment evidence your team needs. A contact request is not a promise of regulatory approval, market access, or universal availability.