FTMO Futures Payout Rules: Eligibility Is More Than a Split

Exact payout matrix by program and account size

The matrix below is rendered from the reviewed canonical launch data. The GROWTH 100K and 150K day thresholds are supported by the supplied exact payout table rather than extrapolated from the 50K row.

Reviewed source set includes the exact GROWTH 100K and 150K threshold matrix. Eligibility is not a payout promise.

Step one: count qualifying days, not merely green days

A qualifying day must meet the exact program-and-size profit threshold. A positive day below that threshold can increase account profit without advancing the qualifying-day count. A later losing day can reduce available profit without deleting a day that already met the threshold, unless the final released terms state otherwise.

Store the session date, net rule-counted P&L, threshold, and yes/no qualification result. Preserve the source session boundary. A local midnight split can turn one program day into two journal days and create a false eligibility date.

PRO requires five qualifying days. GROWTH requires four. That changes the eligibility sequence under an otherwise identical daily path, but it says nothing about processing time, approval, or the amount that can be requested.

Step two: separate withdrawal share from profit split

The eligible-withdrawal percentage limits how much of the relevant profit can enter the request calculation. The profit split determines how an approved reward is allocated between trader and firm. These are different percentages with different denominators.

PRO permits the full eligible-profit amount to enter the request calculation before its cap. GROWTH permits half. Both then apply the stated 90/10 split under the reviewed matrix. Writing “90% payout” without the withdrawal-share boundary would overstate the GROWTH request path.

The payout-proof guide explains how to distinguish a published policy, an eligible request, an approved reward, and independently observable payment evidence.

Step three: apply the per-request cap

The cap is attached to the exact program and account size. It is not a lifetime account maximum, a promise that the maximum will be approved, or proof of money available at the time of request. Take the smaller of the eligible-withdrawal amount and the applicable cap before applying any remaining request condition.

Do not borrow a larger account's cap for a smaller account and do not convert the three account sizes into a single “up to” verdict without showing which row produces it. The component keeps the selected program and size visible beside every value.

Step four: test the new-profit condition

The reviewed rules require new profit equal to at least half of the requested amount in each new cycle. That condition should be stored as a separate boolean with its own formula and cycle start. It is not the same as the best-day consistency objective used during evaluation.

Cycle boundaries matter. A payout request can change the retained balance and the next cycle's available-profit calculation. Keep request timestamp, amount, pre-request balance, post-request balance, and the rule version together. Do not carry a prior cycle's qualifying profit into a new calculation unless the final official terms explicitly allow it.

Worked logic without a frozen price

Suppose a PRO account has completed the required number of threshold-qualified days and accumulated eligible new profit. First, the full eligible share enters the request calculation. Second, the exact account-size cap limits it. Third, the 90/10 split describes the allocation of an approved reward.

For GROWTH, the same sequence begins with fewer qualifying days but only half of eligible profit enters the request calculation before the lower account-size cap. This is the real trade-off: earlier cycle eligibility versus less profit eligible per request. The plan comparison shows when that trade-off fits a withdrawal-oriented or recovery-oriented profile.

What a payout tracker must preserve

• Exact firm, program, account size, phase, and rule version.
• Program session date and net rule-counted daily result.
• Qualifying threshold and qualification result for every day.
• Cycle start, accumulated new profit, eligible withdrawal share, and cap.
• Request amount, status, timestamps, retained balance, and evidence.

TSB can use reconciled imported history to reconstruct the daily path, but a journal cannot certify an approval or payment it did not observe. Record those later events from the official dashboard and payment evidence. The hands-on review shows why fee-separated export rows must be reconciled before the daily thresholds are trusted.

Eligibility cadence is only one part of the payout path

A shorter qualifying sequence can be attractive, but the eligible amount, risk remaining after a request, review process, and account survival matter too. Compare the complete payout conditions rather than treating the day count as a payout promise.

Cost also continues before the post-pass stage. Use the pricing model to keep evaluation spend separate from an assumed future reward.