Zero-Plaintext Gateway Credentials
By design, HMRC Government Gateway passwords and Companies House 6-character authentication codes are never stored in plaintext logs, never displayed to support staff, and are purged immediately after submission transmission.
Encryption in Transit & at Rest
All browser, API, and UK government gateway communications enforce TLS 1.2/1.3. Archived statutory PDFs, iXBRL packages, and audit records are encrypted at rest using AES-256.
At-Most-Once Submission Boundaries
Every Companies House and HMRC filing leg persists an immutable boundary timestamp prior to transmission release, preventing accidental duplicate returns on network retries or timeouts.
Cryptographic Integrity (IRmark)
CT600 XML envelopes compute canonicalised SHA-1 Base64 IRmark fingerprints prior to HMRC transmission and retain immutable SHA-256 document hashes for every filed artifact.
1. Pre-Submission XBRL & Schema Validation
By design, prior to reaching any UK government endpoint, AlderTax checks every generated annual accounts file and tax computation locally against official Financial Reporting Council (FRC) and HMRC taxonomies using Arelle. Submissions that fail structural, calculation linkbase, or business rule checks are blocked before transmission.
2. Tenant Isolation & Access Controls
- Strict Organisation Isolation: Every company, accounting period, filing draft, and archived document is scoped to an authenticated organisation ID with role-based access control (Owner, Admin, Preparer, Viewer).
- API Key Hygiene: Practice API keys are stored solely as salted cryptographic hashes. Separate sandbox (
sk_test_) and live (sk_live_) environments prevent accidental production submissions during integration testing. - Automated Log Redaction: Application logs and diagnostic payloads automatically redact Unique Taxpayer References (UTR), Government Gateway credentials, authentication codes, and session tokens.
3. Gateway Onboarding Status
4. Responsible Security Disclosure
If you identify a potential security vulnerability or compliance concern, please contact our engineering security team directly at [email protected]. We acknowledge reports within 2 business days.