Receivable entry
Outstanding customer invoices and the aged receivables balance.
Part of Counterparties in the register catalog.
- Register ID
receivable_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
- 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
Fields
15 fields: 8 required, 7 optional.
Required
Every record carries these fields.
- source_systemText
The system the entry was read from.
Example:
D365_BUSINESS_CENTRAL- external_idNumber
The source entry's own identifier (BC
Entry_No)Example:
774521- occurred_atDate and time
The posting date the entry was booked on.
Example:
2026-08-05T00:00:00Z- customerText
The client the receivable is owed by.
Example:
7001- financial_periodText
The accounting period the entry falls in.
Example:
2026-08- amountDecimal number
The signed movement of the line.
Example:
245000- remainingDecimal number
The running balance still outstanding on the entry.
Example:
245000- due_dateDate
The date the receivable falls due.
Example:
2026-09-04
Optional
Present when the source system records them.
- document_numberText
The source customer document (invoice / credit memo) number.
Example:
PC-BWG-2025-001-07- document_typeText
The BC ledger document type (invoice / credit memo / payment / application)
Example:
Progress Claim- document_dateDate
The date of the customer document, distinct from posting.
- is_openTrue or false
Whether the entry is still open.
Example:
true- currencyText
The transaction currency of the amounts.
Example:
AUD- pmt_discount_dateDate
The settlement-discount date, if the customer's terms offer one.
- customer_nameText
The customer name as the source states it.
Example:
Central Highlands Regional Council
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "amount": 245000, "currency": "AUD", "customer": "7001", "customer_name": "Central Highlands Regional Council", "document_number": "PC-BWG-2025-001-07", "document_type": "Progress Claim", "due_date": "2026-09-04", "external_id": 774521, "financial_period": "2026-08", "is_open": true, "occurred_at": "2026-08-05T00:00:00Z", "remaining": 245000, "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.
https://docs.demiton.io/registers/receivable_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 keep current from them, on your data, in a 30-minute call.