Skip to content

Plan: recognition by HMRC and Companies House ​

Status: plan, awaiting the Product Owner's approval; no code yet. Checked 2026-09-30. Where a step could not be checked against an HMRC or Companies House page, it says "to confirm with SDST" (or with Companies House).

Why ​

Today GetMy Books prepares and checks; others file. FEAW's VAT returns go through Xero, and its accounts and Company Tax Return go through the accountant (docs/plans/making-tax-digital.md). That is route (a): GetMy Books prepares, a recognised product or the accountant files. It stays the plan while FEAW and WealthTechPros are the only users.

If GetMy Books is sold to other owner-directors (ADR 0015's direction, with Xero's connection limits in ADR 0024), "prepares and files" becomes the product. Each filing channel has its own route to being allowed to file:

ChannelTechnologyWho recognises itSection
VAT returnsMTD VAT REST API, Developer Hub, OAuthHMRC SDST1
Company Tax Return (CT600)GovTalk XML to HMRC's Transaction EngineHMRC SDST2
Accounts, confirmation statementCompanies House XML gateway (software filing)Companies House3

This plan says what each needs, in what order, and what sets it off.

Finexer is not part of this. Finexer (open banking, ADR 0015) makes GetMy Books an FCA-registered agent for reading bank data. It gives no standing with HMRC or Companies House, and neither body asks about it.

House rules that hold for every channel:

  • No MCP tool submits or approves. Only src/approvals/ calls a submit function, after approval on a web page with fresh sign-in and MFA: a single-use link, 24-hour expiry, bound to a hash of the payload, one submission per entity and period (ADR 0005).
  • A timeout is resolved by reading back (VAT obligations, the Transaction Engine poll, Companies House submission status), never by resending.
  • MCP tools never call HMRC or Companies House; syncs fill a cache (ADR 0006).
  • Every figure is integer pence from pure code in src/rules/ or src/vat/; the entity comes only from the session, under RLS.

1. MTD for VAT (REST API, Developer Hub) ​

What it is ​

The VAT (MTD) API on HMRC's Developer Hub, with OAuth per company. Planned in full in docs/plans/hmrc-connection.md (issue #85, QD-23, QD-25, QD-26). This section only adds what that plan leaves out.

Steps to recognition ​

  1. Developer Hub account and sandbox application (hmrc-connection stage 0).
  2. Build the minimum HMRC sets for production: retrieve obligations and submit a return, with fraud prevention headers.
  3. Test both endpoints in the sandbox with a Create Test User organisation; validate headers with the Test Fraud Prevention Headers API.
  4. Email SDSTeam@hmrc.gov.uk within 2 weeks of finishing testing, so they can still see the sandbox logs. Answer the two questionnaires.
  5. Accept the Developer Hub terms of use (required before production credentials are issued).
  6. HMRC advises within 10 working days.
  7. Make a live submission and give HMRC the VRN.
  8. Only then, and only for a retail or commercial product, ask to be added to gov.uk's list of software compatible with MTD for VAT. In-house use for our two companies does not qualify for the list.

What the existing plan does not cover ​

  • Terms of use. Beyond the fraud headers: handle customer data under UK GDPR; encrypt tokens and anything that identifies a person; keep each customer's data separate; test for security vulnerabilities before going live, "including regular penetration testing"; report issues affecting customer data to HMRC with full details within 72 hours; give customers a way to report security issues; never store customers' HMRC sign-in details; never claim or imply the software is "HMRC approved, accredited, certified, Kitemarked or similar"; no HMRC logos. HMRC may revoke access.
  • HMRC Assist for VAT (the VAT Assist (MTD) API), from April 2027. It flags likely mistakes in a draft return before filing, with links to guidance. Not in HMRC's minimum functionality; using it is optional. It fits the "check before filing" promise (SPEC-001): call it from the approval page or a server job, never from an MCP tool.
  • Penalties and financial details. HMRC lists penalties, penalty financial details and appeals information as recommended, not required. The hmrc-connection sync already reads penalties "if enabled".
  • Filing itself (SPEC-002, write:vat): the submit call sits in src/approvals/, sends WEB_APP_VIA_SERVER headers (a person is acting on the approval page), and records HMRC's receipt (form bundle number, processing date) against the approval.

