There are several different methods for loading data from outside of your core system into FI Works. The method used is based on the structure of the data in the external system.
FI Works stores data in a similar way to your core system. When we load information for external systems, it get loaded into the same structure:
|
Customer |
Customer / Account |
Account |
|
|
|
Completely External Systems
Some external systems are completely separated from the core system. In this case, we need customer, customer/account, and account data in order to load the data. The export capabilities of these systems is often limited and it may not be possible to separate the data into the structure above. While providing the data like this is preferred, it may be necessary to extract a single flattened file. FI Works can then load the data and break it down into the preferred structure.
External Accounts Referenced in the Core
Some institutions have information in the CIF/CIS that contain references to external accounts. In these cases, all of the information for customers that have external accounts are in the CIF/CIS with reference to the external account. FI Works can then load the account-level data and link it back to the data from the CIF/CIS. The application code and account number in the external must match the customer/account data in the core.
External Customer Service
In this scenario, the external system has information about a service (online banking, mobile banking, etc.) for a specific. We load this kind of information as a service attached to the customer. To load this data, FI Works just needs the Customer ID and the service name.
External Account Service
In this scenario, the external system has information about a service (e-statements, merchant services, etc.) for a specific account. We load this kind of information as a service attached to the account. To load this data, FI Works just needs the application code, account number, and service code/name.