Employee list
Employee list is one of Demiton's published registers for Australian civil construction. Employees registered in your payroll system. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.
Part of Workforce in the register catalog.
- Register ID
employee_listUse this name to ask for the register. The API calls it a shelf ID.- Each record is
- A stateThe current value of something, replaced when it changes.
- Status
- AvailableFilled today from connected systems, uploads or public data.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.3)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- ATO tax file number declarationTax file number and withholding declarations - kept with employee records
- Fair Work Act 2009Fair Work Act 2009 - employee records and National Employment Standards
- Fair Work Act 2009Fair Work Regulations 2009 - employee record content
- Privacy Act 1988Privacy Act 1988 - Australian Privacy Principles; employee-records exemption; health information s.6FA
- Single Touch PayrollSingle Touch Payroll Phase 2 employer reporting guidelines
- GDPRGeneral Data Protection Regulation
- ISO 30414Human resource management - Requirements and recommendations for human capital reporting and disclosure
- Employment Leave Act 2026 (NZ)Employment Leave Act 2026 (2026 No 48)
- Privacy Act 2020 (NZ)Privacy Act 2020 and Health Information Privacy Code 2020
- HMRC Real Time Information (RTI)PAYE Real Time Information - Full Payment Submission and Employer Payment Summary
- UK GDPRUK GDPR and Data Protection Act 2018
Connectors
Connected today
Demiton keeps this register current from these systems now.
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
- EROADPartial
- GeotabPartial
- HammerTechPartial
- MapTrackPartial
- MittiPartial
- MYOB Acumatica
- MYOB Business
- PayappsPartial
- ProcorePartial
- SignOnSitePartial
- SitematePartial
- Xero Accounting
- Xero Payroll AU
Fields
20 fields: 5 required, 11 optional, 4 defined by each organisation.
Required
Every record carries these fields.
- display_nameText
The worker's display name.
Example:
Aaron Patel- employment_typeText
The engagement basis.
Example:
Full-time- worker_entity_idWhole number
Demiton canonical worker spine node this fact anchors to (the subject)
Example:
5501- source_external_idText
The raw record id in the producing system.
Example:
1001- employment_start_dateDate
Date the employment relationship started.
Example:
2022-03-07
Optional
Present when the source system records them.
- emailText
Work/contact email used as an identity bridge.
- titleText
Honorific or name prefix.
- genderText
Gender, for diversity aggregation.
- job_titleText
Role/job title at the employer.
Example:
Site Supervisor- given_nameText
First/given name as a separate part.
Example:
Aaron- family_nameText
Surname/family name as a separate part.
Example:
Patel- date_of_birthDate
Worker date of birth.
- legal_entity_idWhole number
The employing legal entity, resolved per record.
- employment_statusText
Current employment state.
Example:
Active- source_created_atDate and time
When the source record was created (freshness)
- employment_end_dateDate
Date the engagement ended, where known.
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- tagsList
Tenant-assigned labels on the employee record.
- work_typesText
Tenant work-type assignment.
- employment_agreementText
Tenant award/agreement name the employee is paid under.
- reporting_dimension_valuesText
Tenant reporting-dimension assignment.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "display_name": "Aaron Patel", "employment_start_date": "2022-03-07", "employment_status": "Active", "employment_type": "Full-time", "family_name": "Patel", "given_name": "Aaron", "job_title": "Site Supervisor", "source_external_id": "1001", "source_system": "KEYPAY", "worker_entity_id": 5501}Use this contract
The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.
https://docs.demiton.io/registers/employee_list/v1.jsonShow the full JSON Schema
Loading the schema…
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would fill from them, on your data, in a 30-minute call.