Best Practices for Loading Data

The recommendation(s) or best practice for loading data into the application is that it should be sequential. For example, if you load Oct-19 after loading Dec-19 data, then you need to load through Dec-19 to calculate the MTD/QTD/YTD correctly in Reporting.

We strongly recommend that a single Data Load Rule is used when loading data for a fiscal year / scenario, loading data for same GL combinations using multiple DLRs will result in incorrect results in Reporting.

Make sure that appropriate segments are enabled as part of Clear Data Segment combination fields.

If you have a DLR set to load data as a specific measure (say MTD for all account types), the best practice is to not change the measure setting after having loaded data into the system.

After the data is loaded and validated in the application, access the Lock Data screen under Maintenance > Reports> Lock Data. Lock the periods so that data for the data for those periods is not manipulated by any further loads.

The Verify Data report will show the numbers loaded based on the Data Input Type property set for an account in the application and you may have to use a Dynamic Report to view MTD or QTD or YTD amounts for an account.

When loading exchange rates via Data Load Rules, the best practice is to the load FX rates only for those periods and currencies which have a change in rate(s). Loading the rates with the “Apply Currency Conversion ” option enabled in the data load rule deletes the existing data set, which reconverts currency and recalculates the numbers. It is advised that the rates are loaded in a chronological period order. After the rates are loaded, numbers validated and the period(s) are closed from accounting perspective, the recommendation is to lock the historical periods using the Lock Data screen (if it is the “Actual” scenario) to avoid accidental data deletion.