X-08 · Archive filing

SOP: SOP_XBRL_Filing.md §6 / Step 8.0 (FILED → ARCHIVED)Actors: XBRL Reviewer or Platform Admin — MANAGE_XBRL_FILING. Pre-state: Filing at FILED. Post-state: Filing at ARCHIVED — terminal state, read-only. Retention policy applies.

0. Prerequisites

• Filing at FILED (see X-07).

1. Steps

POST /ops/xbrl/filings/<filingId>/archive
Authorization: Bearer <xbrl-reviewer-jwt>

(Or click Archive on the filing detail page.)

The handler:

1. Asserts MANAGE_XBRL_FILING.
2. Asserts filing is at FILED.
3. Transitions filing FILED → ARCHIVED.
4. Emits AuditEvent xbrl.filing.archived.

2. Verification

Database

SELECT status FROM xbrl_filings WHERE id = '<filingId>';
-- expect 'ARCHIVED'

Audit log

Event type	Notes
xbrl.filing.archived	actor + timestamp

3. Negative & edge cases

• Archive from EXPORTED — refused; mark filed first. The platform deliberately requires a regulator reference before an archive can seal the filing.
• Re-open an archived filing — not supported in code; the FSM has no transition out of ARCHIVED. If the client genuinely needs to amend, create a new filing for the same period with a different taxonomyVersion (if applicable) or as a re-filing with a documented reason in the activity log.
• Retention purge — out of scope for this flow. The retention job purges bytes after the configured window; audit metadata is retained.

Next

End of the XBRL filing lifecycle. For the upstream engagement, see the Financial Statements userflows.