How platform administrators manage rules, schemas and connectors
Use this guide in your Britixo workspace. Follow the Tax Compliance Administration workflow in Britixo to tform administrators manage rules, schemas and connectors.
Before you start
Required access: Platform compliance context and Manage compliance rules and schemas. The module must be enabled and its installed version ready for your workspace. Select the intended taxpayer, authority and period before changing a record.
How platform administrators manage rules, schemas and connectors
- Create a Draft rule pack for the exact authority/type/year/version with effective dates, official source and Rules JSON; require independent Verify.
- Register schema metadata including authority, return type, tax year, processing year, version, SHA-256, official source and production dates; require independent Verify.
- Create a gated connector with code, authority, protocol, version, environment, credential reference and non-secret configuration. Require Approve definition.
- Create capability release for the exact authority, tax type, return, filing method and years.
- Use Validate & apply to advance only controls whose prerequisites and evidence pass. Check the Authority capability matrix.
Controls and limits
- A new release starts in DISCOVERY; creating it does not enable preparation or filing.
- Connector approval, schema verification, certification, test filing, production filing, payment, amendments and status support are separate gates. Never place secrets in configuration notes or public help.
Check the result
Reopen the affected record and confirm the taxpayer, period, saved values and status. For external actions, inspect the actual authority acknowledgement or settlement evidence; a local saved or queued state is not acceptance.
If you cannot continue
Read the displayed validation or readiness message. Check the module version, role, source scope, authority, period and current approval evidence. If another person changed the record, refresh and review the current version. Give support the screen, error wording and correlation reference; keep passwords, one-time codes and tax identifiers out of public messages.