How to choose a forex CRM: a 12-point checklist for brokers

Every forex CRM demo shows a dashboard, a client list and a deposit form. The differences that matter only show up later: on the day a deposit is credited twice, when a regulator asks who approved a withdrawal, or when your best IB disputes a commission. These twelve questions bring those days forward to the demo.

The trading server connection

1. Where does the account data come from? Ask whether balances, equity and first-deposit dates are read live from the trading server or imported on a schedule. A CRM that imports nightly will always be a day behind your sales desk.

2. What happens when the server doesn't answer? Balance operations on MetaTrader 5 have no idempotency key. If the CRM sends a deposit, loses the answer and sends it again, the client is credited twice. The right answer is that a lost operation is settled from the server's own deal history, never resent blindly.

3. Does it need a plugin on your server? Plugins add an upgrade dependency on your trading server. A CRM that works through the platform's official API keeps your server yours.

Money and approvals

4. Can you require two people for large withdrawals? Look for a threshold per brand, set in one approval currency, with any other currency always needing a second person. Check that the rule is enforced for every role, administrators included.

5. Is the ledger frozen? Ledger entries should never be edited or deleted. Corrections are new entries. If the vendor can show you a "fix balance" button, so can a fraudster.

6. Is there daily reconciliation? Ask how the CRM proves its ledger matches the server. The strongest answer is a day-by-day re-read of the server's deals, matched by deal ticket.

Clients and compliance

7. Is KYC built into onboarding? Documents should be scanned for malware, encrypted at rest and reviewed in a queue. A refused document should be the only one the client is asked to send again.

8. Is there an audit trail you can't edit? Who changed a client's email, who sent a link, who approved a withdrawal: the trail should be append-only, with who, what, before and after, recorded in the same transaction as the change itself.

9. Is access enforced in the database? Brand and role access should be enforced by the database itself, so a mistake in one screen can't widen what someone sees.

Growth

10. How do partner commissions work? Multi-level trees, per-lot rates by asset class, pending lines that confirm when the trading day settles, and payouts that are normal, approved balance operations.

11. Can each brand have its own portal and domain? If you plan more than one brand or licence, check that each gets its own look, domain and sending address.

12. How do you switch? Ask for the migration plan: what imports, how long the parallel run lasts, and how migrated clients set their passwords.

Using the checklist

Score each vendor from 0 to 2 on every question, and ask for the answer to be shown, not described. A two on question 2 is worth more than any dashboard: it is the difference between an operations team that trusts its numbers and one that checks them by hand.