Reporting
See which reporting duty needs attention next, review filing attempts, check the published version each duty files under, and see who performed an operation.
Reporting covers two different jobs, spread across four pages. Filing calendar, Filings, and Obligations are the three faces of the first job: tracking the organisation's reporting obligationsA 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, the requirements a given regime imposes. Filing calendar ranks each duty's filing periods by urgency so you know what needs attention next, Filings shows the attempts made against those periods and their anchor state, and Obligations reports the published version each duty currently files under. The audit trailAn audit trail lets you show a regulator or an auditor who did what, under which role, without relying on the requester's own account of the request.Read the concept is the second job. It records who did what across the organisation and with what outcome; it is not scoped to reporting, so an obligation publish or disable lands here too, like everything else.
Any organisation member, Owner, Admin, or Member, can open all four pages: reading reporting data carries no extra role requirement. The Console lists filing periods, filing attempts, and their status. Obligations also lets an authorized operator publish a prepared draft and configure optional chain anchoring, while Filings lets an authorized operator download a stored artifact or resolve a failed anchor from the row it appears on. Creating or editing drafts, disabling obligations, and submitting filings use the Platform API. Obligation changes and restricted filing actions require the organisation's owner or a platform administrator.
Audit trail is the organisation's shared operational record, not scoped to reporting alone. Pages across the Console, from Data feeds to Admins & roles to Webhooks, point back to it as where their own changes land. Expect to arrive at Audit trail from another page's own troubleshooting section as often as you open it directly. The trail covers the last 30 days only, and it holds no before-and-after values, just that something happened, who did it, and the result; for a record's own field history, use that record's own owning page instead.
Find what you need
| What you need | Open | Why this one |
|---|---|---|
| What is due soon, ranked by urgency | Filing calendar | The only page in this group built around urgency: a duty with more than one open filing period can appear here more than once. |
| Which filing attempts exist and whether their anchors landed | Filings | One row per attempt, with the filing state, anchor state, artifact download when permitted, and follow-up controls for a failed anchor. |
| The published version a duty currently files under, or whether it is disabled | Obligations | One row per duty regardless of how many filing periods it has produced, Published version, disabled state, publication, and optional chain anchoring. |
| Who performed a specific operation and whether it succeeded | Audit trail | The only page in this group not scoped to reporting: it also covers sensitive reads, and a busy organisation only sees the oldest 200 rows in the 30-day window. |