Employee contact detail

Employee contact detail is one of Demiton's published registers for Australian civil construction. Employee contact and emergency-contact details from payroll. Readable only by roles permitted to see personal information. 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_contact_detailUse this name to ask for the register. The API calls it a shelf ID.

Each record is

An eventSomething that happened at a point in time.

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.

Download JSON SchemaSee an example record

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 recordsAustralia · ATO guidance updated 11 Jun 2025 · public summary
• Fair Work Act 2009Fair Work Act 2009 - employee records and National Employment StandardsAustralia · compilation 2026-07-07 · clause s.535 · verified against full text
• Fair Work Act 2009Fair Work Regulations 2009 - employee record contentAustralia · compilation 2026-06-20 · clause regs 3.31, 3.32, 3.44 · verified against full text
• Privacy Act 1988Privacy Act 1988 - Australian Privacy Principles; employee-records exemption; health information s.6FAAustralia · current · public summary
• Single Touch PayrollSingle Touch Payroll Phase 2 employer reporting guidelinesAustralia · Phase 2 (mandatory from 1 Jan 2022) · public summary
• GDPRGeneral Data Protection RegulationEuropean Union · 2016 · verified against full text
• ISO 30414Human resource management - Requirements and recommendations for human capital reporting and disclosureInternational · 2nd ed. 2025 (supersedes ISO 30414:2018) · paywalled, from a secondary description
• Privacy Act 2020 (NZ)Privacy Act 2020 and Health Information Privacy Code 2020New Zealand · Act 2020; HIPC version as at 1 May 2026 · public summary
• Tax Administration Act 1994 (NZ) Schedule 4Reporting of employment income information (payday filing)New Zealand · version as at 1 Jul 2026 · clause Schedule 4 Table 2 · verified against full text
• HMRC Real Time Information (RTI)PAYE Real Time Information - Full Payment Submission and Employer Payment SummaryUnited Kingdom · guidance updated 6 Apr 2026 · public summary
• UK GDPRUK GDPR and Data Protection Act 2018United Kingdom · current · public summary

Connectors

Connected today

Demiton keeps this register current from these systems now.

• Employment Hero Payroll

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
• HammerTech
• MapTrackPartial
• MittiPartial
• MYOB Acumatica
• MYOB Business
• PayappsPartial
• Procore
• SitematePartial
• Xero Accounting
• Xero Payroll AU

Fields

12 fields: 2 required, 10 optional.

Required

Every record carries these fields.

workerText

The worker the contact card belongs to; the anchor that makes the fact reachable.

Example: 1001

external_idText

The source system's own employee identifier, as text.

Example: 1001

Optional

Present when the source system records them.

emailText

Work email address.

Example: aaron.patel@bridgeworks.example

home_emailText

Personal email address, where supplied.

home_phoneText

Home phone number.

work_phoneText

Work phone number.

Example: 07 5222 0100

legal_entityText

The payroll business that owns the employee; KeyPay is multi-business.

Example: Bridgeworks Group Pty Ltd

mobile_phoneText

Mobile number.

Example: 0400 000 111

postal_addressGroup of fields

Postal address, when different from residential.

residential_addressGroup of fields

Where the worker lives.

emergency_contact_primaryGroup of fields

First emergency contact.

emergency_contact_secondaryGroup of fields

Second emergency contact.

Filed against

Records are indexed along these dimensions, so they can be asked for by any of them.

• Workerwhat the record is about, from Always set
• Legal entitycontext for the record, from When known

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

employee_contact_detail.example.json

{
  "email": "aaron.patel@bridgeworks.example",
  "emergency_contact_primary": {
    "name": "Priya Patel",
    "phone": "0400 000 112",
    "relationship": "Spouse"
  },
  "external_id": "1001",
  "legal_entity": "Bridgeworks Group Pty Ltd",
  "mobile_phone": "0400 000 111",
  "residential_address": {
    "country": "AU",
    "line1": "12 Anzac Ave",
    "postcode": "4556",
    "state": "QLD",
    "suburb": "Buderim"
  },
  "source_system": "KEYPAY",
  "work_phone": "07 5222 0100",
  "worker": "1001"
}

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.

Schema URL

https://docs.demiton.io/registers/employee_contact_detail/v1.json

Show the full JSON Schema

Loading the schema…