HRIS Systems

Contract-as-Code works with any HRIS or payroll system that can export employee data as CSV. No direct API integration is required.

How it works

1. Export employee payroll data from your HRIS as a CSV file
2. Upload the CSV to Contract-as-Code
3. The column-mapping engine recognises your HRIS format
4. Validation runs against your approved agreement rules

The platform is designed to work alongside your existing payroll infrastructure — not replace it.

Supported platforms

Automatically recognised formats

Platform	Export path	Notes
ADP Workforce Now	Reports → Custom → Export to CSV	Recognised column names: Employee ID, Hours, Rate, Position
Ceridian Dayforce	Reporting → Standard Reports → Payroll Detail	Time detail exports include shift start/end times
Workday	Report Builder → Custom Report → Export CSV	Works with both standard and custom report layouts
UKG / Kronos	Reports → Timecard Detail → Export	Includes shift-level detail for premium validation
Sage Payroll	Reports → Employee Summary → Export	UK and AU versions both supported
Micropay	Reports → Pay Detail → Export CSV	Australian payroll format
BambooHR	Reports → Custom → Export	Recognised for basic employee data; supplement with payroll detail

Generic CSV

Any system that exports CSV is supported. On first upload, you'll map columns manually. The mapping is saved for future use.

Export checklist

For the most accurate validation, include these fields in your HRIS export:

Minimum (required for basic validation)

• [ ] Employee identifier (employee ID, badge number, etc.)
• [ ] Date or pay period
• [ ] Hours worked
• [ ] Hourly rate
• [ ] Job classification or title

Recommended (enables full rule coverage)

• [ ] Shift start and end times
• [ ] Overtime hours and rate
• [ ] Years of service or hire date
• [ ] Vacation hours taken and vacation pay
• [ ] Department and location

Best practice

• Export at the shift level (one row per shift per employee) rather than the pay period level — this enables daily overtime and shift premium validation
• Include the date of each record, not just the pay period end date
• Export all employees in the bargaining unit, not just those you suspect have issues

Multi-HRIS environments

If your organisation uses multiple payroll systems (e.g., different systems for different bargaining units or locations):

1. Export from each system separately
2. Upload each CSV to the appropriate validation job
3. Use the same contract(s) across jobs if the agreement covers both groups
4. Generate a portfolio report to see aggregated findings

Data handling

All uploaded employee data follows the same data privacy controls:

• Employee identifiers are hashed (SHA-256) before processing
• Data is stored in your regional data centre
• CSV files are automatically deleted 90 days after upload
• Data is never used for AI model training
• Data is never shared with other customers

See CSV Data Ingestion for the full CSV schema reference.