Scaling Funded Accounts: Eligibility and the Approval Process
Contractual scaling changes an account allocation under a specific programme. Buying a new evaluation and holding parallel accounts are different actions. Passing a challenge or recording one profitable month does not automatically unlock all three.
Record the product and starting state
Identify entity, product, purchase/reset date, agreement version, order and account model. FTMO describes its CFD accounts as simulated. Account label, usable loss room, trader share and received Reward are different quantities.
A new evaluation has its own fee and eligibility. Parallel accounts require separate checks of account count, total allocation, linking and trading permission. Adding their labels does not establish cash you control or independent risks.
Build a scaling record with every gate
| Field | What to document |
|---|---|
| Version | Product, purchase/reset date, order and applicable rule source. |
| Measurement | Period, net-result basis, closed/other entries and received Rewards. |
| Additional conditions | Account status, balance, mergers and every other stated criterion. |
| Process | Automatic transition or request; pending review versus actual approval. |
| New state | Confirmed size, loss boundaries, permissions and next measurement-period start. |
Mark each condition met, unresolved or unmet. Profit alone does not replace a missing payment or minimum period. Scaling eligibility also differs from ongoing trading-rule compliance.
Current examples are not one industry rule
Sources checked on 15 October 2026 UTC. FTMO CFD: excludes Instant; four months, at least 10% net simulated profit, two processed Rewards and positive balance. Check the plan’s exact order and period basis.
FundedNext’s purchase/reset cohort distinguishes the previous plan from Pro. The old 40% rule is not a blanket rule for new products. The 5ers High Stakes has its own stage table, not a universal monthly increase matching trading profit. Compare exact products rather than brands alone.
Fixed starting basis or current amount?
Fictional USD arithmetic, not a provider plan or growth forecast. Start at $10,000. Model A adds 25% of the current amount at each assumed approved step: $12,500, then $15,625. Model B adds 25% of the original $10,000 each time, a fixed $2,500: $12,500, then $15,000.
The first step looks identical; the second does not. A 25% increase or initial success does not imply doubling. Establish basis, rounding, stages and ceiling from the actual agreement. None of these account amounts is a received payment.
After approval, reassess rather than automatically increasing size
Record new account conditions, current equity, costs, contract values and loss floors. Keeping the same label percentage does not automatically preserve distance to a rule boundary. Larger positions are not an obligation; stops do not guarantee every execution outcome. For parallel accounts, do not add loss or risk percentages without a stated weighting and basis.
Do not claim a typical scaling duration or success rate without a defined cohort. Keep complete statements, decisions and settings changes. Tax or reporting treatment cannot be inferred solely from account size, number of accounts or whether someone trades full-time; it requires a separate applicable assessment.
Keep software and company figures in scope
FTMO personal-use conditions and The 5ers’ rules need a separate permission check. EAs can execute faulty instructions; they do not establish compliance or a scaling advantage.
The JPTC EA Hub differs from the hosted JPTC Algo. The hosted service is not offered for prop evaluations; customers install or run nothing and need no VPS for it. Company broker-statement figures are not an independent audit or a study of customer scaling.
Is buying a larger evaluation already scaling?
Does a profit target alone trigger an increase?
Does a 25% increase always produce the same account path?
Can an EA guarantee scaling or unchanged risk?
Review the JPTC EA Hub
EA software with version-specific documentation and account-level risk controls. Review the selected programme’s current automation rules and test the chosen version; software does not guarantee compliance, a pass or a payout.
See the EA Hub




