Skip to content
Demiton

Bank accounts

Bank accounts registered in your ERP.

Part of Counterparties in the register catalog.

Register ID
bank_accountsUse 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
AvailableFilled today from connected systems, uploads or public data.
Data
OrganisationPrivate to each organisation's own workspace.
Version
v1Current version.
Download JSON SchemaSee 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 AcumaticaPartial
  • MYOB BusinessPartial
  • Xero Accounting

Fields

9 fields: 3 required, 5 optional, 1 defined by each organisation.

Required

Every record carries these fields.

source_systemText

The system the account record was read from.

Example: D365_BUSINESS_CENTRAL

canonical_keyText

The dedup key the spine used (BC number)

Example: BANK-OP-001

account_nameText

The human label of the account.

Example: Bridgeworks Group Operating Account

Optional

Present when the source system records them.

external_idText

The source system's own identifier for the account.

Example: BANK-OP-001

currency_codeText

The account's denomination.

Example: AUD

last_modified_atDate and timeISO 8601, with time zone

When the source last changed the account.

Example: 2026-08-15T09:30:00Z

summaryText

One-line prose digest injected by the projector.

Example: Primary operating account for day-to-day project disburse…

Defined by each organisation

Their contents come from the organisation's own forms or systems, so they differ between organisations.

account_numberText

The bank's own account number for this account.

Example: 014-000 123456789

Example record

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

bank_accounts.example.json
{
  "account_name": "Bridgeworks Group Operating Account",
  "account_number": "014-000 123456789",
  "canonical_key": "BANK-OP-001",
  "currency_code": "AUD",
  "external_id": "BANK-OP-001",
  "last_modified_at": "2026-08-15T09:30:00Z",
  "legal_entity_id": "Bridgeworks Group Pty Ltd",
  "source_system": "D365_BUSINESS_CENTRAL",
  "summary": "Primary operating account for day-to-day project disbursements."
}

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/bank_accounts/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