Data Integrity Module
Automatic Data Health Checks
A background system that quietly checks your data for a handful of known trouble spots every day, and fixes what it safely can — with no screen of its own to visit.
Start here
What this keeps healthy
This module isn’t a screen you open — it’s a set of checks that run on their own, across every company on your install, looking for the same handful of specific issues that have shown up before in this app: things like an employee record missing its linked Contact, a department that lost track of which company it belongs to, or a GL journal reference pointing at nothing. Where a check can safely correct what it finds, it does — automatically, without asking.
How it runs
A scheduled job runs once a day and works through each registered check in turn, across every company. Every check is written to be safe to repeat endlessly — running it again when there’s nothing wrong simply finds nothing, so there’s no risk in it running quietly forever in the background.
Where to see what it found
You won’t see this module’s own page anywhere in the app — but if a run actually fixes something, it leaves a record. Open System Logs and filter Source to data-integrity to see exactly what was found and corrected, and when.
A quiet day for this module is the normal, healthy outcome — it only writes to System Logs when it actually repairs something.
Running a check now
The Data Health panel in System Logs lists every check with its last result and its own Run now button, so you don’t have to wait for the daily run after fixing something.
- A Company Admin sees only the checks that can be limited to one company (for example the bank-account ledger links and payments posted straight to
1020), and Run now repairs the active company only. “Run all now” runs all of those for that company. Their results and details never include another company. - The platform administrator sees every check, and Run now runs that check across every company.
A check that finds something it can’t safely fix itself lists the details under it (for example, a tax payment posted straight to 1020 in a company with several bank accounts, which needs you to record it against the right account).
What this module doesn’t do
There’s nothing to configure or switch off: the checks always run daily. You can run them sooner, but not skip them.
Each check targets one specific, previously-seen problem — it’s not a general-purpose data validator that catches anything that could ever go wrong.