G/L Account History Validation Testing

Document path Reference Contents > Ledgers Manager > G/L Account History Validation Testing

This window opens from the Audit Trail of Transactions window.

Testing of accounts data integrity is performed over the selected period range for which transactions are assumed to be available in full, by default based on the current archiving policy for the G/L.

The History Integrity Test compares the G/L account history values saved at the month-end with the transaction data that was used to generate it. If something has been changed subsequent to the month-end such that the integrity is broken, an error will be logged. Such loss of integrity may be due to data corruption or deliberate manipulation using Peek and Poke. This may be by value changes or period number changes.

The Transaction Data Test scans the transactions for the selected periods and any significant foreign currency to local currency value inconsistancies. You will be prompted for a percent deviation for foreign currency transactions above which errors are reported. The default is 5%. Deviations can be legitimate but large ones tend to be errors either caused by data damage or deliberate manipulation.

Warning WARNING: These tests can take some time to run on large databases, especially where a large period range is selected.



Period List

Period list with range selected. You can select an alternative range.

Result List

Results of the test. Right-click to print the results.



History Itegrity Test

Click to run the test.

Transaction Data Test

Click to run the test.

See also: -

Compiled in Program Version 3.10. Help data last modified 10 MAY 2008 04:02. Class wAcAuditHistoryTest last modified 2 JUN 2011 07:23:32.

Document path Reference Contents > Ledgers Manager > G/L Account History Validation Testing