The 12 Ways an upme Account Can End

An upme account has a small, enumerated set of end states. This article lists them, with the breach consequence for each, drawn from the published rulebook and the payouts page. Some of the entries are “a way it does not end” — stated as a rule rather than left as an omission, so that adding one later is visibly a change to the document.

The rulebook now numbers its rules 1 through 18: rules 1–10, the two consistency caps (11a and 11b), and the feed, fill, execution and conduct rules 12–18 that v1.1 added. Ten of them — rules 1 through 10, with the consistency requirement spelled out in caps 11a and 11b — map onto the account lifecycle enumerated here. The seven added in v1.1 (rules 12–18) are additional grounds on which a pass is withheld or an evaluation is voided, not new lifecycle states, and they are described together after the list. The payouts page has five refusal grounds. One rule (rule 10) and one refusal ground (account multiplication) overlap, and the three remaining refusal grounds pause a payout rather than ending an account. Counted honestly, the ten lifecycle-bearing rules and the refusal grounds produce twelve distinct lifecycle outcomes — eleven ways an account or a payout request can end, and one reversible archive state that is not an end.

Nothing here is in force today. The rulebook is published at v1.1 before any account exists, for the reason set out on the rulebook page: a set of rules written before there is a single trader to apply them to cannot have been reverse-engineered from a dispute. The same applies to this enumeration. It is a restatement, not a new document; if any rule moves, this list moves with it and the version number on the rulebook moves first.

1. Profit target reached — the evaluation ends by converting

The first way an evaluation ends is by succeeding. Closed profit reaches 10% of the starting balance in phase one and 5% in phase two (10% in a single phase on the one-step route), measured against the starting balance with no minimum number of winning days. From v1.0 the profit does have to be spread: at the moment the target is reached, no single trading day and no single trade may carry more than 40% of it (the best-day and best-trade caps, way 6). A phase closes on consistent profit, not on one clean trade.

What happens: nothing breaks. The account converts to the next stage. This is the only end state that is also the goal, and it is listed first so the rest of the list reads as exceptions to it.

2. Daily loss limit hit — the day ends, the account does not

A 5% loss against equity at 00:00 UTC (4% on the one-step route), including open positions, measured against the equity snapshot at the start of the day and not trailing an intraday high.

What happens: trading pauses until 00:00 UTC. The account survives and nothing is forfeited. This is on the list because a trader can hit it, and it is flagged as “does not end” because the most common reading of “loss limit” in this industry is that the account closes on it. Here it does not.

3. Maximum drawdown breached — the evaluation ends

A static 10% floor from the starting balance on the evaluation (8% on the one-step route), set once and never moved. It does not trail peak equity, so profit already made is yours to give back without ending the evaluation.

What happens: the evaluation ends. One retry is offered at a reduced fee. This and rule 4 are the two ends that cost the account outright.

4. Trailing drawdown breached — the funded account closes

An 8% trailing floor on the funded account, following the highest closed equity until it reaches the starting balance, then locking there permanently. It does not trail unrealised profit and does not reset when a payout is taken.

What happens: the funded account closes. Any payout already accrued is still paid. The accrued-payout line is the part that distinguishes this end from rule 3: a funded account that closes on the trailing floor does not forfeit a balance that was already earned.

5. Minimum trading days not met — the target cannot be claimed

Four days, where a day counts when at least one position is opened or closed. Days do not have to be consecutive, there is no upper bound, and there is no minimum volume attached to a day. v1.0 raised this floor from three days to four.

What happens: the target cannot be claimed yet. Nothing else changes and nothing is lost. This is on the list because it is a state a trader can be in, and it is flagged as “does not end” because the account is intact and the target is still reachable on the next traded day.

6. Consistency caps — the pass is withheld until the profit is spread

Two caps, added in v1.0 and read at the single moment the profit target is reached: no single trading day and no single trade may carry more than 40% of the total profit (rules 11a and 11b in the rulebook).

What happens: while either cap is exceeded, the target cannot be claimed — the pass is withheld, not the account voided. The evaluation does not end and nothing is forfeited; the trader keeps going until the profit is spread within both caps, the same shape of outcome as way 5. This is a real state a trader can be in, no longer an absence: earlier versions through v0.11 ran with no consistency cap and said so, and v1.0 reverses that in public and dated in the changelog, so that a pass is a demonstration of repeatable skill rather than one lucky day or one lucky trade. The cap is a published number — 40%, the same for every account, checked at the target — not a discretionary consistency score reconstructed after the fact from a trader’s history. That kind of post-hoc score is one of the most common reasons a payout is refused elsewhere in this industry; we still do not run one. What v1.0 added is a fixed, versioned limit, not a judgement call.

