The canonical schema for List data

The files you are uploading to the Screener need to adhere to this canonical schema. The file must contain all of these field names in this order, whether data exists in each field or not. The field length also does not matter.

ActiveFlag|AddressKey|AddressLine1|AddressLine2|AddressType|Alias_CompanyName|
Alias_FirstName|Alias_FourthName|Alias_LastName|Alias_MaturitySuffix|Alias_Name|
Alias_SecondName|Alias_ThirdName|AliasID|AliasQuality|AltCitizenship|AlternateSpelling|
ApartmentNumber|Category|Citizenship|City|Country|Deceased|Designation|Details|DOB|
EmailAddress|FirstName|FourthName|Gender|HouseNumber|IdentifierCountry|IdentifierID|
Identity_CityOfIssue|Identity_DateOfExpiration|Identity_DateOfIssue|IdentityNumber|
IdentityType|LastName|LastUpdateDate|LeadingDirectional|List_UDAID|ListSourceType|
MaturitySuffix|Name|NationalID|Nationality|Organization|PlaceOfBirth|PostalCode|
RecordCreationDate|RecordEndDate|RecordLastUpdateDate|ReferenceNumber|SecondName|
StateProvince|StreetName|StreetSuffix|SubCategory|ThirdName|TrailingDirectional|
UDA_EffectiveEndDate|UDA_EffectiveStartDate|UDA_Name|UDA_Type|UDA_Value|UID|EntityType|
ActiveStatus|TitleHonorific|ScriptLanguage|NameType|AddressRemarks|IdentityNotes|NameId|
ReferenceGroup|ActiveDate|AliasTitle|AliasTitleHonorific|AliasScriptLanguage|Title|AliasNameType|
AliasRemarks|Remarks