Data Validation and Import Checks 🚀- Emfino Super Feature #2

Automated, built-in, and customizable DATA VALIDATION RULES and IMPORT CHECKS allow only high-quality data for all legal entities to be imported into the system, ensuring reliable reporting and consolidation.

Emfino will notice:

• mistakes

• inconsistencies

• missing data

• even silent adjustments of historical accounting data 🔎.

Delight your financial controllers by letting them focus on data analysis while Emfino catches the errors 😊!

Data Validation and Import Checks - Emfino Super Feature #2

Data Validation and Import Check Examples in Emfino DEMO System

1) Automated, built-in data validation rules and import checks

Example 1 shows insight into the list of automated data validation rules and import checks that are built into the system. It is impossible for users to switch them off, thus ensuring that all imported Transaction files, Trial balance reports, and Balance split reports are validated during the import. If uploaded files contain errors, the users are provided with the error list, and incorrect data are not imported into the system.

1) Emfino Demo: Built-in and automated data validation and import checks

Example 2 shows a data import error list when imported data have failed Emfino built-in data validation and import checks.

2) Emfino Demo: Data import error list for built-in data validation and import checks

2) Custom data validation rules and import checks

In addition to the built-in data validation rules, it is possible to set up custom data validation checks (Example 3). Finance controllers usually set up custom data checks, which can be as many as needed to control data quality in all accounts for all legal entities. Typically, custom checks are used to control whether transaction data have the necessary dimensions or partner names.

3) Emfino Demo: Customizable data validation and import checks

Example 4 shows a data import error list when imported transaction data have failed Custom data validation and import checks.

4) Emfino Demo: Data import error list for custom checks

3) Example of Custom check set-up

This is an example (Example 5) of a custom check set for a construction company (PL001). The company wants to control that all transactions in construction revenue accounts contain project codes. The cost center field cannot be empty or contain profit/cost centers other than the project codes:

Steps to set the custom check (Example 5):

• Set the custom check name.

• Set the action for the system if an error is identified - in this case, 'DO_NOT _IMPORT'.
  

• Define by a formula which transactions (TX) should be checked - in this case, all transactions in accounts within Account Group '151'. Example 6 shows that Account Group '151' in the Group P&L Chart of Accounts (COA) contains all construction revenue accounts.

• Define which field (column) of transaction data you want to check—in this case, the company wants to check the field 'COST_CENTER'.

• Define what the selected field should contain. In this case, the company creates a formula that allows 'COST_CENTERS' to belong only to the departments '06CON—Construction project department', '07TEL—Telecommunication infrastructure project department', and '08DSG—Designing project department'. In Example 7, you can see the Group Dimension structure and that the mentioned dimensions contain all construction-related project codes.

• Then, it is possible to choose whether the rule should be applied to all companies or selected companies and the starting date. Here, the company chooses to apply the rule to company PL001 and does not identify any starting or ending dates; then, the rule is applied to all periods.

5) Emfino Demo: Customizable data import check set-up

6) Emfino Demo: Account Group from Group COA used in custom import check

7) Emfino Demo: Dimensions used in the custom import check set-up