A cleaner profile can conceal a broken money record
A broker discovers two profiles that appear to belong to the same client. One contains a current trading account; the other contains an older payment method and an unresolved withdrawal. Combining them may simplify login and support, but an ordinary database merge can destroy the identifiers that explain the money. The right objective is a coherent client view with a preserved historical record.
This operating framework applies only within the firm's approved account and client-money arrangements. It does not authorize transfers between legal entities, customers or account categories. Identity, eligibility and the relevant regulatory treatment must be established by the responsible teams. Apparent similarity in a name or email address is a reason to investigate, not sufficient authority to consolidate financial relationships.
Anchor the design in traceable client ownership
FCA CASS 7.15 requires applicable firms to maintain records that distinguish clients' money and support an accurate audit trail. That UK requirement provides the context for this analysis. The proposed merge controls are independent implementation suggestions, not a complete description of the Handbook or a substitute for the firm's compliance assessment.
Begin by defining what merge means in the relevant systems. It might consolidate contact details, link a shared identity or move a service relationship to a surviving profile. Those operations are not interchangeable. Write down which records will change, which identifiers remain permanent and which balances or commitments require a separate authorized action rather than an automatic database update.
Resolve identity before choosing a surviving profile
Verify that both profiles belong to the same legal client using the firm's approved process. Examine differences in names, jurisdiction, account status and contractual entity. Escalate contradictory information instead of selecting the record with the most recent activity. Where a relationship cannot be established, keep the profiles separate and preserve the review outcome for staff who encounter the case later.
Selecting a surviving profile should not erase restrictions associated with the other record. Carry forward relevant review flags and unresolved service issues through an approved mapping. Avoid turning the merge into a fresh onboarding state that silently resets prior decisions. The person reviewing identity should be able to see the consequences without obtaining unrestricted authority to move funds.
Inventory every unsettled financial item
Before implementation, list deposits awaiting confirmation, pending withdrawals, refunds, disputes and any other financial commitments associated with each profile. Include provider references and currencies. A zero displayed trading balance does not prove that an account has no outstanding payment activity. Late provider events may still arrive, and historical transactions may still require support or reconciliation after the profile becomes inactive.
Take a controlled snapshot that allows the team to compare the before and after positions. Define how new events will be handled during the change so the snapshot does not immediately become misleading. If a temporary operational restriction is necessary, keep it narrowly scoped and communicate it appropriately. The process should not create unexplained friction around a client's legitimate access to funds.
Link historical records instead of rewriting them
Retain the original account and payment identifiers on historical entries. Add a documented relationship to the surviving profile, with the effective time and approved reason for the change. That approach lets staff search from the current client view while still explaining which account initiated a deposit or requested a withdrawal. Historical references should remain usable in provider queries and audit exports.
Avoid replacing every old identifier in place. Such a rewrite can make a provider response appear unmatched or change the apparent owner of an earlier transaction. If a system requires migration, design an explicit mapping table and preserve its version. Validate the mapping independently before enabling automated callbacks or reporting against the new profile structure.
Keep payment-method permissions explicit
A method associated with one profile should not automatically become available in every account now visible under the combined identity. Check the provider arrangement, account eligibility and the firm's payment controls. A token's technical availability is not proof that its use is authorized for a different product or contractual relationship. Preserve any restrictions that applied before consolidation.
Support should explain what changed without making broad claims about money movement. A profile consolidation may leave all funds in the same underlying accounts. If a separately authorized transfer occurs, show it as its own operation with an identifiable reason and outcome. Combining those two explanations into a single merge note makes later statements and customer complaints harder to reconcile.
Verify the result with late events
After the change, compare balances and outstanding commitments against the approved snapshot and mapping. Test a late deposit confirmation, an old refund reference and a statement request covering both profiles. Confirm that reporting can reconstruct the original account history and that customer support can find the relevant transaction from either identifier. Preserve unresolved differences in a tracked exception queue.
Have a recovery plan for an incorrect link. Reversing a profile association must not reverse valid payments or erase later activity. Document which relationships can be safely undone and which require a correcting entry or specialist review. The most useful completion criterion is not that the duplicate profile disappeared; it is that ownership, obligations and transaction history remain explainable after the change.
What it means to Merchants
Treat duplicate-profile consolidation as a controlled identity and records change with separate financial decisions. Establish the client relationship, inventory unsettled items and preserve the original transaction identifiers before implementation. Then verify late provider events and historical statements against the resulting account view. A successful merge makes service simpler while retaining an accurate explanation of whose money was held, which account initiated each operation and how every outstanding commitment will be resolved.