Why CT600 is a good automation target

CT600 work is structured. A return has an accounting period, company details, computation figures, supplementary-page indicators, accounts and computation attachments, and a submission route. That makes it a better automation target than many free-form advisory jobs.

But structure does not make it risk-free. HMRC treats the Company Tax Return as a package: the main CT600, supplementary pages, accounts, computations, and supporting material. An AI workflow that only drafts answers into a form misses the review and evidence problem.

What AI should and should not do

AI is strongest when it helps with intake, classification, explanation, and consistency checks. It is weakest when it makes unreviewed tax judgments or silently changes filing data.

Good use: classify source documents, flag missing data, explain CT600 sections, suggest likely supplementary-page triggers, and prepare reviewer checklists.
Good use: compare trial balance movements with prior-year patterns and ask targeted follow-up questions.
Careful use: draft computation narratives or client explanations that a qualified reviewer can approve.
Avoid: submitting a return without explicit approval, hiding uncertainty, inventing source figures, or treating HMRC response codes as optional.

The API workflow a CT600 agent needs

A robust API workflow should separate data capture, calculation, validation, review, approval, and filing. That separation helps AI agents operate inside controlled boundaries.

Import company and accounting-period data.
Ingest trial balance, accounts, or structured accounting outputs.
Map source categories to tax computation areas.
Identify possible supplementary-page requirements.
Create review tasks for uncertain or high-risk areas.
Produce CT600, computation, and attachment-ready outputs.
Hold the return for approval before Government Gateway submission.
Record submission status, response, rejection, amendment, and resubmission history.

Supplementary-page intelligence

One valuable role for AI is early supplementary-page triage. It can ask whether a company has close company loans, group relief, R&D claims, residential property development activity, creative industry claims, cross-border royalties, or other specialist facts.

The output should be a review checklist, not an automatic conclusion. For example, if the accounts show an overdrawn director's loan account, the system can flag possible CT600A review. The reviewer still decides whether the company is a close company, whether the borrower is a participator or associate, and what happened after the period end.

iXBRL and attachments are part of the automation problem

CT600 automation cannot stop at box values. Online Company Tax Returns generally need accounts and computations in the required electronic format. HMRC and Companies House guidance explains that XBRL tagging is part of the electronic filing environment.

For developers, that means the filing API surface should treat attachments as first-class objects. A workflow should know which accounts and computations were used, whether they are attached, and whether the final return package matches the approved computation.

Controls for AI-assisted filing

Source traceability: each material figure should connect back to a source document, import, or reviewer entry.
Uncertainty flags: the agent should expose missing facts rather than filling gaps creatively.
Approval gates: filing should require an explicit approval step from the responsible user or practice workflow.
Change log: changes after approval should be visible and require fresh review where material.
Submission evidence: HMRC responses, rejection messages, and successful submission records should be retained.
Privacy boundaries: prompts, logs, exports, and integrations should avoid exposing credentials or unnecessary client data.

How Robocount fits API and MCP-native CT600 workflows

Robocount is built for browser, API, and MCP-native Corporation Tax workflows. The aim is to give software developers and AI builders a structured CT600 path while keeping the tax return package reviewable.

Structured CT600 workflow for preparation, validation, review, and filing readiness.
Supported supplementary pages tied back to the main return.
API surface for developers building around Corporation Tax filing.
MCP-native approach for AI agents that need controlled access to CT600 workflow steps.
Audit-trail-first design so automation does not erase reviewer accountability.

FAQ

Can AI file a CT600 by itself?

A CT600 filing workflow can be automated in parts, but a responsible workflow should keep source data, review decisions, approvals, attachments, and submission evidence visible. AI should not silently submit unchecked tax returns.

What is an API-led CT600 workflow?

It is a structured filing workflow where company data, accounts, computations, supplementary-page inputs, validation, approvals, and submission status can move through software interfaces instead of manual form entry alone.

Why does MCP matter for CT600 work?

MCP-style tooling can let AI agents use defined tools and data boundaries. For Corporation Tax, that is useful because the agent can be guided through controlled actions instead of being given unrestricted access to filing systems.

Does Robocount replace professional judgment?

No. Robocount is designed to support CT600 preparation, review, and filing workflows. Tax judgments still need appropriate review against the company's facts and current guidance.

Useful official references

This guide is general product and filing workflow information, not tax advice. Developers should design against current HMRC requirements and the facts of each filing workflow.

AI-assisted CT600 filing needs structured API workflows, not unchecked form filling.