3.11.6 How to prepare flat files

This topic provides information on preparing the flat files.

• Data must be prepared in the form of flat files with columns separated using “~|” and rows separated with a new line.
• Every record in the flat file must have a unique identifier that can uniquely identify the record in the same file and also across all uploaded versions of the flat file. This is required for reconciliation in case of errors. File upload will fail if the unique identifier is repeated/or is present in an already uploaded file version.
• For each migration type, data of a single account is spread across multiple different flat files. A specification file describing the mapping and the format of the data expected in the flat files will be shared.
• Out of the multiple flat files, there must be one master file which contains the account number, keyId, basic account details and all the other columns as prescribed in the file format document.
• The remaining flat files contain additional account attributes. The records in the other files should contain a key id, which links the record to that of the parent in the master file.
• An Entity Mapping file should be provided for each Migration Type and this file contains information about the entities that are applicable for each Account in the master file linked by the key_id in this file.
• The child entities which are not applicable for the bank or account can marked as “N” in the entity mapping file.
• If multiple migration events are present, then for example, in case of Financial migration, entries must be present in flat files for all accounts that were migrated. Even if an account doesn’t have transaction, a zero balance entry with the key of the account with empty value for other columns must be present in the appropriate files that contain book dated, value dated and turnover balances.