Configure an organization and reporting entity

Who can perform the task

An authenticated user can create their first organization and becomes its administrator. Only administrators can later edit reporting-entity settings.

Operator-provisioned demo accounts are an exception: their organization and synthetic preset already exist, and the demo-only account cannot create another organization.

Before you begin

Have the approved legal or internal organization name, reporting-entity name, identifier and identifier type. For reporting defaults, obtain business type, financial year end, currencies, and approved exchange-rate source descriptions.

Quick path

1. Open Administration and create or select the organization.
2. Record the organization identity and reporting defaults.
3. Add the reporting entity using its verified legal identity and authority identifiers.
4. Configure jurisdiction, currency, reporting level, and other approved defaults.
5. Save the settings and verify them before creating a filing.

Detailed guidance

1. On Filings, use Create your organization when no workspace exists.
2. Enter the organization name, reporting-entity name, and identifier.
3. Select Create workspace.
4. From the organization card, select Reporting settings, or open Organization settings from the authenticated navigation menu.
5. Add reporting entities and manage ingestion service accounts on this dedicated administration screen. These durable controls are intentionally kept out of the filing-priority queue.
6. Open the relevant reporting entity, record the identifier type and reporting defaults, then save.
7. To add another reporting entity, confirm that the organization still has an available entity allowance under its billing plan.

Expected result

The organization card shows the entity. New filing cycles can use its saved defaults.

Reusable identity and reporting defaults are configured before filing creation.

An active prospect demo is clearly labelled with its versioned preset and exact expiry so the user can distinguish synthetic evaluation data from a production workspace.

How to verify

Reopen Organization settings and compare every identifier and default with the approved source. A saved default does not retroactively change an existing filing.

Common problems

• A banner identifies a demo workspace and its expiry. At expiry, access stops immediately and the page explains how to request an extension. The demo data remains preserved until an operator extends or removes the workspace.
• If the organization already exists, do not create a duplicate. Ask its administrator to add your account.
• If the entity identifier is uncertain, stop and resolve it before creating a filing.
• If the entity allowance is exhausted, creation and restore into that organization are refused. An administrator must move to a plan with a larger allowance or contact the operator about a Private Cloud allowance.

Audit and data consequences

Entity identity affects filing contexts and supported exports. Correct mistakes before filing creation where possible; later corrections may require recreating or formally reopening affected filings.

Product and regulatory limitations

SolvencyBridge does not verify an entered identifier against an authority register. Your organization owns that verification. Core includes two reporting entities and Group includes five. Private Cloud uses the entity allowance recorded for the annual contract.