What GetMy Books must build ​

The hmrc-connection plan (connect, sync, cache, tools), plus SPEC-002: submit on approval, read back on timeout, store the receipt.

Testing ​

Sandbox only until SDST approves; header evidence from the test API; one real live submission (QD-25 option 2) if HMRC will not issue credentials for read-only in-house use.

Ongoing obligations ​

Keep headers accurate as the web page and NAS change; stay within rate limits; reconnect each company every 18 months (refresh token life); security testing on a regular cycle; breach reporting within 72 hours; follow API version changes. Whether VAT production approval has a periodic renewal: none found; to confirm with SDST.

Effort and elapsed time (estimates) ​

  • Build on top of hmrc-connection: SPEC-002 filing, 1 to 2 weeks.
  • Elapsed from SDST email to production credentials: 3 to 6 weeks.
  • gov.uk listing: after the first live submission by a paying customer.

2. Corporation Tax: CT600 online filing ​

What it is ​

Not a Developer Hub REST API. The Company Tax Return goes as a GovTalk XML message to HMRC's Transaction Engine. The Developer Hub lists only one Corporation Tax API, "Corporation Tax Online", and it is XML. No REST replacement is announced: MTD for Corporation Tax was dropped (July 2025 roadmap, docs/not-doing.md), and the CoTax replacement has no announced API. Whether a REST channel is planned: to confirm with SDST.

A CT600 submission carries:

  • the CT600 return in XML (RIM artefacts: schema plus schematron business rules);
  • the company's accounts in iXBRL, tagged with an HMRC-accepted taxonomy (FRC 2026 suite added April 2026; FRS 102 and FRS 105);
  • the tax computations in iXBRL, tagged with HMRC's Corporation Tax computational taxonomy (2025 added February 2026);
  • an IRmark: a hash of the body, computed by the software and checked by HMRC, which returns a digital receipt.

Current artefacts: CT600 V3 (2026) Artefacts V1.994 (10 October 2025), live in LTS, TPVS and live. CT600 V3 (2027) Artefacts V1.995 (25 September 2026) is awaiting implementation. V2 (2009) remains for older periods.

Why demand has grown ​

HMRC's free Company Accounts and Tax Online service (CATO) closed on 31 March 2026. Since 1 April 2026, every company must use commercial software (or an agent) to file its CT600, and cannot view returns filed through CATO. CATO served small unrepresented companies with simple affairs: exactly the owner-directors GetMy Books would sell to. The Government said in May 2025 that no free commercial filing software exists.

Steps to recognition ​

  1. Register as an XML software developer. Email SDSTeam@hmrc.gov.uk with company name, contact names, email addresses and the XML API (Corporation Tax Online). This is separate from the Developer Hub account. SDST allocates a 4-digit vendor ID and test credentials.
  2. Read the packs: Transaction Engine Document Submission Protocol; CT generic specifications (online service guidance 1.6, validation rules 1.17a, how to use the test service 1.4a, recognition instructions 1.0); CT600 RIM artefacts; XBRL and iXBRL specifications (CT computations format, style guide, joint filing validation checks); the generic IRmark pack; Taxonomies accepted by HMRC.
  3. Test offline in the Local Test Service (LTS 8.3, Java 11 or later). It checks the message body only, not the Transaction Engine.
  4. Test end to end in the External Test Service (ETS), https://test-transaction-engine.tax.service.gov.uk/submission and /poll. ETS checks the GovTalk header and test credentials, routes the body to TPVS (schema and business rules), and returns pass or fail. Supported Monday to Friday, 9am to 5pm.
  5. Ask for a new applicant's pack. Email SDSTeam@hmrc.gov.uk with the vendor ID. The pack holds HMRC's test scenarios.
  6. Run the scenarios through ETS and send SDST the XML outputs.
  7. SDST aims to decide within 10 working days of receiving the documents (2 weeks for renewals).
  8. Listed on gov.uk "Filing your Company Tax Return online" (commercial software suppliers, under "Produce and Submit CT600" and, if applicable, iXBRL providers). HMRC "accepts returns filed using any of the products shown".
  9. Live: submissions go to https://transaction-engine.tax.service.gov.uk/submission. The class HMRC-CT-CT600-TIL ("Test in Live") validates a return with the company's live credentials without sending it to HMRC's back end: the safe first step with real data.

