Customer list (v2)
Customer list is one of Demiton's published registers for Australian civil construction. Customers registered in your ERP. 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
customer_listUse 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
- v2 (2.0.1)Superseded by v3.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- A New Tax System (Australian Business Number) Act 1999ABN and the Australian Business Register (ABN Lookup)
- A New Tax System (Goods and Services Tax) Act 1999 - tax invoice requirementsGST tax invoice particulars (ATO tax invoice guidance)
- PINT A-NZ Billing BISPeppol PINT A-NZ Billing BIS (Australia and New Zealand)
- Privacy Act 1988Privacy Act 1988 - Australian Privacy Principles
- Council Directive 2006/112/EC (VAT Directive)Common system of value added tax - invoice particulars
- EN 16931-1:2017Electronic invoicing - Part 1: Semantic data model of the core elements of an electronic invoice
- GDPRGeneral Data Protection Regulation
- Peppol BIS Billing 3.0Peppol BIS Billing 3.0 (CIUS of EN 16931)
- Goods and Services Tax Act 1985 (NZ) - taxable supply informationGST taxable supply information (Inland Revenue guidance, in force 2023-04-01)
- New Zealand Business Number Act 2016NZBN Act 2016 and the NZBN Register
- Privacy Act 2020 (NZ)Privacy Act 2020 - Information Privacy Principles
- UK GDPRUK General Data Protection Regulation with Data Protection Act 2018
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.
- HammerTechPartial
- MapTrackPartial
- MYOB Acumatica
- MYOB BusinessPartial
- Oracle Aconex
- PayappsPartial
- ProcorePartial
- Xero Accounting
Fields
26 fields: 1 required, 20 optional, 5 defined by each organisation.
Required
Every record carries these fields.
- customer_entity_idWhole number
Demiton canonical CUSTOMER spine node this fact is about.
Example:
7001
Optional
Present when the source system records them.
- cityText
Locality.
Example:
Emerald- nameText
Registered/trading name of the customer party.
Example:
Central Highlands Regional Council- emailText
Customer contact email.
- phoneText
Customer contact phone.
- statejurisdiction
State/territory code.
Example:
QLD- blockedText
Source's blocked/credit-hold status for the customer.
- websiteText
Customer website / domain.
- tax_liableTrue or false
Whether the customer is taxable in the source's tax setup.
Example:
true- modified_atDate and time
Source last-modified timestamp (freshness)
- postal_codeText
Postal code.
- country_codejurisdiction
Customer's country.
Example:
AU- credit_limitNumber
Credit limit the tenant extends to this customer.
- customer_typeText
The source's customer type (e.g. person/company distinction)
- address_line_1Text
Street address line 1.
- address_line_2Text
Street address line 2.
- customer_numberText
The customer account code that joins this record to AR transactions across systems.
Example:
CUST-7001- source_external_idText
The raw record id in the producing system.
- default_currency_codecurrency
The customer's default transaction currency.
- tax_area_display_nameText
Human label of the source's tax area.
- tax_registration_numberText
The customer's ABN / GST / VAT identifier.
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- salesperson_codeText
Tenant's internal salesperson code for this customer.
- tax_area_referenceText
Source id of the tenant-configured tax area row.
- payment_terms_referenceText
Source id of the tenant-configured payment-terms row.
- payment_method_referenceText
Source id of the tenant-configured payment-method row.
- shipment_method_referenceText
Source id of the tenant-configured shipment-method row.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "city": "Emerald", "country_code": "AU", "currency": "AUD", "customer_entity_id": 7001, "customer_number": "CUST-7001", "name": "Central Highlands Regional Council", "source_system": "D365_BUSINESS_CENTRAL", "state": "QLD", "tax_liable": true}Version history
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/customer_list/v2.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.