Timesheet code list
Timesheet code list is one of Demiton's published registers for Australian civil construction. Timesheet and pay codes: award codes, allowances and the like. 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 Payroll in the register catalog.
- Register ID
timesheet_code_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.
- Fair Work Act 2009Fair Work Act 2009 - employee records and National Employment Standards
- Fair Work Act 2009Fair Work Regulations 2009 - employee record content
- Single Touch PayrollSingle Touch Payroll Phase 2 employer reporting guidelines
- ISO 30414Human resource management - Requirements and recommendations for human capital reporting and disclosure
Connectors
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
- MYOB BusinessPartial
- Procore
- Xero Payroll AU
Fields
9 fields: 4 required, 5 optional.
Required
Every record carries these fields.
- codeText
The pay / timesheet code the cross-source alias binding matches on.
Example:
EARTHWORKS- nameText
Human name of the timesheet code.
Example:
Earthworks and Excavation- source_external_idNumber
The raw record id in the producing system.
Example:
3301- timesheet_code_entity_idWhole number
Demiton canonical
TIMESHEET_CODEspine node this fact is about.Example:
8801
Optional
Present when the source system records them.
- legal_entity_idWhole number
Owning legal entity where the source is multi-company.
Example:
1- source_created_atDate and time
When the source system created the code.
Example:
2025-01-10T00:00:00- source_deleted_atDate and time
Soft-delete time in the source system, if the system keeps deleted codes in the feed.
- source_modified_atDate and time
When the source system last modified the code.
- parent_time_code_referenceGroup of fields
The source's nested parent/owning time-code object, if the code table is hierarchical.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "code": "EARTHWORKS", "legal_entity_id": 1, "name": "Earthworks and Excavation", "source_created_at": "2025-01-10T00:00:00", "source_external_id": 3301, "source_system": "ASSIGNAR", "timesheet_code_entity_id": 8801}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/timesheet_code_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.