Payment schedule (v1)
Payment schedule is one of Demiton's published registers for Australian civil construction. The payment schedule answering a progress claim under Security of Payment legislation. 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 Contracts in the register catalog.
- Register ID
payment_scheduleUse this name to ask for the register. The API calls it a shelf ID.- Status
- PlannedDefined ahead of the connector that will fill it.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.1)Superseded by v2.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- Security of paymentBuilding and Construction Industry (Security of Payment) Act 2009 (ACT)
- AS 4000General Conditions of Contract (superseded edition, still in use)
- AS 4000General Conditions of Contract (construct only)
- Corporations Act 2001 (Cth) s 286Corporations Act 2001 (Cth) - financial records, 7-year retention
- Security of paymentBuilding and Construction Industry Security of Payment Act 1999 (NSW)
- Security of paymentBuilding Industry Fairness (Security of Payment) Act 2017 (Qld)
- Security of paymentBuilding and Construction Industry Security of Payment Act 2009 (SA)
- Security of paymentBuilding and Construction Industry Security of Payment Act 2009 (Tas)
- Security of paymentBuilding and Construction Industry Security of Payment Act 2002 (Vic), as amended from 15 Apr 2026
- Security of paymentBuilding and Construction Industry (Security of Payment) Act 2021 (WA)
- NZ CCA 2002Construction Contracts Act 2002 (NZ), 2002 No 46, as amended 2015 and 2023
- HGCRA 1996 Part IIHousing Grants, Construction and Regeneration Act 1996, Part II (as amended by LDEDCA 2009)
- SI 1998/649Scheme for Construction Contracts (England and Wales) Regulations 1998
- AIA G702/G703Application and Certificate for Payment; Continuation Sheet
Connectors
Connected today
Demiton keeps this register current from these systems now.
No system fills this register yet.
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
None planned yet.
Fields
14 fields: 8 required, 6 optional.
Required
Every record carries these fields.
- claimText
The payment claim this schedule responds to.
Example:
SI-26014- projectText
The project the claim and schedule relate to.
Example:
BWG-2025-001- currencyText
The currency of the amounts.
Example:
AUD- issued_onDate
The date the schedule was provided.
Example:
2026-08-07- external_idText
The source system's own id for the schedule.
Example:
PS-2201- jurisdictionText
The Security of Payment Act that governs the schedule.
Example:
Building Industry Fairness (Security of Payment) Act 2017…- source_systemText
Which bound system emitted the row.
Example:
D365_BUSINESS_CENTRAL- scheduled_amountMoney amount
The amount the respondent proposes to pay.
Example:
295500
Optional
Present when the source system records them.
- claimantText
The party that made the claim.
Example:
Bridgeworks Group Pty Ltd- claimed_amountMoney amount
The amount the claim sought.
Example:
312000- payment_due_onDate
The due date for payment of the scheduled amount.
Example:
2026-08-21- calculation_basisText
How the scheduled amount was calculated.
Example:
Assessed against measured works to 31 July 2026 per progr…- reasons_for_differenceText
Why the scheduled amount is lower.
Example:
Traffic control claimed at contract rate; assessed at mea…- reasons_for_withholdingText
The reasons for withholding payment.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "calculation_basis": "Assessed against measured works to 31 July 2026 per progress claim SI-26014.", "claim": "SI-26014", "claimant": "Bridgeworks Group Pty Ltd", "claimed_amount": 312000, "currency": "AUD", "external_id": "PS-2201", "issued_on": "2026-08-07", "jurisdiction": "Building Industry Fairness (Security of Payment) Act 2017 (Qld)", "payment_due_on": "2026-08-21", "project": "BWG-2025-001", "reasons_for_difference": "Traffic control claimed at contract rate; assessed at measured hours.", "scheduled_amount": 295500, "source_system": "D365_BUSINESS_CENTRAL"}Version history
- v2 (current)
- v1
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/payment_schedule/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.