Making Tax Digital, for a whole client book.
MTD for Income Tax multiplies your filing frequency. It should not multiply your headcount. Qgentic MTD is bridging software that prepares returns across a whole client book, with each client's data isolated, every total computed from the records you already keep, a named approval on every submission and an audit trail behind every figure.
What it costs: from £249 a month for a practice, one price per client across VAT and Income Tax.
One return, ledger to HMRC
The export comes in, boxes 3 and 5 are computed, a named person approves, and the return goes out with its fraud-prevention headers and hashes. It plays in your browser, with nothing to install.
How your data gets in: integration and data.
More filings, the same team
Quarterly updates multiply the submissions a practice makes. Qgentic takes the re-keying out of each one, so the extra volume runs through software.
Volume
One annual return becomes four quarterly updates and a final declaration, and the processing time stays where it was.
The digital link
Nothing is re-keyed, so the mandatory digital link runs unbroken from the source records to the submission HMRC receives.
Evidence for every declaration
Every submission carries cryptographic evidence of who reviewed and approved it, and when.
A whole book, client by client
Every client gets its own data boundary and its own audit trail, and the isolation costs nothing in speed: 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 each client's approval record 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 dashboard into that tenancy, and each run still stops at that client's own approval gate.
Licences count active clients, not user seats, so the cost follows the size of the book: see pricing.
Every MTD regime on one engine
One engine carries every MTD mandate, current and future. Connectors, validation rules and audit trails are shared, so a new reporting regime slots into the same architecture.
MTD for VAT
The nine-box VAT return, with boxes 3 and 5 calculated by the software, the VRN checked against its modulus-97 checksum and the precision rules enforced, all before a person approves it.
MTD for Income Tax (ITSA)
Quarterly updates for self-employment and property income, HMRC's tax calculation and the year-end final declaration, each validated against HMRC's own data. Registration is open for the next filing cycle.
Construction Industry Scheme (CIS)
The CIS300 contractor monthly return. The software computes every subcontractor's deduction (0%, 20% or 30% of the payment after materials), checks UTRs, reconciles HMRC verification numbers against the payment status, handles nil returns and inactivity, and puts 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.
HMRC connectivity, audit logging and the evidence portal are set up once and shared by every module. CIS sits outside MTD, since HMRC has not brought it into 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: in August 2026 HMRC paused production access for new Income Tax filing software pending a controlled access model, and said it would publish future onboarding arrangements by the end of September 2026.
Data in, from whatever you run
Configurable connectors bring the data in and keep the digital link intact, with no ERP tax module and no integration project.
Native reporting modules
A REST connection to systems such as SAP (DRC), Oracle Fusion or Dynamics 365. Extraction runs system to system, with no one in between.
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, and that is the whole integration.
Scheduled file drops
Scheduled CSV exports from mid-market systems such as Sage, NetSuite and Xero. The filesystem connector picks up each new file and logs it to the audit trail.
Every path keeps the digital link unbroken. If anyone overrides a figure by hand, the run raises compliance warning MTD-DL-007 before anything is submitted.
Which systems it reads
Qgentic reads the standard VAT or ITSA summary export from any system, over an API or secure file transfer, so no system needs custom 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. Batch runs across a whole client portfolio.
Any system that can export a financial summary works, and the mapping is done once, at deployment. Direct API submission to HMRC is switched on per client once HMRC enrolment is complete; filing through your existing channel carries on in the meantime.
How a return gets made
- IntakeThe export arrives as JSON or CSV, and identifiers such as VRNs are normalised before anything else runs.
- ComputationThe software computes the derived values, such as boxes 3 and 5 for VAT, which keeps the digital link intact; an upstream total that disagrees is rejected.
- ValidationDeterministic rules check the VRN's modulus-97 checksum, precision requirements and negative-value constraints, and the return's internal logic.
- Approval and exportA named person approves the figures. Qgentic builds the payload HMRC expects, with the mandatory fraud-prevention headers, sealed by a cryptographic hash.
What the code enforces
| Check | What it does |
|---|---|
| Modulus-97 checksum | A VAT Registration Number (VRN) that fails its checksum never reaches a submission. |
| Computed totals | Boxes 3 and 5 are computed from the inputs, and a total that disagrees is rejected. |
| Format rules | Precision, signs and period keys are validated. |
| Audit chain | A hash-chained log of every action, approval and generated file. |
Every step of the MTD pipeline is deterministic code; no probabilistic AI model processes or validates the data.
What goes to HMRC
The payload
The exact JSON body HMRC's endpoint expects, with a SHA-256 hash and every mandatory Gov-* fraud-prevention header, each one taken from real operating data.
Filing to HMRC
Returns file through the MTD API on the client's own Government Gateway authorisation, a one-time step at onboarding. (HMRC's software directory listing is pending.) Shadow mode runs the pipeline alongside your current process until you switch filing over.
Deadline tracking
The dashboard keeps a live calendar of statutory obligations, synced with HMRC's API. Alerts are configurable, and each submission is staged, waiting for a person's 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 |
Reminders go out 14, 7 and 1 day before each deadline, and administrators can change the schedule.
What it costs
A practice pays one price per client across every MTD regime; a business filing its own pays per registration. Prices are in GBP only, as MTD is a UK regime.
For practices: per client, VAT and Income Tax together
Practice Starter
£4.98 per client per month. Any mix of VAT and Income Tax; a client filing both is counted once. Four quarterly submissions per client per regime plus the final declaration, the client roster, whole-book runs and email support.
Practice Growth
£3.25 per client per month. Batch runs across the book, the self-serve ERP connector and priority email support.
Practice Scale
£1.93 per client per month. Assisted onboarding, whole-book runs and a named contact.
Practice Enterprise
Banded per client above the Scale tier, with assisted implementation and dedicated account management, metered against the audit chain.
If you file for yourself
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 plus amendments, the evidence portal and audit chains. Billed annually, or monthly at +20%.
Multi-entity VAT
4 submissions per VRN, the self-serve ERP connector and priority email support.
A practice band counts clients, not regimes: one client filing both VAT and Income Tax is counted once, and each client stays its own tenant with its own data, audit chain and named approver. The bands are set ahead of the pilots; the structure is settled, and the figures firm up with the first practices. Beyond the allowance: £15 per extra prepared submission, £5 per ad-hoc validation run, £4 per quarterly update, £9 per final declaration. Onboarding pilot: £750 for one shadow quarter through the full cycle, credited against year one. Full detail is on the pricing page. Contract stack: Master Terms, Schedule C (MTD) and an Order Form.
Frequently asked questions
What constitutes a digital link?
A digital link is a machine-to-machine transfer of data with no manual step in between, such as an API call or an automated file import. Typing or copy-pasting a figure breaks it. Qgentic keeps the link by working directly from the source export, so nothing is re-keyed.
Does Qgentic support both VAT and ITSA?
Yes: the nine-box VAT return and ITSA reporting (quarterly updates and the year-end declaration) on one engine and one 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 is an isolated tenant with its own data and audit trail. 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 through the API. Each client's run stops at its own approval gate.
Is a specific ERP tax module required?
No. Qgentic calculates the figures from a standard ledger or summary export, over standard formats (JSON, CSV) and protocols (REST, SFTP). See integration and data.
What is the status of HMRC recognition?
HMRC's software directory listing is in progress. Returns file through the MTD API on 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.
Making Tax Digital guides
MTD for practices: a capacity plan
Quarterly reporting multiplies every client by five. The arithmetic, where the hours actually go, and what to automate first.
MTD bridging software for VAT, explained
Digital links, the nine-box return, and filing VAT from your ERP or spreadsheet under Making Tax Digital.
Making Tax Digital for Income Tax (ITSA)
Quarterly updates, who's mandated and when, and how ITSA runs on the same engine as VAT.
MTD digital links explained
What qualifies as a digital link, what breaks the chain, and why re-typing a figure is the classic failure.