Brokerpilot runs as an independent copy of the trading platform's dealing — calculating everything separately, in parallel. Think of it as a shadow ledger: the platform says one thing, Brokerpilot calculates another, and any divergence between the two is a signal worth investigating.
The Invalid Balances trigger formalises this check. Once a week it verifies each account's balance against the order history. If the balance recorded in the trading platform does not match the independently calculated value, a notification is generated.
Where discrepancies come from
The most common cause is not a system failure — it is human error during manual account review. A dealer inspecting an account on the trading platform accidentally deletes a trade. It happens quickly and is easy to miss. Without an independent check, that discrepancy can sit undetected for days or weeks, quietly distorting the account's P&L and margin calculations.
This is exactly the kind of operational risk that rarely shows up in standard monitoring — no alert fires, no threshold is breached — but accumulates into real problems over time. For a broader look at how operational habits create hidden risk: the hidden latency in every broker stack.
Detection and correction
When a discrepancy is found, the trigger can handle it in two ways. With automatic correction enabled, the incorrect balance in the trading platform is adjusted without manual intervention — the dealer is notified after the fact. With automatic correction disabled, the trigger sends a notification and the balance is corrected manually. Either way, the discrepancy does not go unaddressed.
Invalid Balances is part of Brokerpilot's dealing operations solution.
