Filing calendar
Review the organisation's filing periods and each one's urgency.
Filing calendar lists your organisation's filing periods, one open window in the life of a reporting obligationA reporting obligation lets your organisation prove to a regulator which rules governed a filing, and keeps that proof fixed even after the duty changes.Read the concept, ranked by urgency so the most time-sensitive one surfaces first. A quarterly obligation produces a new period each quarter, so the same duty can show more than one row here at different urgencies. This page decides what needs attention next; it does not decide what an obligation requires, which version it currently files under, or whether it is disabled, all of which live on Obligations. Reach for this page when you want that single, ranked view across every reporting duty; open Obligations to review or publish the duty's prepared draft.
Any organisation member, Owner, Admin, or Member, can open this page: reading reporting data carries no extra role requirement. The Console has no screen, here or anywhere else, to submit a filing or approve one; the Platform API does, through its own submit, approve, acknowledge, and publish endpoints.
Each row's urgency badge is derived from the period's own state and how close its deadline is, together, never from either alone. A period already fulfilled never reads as due soon no matter how close that deadline was, and one already overdue stays overdue even once its window has passed. The full set of values, and what each one asks of you, follows the steps below.
Reading the calendar changes no filing or asset state.
Steps
Open Filing calendar
Open "Reporting", then "Filing calendar". Each row is one filing period, a single cycle's window for a reporting obligation, not the obligation itself, so a duty that repeats can show more than one row here at different urgencies. The fiscal period next to the regime, for example mica · 2026-Q2, is what tells those rows apart.
Screen equivalent: each row names the obligation, its regime and fiscal period, for example mica · 2026-Q2, shows its due date and time, and stacks chain family coverage badges above an urgency badge.
Read the urgency badge
Read the badge at the end of each row, one of seven values from Overdue to Waived; see Match the badge to what it means below for what each one asks of you. The list is already sorted by that value, most at risk first, so the row nearest the top is the one to act on first regardless of its deadline date.
Check chain family coverage
Read the EVM coverage badge above the urgency badge when the period claims EVM coverage. Covered means the platform confirmed reporting data for that family. Pending means nothing has been generated for the period yet. Unconfirmed means a submission exists but recorded no coverage for that family, with one reason given underneath. Refused means the submission could not produce valid data for that family. The listed reasons explain why. This verdict does not block review, approval, acknowledgement, or publication. A later submission for the same period can produce a different verdict. A family the period never claimed shows no badge here at all.
Continue to Obligations
Note the row's obligation name and regime, then open "Obligations" and scan its list, which carries no search or filter, for the same name to see its published version, ownership, and whether it is disabled. Open "Filings" when you need the attempts already made for a period. Filing calendar tells you what is urgent; Obligations tells you what governs it.
Match the badge to what it means
A row's urgency badge holds one of seven values. The list itself is sorted in this same order, the most at risk first.
| Badge | What it means | What to do |
|---|---|---|
| Overdue | The deadline has passed. This also covers a period whose own record has not yet caught up to reflect it; a late deadline never reads as Open or Waiting for finality. | Treat the duty as late. Open Obligations to confirm the published version that applies, then follow your organisation's process to file it. |
| Due soon | The deadline falls within the next five days and the period is not waiting on chain finality. | Prioritise this duty ahead of any row ranked below it. |
| Open | The period has started and its deadline is more than five days away. | Prepare the filing according to your organisation's process; higher-ranked rows have more urgent deadlines. |
| Waiting for finality | The period needs a chain finality confirmation before it can open, and keeps this badge even inside the five-day window until that confirmation lands. | Nothing to do here; the period opens once finality confirms, not on a fixed date you can move by acting sooner. |
| Scheduled | The period exists and will open when its window begins, more than five days from now. | Nothing to do yet. |
| Fulfilled | The duty has been discharged for this period. | Nothing further; its deadline no longer applies. |
| Waived | The obligation that produced this period was disabled before the period opened, so it closes with no duty to fulfil. | Nothing further; this period carries no outstanding duty. |
Troubleshooting
A duty you expect is missing
Filing calendar and Obligations read the same catalog, but a period only appears here once its obligation has a published version; a draft obligation produces no periods yet. Confirm you selected the organisation that owns it, then check Obligations for whether a version has been published.
The page will not open
Filing calendar needs an active organisation. Select one before you open "Reporting".
The list says the calendar is unavailable
The Console shows "Filing calendar unavailable" when the complete list could not load. Refresh the page to try again.
Filing calendar shows no rows
The Console shows "No filing periods yet" when no obligation in this organisation has a published version. Publish one on Obligations and its periods appear here on schedule.
Frequently asked questions
Does Filing calendar show every filing period, or only current ones?
Every one your organisation has. The page carries no date filter and no separate archive, unlike Audit trail's fixed 30-day window, so a period keeps its row for as long as it exists, including one already fulfilled or waived long ago. An organisation with many obligations and a long history sees its list grow accordingly; nothing here expires on its own.
Who can publish or disable an obligation?
Any role can read this page. Publishing or disabling an obligation requires the organisation's Owner role or a platform administrator. Publish a prepared draft on Obligations; use the Platform API to disable the duty.