Prop Firm Payout Date Calculator
Combine your entered payout waiting period with remaining candidate qualifying days, selected weekdays and excluded dates. The result is an earliest request-date and processing-date scenario—not proof that a trading day will qualify or that a provider will approve or deliver a payout.
Enter one verified payout calendar
Use the provider’s exact anchor, count basis and qualifying-day definition. The page never reads trades or provider status.
Entered calendar gates
Entered Prop-Firm Rule Planning 1.0.0
On smaller screens, scroll horizontally to inspect the complete entered and derived audit.
| Calendar row | Date | Basis | What the row means |
|---|
How the payout calendar is calculated
Remaining qualifying days = max(required − completed, 0)
Earliest candidate request = max(as-of date, wait gate, final candidate qualifying date)
The anchor date is day zero. Calendar-day addition counts every following date. Weekday addition counts Monday through Friday and skips the entered excluded-date list.
Remaining qualifying days are required minus completed, floored at zero. The page does not inspect trades or determine whether the completed count is correct.
Future candidate slots begin strictly after the as-of date. A slot must match one selected weekday and must not be in the entered excluded-date set.
The request-date scenario is the latest of the as-of date, waiting-period gate and final candidate qualifying date. A count gate that is already complete does not move the date beyond the as-of date.
The processing-date scenario adds the entered count after the request date using calendar days or Monday-to-Friday weekdays. It is not a delivery estimate and excludes provider review, banking and payment-rail uncertainty.
Worked example from the audited fixture
The audited example uses an as-of date of 2026-07-27, anchor 2026-07-20, a 14-calendar-day wait, five required qualifying days with two complete, Monday-to-Friday candidates, exclusions on 2026-07-31 and 2026-08-03, and three processing weekdays.
- The three remaining candidate slots are July 28, July 29 and July 30. That places the candidate qualifying-day gate on July 30, while the 14-day waiting gate is later on August 3.
- The earliest request-date scenario is August 3. Adding three entered weekdays while excluding August 3 produces an August 6 processing-date scenario. Neither date establishes eligibility, approval or funds received.
Reproduce it: select “Load audited example” above. The governed fixture was independently recomputed from decimal arithmetic and UTC date-only rules.
How to interpret the result
- Verify whether the provider counts calendar days, weekdays, trading days, winning days or profitable days; those labels are not interchangeable.
- Use the as-of date as the last date for which the completed qualifying-day count is known.
- Select only weekdays that can become qualifying days under the independently verified rule and enter holidays or unavailable dates explicitly.
- The later gate explains which entered timing condition controls the current candidate request date.
- Processing arithmetic begins after the candidate request date and is a user-entered scenario, not a service-level promise.
- Recalculate after each actual qualifying day, payout request, provider reset or rule change.
Assumptions and limits
- The page does not observe orders, profit thresholds, consistency, balance buffers, account age, compliance or provider approval.
- Dates are processed as ISO date-only UTC values; no session cutoff, timezone or daylight-saving conversion occurs.
- Weekday basis means Monday through Friday, not a jurisdiction-specific banking or exchange calendar.
- Excluded dates are accepted exactly as entered and are not fetched from a holiday source.
- Banking delays, provider review, KYC, payment rails, weekends, jurisdiction and tax requirements remain outside the result.
- No trading schedule, qualifying-day tactic, payout request, provider or trade is recommended.
Which prop-firm calculator answers which question?
The three Batch 48 tools separate a drawdown floor, an allocation ladder and a date calendar. The existing Challenge Planner keeps target and day counts, while the existing Payout Split Calculator keeps reward-share arithmetic. This prevents one convenient screen from implying a provider verdict it cannot make.
| Tool | Primary input | Primary output | Hard boundary |
|---|---|---|---|
| Trailing Drawdown | Reference values, amount and optional lock | Entered floor and signed arithmetic distance | No provider breach decision |
| Scaling Plan | Allocation, increment, cap and reference percentages | Tier-by-tier entered allocation ladder | No provider scale-up approval |
| Payout Date | Anchor, counts, weekdays and exclusions | Earliest candidate request and processing dates | No qualification or delivery promise |
Frequently asked questions
- It combines an entered waiting-period gate with remaining candidate qualifying-day slots and shows the later request-date plus an entered processing-date scenario.
- No. The page does not inspect trades, profit, consistency, buffers, account age, compliance, identity checks or provider approval.
- The anchor is day zero and every following calendar date counts, including weekends and entered exclusions unless the selected basis is weekdays.
- Weekday addition counts Monday through Friday after the anchor and skips dates supplied in the excluded-date field. It is not a jurisdiction-specific business-day calendar.
- Slots begin strictly after the as-of date, match one selected weekday and exclude entered dates. Each slot still must later satisfy the provider definition.
- The candidate qualifying-day gate remains on the as-of date, so it does not push the request scenario later than the waiting-period or as-of gate.
- No. It only adds the entered count after the candidate request date and does not model review, banking, payment rails, holidays, jurisdiction or rejection.
- No. Version 1.0.0 uses ISO date-only UTC arithmetic and performs no timezone, daylight-saving, session-reset or trading-day-boundary conversion.
Sources and methodology
- FundedNext — Performance Reward timing — Official evidence that first and later cycles can differ by program.
- FundedNext — minimum trading days — Official example of phase-specific day counts and an entered-trade definition.
- Topstep — Payout Policy — Official evidence of winning-day, trading-day and restart conventions that vary by account.
Version 1.0.0 performs deterministic local arithmetic and uploads no entered values. Official provider pages establish that definitions vary; they do not become embedded presets. Verify the current program, phase, cohort and legal terms before each use.
Check the non-date payout gates separately
Keep broker execution separate from prop-firm rules
Prop-firm arithmetic does not replace the broker or platform specification for volume, margin, price, session, liquidation and order execution. Verify both rule sets before exposing capital.
FXOpen
Verify the applicable platform and jurisdiction-specific trading conditions.
Check FXOpen termsRisk and affiliate disclosure: Leveraged forex and CFD trading can result in substantial losses. Prop-firm programs can change rules, deny requests after review or close accounts under their terms. These are affiliate links, so ForexMT4Indicators.com may receive compensation if you register or trade through them, at no additional cost to you. Availability and terms vary by jurisdiction and entity.