Data check standards do not exist of which I am aware. I have performed several reviews in this area. You need to concern yourself with the accuracy of the data and the consistency of the appliaction (change control).
Data accuracy can be measured by taking a snapshot of important fields in the record, processing 'fake' or real data, and finally reviewing the impact the processed data has on the snapshot data. If the changes come through as expected, data integrity for the tested field can be attested.
If there is not much (or never) change to the software, then you shouldn't worry on this. If there is constant tinkering, they need version control, naming conventions, access rights, module approvals, code reviews, quality testing, production and testing separation, etc.
This is not much of a response for a very technical area, but maybe it will give you some ideas.
_________________
The sharper the mind, the smoother the ride.