Obligations
Review reporting duties, publish a version, and manage optional on-chain evidence for future filings.
Obligations lists your organisation's reporting duties and the published version used to generate each duty's filings. Use this page to review the version, publish a prepared draft, or manage optional chain anchoring. To see which filing period needs attention, open Filing calendar. To see attempts already made against those periods, open Filings.
Publishing freezes the draft as a numbered version. A period generated under that version keeps its reference after a later version is published. The Platform API supports creating and editing drafts and disabling obligations; the Console provides the publication confirmation and anchoring controls.
Steps
Review an obligation
Open "Reporting", then "Obligations". Each row shows the duty name and regime, its cadence when available, and a "Version" badge when a published version exists. "Disabled" marks an obligation that no longer produces new filing periods. "Anchored on chain" marks an obligation with anchoring enabled.
Screen equivalent: each row identifies a reporting duty and its current version. Available controls depend on the obligation's state and your role. The current Console also offers publication and chain anchoring controls.
Publish a reviewed draft
Select "Publish" on the obligation's row. The "Publish obligation?" dialog explains that publication freezes the draft as the next version and starts filing periods. Confirm "Publish" only after reviewing that draft. A refusal stays in the dialog with its reason; the list refreshes after the attempt.
Publication is unavailable on a disabled obligation. If the server refuses your role, ask an organisation owner or platform administrator to publish the draft.
Check the filing periods
Open Filing calendar and find the duty's name and regime. Its published version generates periods on its configured schedule. Read each period's urgency and EVM coverage badge to decide the next step.
Optional chain anchoring
Chain anchoring records a fulfilled filing's digest on the selected network. It lets a holder compare a supplied document with its on-chain record. Turning it off later stops new anchors; it does not remove existing records or reverse their disclosure.
To enable it, select "Turn on anchoring". Check "Chain", then choose the available severity for a missing anchor and a "Document type": "Regulatory filing" or "Investor report". Enter a short "Document label" that contains no organisation, period, or submission identifier. Record why you are enabling it, read the disclosure warning, and confirm that you understand its permanence before submitting.
The available severities depend on the obligation. When publication fulfils the duty, only "Warning" is offered so a missing anchor cannot block that publication. To stop anchoring, select "Turn off anchoring", enter the reason, and confirm. A disabled obligation can still have open filing periods, so its anchoring stop remains available when needed.
Troubleshooting
Publish is refused
Read the error in the confirmation dialog. Publication requires an organisation owner or platform administrator. The draft must be internally consistent, its holiday calendar must be visible to the organisation, and a maker-checker duty needs enough eligible approvers. Correct the stated cause before retrying.
A published version contains a mistake
Prepare and publish a corrected version. The earlier version remains unchanged so filings generated under it retain the rules that applied at the time.
An obligation was disabled by mistake
The Console has no control to re-enable it. Existing open periods continue; periods waiting to open become waived. Ask the platform operator to review the duty before creating a replacement through the API.
Turn on anchoring is missing
Confirm that the obligation is enabled, an EVM network is selected, and your account can manage reporting. A session in which an administrator impersonates another user cannot start a new disclosure. The emergency stop for existing anchoring has separate authorization checks.
An anchoring change is refused
Read the reason retained in the dialog. Check the selected chain, document label, and permitted severity before trying again. Do not remove the disclosure acknowledgement or change the label to conceal an identifier.
Related pages
Read Reporting Obligation for versioning, Filings for filing attempts and anchor follow-up, and Audit trail to investigate the actor and outcome of a publication or anchoring change.