Forex and CFD accounts: separate loss protection from payment corrections

Start with the reason for the negative figure

A negative account figure can come from market movement, a delayed payment correction, a duplicate credit or a bookkeeping error. Those causes need different analysis. A broker should not use one generic workflow to collect every apparent deficit or erase every unexplained balance. This guide concerns the relevant UK retail CFD framework and proposes operational controls; it does not extend those protections automatically to every forex product, professional client or offshore account. Confirm the legal entity, product and client classification first. The payment team needs that scope because an account label alone does not explain the customer's rights.

Keep the protection clear

FCA Handbook COBS 22.5.17 limits a retail client's liability for restricted speculative investments connected to the account to the funds in that account. Related guidance explains that this includes cash and unrealised net profits from open positions, while excluding funds or assets held for other purposes. The FCA's CFD overview also describes leverage restrictions, margin close-out and protection against losses beyond account funds.

These rules do not make every disputed payment a resolved accounting question. The merchant should obtain appropriate compliance or legal review where a payment reversal intersects with trading losses. It should not present negative balance protection as a guarantee against losing deposited funds.

Maintain separate ledgers and reason codes

Record incoming money, trading results, fees, payment reversals and protective adjustments under distinct categories. A protective adjustment should remain visible rather than being hidden inside an unexplained deposit entry. Link payment corrections to the original instruction and provider reference. That structure lets finance reconstruct what the account showed at a particular time and why it changed. Avoid overwriting earlier records merely to make the current balance look clean. A readable sequence is essential when a customer asks why a new deposit was applied in a particular way or disputes the firm's explanation of an earlier account deficit.

Control provisional funding

If the business makes funds available before final payment confirmation, define that exposure explicitly within its approved model. Identify the event that permits trading credit and the evidence required before a pending item becomes confirmed. Do not assume that a browser success page proves settlement. Conversely, a missing browser response does not prove failure. The system should prevent the same funding operation from being credited twice and should show uncertain deposits accurately. Review whether provisional credit creates unacceptable customer or firm exposure, particularly during volatile conditions. Commercial demand for instant funding should not leave the underlying responsibility undefined.

Review reversals without automatic collection

When a previously credited payment is reversed or disputed, assemble the payment history, trading timeline, communications and applicable terms before deciding the response. A correction may raise issues that differ from ordinary market losses, but staff should not improvise a legal distinction to demand payment. Route ambiguous cases through qualified review. Prevent automated collection messages or automatic application of fresh deposits while the basis remains unresolved. Explain confirmed transaction facts to the customer and provide a route to challenge the record. Any account restriction or corrective action should follow the applicable obligations and documented decision, with an identifiable owner.

Protect the next deposit from old ambiguity

A customer returning after an account adjustment should see an intelligible opening position. Reconcile unresolved items before relying on a simple displayed balance. If the firm proposes to apply new money against an earlier amount, the legal and contractual basis must be established and communicated appropriately. Do not let a generic accounting offset defeat an applicable protection. Equally, do not label an operational refund or manual credit as protected trading compensation when that is not its basis. Clear statements help the customer understand what funds are available, which items remain under review and how any final correction will be recorded.

Make support explanations consistent

Provide support with an approved account timeline, not only the latest net figure. Distinguish available cash, open-position effects, pending funding and completed adjustments in terms appropriate to the platform. Staff should avoid assuring customers that a payment method makes trading safer or that a further deposit will recover prior losses. Escalate complaints about loss protection to the responsible compliance team. Maintain a common case reference so finance and support do not issue incompatible answers. If a previous explanation was wrong, correct it clearly and retain the earlier communication for review rather than silently editing the case history.

Test a complete correction scenario

A useful rehearsal follows a confirmed deposit, market loss, protective adjustment and later payment correction through every affected system. Include a separate scenario where the initial funding entry was simply duplicated. Compare expected customer statements, general-ledger postings, provider records and support messages. The purpose is to expose accidental offsets and inconsistent classifications before they reach customers. Assign access restrictions to manual adjustments and require evidence for material changes. Management reporting should distinguish trading-related protection costs from payment disputes and processing defects, since combining them obscures the cause and prevents an appropriate corrective response.