SFTP Eligibility File Guidelines
File format, naming, and structure requirements for eligibility files sent via SFTP.
Eligibility files tell Roundtrip which members are eligible for a transportation benefit. Following these guidelines keeps your data clean and reduces errors.
Want an example? View our eligibility file template.
Supported File Formats
- Excel (.xlsx)
- Pipe-delimited text (.txt)
- Comma-separated values (.csv)
File Naming Rules
- Must end in one of the formats above
- Only these characters are allowed: A–Z, a–z, 0–9, underscore (_), and dash (-)
- No spaces — remove them before uploading
Header and Field Formats
The eligibility file consists of the following fields:
Field Name | Also Known As | Required? | Description | Data Format |
Plan ID | Contract ID, PBP | Required | Maps members to the correct plan. Suggested format: the MA Contract number followed by the PBP (e.g., H1234-001) | Text |
Plan Name | Plan | Optional | — | Text |
Member | Member ID | Required | The rider's member ID — should match what's on their ID card | Text |
First Name | Member First Name | Required | — | Text |
Last Name | Member Last Name | Required | — | Text |
Email Address | Email | Optional | — | Text |
Phone | Phone Number | Optional | Doesn't need to be valid, but must include a valid area code | nnnnnnnnnn |
Date of Birth | DOB | Required | — | mm/dd/yyyy |
Gender | — | Required | Valid values: Male, Female, Other (can be abbreviated M, F, O) | Valid Values |
Address | Residence Address 1 | Optional | Rider's home address | Text |
City | Residence City | Optional | Rider's home address | Text |
State | Residence State | Optional | Rider's home address | Text |
Zip | Residence Zip Code | Optional | Rider's home address | Text |
Time Zone | — | Optional | Rider's time zone | — |
Budget | — | Optional | Only if the benefit is tailored per rider — the dollar amount included in their benefit | Decimal number |
Rides Limit | — | Optional | Only if the benefit is tailored per rider — the number of rides allowed | Integer |
Language Preference | Primary Language | Optional | Valid values: "en", "es" | Valid Values |
Communication Preference | — | Optional | Valid values: "sms", "voice_call" | Valid Values |
Effective Date | — | Optional | Start date of the eligibility period | mm/dd/yyyy |
Expiration Date | Termination Date | Optional | End date of the eligibility period | mm/dd/yyyy |
Important: This File Is a Full Replacement
Each new file completely replaces the last one. If a member isn't on the new file, their record gets deactivated — so always include your complete, current population, not just changes.
Did this answer your question?
😞
😐
🤩