Administration
Permanently delete a filing
Apply the retention decision carefully and verify the non-sensitive deletion record.
Who can perform the task
Only an organization administrator can use the filing deletion control.
Before you begin
Obtain an approved retention or deletion decision. Confirm the organization, reporting entity, period, filing status, submission obligations, litigation or audit holds, and the identity of any required backup. Verify that deleting the filing will not remove evidence your organization must retain.
Quick path
- Confirm that retention, legal-hold, export, and approval requirements permit deletion.
- Open the filing administration controls and select Delete filing.
- Review the exact filing identity and the data that will be removed.
- Enter the required reason and confirm the permanent deletion.
- Verify that the filing is gone and that the value-safe deletion record remains available.
Detailed guidance
- On Filings, find the exact entity and period in Operational filing overview, then expand Permanently delete filing. You can alternatively open the filing and use the same control under Review and audit.
- Create and verify an encrypted portable bundle only when policy authorizes retaining one.
- Read the consequence text next to the control.
- Select the acknowledgement that the deletion is permanent and cannot be undone in the application.
- Enter a specific deletion reason of 10 to 500 characters.
- Select Permanently delete filing only after checking both entries.
Expected result
The filing values, comments, audit events, attachments, and exports are permanently removed from the active product data. A non-sensitive tombstone remains to record that the deletion occurred.
How to verify
Return to Filings and confirm the filing is unavailable. An authorized operator can verify the tombstone without reconstructing deleted customer content. Record completion in the organization’s retention register.
Common problems
- The action remains unavailable until you acknowledge that deletion is permanent and enter a reason of at least 10 characters.
- A vague, short, or excessively long reason is rejected.
- A portable bundle retained before deletion still contains filing data and must follow the same retention decision.
- Deleting a filing does not withdraw an artifact already submitted to an external authority.
Audit, locking, and data consequences
Deletion is destructive and is not reversible in the application. Normal database or infrastructure recovery is governed by the deployment’s backup policy and must not be treated as an end-user undo function. Never delete a filing merely to correct it; use the correction or authorized reopen workflow.
Product and regulatory limitations
SolvencyBridge cannot determine the applicable statutory, contractual, audit, or litigation retention period. Your organization must approve the decision before the product action.