Recognition is per product and yearly ​

HMRC's CT recognition instructions: "Corporation Tax recognition has a yearly renewal process." Each year SDST opens renewal (announced by the Corporation Tax email alerts on the Developer Hub); the supplier asks for a checklist link and completes it to stay on the list. New RIM artefacts (for example V1.995 for 2027) must be adopted as HMRC brings them live. Whether a new schema version triggers re-testing beyond the yearly renewal: to confirm with SDST.

Whether unlisted, in-house software may make live CT600 submissions for its own companies: to confirm with SDST.

What GetMy Books must build ​

Large. Most of it is new scope, not on the roadmap (rule 8: needs a decision).

  • Statutory accounts for small and micro companies (FRS 102 section 1A, FRS 105), rendered as iXBRL with the FRC taxonomy. Shared with Companies House (section 3): build once.
  • Tax computation in pure code (src/rules/, integer pence): profits, capital allowances, losses, marginal relief; rendered as iXBRL with the CT computational taxonomy.
  • CT600 XML from the computation, validated locally against the RIM schema and schematron before approval.
  • IRmark and the GovTalk envelope with the vendor ID.
  • Transaction Engine client in src/hmrc/: submit, acknowledgement, poll by correlation ID, delete. The poll is the read-back that resolves a timeout (ADR 0005).
  • Credentials. The Transaction Engine takes the company's Government Gateway user ID and password in the GovTalk header; there is no OAuth. HMRC's Developer Hub terms say software should not store customers' sign-in details. So the approval page asks for them at the moment of submission, uses them once, and never stores or logs them. How this works for companies moving to GOV.UK One Login: to confirm with SDST.
  • Approval as for VAT: the approval hash covers the CT600 XML and both iXBRL documents.

Testing ​

LTS in the pipeline (a container with Java 11, run on synthetic companies); ETS for the protocol; HMRC's scenarios for recognition; Test in Live with FEAW's real credentials before any live filing.

Ongoing obligations ​

Yearly renewal; adopt each new RIM artefact and taxonomy year; keep the IRmark and protocol current; watch HMRC service availability; support customers whose returns are rejected (error codes in the validation rules).

Effort and elapsed time (estimates) ​

  • Accounts and computations to iXBRL: 4 to 8 weeks.
  • CT600 XML, IRmark and Transaction Engine client: 2 to 4 weeks.
  • SDST registration to recognition: 4 to 8 weeks elapsed, most of it waiting on scenarios and review.

3. Companies House software filing ​

What it is ​

Companies House's XML gateway (software filing service). Documents go over HTTPS as XML to the structure in its Technical Interface Specification (TIS). Accounts go as iXBRL. The same route files confirmation statements, officer changes and most other forms. Companies House plans to replace the XML platform with its REST JSON API "in the long-term future", with no timetable; its public REST API today is for reading data.

What changes under the Economic Crime and Corporate Transparency Act ​

  • Accounts: software only from 1 April 2028 (moved from April 2027). Web and paper filing close for accounts, with no transition. From the same date small companies file a profit and loss account, abridged accounts go, and micro-entities file more. Small and micro companies may opt out of publishing the profit and loss account.
  • Directors and PSCs have had to verify identity since 18 November 2025; the confirmation statement needs each director's personal code (FEAW's is overdue, SPEC-004 S7).
  • Presenters (people who file) must verify identity, or file through an Authorised Corporate Service Provider (ACSP), from no earlier than November 2027, with at least 6 months' notice. Companies House says "in the future, businesses will also need to register as an authorised agent to be able to file on behalf of clients".

