BreezyCorp Handbook

Appearance

Onboard an XBRL client ​

Who does this: Platform Admin · Senior Accountant When: A client needs to start filing XBRL with ACRA through the platform. Result: Client has XBRL_FILING in enabledProducts, xbrlConfig populated, and the green Setup health gauge reflects XBRL readiness.

Before you start ​

  • [ ] Client record exists (with at least clientCode, legalName, timezone).
  • [ ] You know the client's UEN, accounting standard, and the applicable ACRA entry point + entity type.
  • [ ] You hold MANAGE_CLIENTS.

Steps ​

  1. Open Clients → client detail.
  2. Scroll to Enabled products and add XBRL_FILING.
  3. Switch to the XBRL Filing tab on the client detail page.
  4. Click Edit xbrlConfig. Fill the form:
    • UEN — Singapore Unique Entity Number (e.g. 202412345A)
    • Entity type — NON_LISTED_COMPANY_FULL for most private companies. Use SMALLER_NON_LISTED_COMPANY for entities meeting ACRA simplified-XBRL criteria. Other values: SGX_LISTED, MAS_LICENSED_BANK, MAS_LICENSED_INSURER.
    • Default entry point — FULL_XBRL for the common case. Use SIMPLIFIED_XBRL, FSH_BANKS, FSH_INSURANCE per ACRA guidance.
    • Accounting standard — SFRS, SFRS_SE, or IFRS.
    • Taxonomy version — acra_2026_v1 (the only version installed at v1.0 of this SOP). Future versions will appear as constitution files are added.
  5. Save.

How to know it worked ​

  • The client detail page's Setup health gauge for XBRL turns green.
  • A subsequent New filing call defaults the entry point, entity type, accounting standard, and taxonomy version from this config.
  • Activity log shows admin.client.xbrl_config_updated.

Sanity-check the taxonomy version ​

bash
node -e "console.log(require('@breezycorp/xbrl').loadTaxonomy('acra_2026_v1').elements.length)"
# expect 1871

If loadTaxonomy throws XbrlUnknownTaxonomyVersionError, the constitution file is missing — file an infra issue.

Internal use only — BreezyCorp