Watch the totals compute themselves.
A narrated walkthrough of the Qgentic dashboard preparing a VAT return, then the engine underneath it: a real, unedited run, offline, on the sample VAT summary bundled with every download. Box 3 and Box 5 never came from a keyboard: the software computed them, which is what an unbroken digital link means. Then try the nine boxes yourself, with the same rules ported line-for-line and running in your browser.
The dashboard, through a full run
A guided, narrated walkthrough of the real Qgentic dashboard, the screen your practice works in. It runs the whole cycle itself: the VAT summary read from your accounting system, Box 3 and Box 5 computed by software, a named person's declaration and approval, the HMRC-exact return prepared with every fraud-prevention header and hashed. No terminal, no input required. See how Qgentic collects this data from your ERP.
The same run, at the engine level
Transcript of an offline run on the bundled sample data (service start-up lines condensed). Reproduce it with the evaluation binary (QGENTIC_PACK=mtd qgentic run) and make the declaration yourself.
Four moments worth pausing on
- The digital link heldThe ERP supplied Boxes 1, 2, 4, 6–9. The software computed Box 3 (£15,000 + £0) and Box 5 (|£15,000 − £8,500| = £6,500). Totals that are computed cannot disagree with their inputs, and a source total that does disagree is refused (MTD-BOX-002/003).
- The VRN passed the checksum firstVRN 123456782 cleared HMRC's modulus-97 check (classic and 9755 methods) before anything else ran. A VAT number that fails the checksum never reaches a submission.
- A named approver finalised the returnMTD requires a person to make the declaration. The approval summary carried the net VAT figure; a 120-second scoped grant then authorised exactly one preparation of the HMRC-exact POST body, with all twelve of HMRC's required fraud-prevention headers filled with real computed values rather than placeholders.
- Ready for HMRCThis offline run prepares and hashes the body without sending it. One Government Gateway authorisation at onboarding and returns go to HMRC through the MTD API, behind the same approval gate and with the same evidence you see here.
The VAT return this run produced
The run above ends by preparing a return, and this is it: the actual files, unedited. The data is synthetic (Northwind Trading Ltd is fictional), but the VAT registration number is checksum-valid, so the validation is real. The body is the exact nine-box JSON that HMRC's interface expects.
| File | What it is |
|---|---|
| vat-return-body.json | The nine boxes in HMRC's own field names, with Box 3 and Box 5 computed by the software |
| manifest.json | The body's SHA-256 hash and all twelve HMRC fraud-prevention headers with real computed values |
| vat-validation.json | The validation verdict: zero errors, zero warnings |
| pipeline-summary.json | Everything that happened in the run, including the audit-chain verification |
Check the arithmetic yourself: in vat-return-body.json, totalVatDue = vatDueSales + vatDueAcquisitions, to the penny.
The nine boxes, live in your browser
These are the engine's MTD rules (VRN modulus-97, box identities, precision checks), ported line-for-line to this page. Nothing you enter leaves this tab.
Your VAT summary (what the ERP supplies)
Prefilled from the bundled sample. Boxes 1–5 are pence-precise; 6–9 whole pounds.
What the software computes
The computation is the digital link.
See the other platforms, or run it for real
The download runs this exact pipeline on your hardware, fully offline. Sample data included.