Customer File

A listing of all Customers in Helix for a given program with these qualities (as of the effective date of the file):

  • Moved to a Verified status on that date after successfully completing registration
  • Remained in a Verified status during the entire date
  • Changed from a Verified status to an Archived status on that date
  • Changed from a Verified status to a Deceased status on that date

i.e. Customers in this file with a status of Archived or Deceased will not appear in files for subsequent dates.
NOTE: On the day a customer is verified, he or she will appear in both this file and the Customer Registration File for that day.

Customer File Definition

The Customer File is created by Helix on a daily basis. It has the following properties:

  1. Exactly one tab-delimited header line
  2. Zero or more tab-delimited content lines
  3. A tab character (\t, or 0x09) embedded in actual text content will be replaced with a space character (" ", or 0x20) during file generation
  4. This file is tab-delimited to help reduce the size of file as it may grow considerably over time and possibly contain large sections of empty columns.
  5. ANSI encoded
  6. Line endings are Windows-style CarriageReturn + LineFeed (\r\n, or 0x0D0A)
  7. File will be available in the relative directory of /CustomerFiles
  8. File name follows a specific, case-sensitive pattern of: yyyyMMddhhmm_CUSTOMER.TXT

🚧

Format Disclaimer
Helix reserves the right to append new field(s) to the end of any Header or Content line without notice. This is to allow new data points to be added as needed in a timely fashion.

Implementation Note
Your code should be written such that unexpected characters after the "last" field but prior to the end of each line should be ignored. That is, if the file is documented as having 30 tabs per line, receiving a file with 31 or more per line should not disrupt your processing. This applies to both Header and Content lines.

File Name Disclaimer
The date in file name should be used as a guideline for human eyes only. Any date-related programmatic dependencies should rely on the FileCreatedDate or FileEffectiveDate contained within the header line of each file, as these will be precise to the second and will be in the appropriate timezone.

Header Row

PropertyData Type (Max Length)Tab OffsetDescription
FileNamestring (50)0The name of this request file excluding path.
Format: yyyyMMddhhmm_CUSTOMER.TXT
Example: 201410210148_CUSTOMER.TXT
RecordCountinteger (10)1The number of records represented within the file. This field is zero-padded on the left side.
Example: 0000000872
FileCreatedDatedatetime (34)2The date the file was created. Follows same format as API.
Example: 2014-10-20T10:30:31.456-05:00
See data format guidelines
FileEffectiveDatedatetime (34)3The date to which the data in the file pertains. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines

Content Row

PropertyData Type (Max Length)Tab OffsetDescription
CustomerIdinteger (10)0The customerId property of the customer object.
CustomerTagstring (50)1The tag property of the customer object.
FirstNamestring (64)2The firstName property of the customer object.
MiddleNamestring (64)3The middleName property of the customer object.
LastNamestring (128)4The lastName property of the customer object.
Suffixstring (20)5The lastName property of the customer object.
BirthDatestring (10)6The birthDate property of the customer object.
Format: yyyy-MM-dd
Example: 1986-07-12
Genderstring (1)7The gender property of the customer object.
Culturestring (50)8The culture property of the customer object.
TaxIdstring (30)9The taxId property of the customer object.
CustomerStatusstring (50)10The status property of the customer object.
CreatedDatedatetime11The date the customer object was created and its status property set to Initiated. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines
ArchivedDatedatetime12The date the status property of the customer object was changed to Archived. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines
DeceasedDatedatetime13The deceasedDate property of the customer object. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines
IdVerificationDatedatetime14The idVerificationDate property of the customer object. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines
IdVerificationDocumentsReceivedDatedatetime15The date documents required to verify the customer's identity were received. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines
DriversLicenseNumberstring (30)16The driversLicenseNumber property of the customer object.
DriversLicenseStatestring (2)17The driversLicenseState property of the customer object.
DriversLicenseIssueDatedatetime18The driversLicenseIssueDate property of the customer object. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines
DriversLicenseExpireDatedatetime19The driversLicenseExpireDate property of the customer object. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines
PassportNumberstring (30)20The passportNumber property of the customer object.
PassportCountrystring (5)21The passportCountry property of the customer object.
PassportIssueDatedatetime22The passportIssueDate property of the customer object. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines
PassportExpireDatedatetime23The passportExpireDate property of the customer object. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines
EmailAddressstring (255)24The emailAddress property of the customer object.
IsSubjectToBackupWithholdingstring (1)25The isSubjectToBackupWithholding property of the customer object.
- Y: yes/true
- N: no/false.
IsOptedInToBankCommunicationstring (1)26The isOptedInToBankCommunication property of the customer object.
- Y: yes/true
- N: no/false.
IsDocumentsAcceptedstring (1)27The isDocumentsAccepted property of the customer object.
- Y: yes/true
- N: no/false.
DocumentsAcceptedDatedatetime28The date the customer accepted the documents. Will typically coincide with the IdVerificationDate. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines
IsLockedstring (1)29The isLocked property of the customer object.
- Y: yes/true
- N: no/false.
LockedDatedatetime30The lockedDate property of the customer object. Follows same format as API.
Example: 2014-10-20T23:59:59.999-05:00
See data format guidelines
LockedReasonstring (255)31The lockedReason property of the customer object.
ResidenceLine1string (100)32The addressLine1 property of the address object associated with the Residence address for this customer.
ResidenceLine2string (100)33The addressLine2 property of the address object associated with the Residence address for this customer.
ResidenceLine3string (100)34The addressLine3 property of the address object associated with the Residence address for this customer.
ResidenceLine4string (100)35The addressLine4 property of the addess object associated with the Residence address for this customer.
ResidenceCitystring (50)36The city property of the addess object associated with the Residence address for this customer.
ResidenceStatestring (2)37The state property of the addess object associated with the Residence address for this customer.
ResidencePostalCodestring (50)38The postalCode property of the addess object associated with the Residence address for this customer.
ResidenceCountrystring (50)39The country property of the addess object associated with the Residence address for this customer.
MailingLine1string (100)40The addressLine1 property of the addess object associated with the Mailing address for this customer.
MailingLine2string (100)41The addressLine2 property of the addess object associated with the Mailing address for this customer.
MailingLine3string (100)42The addressLine3 property of the addess object associated with the Mailing address for this customer.
MailingLine4string (100)43The addressLine4 property of the addess object associated with the Mailing address for this customer.
MailingCitystring (50)44The city property of the addess object associated with the Mailing address for this customer.
MailingStatestring (2)45The state property of the addess object associated with the Mailing address for this customer.
MailingPostalCodestring (50)46The postalCode property of the addess object associated with the Mailing address for this customer.
MailingCountrystring (50)47The country property of the addess object associated with the Mailing address for this customer.
HomePhonestring (50)48The number property of the phone object associated with the Home phone for this customer.
MobilePhonestring (50)49The number property of the phone object associated with the Mobile phone for this customer.
OfficePhonestring (50)50The number property of the phone object associated with the Office phone for this customer.
CustomField1string (100)51The customField1 property of the customer object.
CustomField2string (100)52The customField2 property of the customer object.
CustomField3string (100)53The customField3 property of the customer object.
CustomField4string (100)54The customField4 property of the customer object.
CustomField5string (100)55The customField5 property of the customer object.
LastActivityDatedatetime56The LastActivityDate is updated whenever a customers information or account is accessed or updated.

Take me to the Example Customer File