Common breaks between custodian files and dashboard totals
When a dashboard total disagrees with a custodian statement, teams often open the pricing screen first. In the files we see in Klang and the Klang Valley, pricing is not the most frequent break. Cash is.
Custodians report cash in several places: settlement cash, income awaiting allocation, variation margin, and residual balances in closed accounts. Dashboard applications often have a single “cash” tile. If the import map grabs only the main settlement account, the tile is tidy and incomplete.
Pending trades are the second regular break. A statement may show a trade that has not settled. The application may book it as a position, as a receivable, or not at all, depending on a flag that was set at implementation and never revisited. Quarter-end packs then argue about a difference that is really a timing policy.
Security identifiers cause a quieter class of error. The same line may arrive as a local code, an ISIN, and a vendor code. If the security master has two records, the dashboard may double-count or drop one. Lineage work that walks five positions from statement to tile usually finds this faster than a full reconciliation project.
None of these breaks require a new vendor. They require an owner for the mapping, a written rule for pending items, and a cash inventory that matches how the custodian actually reports. Those are ordinary control tasks. They are also the tasks that get postponed because the dashboard “looks fine” in the committee meeting.