ASIC record status, charge and other code tables

Several small ASIC code tables appear throughout company records without belonging to any one section. The record status table tells you whether a fact is current, ceased or future dated, and it is attached to almost every dated record: office holders, addresses, share classes, members and licences. The charge tables describe the security interests ASIC held before the Personal Property Securities Register took over in 2012. The organisation number type table explains whether a nine-digit identifier is an ACN, ARBN or ARSN. Finally, ASIC's statutory fee codes are the reason each purchase and order response carries a product, and this page maps the two together.

Where it appears in the API

• status on officeholder, address, shareClass, shareholding, licence and role objects uses the record status table.
• charge.type (the charge types table) and charge.status (the charge statuses table) from GET /v1/companies/{id}/charges, which reads a purchased historical extract, and GET /v1/charges/{chargeNumber}.
• numberType on every company summary, company object and organisation party uses the number types table.
• meta.product appears on purchase and order POST responses only and corresponds to an ASIC fee code from the ASIC fee codes table. Section GET responses carry "billable": false and "product": null; see purchasing.
• the information products table names the ASIC information products that asicapi's endpoints are built on.

Record status

Within each role or address type, ASIC orders C records first, then E records in reverse chronological order of ceasing.

Charge types

A fixed charge (X) attaches to specific assets such as land or plant. A floating charge (F) hovers over a changing pool of assets such as stock and receivables and crystallises on default. Most bank securities over a company were both (B).

Charge statuses

Since 30 January 2012 current security interests are registered on the Personal Property Securities Register (PPSR), not with ASIC. ASIC's register now holds only satisfied charges (SATF), plus charges marked deleted (DELT) because they were lodged in error or migrated. Charges appear in the historical extract only: GET /v1/companies/{id}/charges reads the historical extract you hold, defaults to status=satisfied, and returns extract_required (HTTP 402) when you hold no historical extract. An image-based charges extract order for a company with no charges on record returns no_charges (HTTP 404). See charges.

Organisation number types

ASIC's own table uses the digits 1 to 4 for these headings; asicapi returns the abbreviations, and the original digit is shown in the ASIC code column of the table above.

All three nine-digit identifiers share the same check digit algorithm. The GET /v1/identifiers/{value} endpoint validates any of them and an ABN. See ACN, ABN, ARBN and ARSN.

Information products

ASIC groups its public information service into six products. Access to each is enabled per jurisdiction on your account, and product_not_enabled (HTTP 403) means the product behind an endpoint is switched off for your key. A different error, extract_required (HTTP 402), means the product is enabled but you have not yet purchased the extract that a section endpoint reads from; its details.purchase names the POST to make.

Name searches, document lists, document details and POST /v1/weekly-summaries are part of the base service and are not listed separately.

ASIC billing charge codes

These are ASIC's statutory fee item codes. Each purchase or order response identifies the product that was consumed in meta.product, and your invoice groups charges by the underlying ASIC code. Only the POST purchase and order endpoints listed here are billable; every GET reads what you already hold and reports "billable": false. The mapping is fixed:

The 955F to 955K codes are legacy items for register extracts that ASIC has since consolidated under the 959 series. Sandbox purchases succeed with "billable": false and never generate an ASIC fee. See purchasing for the three tiers of free lookups, purchased extracts and asynchronous orders, and requests and responses for the full meta object.

Related