Why data quality is a compliance issue
Missing FX rates, stale valuations and unreconciled feeds distort the numbers a family office relies on — and its compliance posture.
- Bad data produces wrong figures and weak compliance evidence.
- Reconciliation should surface issues by severity, not hide them.
- Trustworthy numbers are a compliance asset, not just an operational one.
The hidden risk
A missing exchange rate silently understates consolidated wealth. A stale valuation misstates performance. An unreconciled feed double-counts. None of these announce themselves — they just quietly corrupt the picture.
Surface, don't hide
A good system names these problems and ranks them by severity so they are resolved before they reach a client or a regulator. Trustworthy data is part of a defensible compliance posture.
Rules that prevent bad data
Data quality is cheapest at the point of entry. A few structural rules prevent most errors: ownership percentages of an entity must not exceed 100%; every natural person needs a date of birth and nationality before screening; identity documents carry an expiry date; each entity has a jurisdiction and a legal form; and every position is linked to a custodian account and a valuation date. When the system refuses an impossible value, nobody has to discover it months later during an audit.
Equally important is ownership of data: for each data domain — people, entities, accounts, documents — someone is responsible for keeping it correct, and changes are attributed to a person and a date.
Reconciliation as a routine
Regular reconciliation closes the remaining gaps. Compare positions and cash against custodian statements, beneficial-ownership data against register extracts, and document inventories against what the risk policy requires. Treat each difference as a task with an owner and a due date rather than a note in a spreadsheet. Over time, the number of open differences becomes a simple, honest indicator of how reliable the office's data really is.
Practical checklist
Define mandatory fields and validation rules for persons, entities, accounts and documents, and enforce them at entry. Assign an owner for each data domain. Log every change with the person and the date.
Schedule reconciliations against custodians, registers and document requirements, and treat each difference as a task. Measure open differences and overdue updates over time, and report them to management as an indicator of data reliability.
Common mistakes
The most frequent mistake is treating data quality as a clean-up project rather than a routine. A one-off migration fixes yesterday's errors, but without validation rules at entry and regular reconciliation the same problems return within months. Another common gap is unclear ownership: when everyone can edit everything and nobody is responsible for a data domain, contradictions between systems are noticed only during an audit or a bank request.
Offices also tend to keep parallel spreadsheets 'just in case'. These copies drift away from the main system and end up being used for important decisions. Retire them deliberately, and make the main system the only place where people, entities, accounts and documents are maintained. Finally, avoid free-text fields for information that should be structured — dates, percentages, countries — because unstructured data cannot be validated, filtered or reported reliably.
Example from practice
Before migrating to a new system, an office runs simple checks and finds ownership percentages above 100 percent in two entities and twelve persons without date of birth. These are corrected before the migration, and validation rules prevent the same errors from being entered again. The monthly list of open differences becomes the team's measure of data reliability.
FAQ
- Basel data-quality principles
Related guides
Compliance, built into the platform
FLIORE is a family office platform with KYC and compliance built into the core.
Explore FLIORE