If you're integrating your HRIS with Stadium, you may be wondering: What employee data fields are required for Stadium? What fields should I share from Workday, BambooHR, or SAP? How do I map fields for HRIS integration with Stadium? This article outlines the recommended fields to be shared via your HRIS platform integration.

To deliver the best possible experience to your employees, we request viewing access to a standardized set of employee data fields.

⚠️ Note:

Field names may vary depending on your HRIS (e.g., Workday, Darwinbox, SAP, BambooHR, etc.). However, we request mapping equivalent data points as outlined below.

The fields listed below represent Stadium’s recommended guidelines for a basic HRIS integration. While only a few are marked as mandatory, we strongly encourage sharing as many relevant data points as possible. A richer data set enables us to provide more personalized experiences, reduce manual coordination, and unlock more robust reporting and automation.

📑 Stadium HRIS Field Requirements – Master Table

Field Name	Description & Example	Importance
first_name	First name of the employee (e.g., John)	Mandatory
last_name	Last name of the employee (e.g., Doe)	Mandatory
email	Work email address (e.g., [email protected])	Mandatory
date_of_birth	DOB in MM/DD/YYYY format (e.g., 07/04/1990)	Strongly Recommended
phone_number	Contact number (e.g., +1-312-555-0198)	Recommended
title	Job title (e.g., Product Manager)	Recommended
team_name	Department/team (e.g., Marketing)	Recommended
manager_email	Employee’s manager (e.g.) Ideal for reporting and approvals	Strongly Recommended
employment_status	Current status (e.g., Active, Inactive, Pending)	Mandatory
employment_start_date	Date of joining (e.g., 03/15/2022)	Strongly Recommended
employment_end_date	Last working date (e.g., 06/30/2025)	Recommended
offer_status	Status of offer (e.g., Accepted, Revoked)	Strongly Recommended
offer_start_date	Offer validity start (e.g., 02/10/2022)	Strongly Recommended
offer_closed_date	When the offer was finalized (e.g., 02/15/2022)	Recommended
home_address	Full home address including street, apartment, city, state, ZIP, and country (e.g., 123 Elm St, Apt 5B, Chicago, IL, 60614, USA)	Strongly Recommended
home_address	Full home address including street, apartment, city, state, ZIP, and country (e.g., 123 Elm St, Apt 5B, Chicago, IL, 60614, USA)	Strongly Recommended
work_address	Full office address including street, suite, city, state, ZIP, and country (e.g., 456 Corporate Blvd, Suite 701, San Francisco, CA, 94105, USA)	Strongly Recommended

🔐 Integration Guidelines

To ensure a smooth experience, please follow these best practices:

✅ Field Mapping

Names may differ — ensure equivalent fields are shared, even if named differently in your HRIS.

✅ Data Accuracy

Avoid placeholder values (e.g., “N/A”, “Unknown”) for critical fields like email, department, etc.

✅ Data Sync:

We sync data daily to keep information current and reliable.

✅ Security:

Stadium only requires read/view-only access. No data is written back to your HRIS system.

✅ Compliance

All data is handled in accordance with GDPR, SOC-2, and other data protection laws.

📩 Need Help?

If you have any questions about your HRIS integration or need support identifying equivalent fields, our onboarding team is here to help.

Feel free to contact us at: [email protected]

Try premium features free for 30 days! After your trial, upgrade to a paid Stadium Package to continue enjoying premium access.

Visit our Pricing Page to explore the details of each Package and choose the one that best suits your needs.

Any question(s)? We're here to help!
Ask us anything via CHAT / FILL OUT OUR CONTACT US FORM:

bystadium.com
✨Contact Us form

Request a demo with our account specialist here.

Recommended HRIS Fields for Stadium Integration

📑 Stadium HRIS Field Requirements – Master Table

🔐 Integration Guidelines

📩 Need Help?