Is ACSP registration needed for GetMy Books? ACSP status attaches to whoever files on behalf of others, not to software. An ACSP must be AML-supervised. If each customer company files as itself (its own presenter account and authentication code, submitted by a verified officer), GetMy Books is the software and does not need to be an ACSP. If GetMy Books ever filed for other companies under its own presenter account, it would be an agent and would need ACSP registration and an AML supervisor, which also cuts against the non-goal "serving accounting firms". Confirm with Companies House before selling.

Steps to recognition ​

  1. Read the TIS and "Important information for software developers"; check the schemas for the forms in scope (accounts; optionally confirmation statement).
  2. Apply for a test account: email xml@companieshouse.gov.uk with the presenter's name, contact name, address, email and phone. Companies House issues test presenter credentials.
  3. Submit test filings with the test flag set to 1, package reference 0012, a unique submission number each time, and the presenter ID and authentication value MD5-hashed. Use realistic data.
  4. Tell Companies House (xml@companieshouse.gov.uk) when test submissions are in; they are reviewed by hand and stay pending until then.
  5. Testing ends when Companies House "is confident that the development, relevant to the form types being tested, meets our strict criteria". Recognition is per form type. No review time is published: to confirm with Companies House.
  6. Live credentials: apply for an online filing presenter account (presenter ID and code), about 5 minutes online. Fee-bearing filings (the confirmation statement) also need a Companies House credit account.
  7. Each company files with its company authentication code (6 characters, posted to the registered office, up to 10 working days).
  8. Listing on gov.uk "Find software for filing company accounts": Companies House "does not endorse or recommend particular products". How a product is added: to confirm with Companies House.

What GetMy Books must build ​

  • The iXBRL accounts from section 2 (shared).
  • A Companies House client in its own module (for example src/companies-house/, importing neither src/xero/ nor src/hmrc/): the accounts submission, then GetSubmissionStatus polling as the read-back.
  • Credentials: the customer's presenter ID and code, and the company authentication code ("treat it with the same care as your bank card PIN"). Entered on the approval page at submission, or held encrypted under RLS with entity_id: a decision (below).
  • Optional: the confirmation statement, including directors' personal codes and the fee through a credit account.

Testing ​

Test account and test flag only, synthetic companies; a first live accounts filing for FEAW only if the Product Owner and the accountant agree.

Ongoing obligations ​

Track TIS and schema changes; the April 2028 accounts changes (profit and loss, no abridged accounts); presenter identity rules from November 2027; the taxonomy year Companies House accepts (to confirm with Companies House).

Effort and elapsed time (estimates) ​

  • Gateway client and accounts form, given the iXBRL: 1 to 2 weeks.
  • Confirmation statement: 1 week more.
  • Test account to live: 3 to 8 weeks elapsed (manual review, no stated timescale).

Cross-cutting ​

Fraud prevention headers ​

  • Required by law for VAT (MTD) and Income Tax (MTD) APIs and all their endpoints. Covered by ADR 0006 and the hmrc-connection plan: WEB_APP_VIA_SERVER on the connect and approval pages, BATCH_PROCESS_DIRECT for the nightly sync. HMRC's Compliance and Sanctions Guidelines allow fines and blocking for missing or wrong headers.
  • CT600 over the Transaction Engine: the fraud prevention guide does not mention XML channels. Whether headers or equivalent data are expected: to confirm with SDST.
  • Companies House: no header requirement found.

Security and data protection ​

  • HMRC terms: security testing before going live, "including regular penetration testing"; regular checks that controls work; encryption of tokens and personal data; per-customer separation; 72-hour reporting to HMRC and the ICO; a way for customers to report security issues.
  • Penetration test: needed before production credentials for anything sold. Scope: the approval page, Access, the MCP endpoint, token storage.
  • ISO 27001: no HMRC or Companies House source found that requires it. Not claimed as "not required"; to confirm with SDST.
  • Data protection: ADR 0026 and ICO registration (ADR 0015) apply; a privacy notice naming HMRC and Companies House as recipients.

Support model HMRC expects ​

