Data Specification - MGA
Data File Requirements: (Note: to load files to the DAT server for testing add the suffix _DAT at end of each of the file names)
Item | Requirement | Details |
|---|---|---|
1 | Each data tab on the Specification must be provided in its own, separate file |
|
2 | All files must be provided in CSV (comma delimited) format |
|
3 | CSV files must be with Windows-style line ending (CRLF) |
|
4 | File Naming Convention must follow this format exactly | Advisors.csv Companies.csv Contracts.csv |
5 | All columns found in each file must be included |
|
6 | All column headings found in each file must be included and match exactly |
|
7 | Files must be in Unicode, UTF-8 format to display accents properly in APEXA |
|
Data Structure Requirements:
Item | File | Requirement | Details |
|---|---|---|---|
1 | Advisors | Must only include records of individual advisors (people) |
|
2 | Advisors | Cannot include duplicate advisor IDs | Duplicate advisor ID records will NOT be loaded into APEXA InTrust |
3 | Companies | Must include a record representing your organization |
|
4 | Companies | Must only include corporate entities (companies only) |
|
5 | Companies | Cannot include duplicate company IDs | Duplicate company ID records will NOT be loaded into APEXA InTrust |
6 | Contracts | Contractual relationships must exist at every level in the Contracts file | If you have a 4 party contract: Carrier > MGA > Corporation > Advisor, you must also include the 3-party contract: Carrier > MGA > Corporation in your data set. |
7 | Contracts | Cannot include duplicate contract IDs or broker codes | Duplicate contract IDs or broker codes will not be loaded into APEXA InTrust |
8 | Contracts | Only include Carrier contract records where your organization is the MGA |
|
Table Diagram:
