Use this section to prepare the business data in the required format using the specified templates to load into the application staging area. This section also explains the type of data files you are required to create, the size of data files, and the template in which you must provide the data.
You must create the data files in the required template (see table 1 for templates) in the .csv format. For more efficient and resilient uploads, it is recommended to split the .csv files that are more than 100Mib into multiple files with the following naming convention for the files:
· Single File : <YYYYMMDD>_<TABLENAME>.csv (For example, 20201124_STG_PARTY_MASTER.csv).
· Split Multiple Files : <YYYYMMDD>_<TABLENAME>_<Sequence number>.csv (For example, 20201124_STG_PARTY_MASTER_1.csv, 20201124_STG_PARTY_MASTER_2.csv, 20201124_STG_PARTY_MASTER_3.csv, and so on).
Multiple files upload in parallel reduce the amount of time and this helps to upload data files swiftly to the Object Storage.
NOTE:
· At the end of every .csv file, the total count (TOTAL COUNT=) can be provided in the file. This row is optional.
· The total count of records must not include the header.
· In the case of a split file for any specific table, all the files must contain the respective file total count.
· All the fields, data type, and length must be in line with the data model, for more information, see Data Model.
· Date values must be in ‘DD-MON-YYYY’ format.
· The maximum size of the data file (object) can be up to 10 TiB. Object parts must not be larger than 50 GiB.
ATTENTION:
Each .csv file should allow only a single Data Origin. Multiple .csv files should not be created to allow for multiple data origins of the same file.
The following image provides an example of the file count and the .csv file.
Figure 2: The sample .CSV file

