Skip to content
Demiton

Budget vs actual

Budget against actual spend for the organisation, by expense category.

Part of Financials in the register catalog.

Register ID
budget_vs_actualUse this name to ask for the register. The API calls it a shelf ID.
Each record is
A stateThe current value of something, replaced when it changes.
Status
DeclaredDefined, and fills when a source produces its first record.
Data
OrganisationPrivate to each organisation's own workspace.
Version
v1Current version.

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
  • Oracle Aconex
  • Procore

Fields

10 fields: 6 required, 4 optional.

Required

Every record carries these fields.

financial_periodText

The accounting period the budget and the actuals cover.

Example: 2026-07

expense_categoryText

The classification the budget line and the actual GL movement share, so the two are comparable.

Example: Labour

source_systemText

The bound ERP the budget side was read from.

Example: D365_BUSINESS_CENTRAL

budget_amountDecimal numberUnit: AUD

Budgeted spend for the category in the period.

Example: 185000

actual_amountDecimal numberUnit: AUD

Net actual GL spend for the category in the period, debits less credits.

Example: 172340.55

Optional

Present when the source system records them.

variance_amountDecimal numberUnit: AUD

budget_amountactual_amount for the category.

Example: 12659.45

currencyCurrency codeISO 4217, e.g. AUD

The currency the two amounts are in; today the measure names hard-code AUD.

Example: AUD

amount_basisText

Whether budget_amount and actual_amount include GST.

Example: excl_gst

budget_entry_countWhole numberUnit: count

Number of source budget rows folded into the row.

Example: 4

Example record

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

budget_vs_actual.example.json
{
"actual_amount": 172340.55,
"amount_basis": "excl_gst",
"budget_amount": 185000,
"budget_entry_count": 4,
"currency": "AUD",
"expense_category": "Labour",
"financial_period": "2026-07",
"legal_entity_id": "BWG-QLD-01",
"source_system": "D365_BUSINESS_CENTRAL",
"variance_amount": 12659.45
}

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/budget_vs_actual/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 callStart free