Payable entry (v1)
Payable entry is one of Demiton's published registers for Australian civil construction. Outstanding supplier bills and the aged payables balance. 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 Counterparties in the register catalog.
- Register ID
payable_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
- 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)
- ATO record-keeping rulesATO business record-keeping rules (ITAA 1936 s 262A; TAA 1953 Sch 1 s 382-5)
- Corporations Act 2001 (Cth) s 286Corporations Act 2001 (Cth) - obligation to keep financial records
- GST Act 1999 (Cth)A New Tax System (Goods and Services Tax) Act 1999 (Cth)
- Security of paymentBuilding and Construction Industry Security of Payment Act 1999 (NSW)
- PINT A-NZ Billing BISPeppol PINT A-NZ Billing BIS (joint Australia-New Zealand specification)
- 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)
- Security of paymentBuilding and Construction Industry (Security of Payment) Act 2021 (WA)
- Directive 2006/112/ECCouncil Directive 2006/112/EC on the common system of VAT
- Directive 2014/24/EUDirective 2014/24/EU on public procurement
- EN 16931-1:2017CEN EN 16931-1 Electronic invoicing - semantic data model
- Peppol BIS Billing 3.0Peppol BIS Billing 3.0 (CIUS of EN 16931)
- Construction Contracts Act 2002 (NZ)Construction Contracts Act 2002 (NZ), 2002 No 46
- GST Act 1985 (NZ)Goods and Services Tax Act 1985 (NZ)
- PINT A-NZ Billing BISPeppol PINT A-NZ Billing BIS (joint Australia-New Zealand specification)
- HGCRA 1996 Part IIHousing Grants, Construction and Regeneration Act 1996 (UK), Part II
- Procurement Act 2023 (UK) / SI 2024/692 reg 38Procurement Regulations 2024 - payments compliance notices
Connectors
Connected today
Demiton keeps this register current from these systems now.
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 Acumatica
- Procore
Fields
18 fields: 8 required, 10 optional.
Required
Every record carries these fields.
- amountDecimal number
The signed movement of the line.
Example:
48250.75- vendorText
The supplier the payable is owed to.
Example:
Statewide Concrete Supplies Pty Ltd- due_dateDate
The date the payable falls due.
Example:
2026-08-14- remainingDecimal number
The running balance still outstanding on the entry.
Example:
48250.75- external_idNumber
The source entry's own identifier (BC
Entry_No)Example:
88231- occurred_atDate and time
The posting date the entry was booked on.
Example:
2026-07-15T00:00:00Z- source_systemText
The system the entry was read from.
Example:
D365_BUSINESS_CENTRAL- financial_periodText
The accounting period the entry falls in.
Example:
2026-07
Optional
Present when the source system records them.
- is_openTrue or false
Whether the entry is still open.
Example:
true- projectNumber
The job the payable is attributed to, when the source supplies one.
Example:
8101- currencyText
The transaction currency of the amounts.
Example:
AUD- gl_accountNumber
The ledger account the line posts to.
Example:
5100- legal_entityText
The company whose books the entry belongs to.
Example:
Bridgeworks Group Pty Ltd- document_dateDate
The date of the supplier document, distinct from posting.
Example:
2026-07-15- document_typeText
The BC ledger document type (invoice / credit memo / payment / application)
Example:
Invoice- purchaser_codeText
The BC buyer/purchaser code on the entry.
Example:
BWG-PUR-02- document_numberText
The source supplier document (bill / credit memo) number.
Example:
INV-22190- pmt_discount_dateDate
The settlement-discount date, if the supplier offers one.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "amount": 48250.75, "currency": "AUD", "document_date": "2026-07-15", "document_number": "INV-22190", "document_type": "Invoice", "due_date": "2026-08-14", "external_id": 88231, "financial_period": "2026-07", "gl_account": 5100, "is_open": true, "legal_entity": "Bridgeworks Group Pty Ltd", "occurred_at": "2026-07-15T00:00:00Z", "project": 8101, "purchaser_code": "BWG-PUR-02", "remaining": 48250.75, "source_system": "D365_BUSINESS_CENTRAL", "vendor": "Statewide Concrete Supplies Pty Ltd"}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/payable_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 fill from them, on your data, in a 30-minute call.