Repayment control

Corporation Tax repayments need a client communication workflow.

A repayable CT600 is good news only if the practice controls the expectation. Keep repayment claims, bank-detail checks, HMRC evidence, and client updates together so refund questions do not become messy follow-up work.

Why repayment cases need more discipline than ordinary filing

When the CT600 shows tax repayable, the client usually wants a simple answer: how much, why, and when. The practice needs a more controlled answer: what created the repayment, how it was claimed, what bank or repayment controls applied, what HMRC evidence is held, and what follow-up remains open.

GOV.UK says companies can use the Company Tax Return to tell HMRC if they think a Corporation Tax repayment is due and how they want it paid. That makes repayment handling part of the CT600 workflow, not a separate afterthought.

Common reasons a CT600 becomes repayable

  • Tax was paid based on an estimate that was higher than final taxable profits.
  • An amended return reduces the Corporation Tax liability.
  • Loss relief, group relief, R&D credits, or other credits reduce tax payable.
  • A payment was allocated to the wrong accounting period and needs correction.
  • The client paid twice or paid after a nil or reduced liability was established.

The repayment workflow checklist

A practice-quality CT600 file should explain the repayment without exposing private bank or tax identifiers in public-facing material:

  • Confirm the accounting period and final CT600 tax position.
  • Record the reason for the repayment and the evidence behind it.
  • Check whether the repayment is expected through the return, a later amendment, payment reallocation, or HMRC account correction.
  • Keep bank-detail handling inside secure client systems, not email threads or public notes.
  • Tell the client what has been claimed, what HMRC needs to process, and who will monitor it.
  • Retain HMRC acknowledgement, repayment statement, or follow-up correspondence with the CT600 file.

Client updates should be specific

Vague updates such as "HMRC owes you money" create avoidable follow-up. A better client update explains the cause of the repayment, the return or amendment version used, whether any other tax debts may be offset first, and when the practice will next check the position.

For directors, this is also a trust issue. They may not distinguish between the CT600, payment account, repayment instruction, and HMRC processing status. The practice should separate "filed", "claimed", "processed", and "received" in plain language.

Do not leak payment identifiers in marketing or client examples

Payment references, bank details, Government Gateway details, submission references, and internal client identifiers belong in the private working file. Public content and anonymised case studies should describe the workflow without publishing operational identifiers.

Robocount marketing copy follows that same boundary: explain the control, the evidence, and the user benefit, but do not publish private identifiers used to operate the filing or repayment process.

How Robocount supports repayment follow-up

Robocount is built around the full CT600 lifecycle: preparation, review, approval, filing readiness, submission evidence, and post-filing follow-up. Repayment cases fit naturally into that lifecycle because the repayment reason is normally visible in the computation, reliefs, payment history, or amendment trail.

  • Keeps repayment positions visible alongside the CT600 and computation.
  • Supports cleaner review of amended returns and reduced liabilities.
  • Helps practices connect repayment expectations to client approval and HMRC evidence.
  • Reduces the risk that repayment follow-up is separated from the return file.

FAQ

How does a company tell HMRC it is due a Corporation Tax repayment?

GOV.UK says companies can use the Company Tax Return to tell HMRC they think a repayment is due and how they want it paid.

Should repayment bank details be included in public examples?

No. Keep bank details, payment references, account identifiers, submission identifiers, and client names out of public content. Use private client systems for operational detail.

What should a practice keep after a Corporation Tax repayment claim?

Keep the return or amendment version, computation, repayment reason, client approval, HMRC acknowledgement, repayment or account evidence, and follow-up note.

Can HMRC offset a Corporation Tax repayment against other amounts?

GOV.UK repayment guidance says companies are refunded the amount left after tax owed has been repaid. Practices should check the company's HMRC account rather than promising a fixed cash date too early.

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, amending, or promising repayment timing.