The trial balance is only the starting point

A trial balance can get a CT600 workflow moving, but it is not the Corporation Tax computation. The filing package needs mapped accounts data, tax adjustments, capital allowances, loss claims, supplementary-page decisions, iXBRL attachments, client approval, and validation evidence.

This distinction matters for practices using imports, APIs, or AI agents. A model can classify and suggest, but the final return still needs a controlled review trail that explains how accounting profit became taxable profit and how the CT600 boxes were populated.

Step 1: map accounts headings carefully

Start by mapping the trial balance to usable Corporation Tax categories. Keep turnover, other income, cost of sales, payroll, depreciation, repairs, travel, entertaining, professional fees, finance costs, tax provisions, fixed assets, and director balances visible.

Use consistent chart-of-account mappings across clients where possible.
Flag suspense, director loan, dividends, tax, penalties, and unusual income accounts.
Keep journal adjustments and post-year-end changes visible to the reviewer.
Separate accounts classifications from tax treatment; they are related but not identical.

Step 2: bridge accounting profit to taxable profit

The computation should show the bridge from profit before tax to taxable total profits. Common review areas include depreciation add-back, capital allowance claims, disallowable entertaining, non-trading loan relationships, legal and professional costs, donations, penalties, prior-year adjustments, and provisions.

The most useful workflow does not hide these adjustments inside a black box. It shows the accounts source, the tax adjustment, the reason, and the reviewer who accepted it.

Step 3: review capital allowances and losses

Fixed asset additions do not automatically become tax deductions. Review capital allowance pools, AIA, full expensing, special-rate assets, disposals, private-use restrictions where relevant, and any carried-forward balances.

Losses need the same discipline. Current-year relief, carry-back claims, group relief, and carried-forward deductions affect both the computation and the CT600. A migration or AI workflow should never guess loss utilisation from a single trial balance.

Step 4: connect supplementary-page decisions

Some trial balance clues should trigger CT600 supplementary-page review. Director loan balances may point to CT600A. Group-company transactions can prompt CT600C review. R&D cost centres may require CT600L and additional information controls. Creative production income can point to CT600P.

These are review prompts, not automatic conclusions. The filing workflow should ask for evidence and approval before changing the CT600 package.

Step 5: attach iXBRL and validate the package

A CT600 filing package normally includes iXBRL accounts and computations. The accounts, computation, and return should tell the same story: same company, same period, same profit bridge, and no avoidable mismatch between attachments and CT600 entries.

Validation should run after computation updates and before client approval. Keep the validation results, reviewer notes, client sign-off, and submission response as part of the practice file.

How to enter this in Robocount

Robocount's workflow is built around structured Data Entry followed by Compute and Validate. That makes it suitable for manual practice work, spreadsheet imports, API-driven trial balance entry, or AI-assisted classification with human approval.

Use Data Entry to bring in trial balance lines and tax adjustment data.
Review mapping exceptions before running the computation.
Use notes and attachments for judgemental add-backs, allowances, loss claims, and client explanations.
Use Supplementary/Indicators to control whether specialist CT600 pages are included.
Run Compute to update taxable profit and CT600 figures from reviewed data.
Run Validate and keep approval evidence before submission.

FAQ

Can a trial balance alone produce a CT600?

Not reliably. A trial balance is an input. A filing-ready CT600 also needs tax adjustments, attachments, supplementary-page review, approval, and validation.

What should an AI workflow do with uncertain mappings?

It should flag uncertainty, request evidence, and keep the reviewer in control. Guessing tax treatment from vague account names is a poor filing control.

Where do iXBRL accounts fit?

iXBRL accounts and computations are part of the online filing package. They should be checked against the CT600 and retained with the approval and submission evidence.

Useful official references

This guide is general product and filing workflow information, not tax advice.

CT600 trial balance to tax computation workflow.