MT5 back office — swaps, Islamic accounts, dividends, reporting

None of the work on this page is glamorous and all of it is expensive when it goes wrong. Overnight financing, corporate actions, swap-free eligibility and regulatory extracts are recurring obligations with fixed deadlines, performed across hundreds of symbols and thousands of accounts. The failure mode of manual work at that scale is not carelessness. It is volume.

These components operate against the MT5 server directly. Rate changes, corporate-action adjustments and account exemptions run as scheduled server operations, each recording what changed, when it took effect and who approved it. Most brokers discover they needed that record only when someone disputes a charge.

ComponentSwap Manager

Centralised overnight-financing management: bulk swap-rate updates across symbols and groups, scheduled synchronisation with coverage rates, triple-swap day configuration, and per-group modes in points, percentage or account currency.

Rates are edited once and applied across the symbol set, not symbol by symbol in a manager terminal. Where a broker covers flow externally, synchronisation keeps the client-facing rate a defined distance from the rate the broker pays. Desync is expensive precisely because it is silent: the position is carried at one cost and billed at another, every night, and nothing turns red. Triple-swap day is the other standing trap — Wednesday for FX, not for every instrument class.

What it solves

• Maintenance across hundreds of symbols becomes one scheduled job
• Drift between coverage cost and client swap stops being a nightly loss
• One consistent policy across every group, not scattered edits
• Changes ship rollover-safe, with an audit trail behind each one

ComponentIslamic Accounts

A swap-free programme for clients whose faith prohibits paying or receiving interest. Status is granted by group or by country, or per request through an approval workflow. Overnight interest is removed and, where the broker chooses, replaced by a transparent fixed administration fee. Holding-time limits are set per instrument class, and abuse controls apply the configured policy automatically. The client sees their status in the cabinet and the terminal.

For MENA and much of Southeast Asia this is an entry condition rather than a promotion: an interest-bearing account is not something those clients prefer to avoid, it is something they will not open. Brokers offer it grudgingly because a naive version is an arbitrage — remove the swap from a high positive-carry instrument and holding it becomes free indefinitely. Holding limits and automated detection make the offer sustainable enough to advertise broadly. An administration fee, where used, is flat and disclosed, independent of the rate differential.

What it solves

• Opens markets where an interest-bearing account is a prohibition, not a preference
• Carry exploitation of exempt accounts is handled by rule, not spot-checks
• Eligibility, assignment and exceptions stop being manual back-office work
• One consistently applied policy: fewer disputes, no ad-hoc decisions

ComponentDividend Manager

Automated corporate-actions processing for share and index CFDs: a maintained dividend calendar feeding automatic ex-date adjustments — longs credited, shorts debited, with tax coefficients — as overnight batch operations with per-client reporting.

On the ex-date every open position in the instrument is adjusted in one batch before the session opens, with a withholding coefficient per instrument. This is the most error-prone routine in a CFD back office because it is calendar-driven and unforgiving: a missed ex-date means clients short the instrument keep money they owe and clients long it are not paid. Sourcing announcements is the other half, and why small teams keep their share list short.

What it solves

• The most error-prone routine in a CFD back office becomes a batch job
• No sourcing or maintaining corporate-actions data issuer by issuer
• Withholding coefficients are applied per instrument, not approximated
• Readable statements cut the support queue after every ex-date

ComponentReporting & Analytics

Regulatory and business reporting: scheduled end-of-day extracts, regulatory trade-reporting formats, and analytics on volumes, revenue by group and book, client lifetime metrics and dealing statistics — delivered as dashboards, files, or a feed into the broker's own warehouse.

Two audiences, one extract. For the regulator, end-of-day reports run on a schedule in the required format, so meeting an obligation is a job that already ran rather than a request that starts a project. For management the question is attribution: most brokers can state total revenue and not where it came from — which group, which instrument, which side of the book. One extract behind dashboards, files and the warehouse means teams argue about decisions, not numbers.

What it solves

• Reporting obligations are met by a scheduled job, not a manual exercise
• Revenue is attributed by group, instrument and book, so pricing has evidence
• Auditor and regulator requests are answered in minutes, not days
• One extract feeds dashboards, files and the warehouse, so numbers agree

Why these four belong together

They share a clock, a data source and an audit trail.

Swaps and swap-free are one policy from two sides. An exemption only means something if the underlying swap policy is coherent, and the controls that keep it viable read the same holding data. Split across two systems, the exemption list and the rate table drift apart.

Dividends and swaps share a batch window. Both adjust open positions overnight, both must finish before the session opens, and both are wrong the same way if they run twice or run half.

Reporting reads all of it. A swap change, a dividend adjustment and an administration fee end as line items a client may dispute. Applied by separate tools with separate logs, "why was this charged" takes a week to answer.

Related components