CFDs are complex instruments and come with a high risk of losing money rapidly due to leverage. Trade only with money you can afford to lose.
Open Exness Account →

Exness Account Types

Adding another account is four states rather than one action: the record is created, the list catches up, a platform is connected, and only then can the account hold a position.

Open Exness Account →

100+ instruments  ·  Founded 2008

Between pressing create and placing a first order on a new account there are four states, and only one of them is slow. The record itself appears immediately, the account list catches up a moment later, and connecting a platform to it takes as long as typing a few fields. Everything that feels like waiting sits in the last state, which depends on something outside the account entirely.

The four states a new account passes through

What each state waits on

StateFinishes whenUsual unitWhat it does not wait for
CreatedThe form is acceptedInstantAny check already completed for an earlier account
ListedThe account list next refreshesSeconds to one refreshAnything you type
ConnectedA platform is given the account and its serverMinutesThe other accounts, which stay connected throughout
ReadyFunds arrive from wherever they startedOutside the account's controlThe three states above, which are already finished

Created is not the same as visible

The moment a new account record is written is the quickest event in the whole sequence: it is a single write, with nothing to check and nobody to consult. Anything already verified once belongs to the person rather than to the account, so it is not repeated for the second, third or tenth record.

What follows immediately afterwards causes more confusion than the wait itself. A list of accounts is a view built at a particular moment, and a view built a second before a record existed will not contain it. Reopening the view is what fixes that, and it is not the same as creating the record again.

The failure mode worth avoiding here is duplication. A record that has been created and is not yet visible looks exactly like a record that was never created, and the instinct to press create again produces two accounts where one was wanted — a mess that takes far longer to sort out than the second it saves.

Connecting is per program, not per account

Connecting is the state people mistake for part of the account creation. It is not: it is a separate act performed by a program, using an identifier and a server entry that the account already has. The same record can be connected on a desktop, on a phone and in a browser, and each of those is its own short act.

Because connecting belongs to the program rather than to the record, it is repeatable, undoable and harmless. Disconnecting a platform does not touch the account, and connecting it on a second machine does not disturb the first. This is the only state on the list that can be redone without consequence.

It is also the only one bounded by your own equipment. A slow connection or a machine busy with something else makes this step longer; nothing at the broker's end is involved once the identifier and server are correct.

Ready is the only state with an unpredictable clock

An account that exists, is listed and is connected still cannot hold a position until it has something in it. That last state is the only one whose duration is not the account's to determine, because it waits on whatever is moving the funds and on that party's calendar rather than on the trading account.

This is why the whole sequence feels slow when three quarters of it is instant. The three fast states are invisible in retrospect; only the slow one is remembered, and it gets attributed to account opening as a whole.

The practical consequence is about ordering. Doing the three fast states in advance, before the moment they are needed, moves the only unpredictable state to the front of the queue instead of the back, and leaves nothing but the wait itself.

Several accounts, one clock each

Additional accounts do not queue behind each other. Each one runs its own four states, and the fast states are fast regardless of how many records already exist. Creating a second account does not slow the first, and a first that is still waiting does not hold up a second.

What does not repeat is anything that belongs to the person rather than to the record. That work was done once, and it is the reason the second record takes a fraction of the time the first one appeared to take.

The one thing that genuinely accumulates is attention. Every additional account is another thing to keep track of, another list entry to read, and another connection to remember — a cost measured in later minutes rather than in the minutes it takes to create.

Getting a new account to ready without a wasted wait

  1. Create the record and stop. It is written the moment the form is accepted, and nothing further is pending on it.
  2. Refresh the list rather than creating again. An account missing from a stale view is a view problem, not a record problem.
  3. Note the identifier and server before leaving the account area — both are needed by every program that will connect to it.
  4. Connect the platforms you actually use, one at a time. Each connection is independent and none of them affects the record.
  5. Start the funding step first if it is the state you need most, since it is the only one whose finishing time you do not control.
  6. Treat the account as ready only when it can hold a position, not when it appears in the list — the two moments are usually far apart.

The order of the states is fixed; only the third can be repeated. Current details for any account are shown in the account area.

What is repeated for a second account and what is not

ItemRepeated per accountDone once for the person
Creating the recordYes — a moment each time—
Being identifiedNoYes
Appearing in the account listYes — one refresh—
Connecting a platformYes, and per program too—
Getting funds inYes, on its own clock—
Keeping track of it afterwardsYes, and it accumulates—

The middle column is where the minutes go; the right-hand column is why a second account is quicker than the first.

Frequently asked questions

How long does creating an additional account take?
The record itself is written the moment the form is accepted. What follows — the list refreshing and a platform being connected — is measured in a refresh and a few minutes respectively.
A new account is not in the list yet. Should it be created again?
No. A list is a view built at a moment, and a view built before the record existed will not show it. Reopening the list is the fix; creating again produces a second account.
When is a new account actually ready to work with?
When it can hold a position. Existing, being listed and being connected are all earlier states, and an account can sit in the third of them for a long time.
Does connecting a platform have to be done again on another device?
Yes, and it is harmless. Connecting belongs to the program rather than to the account, so each device does it once and none of them disturbs the others.
Which part of opening a second account is the slow part?
Only the last one. The first three states finish quickly and predictably; the wait people remember is the one that depends on something outside the account.
Is anything repeated that was already done for the first account?
Anything belonging to the record is repeated, briefly. Anything belonging to the person was done once and is not asked for again, which is why a second account is much faster than the first appeared to be.

Related Exness pages