Configure xbrlConfig for a client

Who does this: Platform Admin · Senior Accountant When: Onboarding a new XBRL client, or correcting an existing client's defaults. Result: Client.xbrlConfig populated; subsequent New filing calls default from it.

Required fields

Field	Format	Example
`uen`	ACRA UEN string	`202412345A`
`entityType`	`NON_LISTED_COMPANY_FULL` \| `SMALLER_NON_LISTED_COMPANY` \| `SGX_LISTED` \| `MAS_LICENSED_BANK` \| `MAS_LICENSED_INSURER`	`NON_LISTED_COMPANY_FULL`
`defaultEntryPoint`	`FULL_XBRL` \| `SIMPLIFIED_XBRL` \| `FSH_BANKS` \| `FSH_INSURANCE`	`FULL_XBRL`
`accountingStandard`	`SFRS` \| `SFRS_SE` \| `IFRS`	`SFRS`
`taxonomyVersion`	Constitution-installed version	`acra_2026_v1`

Steps

Web UI

Open Clients → client detail → XBRL Filing tab.
Click Edit xbrlConfig.
Fill; save.

API

http

PATCH /admin/clients/<clientId>/xbrl-config
Content-Type: application/json
Authorization: Bearer <admin-jwt>

{
  "uen": "202412345A",
  "entityType": "NON_LISTED_COMPANY_FULL",
  "defaultEntryPoint": "FULL_XBRL",
  "accountingStandard": "SFRS",
  "taxonomyVersion": "acra_2026_v1"
}

Validation

The handler asserts:

taxonomyVersion is loadable via loadTaxonomy(version) — unknown versions are rejected.
entityType and defaultEntryPoint are in their respective enum lists.

Editing `xbrlConfig` does not affect existing filings

xbrlConfig provides defaults at filing-creation time. Existing filings keep the values they were created with — including taxonomyVersion, which is pinned and immutable per filing.

Configure xbrlConfig for a client ​

Required fields ​

Steps ​

Web UI ​

API ​

Validation ​

Editing xbrlConfig does not affect existing filings ​

Related runbooks ​