A useful FundedNext journal starts with the exact program, not the firm name. Stellar 1-Step and Stellar 2-Step have different targets, loss limits, phase structures, minimum days, and account conditions. A generic “FundedNext” rule row can therefore show a correct number for the wrong contract.

The server-rendered comparison above is the changing fact layer for the same global/default simulated account size and first evaluation stage. It supplies current price, objectives, loss rules, minimum days, payout context, platforms, restrictions, official sources, and verified dates from the canonical catalog. The workflow below remains editorial. If a catalog update conflicts with it, the component warns for review instead of silently changing the conclusion.

Use the dashboard and the terms attached to your purchase as the live authority. A journal can preserve rule inputs, trades, screenshots, and calculations; it cannot see every open-position change, override a breach, or guarantee a Performance Reward.

FundedNext Challenge Rules

At setup, record firm slug, program ID, phase ID, region, account size, base currency, platform, add-ons, purchase/reset date, server timezone, and lifecycle status. FundedNext publishes separate current rules for Stellar 1-Step and Stellar 2-Step, while older Express and Evaluation models remain legacy products for existing users rather than current choices for a new buyer.

Journal control Stellar 1-Step Stellar 2-Step
Evaluation structure One Challenge phase, then review and KYC before a FundedNext Account if approved Phase 1 and a separate Phase 2, then review and KYC before a FundedNext Account if approved
Rule snapshot Store the 1-Step target, daily-loss amount, maximum-loss floor, and minimum-day state Store Phase 1 and Phase 2 as different lifecycle records with their own targets and day counts
Live authority Exact dashboard state and purchase terms Exact dashboard state and purchase terms
Do not inherit 2-Step limits, phase count, EA scope, or reward timing 1-Step limits, one-phase workflow, or account-size restrictions

The exact live numbers belong in the SSR rows and your dated account record, not duplicated prose. For broader firm evidence, regional caveats, and buyer checks, use the FundedNext review.

Do Not Treat Add-Ons as Footnotes

FundedNext sells add-ons that can change commercial terms and, for eligible combinations, minimum-day or reward mechanics. Save the checkout selection and final terms as evidence. Never apply an add-on merely because the same label appears on another program or account size.

A strong journal stores both a machine key and a readable label. A name such as “FN 100K” is not a stable key: it omits route, phase, region, add-ons, and attempt. A reset or next phase starts a new lifecycle record even if the platform login or nickname looks similar.

The Daily Loss Rule — How It Calculates

The old guide incorrectly said the next day's allowance was a percentage of the previous closing balance. FundedNext's current general CFD explanation says each enrolled Challenge has a fixed daily-loss amount based on Initial Balance × the exact program percentage. Current-day closed and floating results count, along with swaps, commissions, and fees. The daily calculation resets at 00:00 FundedNext server time.

Daily-loss amount = Initial Balance × current program daily-loss percentage.

Current daily result = closed results since server reset + open-position result − swaps − commissions − applicable fees.

Remaining daily room = daily-loss amount + current daily result, when profit is positive; subtract accumulated loss when it is negative.

Do not use that simplified journal result if its sign convention, open P&L, costs, or reset boundary is uncertain. FundedNext says the server offset changes seasonally and provides a dashboard countdown. Record the displayed next-reset time rather than hardcoding a permanent UTC offset.

An overnight floating loss can be within the current day's allowance and breach immediately after the reset because the prior day's profit no longer expands the new day's room. Before holding across midnight, model both the pre-reset and post-reset state. The prop-firm drawdown tracker provides the full floor-and-buffer record.

Maximum Loss Is a Separate Static Floor

For the two exact Stellar Challenge routes above, FundedNext documents Maximum Loss against the initial balance. Profit can increase the distance above that floor, but the floor itself does not trail upward with profit. Use the route-specific percentage from the component. Keep balance and equity evidence because either crossing the fixed floor can matter.

Maximum-loss floor = Initial Balance − exact program maximum-loss amount.

Maximum-loss buffer = current rule-counted equity − maximum-loss floor.

Usable pre-trade buffer = smaller verified buffer − open/pending exposure − execution cushion.

The execution cushion is your policy, not FundedNext's rule and not a guarantee. It should reflect gaps, spread changes, stop slippage, correlated positions, and data delay. Size the next order from the smaller verified buffer and the strategy's tested risk—not from the simulated account label alone. See the prop-firm position-sizing method.

What to Track in Your Journal

  1. Exact contract identity: firm, program, phase, region, size, currency, platform, account type, add-ons, purchase/reset date, official source URL, and verified date.
  2. Server-day state: server time, next reset countdown, Initial Balance, day-opening evidence, closed result since reset, floating result, swaps, commissions, fees, and current equity.
  3. Both loss controls: fixed daily-loss amount, accumulated daily result, remaining daily room, static maximum-loss floor, maximum-loss buffer, and calculation timestamp.
  4. Objective state: current phase, target progress with the correct calculation basis, qualifying trading days, passed/pending/review status, and any account-specific requirement.
  5. Execution evidence: source ticket or fill, normalized logical trade, market, direction, size, timestamps, entry, stop, exit, gross result, costs, and net result.
  6. Decision evidence: setup, session, pre-trade thesis, invalidation, screenshot, planned risk, actual maximum exposure, news/event context, and deviation reason.
  7. Data quality: source file or connection, import batch, last synchronized execution, duplicate/missing-ticket check, balance variance, reviewer, and unresolved fields.
  8. Lifecycle and rewards: Challenge, next phase, review, FundedNext Account, breached, reset, archived, reward eligibility, request, approval, deductions, and received evidence as separate states.

