Data Validation Part 4: Resolve & Complete
Many validation issues can be resolved by your team directly or by requesting updated data from your partners. Occasionally, you will also need direct assistance from Pereview Support. The table below provides a quick reference guide to common issues and their expected resolution path.
|
Finding |
What to Do |
|
Expected file never arrived |
Contact the partner for the missing file, then load manually or through automation. |
|
Missing month of data |
Request the missing statements from the partner, then load manually or through automation. |
|
Prior period adjustment |
Request updated statements for the affected periods and load manually or through automation. |
|
Account codes in the source file are not mapped |
Map the codes in the PMC Chart of Accounts, then reload the affected period. Unmapped codes do not load, so the amounts are absent rather than misplaced. |
|
Account missing from a hierarchy or metric mapping |
Update the Account Hierarchy and Metric Mapping or contact Pereview Support to have the account added. |
|
Account mapped incorrectly from the partner chart of accounts |
Correct the mapping yourself. The correction applies to future loads; contact Pereview to refresh periods already loaded under the old mapping. |
|
New account created in the source system |
Map the new account, then work with Support to add it to the hierarchy and metric mappings. |
|
Historical periods loaded under an old mapping |
Contact Pereview. Mapping changes apply going forward only; history must be refreshed on the back end. |
|
Incorrect accounting basis (Cash where Accrual expected) |
Request a re-export from the partner on the correct basis. The incorrect period must be deleted before the corrected file is loaded. |
|
Duplicated data, or the incorrect statement was loaded |
The incorrect data must be deleted first before loading the updated data. |
When Data Has to Be Deleted
Some problems cannot be fixed by loading a new file and overwriting the existing data in the system. Whether a reload will resolve the discrepancies depends on the situation. See Deleting Data Loads.
Upon Validation Completion
Once you have completed validation for the period in question and all discrepancies have been resolved or accepted, you can proceed with your internal business processes such as approving and distributing reports as needed.
Recommended Best Practices: Closing the Reporting Month
☐ Observations have been compiled, including accounts to reclassify and mapping to adjust.
☐ Corrections within your control have been made.
☐ Items requiring Pereview action have been submitted to Support with the supporting detail.
☐ Any unresolved exception is documented with an owner and an expected resolution date.