Automated MTD Filing for Scale.
MTD for Income Tax multiplies your filing frequency. It should not multiply your headcount. Qgentic MTD runs high volumes with per-client data isolation, computations taken from the records you already keep, mandatory approval workflows, and an audit trail behind every submitted figure.
Volume-based licensing. Unified engine for VAT and Income Tax. Single-entity configurations available.
End-to-End Submission Workflow
Review a complete execution cycle: automated data ingestion, programmatic Box 3 and 5 computation, manual approval gating, and the generation of an HMRC-compliant return complete with necessary fraud-prevention headers and cryptographic hashes.
Review integration capabilities: Architecture & Data Ingestion →
Managing Compliance Volume
Quarterly reporting significantly increases submission volumes. Qgentic addresses this through automation, replacing manual data entry with scalable, system-driven workflows.
Volume Processing
Transition from annual submissions to continuous quarterly updates and final declarations without linear increases in manual processing time.
Digital Link Integrity
Eliminate manual data re-keying, preserving the mandatory digital link from source records to the final HMRC submission.
Auditable Declarations
Ensure every submission is backed by cryptographic evidence, providing irrefutable proof of review and approval for each declaration.
Secure Bulk Processing
Strict multi-tenant architecture: every entity gets its own data boundary and its own audit trail. Isolation does not slow the portfolio — one platform's cycle starts for a set of clients in a single action, from the practice cockpit or the API, with segregation of duties and per-entity approval records intact.
The practice cockpit is one sign-in over the whole book: a client roster ordered by what needs a person first, a deadline board spanning every client at 30, 60 or 90 days, and batch runs. Opening a client switches the console into that tenancy, and each run still stops at that client's own approval gate.
Licensing is based on active entities rather than user seats, aligning costs with operational scale. Refer to pricing for details.
Extensible MTD Framework
One engine carries every MTD mandate, current and future. Connectors, validation rules and audit trails share one architecture, so a new reporting regime is an addition, not a rebuild.
MTD for VAT
Automated generation of the nine-box VAT return. Features software-calculated Box 3 and Box 5 totals, VRN modulus-97 validation, and strict numerical precision rules, all executed prior to manual approval.
MTD for Income Tax (ITSA)
Full ITSA coverage: quarterly updates for self-employment and property income, HMRC tax calculation retrieval, and final year-end declarations — validated directly against HMRC's own data. Registration is open for the next filing cycle.
Construction Industry Scheme (CIS)
The CIS300 contractor monthly return. Every subcontractor's deduction is computed by the software — 0%, 20% or 30% of the payment after materials — with UTR checksums, HMRC verification numbers reconciled against the payment status, nil returns and inactivity, and the 19th-of-the-month deadline on the same calendar as your VAT and Income Tax dates. Prepared and validated behind a named approval; filed through HMRC's CIS online service.
Core infrastructure components (HMRC connectivity, audit logging, evidence portals) are provisioned once and shared across all active compliance modules. CIS is not itself an MTD regime — HMRC has not digitised it under that programme — but it is the same client, the same ledger and the same practice workflow, so it runs on the same engine. Income Tax registrations begin with a shadow quarter: HMRC paused production access for new Income Tax filing software in August 2026 pending a controlled access model, and will publish future onboarding arrangements by the end of September 2026.
System-Agnostic Data Ingestion
Data ingestion is achieved through configurable connectors, preserving digital links without requiring dedicated ERP tax modules or complex integration development.
Native Reporting Modules
Connect directly via REST APIs to systems like SAP (DRC), Oracle Fusion, or Dynamics 365. Data extraction is fully automated and system-to-system.
Automated File Transfer
Use the ERP reporting you already have (SAP AL11, for example). Your middleware — MuleSoft, Boomi, SAP CPI — drops JSON or CSV into a secure ingestion directory. That is the whole integration.
Scheduled File Drops
Supports scheduled CSV exports from mid-market systems (Sage, NetSuite, Xero). The filesystem connector automatically detects and processes new files while maintaining audit records.
All integration paths preserve an unbroken digital link. Any manual overrides required during the process trigger explicit compliance warnings (MTD-DL-007) prior to submission.
Universal ERP Support
The platform is engineered to be ERP-agnostic, interpreting standard summary exports (VAT or ITSA data) from any system via API or secure file transfer, eliminating the need for custom, platform-specific development.
Tier 1 ERPs
SAP, Oracle Fusion & EBS, Dynamics 365 F&O, Infor, Unit4, IFS, Workday, Epicor.
Tier 2 ERPs
NetSuite, Dynamics 365 Business Central, Sage Intacct/X3/200, SAP ByDesign, Access Group.
Accounting Systems
Sage 50, Xero, QuickBooks, FreeAgent, Zoho, IRIS. Fully supports batch processing for portfolio management.
Any system capable of exporting financial summaries is compatible. Initial data mapping is executed during deployment. Note: Direct API submission to HMRC is enabled per-tenant upon completion of HMRC enrolment; manual filing via existing channels remains supported during the transition.
Automated Processing Pipeline
- Ingestion & NormalisationData is securely ingested (JSON/CSV). Identifiers like VRNs are standardised before processing begins.
- ComputationDerived values (e.g., Box 3 and 5 for VAT) are computed by the software, preserving the digital link; conflicting upstream totals are rejected.
- ValidationData passes through deterministic rule gates (e.g., modulus-97 VRN checks, precision requirements, negative value constraints) enforcing structural and logical integrity.
- Authorisation & ExportA designated user approves the final data. The system generates the exact HMRC-compliant payload, including mandatory fraud-prevention headers, secured by a cryptographic hash.
ITSA processing follows the same sequence: aggregating quarterly data, validating against rulesets, and finalising year-end declarations against HMRC data, all within the identical approval and audit framework.
Deterministic Validation Guarantees
| System Control | Purpose |
|---|---|
| Modulus-97 Checksums | Prevents submission of invalid VAT Registration Numbers (VRNs). |
| Algorithmic Totals | Ensures derived boxes (3 & 5) mathematically match inputs, rejecting discrepancies. |
| Format Enforcement | Strict validation of precision rules, signs, and period keys. |
| Cryptographic Auditing | Maintains a hash-chained log of all actions, approvals, and generated artifacts. |
The MTD pipeline is entirely deterministic; no probabilistic AI models are involved in data processing or validation.
Final Submission Artifacts
HMRC-Compliant Payloads
Generates the precise JSON payload required for HMRC endpoints, accompanied by a SHA-256 hash and all mandatory Gov-* fraud-prevention headers derived from real operational data.
Filing to HMRC
Returns file to HMRC through the MTD API using the client's own Government Gateway authorisation — a one-time step at onboarding. (HMRC software directory listing is currently pending.) Shadow mode runs the pipeline in parallel with your current process until you switch filing over.
Automated Deadline Tracking
The console maintains a real-time calendar of statutory obligations, synced directly with HMRC API data. Automated alerts are configurable and submissions are pre-staged pending final human approval.
| Obligation | Period | Due | Status |
|---|---|---|---|
| VAT Return | 1 Jul → 30 Sep | 7 Nov 2026 | Due in 86 days |
| ITSA — Q2 Update | 6 Jul → 5 Oct | 7 Nov 2026 | Due in 86 days |
| VAT Return | 1 Oct → 31 Dec | 7 Feb 2027 | On Track |
| ITSA — Final Declaration | 6 Apr '26 → 5 Apr '27 | 31 Jan 2028 | On Track |
Notification schedules (14, 7, and 1 day prior) are fully configurable by administrators.
Per Income Tax taxpayer for a practice; per VAT registration for a business.
Practice — Growth
Four quarterly updates per income source, HMRC's tax calculation and the year-end final declaration for every client. Self-serve connector, batch runs, priority email support.
Practice — Enterprise
Assisted onboarding and whole-book runs for larger practices. Metered beyond allowance: £4 per quarterly update prepared, £9 per final declaration prepared.
Practice / Enterprise — VAT
Where the practice also files VAT for clients. Assisted onboarding, priority support, named contact.
Sole trader / landlord
Your own quarterly updates and final declaration, on the same engine and the same approval gate a practice uses.
Single Entity — VAT
4 quarterly submissions + amendments, evidence portal, audit chains. Annual billing; monthly +20%.
Multi-Entity — VAT
4 submissions per VRN, self-serve ERP connector, priority email support.
Income Tax per-taxpayer figures are indicative and are being firmed up with pilot partners — the structure is settled, the bands are not. VAT metered beyond allowance: £15 per extra prepared submission, £5 per ad-hoc validation run. Onboarding pilot: £950 — one shadow quarter through the full cycle, credited against year one. Full detail: pricing. Contract stack: Master Terms + Schedule C (MTD) + Order Form.
Common Integration Questions
What constitutes a digital link?
A digital link is a machine-to-machine transfer of data without manual intervention (e.g., API calls, automated file imports). Manual data entry or copy-pasting breaks this link. Qgentic maintains the digital link by processing data directly from source exports without requiring re-keying.
Does Qgentic support both VAT and ITSA?
Yes. The platform supports the nine-box VAT return and full ITSA reporting (quarterly updates and year-end declarations) via a unified compliance engine and a single Government Gateway connection. VAT files to HMRC today; new Income Tax registrations begin with a shadow quarter while HMRC's pause on production access for new Income Tax filing software stands.
How does multi-tenant processing work?
For organisations managing multiple entities or client books, each entity exists as an isolated tenant with distinct data and audit trails. The practice cockpit puts one sign-in over the whole book — a client roster, a cross-client deadline board and batch runs — and the same jobs run programmatically via the API. Each client's run stops at its own approval gate.
Is a specific ERP tax module required?
No. Qgentic calculates the required compliance data directly from standard ledger or summary exports. Integration is handled via standard data formats (JSON, CSV) and protocols (REST, SFTP), avoiding the need for proprietary ERP tax modules. See Integration Architecture.
What is the status of HMRC recognition?
Official HMRC directory listing is currently in progress. Returns file through the MTD API using your own Government Gateway authorisation — a one-time step at onboarding.
How does this compare to spreadsheet bridges?
Bridging tools move finished numbers. Qgentic is the pipeline that produces them: ERP-integrated, deterministically validated, approval-gated and cryptographically logged.
Enterprise-Grade Compliance Infrastructure. Move beyond simple spreadsheet bridges. Ensure data integrity, maintain digital links, and enforce strict audit trails across your organisation. Contact us to discuss your requirements.