Description of sample .csv format
The total count helps to assess the records that are loaded into the application staging tables.
Use this section to refer to the complete list of tables and templates, For more information, see Table 1. You must refer to these tables and corresponding templates to update your data accordingly in the .csv format. For more information, see Loading Data Files.
ATTENTION:
If your firm has implemented multiple products, you are not required to load data separately for each product. You must load data once for all products.
The following table provides a list of table names and templates.
Table 1 - The List of Table Names and Templates.
Table Name |
Entity Type |
Description |
Mandatory |
Transaction Monitoring |
Customer Screening |
Know Your Customer |
Investigation Hub |
STG_ACCOUNT_ADDRESS_MAP |
Account |
The address associated with accounts held at the firm. Note: Refer to Supplemental Information for Account Address for more information about this table. |
Y |
Y |
|
|
|
STG_ACCOUNT_ALT_CCY_VALUES |
Account |
The values are expected in reporting or local currency for a particular account. |
Y |
Y |
|
|
|
STG_ACCOUNT_EMAIL_MAP |
Account |
An e-mail address for an account. An account can have multiple e-mail addresses, such as home and business. |
Y |
Y |
|
|
|
STG_ACCOUNT_GROUP_MEMBER |
Account |
Account groupings that relate an account to other accounts through membership in the group. |
Y |
Y |
|
|
|
STG_ACCT_ANTICIPATORY_PROFILE |
Account |
Projections of expected trading and transactional activity collected from a customer during the account opening. |
Y |
Y |
|
|
|
STG_ACCT_GROUP_MASTER |
Account |
Account groupings that relate an account to other accounts through membership in the group. Households are an example of Account Groups. |
Y |
Y |
|
|
|
| STG_ANNUITY_CONTRACTS | Account |
The annuity contracts which are defined as a written agreement between a financial institution and a customer outlining each party's obligations in an annuity coverage agreement. |
N |
Y |
|
Y |
|
| STG_CARDS | Account |
Credit cards are issued by financial institutions giving the holder an option to borrow funds. Credit cards charge interest and are primarily used for short-term financing. |
N |
Y |
|
Y |
|
| STG_CASA | Account |
Current Account and Savings Account data of the financial institution. Demand Deposit comprises of Current and Savings Account, held at a bank or other financial institutions with no maturity. |
Y |
Y |
|
Y |
|
| STG_CORRESPONDENT_ACCOUNT | Account |
A correspondent account is used to record accounts held at other banks including central banks. Central bank accounts including reserve accounts are stored. |
|
Y |
|
Y |
|
| STG_LEASES_CONTRACTS | Account |
Leases contracts are a formal document that identifies the lessor, lessee, and the leased asset or property; states lease term and fee (rent), and detailed terms and conditions of the lease agreement. |
N |
Y |
|
Y |
|
STG_LOAN_CONTRACTS |
Account |
A loan contract is a contract between a borrower and a lender which regulates the mutual promises made by each party. |
N |
Y |
|
Y |
|
STG_MERCHANT_CARDS |
Account |
All contracts are related to merchant cards. |
N |
Y |
|
Y |
|
STG_MM_CONTRACTS |
Account |
Money market contracts data. |
N |
Y |
|
Y |
|
STG_OD_ACCOUNTS |
Account |
Overdraft is an extension of credit from a lending institution when an account reaches zero. |
N |
Y |
|
Y |
|
STG_REPO_CONTRACTS |
Account |
A repurchase agreement (REPO) is a form of short-term borrowing for dealers in government securities. The dealer sells the government securities to investors, usually on an overnight basis, and buys them back. |
N |
Y |
|
Y |
|
STG_RETIREMENT_ACCOUNTS |
Account |
A retirement account is an investment tool used by individuals to earn and earmark funds for retirement savings. |
N |
Y |
|
Y |
|
STG_SWAPS_CONTRACTS |
Account |
Swaps contract where one party exchanges or "swaps" the cash flows or value of one asset for another |
N |
Y |
|
Y |
|
STG_TD_CONTRACTS |
Account |
A term deposit is defined as a deposit held at a financial institution that has a fixed term. These are generally short-term with maturities ranging anywhere from a month to a few years. |
N |
Y |
|
Y |
|
STG_TRUSTS |
Account |
A trust account is managed by one party for the benefit of another. It is sometimes called an account held in trust, and the trust relationship can be either explicit or implied. |
N |
Y |
|
Y |
|
STG_TRUSTED_PAIRS |
Account |
Trusted pairs are entities that are considered to enjoy a trusted relationship, meaning transactions between these two entities represents little or no risk to the institution. | N | Y | |||
STG_ACCOUNT_PHONE_MAP |
Customer |
Phone numbers associated with an account. An account can have multiple phone numbers, such as home, business, and cellular. |
Y |
Y |
|
|
|
STG_ADDRESS_MASTER |
Customer |
The customer addresses. Each customer can have multiple addresses. |
Y |
Y |
Y |
Y |
|
| STG_COUNTRY_MASTER | Customer |
The countries associated with the customer. This stores the master List of countries. |
Y |
Y |
|
Y |
|
| STG_CUST_ANTICIPATORY_PROFILE | Customer |
The projections of expected trading and transaction activity were collected for a customer. |
Y |
Y |
|
Y |
|
STG_CUSTOMER_ALT_CCY_VALUES |
Customer |
The values expected in reporting/local currency for a particular customer. |
Y |
Y |
|
Y |
|
| STG_EMAIL_MASTER | Customer |
The customer’s e-mail addresses. A customer can have multiple e-mail addresses. |
Y |
Y |
Y |
Y |
|
| STG_PARTY_ACCOUNT_ROLE_MAP | Account |
The mapping of an account to multiple roles played by a party. |
Y |
Y |
|
|
|
| STG_PARTY_ADDRESS_MAP | Customer |
Mapping of party and address. Note: Refer to Supplemental Information for Customer Address for more information about this table. |
Y |
Y |
Y |
Y |
|
STG_PARTY_DETAILS |
Customer |
The complete details of a party. |
Y |
Y |
Y |
Y |
|
| STG_PARTY_EMAIL_MAP | Customer |
Mapping of party and email. |
Y |
Y |
Y |
Y |
|
| STG_PARTY_MASTER | Customer |
Party refers to customer, issuer, guarantor, and so on. |
Y |
Y |
Y |
Y |
|
STG_PARTY_PARTY_RELATIONSHIP |
Customer |
Parties related to each other. |
Y |
Y |
|
Y |
|
STG_PARTY_PHONE_MAP |
Customer |
This entity contains customer phone numbers. |
Y |
Y |
|
Y |
|
STG_PHONE_MASTER |
Customer |
Phone numbers of customers of the firm. |
Y |
Y |
|
Y |
|
STG_CORRESPONDENT_MKT_SERVED |
Customer |
This table identifies the association between the customer and the markets it serves. In this case, the customer is expected to be a legal entity (versus an individual customer) that may serve many different markets. |
N |
|
|
Y |
|
STG_CORRESPONDENT_PROD_SERVED |
Customer |
This table identifies the association between the customer and the products it offers. In this case, the customer is expected to be a legal entity (versus an individual customer) that may offer many different products. |
N |
|
|
Y |
|
STG_CUSTOMER_IDENTIFCTN_DOC |
Customer |
The Customer Identification Document table contains information regarding identification documents provided by customers for the purpose of Know Your Customer (KYC) identity verification when opening an account. |
N |
|
|
Y |
|
STG_PARTY_APPLICATION_ROLE_MAP |
Customer |
This table maps an account to multiple roles played by a party. |
N |
|
|
Y |
|
STG_TRADING_ACCOUNT |
Account |
An investment account containing securities, cash or other holdings. |
N |
Y |
|
Y |
|
| STG_ANNUITY_TXNS | Transaction |
Entity contains the annuity transactions. |
N |
Y |
|
|
|
| STG_CARDS_PAYMENT_TXNS | Transaction |
The cards payment details with transaction granularity |
N |
Y |
|
|
|
| STG_CASA_TXNS | Transaction |
The CASA Account Ledger populated at the end of the day. |
Y |
Y |
|
Y |
|
| STG_CORRESPONDENT_ACCT_TXNS | Transaction |
Entity contains the correspondent account transactions. |
N |
Y |
|
|
|
| STG_FRONT_OFFICE_TXN_PARTY | Transaction |
A list of the parties, internal or external, involved in a front-office transaction that can vary with the type of transaction. |
Y |
Y |
|
Y |
|
| STG_LEASES_TXNS | Transaction |
The transactions occurred on lease contracts. |
N |
Y |
|
|
|
| STG_LOAN_CONTRACT_TXNS | Transaction |
The transactions occurred on loan contracts. |
N |
Y |
|
|
|
| STG_MERCHANT_CARDS_TXNS | Transaction |
The transactions occurred on merchant card contracts. |
N |
Y |
|
|
|
| STG_MM_TXNS | Transaction |
The transactions occurred on money market contracts data. |
N |
Y |
|
|
|
| STG_OD_ACCOUNTS_TXNS | Transaction |
The transactions occurred on OD Accounts. |
N |
Y |
|
|
|
| STG_REPO_TRANSACTIONS | Transaction |
Entity contains the REPO transactions. |
N |
Y |
|
|
|
| STG_RETIREMENT_ACCOUNTS_TXNS | Transaction |
The transactions occurred on Retirement accounts. |
N |
Y |
|
|
|
| STG_SWAP_ACCOUNT_TXNS | Transaction |
The swap account transactions. |
N |
Y |
|
|
|
STG_TERMDEPOSITS_TXNS |
Transaction |
Term or Time deposit ledger details. |
N |
Y |
|
|
|
| STG_TRADING_ACCOUNT_TXNS | Transaction |
The transactions performed on a trading account. |
N |
Y |
|
|
|
STG_TRUSTS_TXNS |
Transaction |
The transactions which occurred on trust accounts. |
N |
Y |
|
|
|
STG_TRUSTED_PAIR |
Account |
The customers involved are considered to be trusted by the financial institution. |
N |
N |
|
|
|
| STG_TXN_ALT_CCY_VALUES | Transaction |
The values expected in reporting or local currency for a particular transaction. |
Y |
Y |
|
Y |
|
STG_WATCHLIST_MASTER |
Watchlist |
The risk and trust lists that are used to monitor transactional or trading activities for money laundering or fraud. Watch Lists are externally published lists from the Office of Foreign Assets Control (OFAC) and the Financial Action Task Force (FATF) for monitoring internal accounts or customers. |
Y |
Y |
|
|
|
STG_WATCHLIST_MEMBER_ENTRY |
Watchlist |
The entities (countries, organizations, accounts, or persons) associated with a watch list for monitoring transactional or trading activities for money-laundering or fraud. |
Y |
Y |
|
|
|
FCC_AM_HOLIDAY_MASTER |
|
Holidays and other non-working days. |
Y |
Y |
|
|
|
FCC_AM_DATAORIGIN_COUNTRY_MAP |
|
The mapping of country to holidays and other non-working days. |
Y |
Y |
|
|
|
FCC_CS_ALERTS |
Customer |
All alerts that are generated after screening batches are stored in this table, and no matching information for alerts are available in this table. |
N |
|
|
Y |
|
FCC_CS_ALRT_MATCHES |
Customer |
This table contains the alert information along with exact matches for each alert, and also matching information for alerts is available in this table. |
N |
|
|
Y |
|
FCC_KYC_ALGORITHMIC_SCORING_DETAILS |
Customer |
This table contains details of the assessed Algorithmic Score for customers and prospects, as provided by your firm’s Know Your Customer application during onboarding. |
N |
|
|
Y |
|
FCC_KYC_BUSINESS_CHECK_DETAILS |
Customer |
This table contains details of the assessed risk score for a business check rule associated with prospects or customers, as provided by your firm’s Know Your Customer application during onboarding. |
N |
|
|
Y |
|
FCC_KYC_CUST_REVIEW_DTLS |
Customer |
This table contains details of why the Risk Assessment was performed for customers. For example, Periodic Review, New Account Review, Accelerated Re-review, and Deployment Initiation. |
N |
|
|
Y |
|
FCC_KYC_RA |
Customer |
This table contains the Risk Assessment Score, or maximum score of the algorithmic and business check scores, for prospects, as provided by your firm’s Know Your Customer application. |
N |
|
|
Y |
|
FCC_KYC_RA_CUST |
Customer |
This table contains the Risk Assessment Score, or maximum score of the algorithmic and business check scores, for customers, as provided by your firm’s Know Your Customer application. |
N |
|
|
Y |
|
FCC_KYC_SCORING_SUMMARY |
Customer |
Summary of how the KYC Risk Score was determined, including assessment details such as the assessment score, assessment ID, batch type, jurisdiction, customer type, customer ID, entity name, SSN/TIN, business domain, created date, and risk category. |
N |
|
|
Y |
|
STG_PRODUCT_MASTER |
Account |
This table contains information about the loan product types available in your implementation. |
N |
|
|
|
|
STG_CARDS_MASTER |
Account |
This table contains information about the credit product types available in your implementation. |
N |
|
|
|
|
STG_FCC_CRM_FEEDBACK |
Customer |
This table stores list of various economic zones that a legal entity is licensed to operate in a particular jurisdiction (e.g. Special Economic Zone, Free Trade Zone etc.) |
N |
|
|
Y |
|
STG_FCC_KYC_EXT_SYS_FEEDBACK |
Customer/Prospect |
This table stores feed back from external case management system integrated with KYC CS. Any Risk Assessments generated as part of KYC system can be fed into this table along with its corresponding investigation feedback conducted in the external system. |
N |
Y |
|
NOTE:
· After the data is prepared in the table csv files. the FCC_AM_HOLIDAY_MASTER and FCC_AM_DATAORIGIN_COUNTRY_MAP must be populated using the AMLHolidayMasterDataLoad batch. For more information, see Managing Batches.
1 In order for the data to correctly load in the AMLHolidayMasterDataLoad batch, headers must be removed in the FCC_AM_HOLIDAY_MASTER csv file.
· For more information on scenarios and table mapping details, see Data Map files.
· For more information on data structure, data type, column name, entity name, and so on, see Data Model files.
· For more information on sample .csv format, see Sample Templates files.
· For more information on Technical Scenario Description (TSDs), see TSD files.
The STG_PARTY_ADDRESS_MAP cannot contain multiple entries with the same address type for a given MIS date for the same customer.
Example 1
Customer |
Date |
Address
Type |
|
C1 |
10-DEC-2020 |
O (Office) |
Supported |
C1 |
10-DEC-2020 |
H (Home) |
Supported |
C1 |
10-DEC-2020 |
H (Home) |
Not supported since Address Type with value of ‘H’ is already given for this date |
The STG_ACCOUNT_ADDRESS_MAP cannot contain multiple entries with the same address type for a given MIS date for the same account.
Example 2
Account |
Date |
Address
Type |
|
A1 |
10-DEC-2020 |
O (Office) |
Supported |
A1 |
10-DEC-2020 |
H (Home) |
Supported |
A1 |
10-DEC-2020 |
H (Home) |
Not supported since Address Type with value of ‘H’ is already given for this date. |