Employee contact detail

Employee contact and emergency-contact details from payroll. Readable only by roles permitted to see personal information.

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

v1Current version.

Download JSON SchemaSee an example record

Standards

This register holds records these standards and laws ask for. Holding them does not by itself certify compliance.

• Fair Work Act 2009National employment standards and modern awardsAustralia
• Single Touch PayrollPayroll reporting to the Australian Taxation OfficeAustralia

Connectors

Connected today

Demiton keeps this register current from these systems now.

• KeyPay

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

13 fields: 3 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

source_systemText

Which bound system emitted the row; KEYPAY today.

Example: KEYPAY

external_idText

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

Example: 1001

Optional

Present when the source system records them.

legal_entityText

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

Example: Bridgeworks Group Pty Ltd

emailText

Work email address.

Example: aaron.patel@bridgeworks.example

home_emailText

Personal email address, where supplied.

mobile_phoneText

Mobile number.

Example: 0400 000 111

work_phoneText

Work phone number.

Example: 07 5222 0100

home_phoneText

Home phone number.

residential_addressGroup of fields

Where the worker lives.

postal_addressGroup of fields

Postal address, when different from residential.

emergency_contact_primaryGroup of fields

First emergency contact.

emergency_contact_secondaryGroup of fields

Second emergency contact.

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…