Why iXBRL version control matters

HMRC online Company Tax Returns normally include computations in Inline XBRL format, and most companies also file iXBRL accounts as part of the return package. When a CT600 is amended, the numbers in the return, computation, accounts, and supplementary pages must still tell the same story.

The risk is not abstract. A practice can file a corrected CT600 figure while accidentally attaching an older computation, the wrong set of accounts, or a client-approved pack that no longer matches the submitted return.

What needs a version label

Treat the amended return as a package, not a single file. The version note should cover:

Main CT600 version and amendment reason.
Tax computation version and generated date.
iXBRL accounts version, approval status, and whether the accounts themselves changed.
Supplementary pages affected by the amendment.
Client or director approval version.
HMRC acknowledgement or rejection response for each filing attempt.

When accounts do not change but the computation does

Some amendments change only the tax computation: capital allowances, loss claims, group relief, marginal relief, repayment claims, or supplementary-page figures. In those cases, the accounts version may remain unchanged, but the computation and CT600 still need a clean revised version trail.

The file should make that clear. A reviewer should not need to infer whether the accounts were deliberately unchanged or accidentally left behind.

When accounts do change

If amended accounts are involved, the workflow needs tighter control. Check that the accounts, computation, CT600, and approval pack all reflect the same final position. If Companies House filing is also affected, keep that workflow distinct from the HMRC CT600 filing evidence.

This is especially important for owner-managed companies where late bookkeeping changes can affect directors' loan accounts, dividends, payroll postings, fixed assets, and tax adjustments at the same time.

The amended-return version-control checklist

Start from the accepted or last submitted CT600 package, not an orphaned draft.
Record the amendment reason before changing figures.
Regenerate the computation where taxable profits, reliefs, credits, or tax payable changed.
Confirm whether iXBRL accounts changed, stayed unchanged, or need separate approval.
Review supplementary-page indicators and page-level figures again.
Produce a client approval pack that matches the exact files intended for re-submission.
Keep HMRC acknowledgement, rejection, or follow-up evidence with the amended package.

Why AI and API workflows need explicit file states

Agent-assisted CT600 workflows can be useful, but they make version control more important. An AI agent or API client should not guess which computation or iXBRL file is final. The workflow should expose structured states such as draft, reviewed, approved, submitted, rejected, amended, and superseded.

That is the difference between automation and loose file handling. The user should be able to ask which version was filed and get a precise, evidence-backed answer.

How Robocount handles this workflow

Robocount is designed for CT600 preparation, review, validation, and filing workflows where the return package matters as a whole. Version-aware handling of CT600 data, computations, supplementary pages, iXBRL attachments, approval evidence, and submission responses is central to reliable Corporation Tax filing.

Keeps CT600 figures connected to supporting computation and attachment review.
Supports controlled amendment workflows rather than loose re-uploading.
Helps practices retain approval and HMRC response evidence beside the return package.
Gives API and AI workflows clearer states for draft, reviewed, approved, and submitted returns.

FAQ

Does every CT600 amendment require new iXBRL accounts?

Not always. Some amendments affect the tax computation or CT600 fields without changing the accounts. The practice should document whether the accounts changed or were deliberately reused.

Do Corporation Tax computations need iXBRL?

HMRC guidance says computations forming part of an online Company Tax Return must be in iXBRL format. Most companies also file accounts in iXBRL, subject to exceptions.

What is the biggest version-control risk with amended returns?

The common risk is mismatch: the client approves one pack, the practice submits another, or the amended CT600 no longer agrees with the computation or attachment.

How should AI filing workflows treat amended files?

They should use explicit file states and require human review before submission. The workflow should know which CT600, computation, accounts file, supplementary pages, and approval evidence belong to the final package.

Useful official references

This guide is general product and filing workflow information, not tax advice. Check current HMRC guidance and the company's facts before filing or amending.

CT600 iXBRL version control for amended returns.