Use Not verified for a missing catalog fact and Unknown for an account calculation that lacks required live state. Zero is a value; it is not a substitute for missing data.

Challenge Reward Share: Track Eligibility, Not an Assumed Payout

The old article said FundedNext paid a challenge share regardless of whether the trader passed and illustrated it as immediate income. Current official terms are more conditional. Availability varies by route, region, purchase/reset cohort, scale-up eligibility, and add-ons. FundedNext's current Stellar 2-Step help article says the challenge reward becomes withdrawable only after later eligibility conditions are met and is unavailable to U.S.-based clients.

Do not record a percentage of Challenge P&L as cash income. Use a state machine:

  1. Observed Challenge result: reconciled trading result, not a receivable.
  2. Potential contractual reward: exact route, region, cohort, and conditions saved from current terms.
  3. Eligibility met: evidence that every condition is satisfied.
  4. Request submitted: timestamp and requested amount from the official surface.
  5. Approved: statement, reward share, deductions, and decision date.
  6. Received: payment evidence, currency, fees, and net amount.

Only the last state is received cash. For a general evidence ladder and red flags, read the prop-firm payout proof guide.

Stellar 1-Step vs 2-Step — Which to Track

This is not a universal “easier” verdict. The 1-Step route has fewer phases but a tighter published loss envelope; 2-Step has two distinct phases and a broader published loss envelope. The component supplies the live numbers. Your decision should use the strategy's own loss distribution and operational needs.

Compare the same evidence set for each route:

  • How often would historical rule-counted equity approach the daily and maximum-loss floors?
  • How many trades and server days did qualifying setups naturally require, without forcing activity?
  • Does the intended account size permit the EA or workflow you actually use?
  • Which region, platform, add-on, reward cadence, and current checkout total apply?
  • Can the data route reconcile floating state and costs, or only closed trades after the fact?

Run both exact rule sets on the same untouched trade sample. Do not optimize the strategy separately until each route “passes” historical data; that turns program selection into overfitting. Select the route whose constraints the already-tested process can respect with an explicit execution cushion.

Express Is a Legacy Branch, Not the Current Alternative

FundedNext states that Express and Evaluation stopped being offered to new clients in March 2025, while existing accounts can continue under their legacy rules. If you hold one, create a legacy program record from its own contract and current dashboard. Do not substitute a Stellar component row, and do not present Express as a product a new reader can choose today.

Daily FundedNext Journal Workflow

Before the Session

  • Confirm program, phase, region, account size, platform, add-ons, and lifecycle state.
  • Open the FundedNext dashboard; record current balance, equity, both limits, server time, reset countdown, and objective state.
  • Reconcile the last import or platform statement. Resolve missing tickets, duplicates, timezone shifts, and unexplained P&L variance.
  • Mark today's eligible setups and event restrictions. Calculate combined open and pending exposure before the first order.
  • Stop if the exact rule state cannot be verified. A stale green dashboard in another tool is not evidence of current capacity.

During the Session

Update closed and floating results after every execution, including costs. Recompute the smaller active buffer before adding or correlating positions. If an order deviates from the pre-trade plan, record the deviation immediately; do not wait for the result to decide whether the decision was valid.

After the Session

Reconcile trade count, gross result, swaps, commissions, fees, net result, balance, equity, and the next reset. Save the dashboard evidence and label every trade as plan-compliant, execution deviation, rule uncertainty, or prohibited-practice concern. Advance the phase only after the official dashboard confirms review or completion.

Set Up the FundedNext Tracker in TSB

Trader's Second Brain is our product. It is relevant to this workflow for exact account separation, recognized-source import, reconciliation, prop-rule context, notes, screenshots, and post-trade review. It is not FundedNext's live risk engine, cannot guarantee complete floating-state coverage, and cannot prevent a breach.

TSB's canonical source registry currently recognizes 328 structured broker, exchange, platform, and prop-export profiles. Recognition is route-specific. Test a representative FundedNext file or connection and compare tickets, timestamps, gross result, swaps, commissions, fees, and net result before importing the full history.

  1. Create a separate account record for every program, phase, and attempt.
  2. Store the exact catalog IDs, region, add-ons, source URL, and verified date.
  3. Import a representative sample and reconcile it against the platform and FundedNext dashboard.
  4. Attach setup, initial risk, screenshot, deviation, and rule state to each normalized trade.
  5. Mark live capacity Unknown whenever open P&L, costs, pending exposure, or the current reset is missing.

Verify the Route Before Importing the Attempt

Check the exact source path, reconcile one sample, then use the prop-rule and evidence workflow. Current monthly and lifetime access values render from server product truth.

Check the import route Review current access options

FundedNext's dashboard and current purchase terms remain authoritative for live limits, objectives, eligibility, and breach state.

For a second firm-specific example of phase separation and source authority, compare the FTMO journal workflow; do not copy its rule formulas into FundedNext.

Methodology and Sources

This correction was checked on September 9, 2026 against current FundedNext first-party help pages. Exact numeric program and commercial fields render from the canonical catalog rather than repeated article text.

Final Verdict: Journal the Contract, Not the Brand

A FundedNext journal is trustworthy only when every number points back to an exact program, phase, region, add-on set, server day, source, and timestamp. The most dangerous error is not a missing chart; it is applying the wrong route's rule correctly.

Keep the catalog as the changing fact layer, the article as reviewed editorial guidance, the FundedNext dashboard as live authority, and TSB as an ownership-disclosed evidence layer. When the data is incomplete, write Unknown and verify before the next order.