QgenticQgentic
Automated Regulatory Filings

Qgentic. Automated compliance data extraction.

Qgentic reads the systems you already run, prepares the filing and checks every field against the regulator's own rules. Nothing is exported until a named person approves it.

View Demo Contact Us
06 modulesone engine, one integration
SHA-256hash-chained audit trail
A named personapproves every filing
Air-gappedon-premise edition
Supported Regulations

Select a Regulation

Pick your regulation for scope, pricing and a working demo. Every module runs on the same engine, so one integration covers them all.

On-Premise

Air-Gapped Deployment

One signed binary on your own infrastructure. No telemetry, no third parties, nothing leaves your network.

View air-gapped edition →

UK · HMRC

Making Tax Digital (MTD)

Quarterly VAT and ITSA filings across a whole client book — prepared in bulk, approved one by one, by name.

View MTD module → · View Demo

EU · Regulation (EU) 2022/2554

DORA Register of Information

Builds the Register of Information from the contract and vendor data you already hold, and validates every LEI and field before it goes anywhere.

View DORA module → · View Demo

UK · PRA & FCA

Operational Resilience

Third-party registers and incident reports, with tolerance breaches computed straight from system timestamps.

View OpRes module → · View Demo

EU · Regulation (EU) 2024/1689

EU AI Act Register

Classifies your AI systems by risk and prepares the Annex IV technical documentation for each one.

View AI Act module →

UK · PRA SS1/23 & ATRS

UK AI Governance

The UK has no AI Act. What it has is SS1/23 and ATRS — a model inventory with computed risk tiers, and transparency records ready to publish.

View UK AI module →

Architecture

Process Overview

AI does the reading. Deterministic code does the deciding. Every field is validated before it can reach a filing.

  1. IngestionYour data arrives by file upload, CSV export or REST API. No one re-keys a figure.
  2. ValidationAI extracts the fields; deterministic rules check every identifier, code and figure. Gaps are flagged, and every change lands in the audit log.
  3. ApprovalA named person reviews and approves. Approval seals the filing pack with cryptographic hashes.
From your systems to a compliance filing A system export, the obligation and the entity's identifiers feed the Qgentic engine. The model reads the export, maps every field and explains what changed; code decides the result — identifiers such as the LEI and VRN are checked against their standards, totals are recomputed rather than accepted, and dates, signs and precision are enforced. A field that fails its rule gate blocks the run. The run then stops for a named person, whose name, note and timestamp are recorded with the decision — no unattended filing. What leaves the engine is a filing pack: the exact payload, a manifest and the source snapshot, every file hashed on a SHA-256 chain, filed via the regulator's API or handed over directly. All six modules run this same shape on one engine. § YOUR SYSTEMS § THE QGENTIC ENGINE § THE APPROVAL § THE FILING PACK System export JSON · CSV · XLSX · API no one re-keys a figure The obligation the return · the period DORA RoI · VAT 24A1 · ATRS Your entity LEI · VRN · company no. checked, not assumed MODEL READS CODE DECIDES reads the export maps every field explains what changed drafts the summary LEI ISO 17442 check VRN modulus 97 check totals recomputed dates · signs · 2 dp NOTHING UNVERIFIED REACHES A FILING A field that fails its rule gate blocks the run. every change lands on the audit chain validated · hashed · traced to the source row AWAITING SIGN-OFF A named person reviews the prepared filing and approves. marta.lindqvist approver · admin Their name, note and timestamp are kept with the decision. no unattended filing The filing pack the exact payload manifest.json the source snapshot SHA-256 hash chain every file hashed, every step on the chain filed via the API or handed to the regulator verifiable years later DORA · operational resilience · VAT · ITSA · EU AI Act · UK AI governance — six modules, one engine, one approval gate, one audit chain.
The shape every module shares. The model does the reading; code does the deciding — identifiers are checked against their standards, totals are recomputed rather than accepted, and the run stops for a named person before anything is filed. What leaves the engine is a hashed filing pack a regulator can verify years later.
User Interface
The Qgentic console dashboard: six compliance platforms — DORA, OpRes, MTD VAT, MTD ITSA, AI Act and UK AI — each with its data staged, and a DORA Register of Information filing awaiting approval with Approve and Decline beside a note field. The Qgentic console dashboard: six compliance platforms — DORA, OpRes, MTD VAT, MTD ITSA, AI Act and UK AI — each with its data staged, and a DORA Register of Information filing awaiting approval with Approve and Decline beside a note field.
Every subscribed platform on one dashboard, each showing whether its data is staged and where its cycle has got to. A prepared filing waits here until a named person approves it — the note they leave is recorded with the decision.

What the model may do — and what only code decides — is on the security page.

Auditability

Verifiable Outputs

Every run leaves evidence you can check: hash-chained logs, rule-by-rule validation results and an exportable filing pack. For networks that allow nothing out, there is an air-gapped edition.

Reference documentation and guides: DORA Register of Information · MTD capacity for practices · Air-gapped compliance requirements.

FAQ

Frequently Asked Questions

What is Qgentic?

Regulatory compliance software that prepares filings for EU DORA, UK operational resilience, HMRC Making Tax Digital and the EU AI Act. Every export needs a named user's approval first.

What does the AI actually do?

AI reads and drafts; deterministic rules validate every field and assemble the filing. The AI cannot bypass a rule or approve anything.

Can it run fully offline?

Yes. The air-gapped edition is a signed binary on your own infrastructure. It runs entirely offline — no telemetry, no external dependencies.

How are filings approved?

A named user reviews and approves each filing — there is no unattended self-approval. The decision is recorded in a cryptographic audit log.

See It Run

Watch a real run end to end: data in, validation, approval, filing out. No account, no install.

View Demo Contact Sales

Pricing information is available on the pricing page.

Auditability and Verification. Qgentic is built to be checked. Every action writes an audit log, and the whole system can run on your premises.