What SolvencyBridge does and does not do

Who should read this

Everyone who prepares, reviews, approves, exports, or records the submission of a filing.

What the product does

SolvencyBridge provides a controlled workspace for configuring reporting entities and filing cycles, deciding template applicability, importing and entering values, running implemented validations, recording evidence and comments, managing review, locking approved values, and generating supported artifacts. It records important actions in the filing audit history.

What the product does not do

• It does not give legal or regulatory advice.
• It does not decide whether your organization is required to file a template.
• It does not prove that every applicable authority rule has been implemented.
• It does not submit an artifact merely by generating or downloading it.
• It does not prove receipt or acceptance unless evidence from the external authority process is recorded and verified.
• It does not recover an encrypted portable bundle if its passphrase is lost.

Before you rely on a result

Confirm the reporting entity, period, reporting level, taxonomy version, jurisdiction profile, applicability decisions, validation-coverage information, and artifact type. Follow your organization’s approved authority-portal procedure outside SolvencyBridge.

Expected result

Users treat SolvencyBridge as a preparation and evidence workspace. They distinguish a product validation result from regulatory completeness, and distinguish export, submission, receipt, and acceptance.

How to verify

Open the filing and check its identity, status, taxonomy, jurisdiction, validation summary, audit history, and artifact details. Compare any submission outcome with evidence obtained from the authority channel.

Common problem

“The file exported successfully, so has it been accepted?” No. Successful export means that SolvencyBridge generated the stated artifact. Continue with export, submission, and acceptance.

Consequences and limitations

Using the wrong entity, period, taxonomy, applicability decision, or authority procedure can produce an unsuitable filing even when product checks pass. Regulatory responsibility remains with your organization.