7. Time limit — none, stated as a rule

No phase has a deadline. An account is archived only after four consecutive quarters with no trade (see way 12), and archiving is reversible on request.

What happens: not applicable. There is no clock to breach. As with way 9 (news, weekend holding, EAs), this is stated as a rule so that adding a deadline later is a visible change rather than a quiet one. A time limit is another common evaluation-ender in this category; it is absent here on purpose.

8. Copying another funded account — payout refused, fee returned

Mirroring another funded account, at upme or elsewhere, is checked on execution timestamps across accounts linked to one identity. It is a timing test, not an opinion about strategy: two accounts holding the same view is not a breach, two accounts filling within the same tick repeatedly is.

What happens: the payout is refused under this clause, the reason is published, and the evaluation fee is returned. The fee-return line matters: this is a refusal, not a forfeiture, and it is recorded in the public ledger on the payouts page with the clause cited.

9. News trading, weekend holding, EAs — permitted, within the v1.1 conduct rules

No blackout window around scheduled releases, no forced flat before the weekend, no ban on automated execution — the three restrictions that constrain or end accounts elsewhere are still absent here. What v1.1 changed is the boundary around them: rule 9 now carries an automation-boundary clarification, and the conduct rules 12–18 (below) spell out what “permitted” does not extend to. Automated execution is fine, but it may not be used to exploit the simulated feed or its fills (rules 12 and 13), to spam the platform or churn sub-minute trades past the caps (rule 14), or to run outsized single-position exposure (rule 16); and while news trading itself stays open, straddling a scheduled event to catch the spike either way is not (rule 15). If any of the permissions themselves change, they change for accounts opened after the change, never for accounts already open.

What happens: not applicable. This is still a way the account does not end — the news, weekend and EA permissions stand — stated as a rule for the same reason as way 7 (time limit): a news or weekend or EA restriction is a common evaluation-ender elsewhere, and the absence is published so its later addition would be a dated, versioned change rather than an unannounced one. The v1.1 conduct rules do not reintroduce those restrictions; they bound how the permissions may be used, and they are additional grounds described after the list, not a new ending here.

10. One trader, counted once — the evaluation is void

Up to 3 concurrent evaluation accounts per person, with the cap binding to a verified identity at payout and to a correlated-behaviour cluster before that. Three things breach it: opposite or offsetting positions across accounts where the combined exposure nets to roughly zero while one side harvests a pass or payout; transferring, buying or selling an account, or having a third party trade an evaluation; and the same trades duplicated across a cluster of accounts to multiply payouts. Detection is a trade-correlation review — timing, instrument, direction, size — that runs continuously through the evaluation, plus payment-method linkage at purchase and identity linkage at KYC.

What happens: the evaluation is void, and the void is recorded in the public denial ledger on the payouts page citing this rule. A violation found after a payout is published the same way. This is the most serious end state on the list: it invalidates the account rather than pausing it, and it does so on a review that runs the whole way through the evaluation rather than being saved for the payout gate.

11. Three payout refusals that pause a request, not an account

Five refusal grounds are listed on the payouts page. Two of them — copying another funded account (way 8) and account multiplication under rule 10 (way 10) — end an account. The remaining three do not. They pause a payout request, and the amount stays payable once the pause is resolved:

Account holder is not the payout beneficiary. The name on the account and the name on the destination must match. Refused pending correction rather than permanently, and payable once they do.
Identity verification not completed. Refused pending completion, not forfeited. The amount stays payable indefinitely and is paid the day verification clears.
The request exceeds the accrued balance. An arithmetic refusal. The payable part is paid; the remainder is not created by asking.

What happens: the request is refused, the account is not. None of these three voids the evaluation or closes the funded stage. They are on this list because a payout request is the other thing that can “end” in this product alongside the account itself, and these three end the request without ending the account behind it.

12. Inactivity archive — reversible, not an end

An account is archived after four consecutive quarters with no trade. A day counts the same way as rule 5: at least one position opened or closed.

What happens: the account is archived and can be restored on request. This is the one state on the list that is explicitly reversible, which is why it sits at the end rather than alongside rules 3 and 4. An archive is not a close. It is the only way an account leaves the active state without a breach and without converting, and it carries a route back.

