| File | Format | Used for |
|---|
CustomerProfile | JSON, FundConnext’s published individual-customer format | Creates and updates customers in the customer book |
AccountProfile | Pipe-delimited text, FundConnext’s published format | Creates and updates accounts |
- Files are uploaded by an officer.
- Each import is a recorded run, with rows created, updated and rejected, and the reason for every rejection. A file with a bad header is refused whole.
- CDD Core never writes particulars back to FundConnext. It is an index, not a master.
The statement job fetches the month’s statement files from FundConnext once a day until they arrive, and also accepts files an officer imports. Each file is matched to the customer’s account and e-mailed as a zip containing PDF and CSV, opened with the password FundConnext specifies. See Duties and reporting.
| Form | When proposed | Format |
|---|
| AMLO 1-02 asset transactions | From trading transactions at or above THB 5,000,000 | AERS v3.0 XML |
| AMLO 1-03 suspicious transactions | From a monitoring result or another fact the committee resolves to report | AERS v3.0 XML |
- A complete entry downloads from the filing register. The file is sealed with a SHA-256 hash when the entry is recorded.
- An entry with missing data lists the gaps and cannot be downloaded until they are filled.
- The officer encrypts the file with AMLO’s tool and files it in AERS. There is no system-to-system link to AMLO.