Filings
Review filing attempts, their anchor state, and the restricted actions available for one attempt.
Filings lists the attempts your organisation has made to discharge reporting duties. Each row is one submission against a filing period, not the duty itself. Use this page after Filing calendar tells you a period is due.
Any organisation member can open Filings and read the attempt state and anchor state. The page keeps the restricted work on the row: artifact download, anchoring retry, and accepting a failed anchor are available only when your role and the filing state allow them. A filing artifact can contain holder-level personal data, so downloading one is narrower than reading the row.
Reading the list changes no filing or asset state. Downloading an artifact is a sensitive read and creates its own audit entry. Re-running or accepting a failed anchor is a follow-up action on the filing attempt, so confirm the filing and anchor state before you choose either control.
Steps
Open Filings
Open "Reporting", then "Filings". Rows with matched filing period data are ordered by newest due date first; a filing whose period could not be loaded stays visible at the end of the list. The page shows up to the 200 most recently created attempts, and says how many of the total it shows when there are more.
Read the filing row
Read the duty name, regime, fiscal period, attempt number, due date, filing state, and anchor state. If the page could not load the matching period, the row still appears and reads "Filing period not loaded", the due date reads "No deadline on record", and the regime and fiscal period stay empty.
Use a row action when one appears
Select "Download" to get one link for each stored artifact part. Each link is valid for 15 minutes. "Download" stays disabled when no artifact exists, and an erased filing shows a notice instead of links. Select "Anchor again" to retry the anchor of a discharged filing whose anchor state is Failed. Select "Accept the missing anchor" to record why your organisation accepts that the filing will not be anchored; "Accept" stays disabled until you enter a reason.
Match the anchor state to the next step
| Anchor state | What it means | What to do |
|---|---|---|
| Not requested | No anchor result is recorded for this filing. This is the default, and it stays after an anchor run is refused, for example because the filing is not yet discharged or anchoring is off. | If you expected an anchor, check the duty's anchoring setting in Obligations. |
| Still running | An anchoring attempt started and has not recorded a result. | Only a later anchoring attempt changes this state. The page offers no control while it lasts. |
| Confirmed | The filing's anchor landed. | Use the row as evidence that the attempt has an anchor. |
| Failed | The anchor did not confirm. The state stays Failed after someone accepts the missing anchor. | On a discharged filing, an owner or platform administrator can select "Anchor again". Either can select "Accept the missing anchor" and record why; the platform accepts it only once. |
Troubleshooting
No filings appear
The Console shows "No filings yet" when no filing period in this organisation has produced an attempt. Check Filing calendar for generated periods and Obligations for whether the duty has a published version.
The duty name or deadline is missing
The page still lists the filing attempt when the matching period could not load, and shows a "Deadlines unavailable" notice. Refresh the page to try again; the attempt itself is still present.
Download is unavailable
A stored artifact must exist, and your account must be an organisation owner or platform administrator. Ask one of those users to download the artifact, or read the filing state and anchor state without the bytes.
The action was refused
A member does not see these controls. An organisation Admin sees them, but the platform refuses the request: only an organisation owner or a platform administrator can download an artifact, retry an anchor, or accept a missing anchor.
Anchor again is unavailable
The Console offers "Anchor again" only on a discharged filing, one that is Acknowledged or Published, whose anchor state is Failed. Before discharge, the filing's artifact can still be regenerated.
Related pages
Use Filing calendar to decide which period needs attention, Obligations to review the duty's published version and anchoring setting, and Audit trail to investigate who took a reporting action.