SDST supports developers (aims to answer within 2 working days). It does not support end users: the product must. The terms require a channel to report security issues; the VAT guide expects clear guidance on credentials and error handling. Any stated response-time standard for supporting end users: to confirm with SDST.

Wording ​

Never "HMRC approved", "accredited" or "certified". Safe: "listed by HMRC as commercial software for Company Tax Returns" or "compatible with Making Tax Digital for VAT", only once true.

OrderStepTrigger
0Keep route (a). Xero files VAT; the accountant files accounts and CT600Now
1hmrc-connection plan (read VAT from HMRC); QD-25 email to SDSTAlready on the roadmap (item 7)
2SPEC-002 VAT filing and production approvalQD-25 outcome, or a decision to sell
3Statutory accounts and iXBRL, prepared only (the accountant files)A decision to sell, or wanting FEAW's own accounts out of GetMy Books ahead of April 2028
4Companies House test account; accounts filingStep 3 done; before April 2028 if selling
5SDST XML registration, CT600, recognition, yearly renewalStep 3 done and a decision to sell (post-CATO demand)
6Pen test; terms of use accepted; listingsBefore the first production credentials for a sold product

Why this order: VAT is already half-planned and is the only regime with a quarterly deadline. iXBRL accounts feed both Companies House and the CT600, so they come before either filing channel. Companies House before HMRC CT: simpler recognition, a hard date (1 April 2028), and no yearly renewal found. CT600 recognition carries the most ongoing cost (yearly renewal, new artefacts each year), so it waits until there are paying customers.

Nothing here changes docs/not-doing.md by itself: billing and multi-user sign-up stay out until the go-to-market decision.

Acceptance tests (synthetic data only) ​

VAT ​

  1. Approval gate. Given a draft return for a sandbox organisation with no approval, when anything other than src/approvals/ tries to submit, then no request reaches HMRC, and no MCP tool name contains "submit" or "approve".
  2. Hash binding. Given an approved draft, when one box changes by 1p, then submission is refused and a new approval is needed.
  3. Timeout. Given the sandbox submit times out, when the approval is retried, then GetMy Books reads obligations back and shows "filed" or "not filed", and sends no second submission.

CT600 ​

  1. Local validation. Given a synthetic small company with a £12,345.67 profit, when the CT600 and both iXBRL documents are built, then LTS reports no schema or business-rule errors and the tax matches a hand-worked figure to the penny.
  2. ETS round trip. Given ETS test credentials, when the approved return is sent, then the poll returns success, the IRmark in HMRC's receipt matches ours, and the receipt is stored against the approval.
  3. Credentials not kept. Given a submission with Government Gateway credentials entered on the approval page, then they appear in no table, log or error report after the request ends.

Companies House ​

  1. Test filing. Given the test account and a synthetic micro company, when its iXBRL accounts are sent with the test flag set to 1, then the gateway parses them and the status poll returns pending or accepted.
  2. Isolation. Given a session for WealthTechPros only, then no FEAW authentication code, presenter credential or submission is readable.
  3. Duplicate guard. Given accepted accounts for a period, when a second filing for the same entity and period is attempted, then it is refused.

Decisions for the Product Owner ​

RefDecisionRecommendation
NewKeep route (a) (GetMy Books prepares; Xero or the accountant files) until a decision to sellYes
NewAdd statutory accounts and iXBRL preparation to scopeNot now; decide with the go-to-market plan, and before 1 April 2028 if FEAW's own accounts are to come from GetMy Books
NewRegister as an HMRC XML developer (vendor ID, LTS)Only when the accounts build is approved; free, but starts nothing useful before then
NewCustomer companies file as themselves (own presenter account and codes); GetMy Books never files as an agent, so no ACSPYes; confirm with Companies House first
NewHold the Companies House authentication code encrypted, or ask for it at each filingAsk at each filing while it is FEAW and WealthTechPros; revisit when selling
NewPenetration test before any production credentials for a sold productYes (HMRC terms require regular penetration testing)
NewProduct wording: never "HMRC approved"Yes; add to the pre-release checklist

Sources (checked 2026-09-30) ​