Skip to content

Create an XBRL filing ​

Who does this: XBRL Preparer · XBRL Reviewer · Senior Accountant · Platform Admin When: A client's financial statements for a period are ready to be filed with ACRA in XBRL format. Result: An XbrlFiling row in DRAFT with a pinned taxonomyVersion. URL settles to /dashboard/xbrl/<filingId>.

The taxonomyVersion is pinned at create time and immutable thereafter. A future ACRA taxonomy release lands as a side-by-side constitution file; in-flight filings continue against their pinned version.

Before you start ​

  • [ ] Client has XBRL_FILING in enabledProducts and xbrlConfig populated (see Onboard an XBRL client).
  • [ ] You hold MANAGE_XBRL_FILING.

Steps ​

  1. Sidebar → XBRL Filings → New filing.
  2. Pick the client.
  3. Fill:
    • Period start / end — YYYY-MM-DD. Start < end.
    • Entry point — defaults from xbrlConfig.defaultEntryPoint.
    • Entity type — defaults from xbrlConfig.entityType.
    • Accounting standard — defaults from xbrlConfig.accountingStandard.
    • Taxonomy version — defaults from xbrlConfig.taxonomyVersion. Pinned at submit.
    • (Optional) FS engagement — only if you intend to pull line items from a FsGeneratedStatement later. Both must share clientId.
  4. Submit. Filing opens at DRAFT.

How to know it worked ​

  1. Filing appears at the top of the XBRL Filings list with status DRAFT.
  2. Activity log shows xbrl.filing.created with pinned taxonomyVersion.
  3. Upload source document CTA is enabled.

Common situations ​

If you see…It means…What to do
400 reason: "unknown_taxonomy_version"The version is not installed in the constitutionVerify with loadTaxonomy('<version>'). Coordinate with infra to add the constitution file
400 "Client does not have XBRL_FILING enabled"Client master was not opted into the XBRL moduleOnboard the client (see Onboard)
Default values don't match expectationxbrlConfig on the client is wrongEdit xbrlConfig (see Configure); existing filings unaffected

Internal use only — BreezyCorp