Setting up the integration
You will need to contact your Jawnt account manager to enable the SFTP integration for your organization. Please first give us a public key (typically provided by your HRIS Provider*), and we will then share with you the username and file directory information.
* NOTE: if you are going to be manually transferring the CSVs to our SFTP, this article provides information on how to generate a public and private key.
Host Name: sftp.jawntpass.com
Username: provided by Jawnt
File directory: provided by Jawnt
File name convention: OrganizationName_TransitBenefits_EmployeeFile_YYYYMMDD.csv (replacing OrganizationName with your organization name and YYYYMMDD with current date)
Export frequency: Weekly
After the integration is set up, your HR roster will automatically be synced with Jawnt going forward.
You'll need to give your columns recognizable names for the import to succeed.
To see an example with all the columns, click here to download a template CSV file.
Each column is described in more detail below. The report exported from your HRIS Provider can include the following fields.
Unique identifier used to track the employee in the HRIS application.
Employee first name
Employee last name
Employee’s email address; used to communicate with the user about benefit enrollment.
Valid email address
Mobile phone number is used to communicate with the user about benefit enrollment.
USA-based phone number with no special characters
Used to determine if an employee is active or inactive. Only active employees can be eligible for benefits.
Either “Active” or “Inactive”
NOTE: If the field names in your report do not match the field name listed, you will need to tell Jawnt how you'd like your fields mapped to the database.
Should the flat file contain eligible employees only, or the entire roster?
By default, Jawnt assumes any active employees included in the flat file are eligible for the SEPTA Key Advantage benefit. Jawnt can also help your organization determine employee eligibility. During the onboarding process, your Jawnt account manager will work with you to understand how your organization is determining eligibility.
Additional data fields can be included in the flat file (report) such as an employee’s home address or date of birth. If this PII (Personal Identifiable Information) is being shared, original values are not stored in the database. In these cases, data shared with Jawnt is processed, re-coded (eg. date of birth is typically recoded as ‘Under 65?’ with true or false values), and the original values are discarded.
Should each subsequent flat file contain the full list of employees or changes only?
Every week, the flat file should contain the full eligible employee roster (or complete roster if Jawnt is determining eligibility) even if there are no changes since the last upload.
How does Jawnt handle inactive/terminated employees? How long should terminated employees be included on the roster?
Jawnt will mark an employee as "Inactive" if the "employee_status" column is set to “Inactive”. We recommend using a 30-day rolling approach to terminated employees. That is, an employee should be included in the roster (and listed as "Inactive") for at least 30 days after their termination date so they can be appropriately marked as "Inactive" in Jawnt. Afterward, they do not need to be included in the file.
If an employee record is missing from a file and has not previously had a status of “Inactive”, Jawnt will assume they are inactive after 90 days.
What flat file formats are supported?
The integration supports CSV files only.
Can I include other data in the flat file?
Please speak with your Jawnt account manager if there is additional data that is important to be visible in Jawnt (eg. employee location, employee type, etc.) so that we can better understand your needs.