Configure the reporting authority profile - SolvencyBridge Help
Dieser Artikel fehlt auf Deutsch, ist veraltet oder wurde noch nicht geprüft. Die maßgebliche englische Quelle wird angezeigt.
Administration
Configure the reporting authority profile
Record jurisdiction-specific identity and reporting-level settings before creating a filing.
Version 2026.8.15 minAdministratorGeprüft 2026-07-29
Who can perform the task
Organization administrators.
Before you begin
Obtain the approved authority profile, registered name, authority identifier, source reference, observation date, and default reporting level. If a product administrator has activated an EIOPA register snapshot, you can use an exact LEI or national identification code to reduce retyping. Some jurisdictions request an additional registration, depositor, or undertaking number.
Quick path
Open Administration and select the reporting organization and entity.
Confirm the jurisdiction, authority, undertaking identity, and reporting level against approved records.
Enter the authority-specific identifiers and defaults without changing source-issued values.
Save the profile and resolve any missing or conflicting identity fields.
Create or reopen a filing and verify that it uses the expected authority profile.
Detailed guidance
On Filings, expand the reporting entity settings.
Optionally search the selected profile's official national company register, the active EIOPA register by an exact LEI or national identification code, or GLEIF by an exact or statistically similar legal name. When an approved national API connector is not active, the product links to the configured official search instead of scraping or guessing a result.
Review the official name, identifiers, home country, NCA, attribution, source publication, and source limitation. For a GLEIF result, also review the legal jurisdiction, entity status, and LEI registration status. A similar-name result is not proof of identity. A result has not changed the entity yet.
Select Apply suggestions or Apply this entity only when the displayed identity is the intended undertaking. The suggested registered name, country, legal address where available, LEI, national identifier, authority, source checksum, and retrieval date are copied into the editable form. This still does not save the entity.
Confirm or correct every field, choose the authority profile, and complete any profile-specific fields shown.
Cite the competent-authority register, correspondence, or approved internal record when it differs from or supplements the EIOPA snapshot.
Save, then reopen the settings. Saving retains the accepted fields, exact GLEIF source record or EIOPA publication reference, source checksum, and attributable administrator decision.
When checking the entity later, run the exact source lookup again. If the retained identity differs from the latest record, review the source-change warning. The refresh creates a review item; it does not rewrite the saved entity or any existing filing.
An official national-register match remains a proposal until you select it and save. Saving retains the exact provider, source URL, observation time, response checksum, accepted fields, administrator, and decision time.
Structured national forms can reuse approved filing and entity context such as the period end, registered name, and national identifier. These are defaults, not locked values: an existing form value or a preparer's explicit edit always wins. Verify inherited values against the applicable authority instructions before export.
Expected result
The authority profile is available when a filing cycle is created and its jurisdiction-specific controls can be configured.
How to verify
Compare the saved values with the source reference. Confirm reporting level explicitly; do not infer it from the organization name or register result. Confirm that the retained EIOPA publication identity or exact GLEIF response checksum refers to the result you reviewed. A later source-change warning must leave the accepted identity unchanged until an administrator explicitly applies and saves a new selection.
Common problems
If no active snapshot is available, ask a product administrator to stage and activate one or verify the entity manually. A missing exact match is not proof that an undertaking is unauthorized or has no LEI. Never treat statistical name similarity as an accepted identity. Review a lapsed, retired, duplicate, transfer-pending, annulled, merged, inactive, or otherwise non-current GLEIF status before use. An ambiguous identifier must be resolved in the applicable national competent-authority register. Do not reuse one authority’s registration number in a different profile.
Audit and data consequences
Authority identity can affect export contexts, filenames, forms, and readiness checks. Changing entity settings does not prove an existing filing was refreshed; verify the filing itself.
Product and regulatory limitations
EIOPA, GLEIF, and national company-register data are reviewable suggestions, not authority certification and not automatic applicability decisions. EIOPA states that the applicable national competent-authority register prevails if it differs. National connectors are enabled only where the official source and deployment configuration support a bounded exact lookup; all other profiles retain an explicit official-search route. Profile availability describes implemented product behavior. See the support matrix and the limitations shown near the affected export.