After the twelve: the v1.1 conduct rules (12–18)

The twelve outcomes above are the ways an account or a payout can end. Version 1.1 added seven more numbered rules — 12 through 18 — but none of them is a new ending. Each is an additional ground on which a pass is withheld (the shape of way 6) or an evaluation is voided (the shape of way 10), so they fold into outcomes the list already has rather than adding a thirteenth.

12 — Feed integrity and 13 — Execution realism. The evaluation is priced from a simulated feed with simulated fills. Exploiting either — trading against a stale or manipulated price, or claiming a fill that could not have existed in a live book — voids the result rather than counting toward a pass.
14 — Trade duration and activity. Trades held under 60 seconds may not account for more than 30% of the total profit at the target (the same share arithmetic the consistency caps use), and an account may place no more than 2,000 platform requests or 200 executed trades in a UTC day.
15 — Event straddling. News trading stays permitted (way 9), but bracketing a scheduled event with orders on both sides to catch the spike whichever way it breaks is not.
16 — Single-position exposure. No single trade may risk more than 2% of the account to its stop.
17 — Reset-window conduct governs behaviour around an evaluation reset, and 18 — Probability-pass ban extends rule 10: manufacturing a pass by running enough correlated accounts or attempts until one clears is void on the same basis account multiplication already is.

These are published now, dated in the rulebook changelog at v1.1, and most of them enforce once the trading platform is wired rather than today — an honest published flag, not a claim they already run. They are on this page because a reader counting the rulebook’s numbered rules now reaches 18, and the point of the list is that every one of those rules maps to a stated outcome rather than a surprise: rules 12–18 withhold a pass or void an evaluation, the outcomes ways 6 and 10 already describe.

Counting them honestly

Read as a list of ends, the twelve break down as:

Two ends that cost the account outright: maximum drawdown (way 3), trailing drawdown (way 4).
One end that voids the account: one-trader-counted-once breach (way 10).
One end that is the goal: profit target reached (way 1).
One refusal that ends a payout and returns the fee: copying another funded account (way 8).
Three refusals that pause a payout and preserve the account: beneficiary mismatch, identity not verified, request exceeds balance (way 11).
One reversible archive: four consecutive quarters with no trade (way 12).
Three states that gate but do not end the account: daily loss limit (way 2), minimum trading days (way 5), and the consistency caps (way 6) — each a state a trader can be in that pauses trading or withholds the pass without ending anything.
Two stated-as-a-rule absences: time limit (way 7) and news/weekend/EA (way 9), each published as a rule so that adding one later is a dated, versioned change to the rulebook rather than an unannounced one. The news, weekend and EA permissions still stand in v1.1 — no blackout, no forced flat, no EA ban — now bounded by the conduct rules 12–18 rather than reversed by them.

That last split is where v1.0 shows: the “does not end” absences are now two, not three. Consistency was a third such absence through v0.11 and is now the two enforced caps in way 6 — the same versioning mechanic working in the other direction, a rule added in the open rather than an absence removed in the open. The two remaining absences (time limit, news/weekend/EA) stay on the list because each corresponds to a rule that ends an account at one or more firms in this industry, and each is published as a rule so its later addition would be visible. v1.1 continues the same mechanic on conduct: rules 12–18 add grounds on which a pass is withheld or an evaluation is voided — not new endings, but new numbered rules — published and dated before any account exists, most enforced once the platform is wired. The versioning mechanic that makes all of this binding is described on the rulebook page: every account records the version it was opened under, that version governs it for life, and a later version cannot reach back into it.

How this compares with the rest of the industry

The number of ways an account can end is itself a point of comparison. The rule mechanics that differ firm by firm — equity versus balance measurement, trailing versus static floors, discretionary consistency scores versus a published cap like ours, news windows, inactivity thresholds — are covered in our comparison of prop-firm rule mechanics, and the share of payout requests refused (the figure no firm in this category publishes) is on its own denial-rate page. The refusal-rate commitment that binds upme to publishing that figure monthly, whatever it is, is on the payouts page.

Written by the upme.com research desk. Every rule and refusal ground above is restated from the published rulebook at v1.1, dated 2026-08-03, and the payouts page, both published before any upme account exists. No figure on this page is a live number; nothing in the rulebook is in force yet. Corrections to the address on our sourcing page. Nothing here is investment or legal advice.

Sources

Every factual claim above is drawn from one of the documents below. Where a document has been superseded since the date given, tell us and the piece is corrected with a dated line.

Source
Source