Payment schedule

The payment schedule answering a progress claim under Security of Payment legislation.

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.

Each record is

An eventSomething that happened at a point in time.

Status

PlannedDefined ahead of the connector that will fill it.

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.

• Security of paymentSecurity of payment legislation for constructionAustralia

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.

external_idText

The source system's own id for the schedule.

Example: PS-2201

source_systemText

Which bound system emitted the row.

Example: D365_BUSINESS_CENTRAL

projectText

The project the claim and schedule relate to.

Example: BWG-2025-001

claimText

The payment claim this schedule responds to.

Example: PC-14

scheduled_amountMoney amount

The amount the respondent proposes to pay.

Example: 268500

currencyText

The currency of the amounts.

Example: AUD

issued_onDateYYYY-MM-DD

The date the schedule was provided.

Example: 2026-07-28

jurisdictionText

The Security of Payment Act that governs the schedule.

Example: Building Industry Fairness (Security of Payment) Act 2017…

Optional

Present when the source system records them.

claimed_amountMoney amount

The amount the claim sought.

Example: 295000

calculation_basisText

How the scheduled amount was calculated.

Example: Assessed against measured works to 25 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.

claimantText

The party that made the claim.

Example: Bridgeworks Group Pty Ltd

payment_due_onDateYYYY-MM-DD

The due date for payment of the scheduled amount.

Example: 2026-08-18

Example record

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

payment_schedule.example.json

{
  "calculation_basis": "Assessed against measured works to 25 July 2026 per progress claim PC-14.",
  "claim": "PC-14",
  "claimant": "Bridgeworks Group Pty Ltd",
  "claimed_amount": 295000,
  "currency": "AUD",
  "external_id": "PS-2201",
  "issued_on": "2026-07-28",
  "jurisdiction": "Building Industry Fairness (Security of Payment) Act 2017 (Qld)",
  "payment_due_on": "2026-08-18",
  "project": "BWG-2025-001",
  "reasons_for_difference": "Traffic control claimed at contract rate; assessed at measured hours.",
  "scheduled_amount": 268500,
  "source_system": "D365_BUSINESS_CENTRAL"
}

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/payment_schedule/v1.json

Show the full JSON Schema

Loading the schema…