Timesheet entry
Timesheet submissions, with hours by date and pay category.
Part of Payroll in the register catalog.
- Register ID
timesheet_entryUse 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.
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 awards
- Single Touch PayrollPayroll reporting to the Australian Taxation Office
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.
- EROADPartial
- HammerTechPartial
- MYOB Acumatica
- MYOB Business
- Procore
- Xero Accounting
- Xero Payroll AU
Fields
12 fields: 5 required, 6 optional, 1 defined by each organisation.
Required
Every record carries these fields.
- workerText
The person whose hours these are.
Example:
5501- occurred_atDate
The day the entry is for.
Example:
2026-08-11- financial_periodText
The pay period the hours are attributed to.
Example:
2026-08- hoursDecimal number
Hours worked in the entry.
Example:
8- source_systemText
Which bound system emitted the row.
Example:
KEYPAY
Optional
Present when the source system records them.
- projectText
The project/job the hours were worked on.
Example:
BWG-2025-001- cost_codeText
Cost code / work activity the hours are coded to.
- statusText
Approval state of the entry.
Example:
Approved- task_nameText
The task/activity the hours were worked on.
Example:
Supervision- start_timeText
The entry's start time.
- end_timeText
The entry's end time.
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- work_typeText
The vendor/tenant pay-category or work-type label.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "financial_period": "2026-08", "hours": 8, "occurred_at": "2026-08-11", "project": "BWG-2025-001", "source_system": "KEYPAY", "status": "Approved", "task_name": "Supervision", "worker": "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/timesheet_entry/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 keep current from them, on your data, in a 30-minute call.