Purchase order

Purchase orders raised against suppliers: committed spend not yet posted.

Part of Financials in the register catalog.

Register ID: purchase_orderUse 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.

Download JSON Schema See an example record

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

15 fields: 4 required, 11 optional.

Required

Every record carries these fields.

vendorText

The supplier the PO is placed with.

Example: Sunshine Coast Quarries Pty Ltd

occurred_atDate and timeISO 8601, with time zone

The order date of the PO.

Example: 2026-06-08T00:00:00

external_idText

Source record identity / dedup key.

Example: BC-PO-44120

amountDecimal numberUnit: AUD

Total committed value of the PO, tax inclusive.

Example: 96800

Optional

Present when the source system records them.

projectText

Project/job the PO is for, when resolvable.

Example: BWG-2025-001

financial_periodDateYYYY-MM-DD

Accounting period the order falls in.

Example: 2026-06-01

legal_entityText

Company that placed the order.

Example: Bridgeworks Group Pty Ltd

currencyText

Denomination of amount

Example: AUD

statusText

PO lifecycle state (Open/Released/Pending Approval/…)

Example: Released

amount_excluding_taxDecimal numberUnit: AUD

Committed value net of tax.

Example: 88000

tax_amountDecimal numberUnit: AUD

Tax component of the committed value.

Example: 8800

posting_dateDateYYYY-MM-DD

Date the PO posted to the ledger, if at all.

Example: 2026-06-08

requested_receipt_dateDateYYYY-MM-DD

Expected delivery date.

Example: 2026-06-22

fully_receivedTrue or false

Whether all lines are receipted.

Example: false

purchaserText

The buyer/approver who raised the PO.

Example: Kim Tanaka

Example record

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

{
  "amount": 96800,
  "amount_excluding_tax": 88000,
  "currency": "AUD",
  "external_id": "BC-PO-44120",
  "financial_period": "2026-06-01",
  "fully_received": false,
  "legal_entity": "Bridgeworks Group Pty Ltd",
  "occurred_at": "2026-06-08T00:00:00",
  "posting_date": "2026-06-08",
  "project": "BWG-2025-001",
  "purchaser": "Kim Tanaka",
  "requested_receipt_date": "2026-06-22",
  "status": "Released",
  "tax_amount": 8800,
  "vendor": "Sunshine Coast Quarries Pty Ltd"
}

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

Show 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.

Book a 30-minute call Start free