Payment workflow

CT600 payment reference reconciliation for practices and directors.

A practical guide to Corporation Tax payment references, nil-to-pay cases, overpayments, repayment details, client updates, and privacy-safe post-filing evidence.

Why the payment reference deserves its own check

A CT600 workflow does not end when the return is filed. The company still needs the right payment status, the right reference, and a clear record of what the client was told. HMRC guidance says the Corporation Tax payment reference is 17 characters and changes with each accounting period.

That means saved bank payees can be dangerous. If a company or practice reuses the previous period's reference, the payment may be delayed or allocated incorrectly. For accountants, that can turn a clean filing job into a messy post-filing support issue.

What to reconcile after the CT600 is ready

Payment reconciliation should be a structured final step, not an afterthought in the covering email. The reviewer should know whether the company has tax to pay, nothing to pay, an overpayment, or a repayment claim.

  • Tax due per the final CT600 and computation.
  • Accounting period covered by the liability.
  • Correct 17-character payment reference for that accounting period.
  • Payment deadline and whether the client already paid anything relevant for the period.
  • Client instruction: pay, no payment due, overpayment expected, or repayment requested.
  • Evidence retained: filing acknowledgement, computation, payment instruction, and client approval.

Nil-to-pay does not mean no communication

Nil CT600 cases still need a clean client message. If the return shows no Corporation Tax to pay, tell the client why: loss position, reliefs, prior payment, repayment offset, or genuinely no taxable profits. Keep the filed computation and the client instruction together.

For owner-managed companies, this reduces confusion when HMRC reminders arrive or the director logs into the Government Gateway and sees an old balance. The practice file should show the exact period and the filed result.

Overpayments and refund details

GOV.UK guidance says companies can use the Company Tax Return to tell HMRC if they think they are due a Corporation Tax repayment and how they want it paid. It also says including bank details on the return can help HMRC repay amounts owed into the bank account.

That creates a privacy control. Bank details, account numbers, sort codes, repayment nominees, and Government Gateway records are sensitive operational data. They may belong in the secure filing workflow, but they should not be pasted into public notes, marketing screenshots, or casual client updates.

Payment reference workflow

  • Confirm the final CT600 liability after all supplementary pages and computations are reviewed.
  • Identify the correct accounting-period payment reference from HMRC correspondence or the company tax account.
  • Compare any pre-existing bank payee reference against the current-period reference before the client pays.
  • Record whether the company has paid, needs to pay, has nothing to pay, or expects a repayment.
  • Send the client a period-specific payment instruction without exposing unnecessary identifiers.
  • Keep HMRC acknowledgement and payment evidence with the final approval pack.

How Robocount supports post-filing control

Robocount is built around the full CT600 workflow: preparation, review, validation, filing, evidence, and post-filing control. Payment reference reconciliation belongs in that same workflow because it connects the filed return to the client's real cash movement.

  • Keeps payment status visible beside the CT600 computation and filing evidence.
  • Supports accountant review of nil-to-pay, overpayment, repayment, and tax-due outcomes.
  • Helps teams keep sensitive payment identifiers inside controlled records rather than scattered messages.
  • Works for practice-led filings and API-led workflows where downstream systems need a clear status.
  • Bridges filing evidence, client approval, and post-filing follow-up in one Corporation Tax workflow.

FAQ

Is the Corporation Tax payment reference the same every year?

No. HMRC guidance says the 17-character Corporation Tax payment reference changes with each accounting period. Check the current period before paying.

What happens if the wrong reference is used?

HMRC warns that payments may be delayed if the wrong reference is used. The practical fix is to keep the period-specific reference in the approval and payment instruction workflow.

Should repayment bank details be included in client emails?

Avoid unnecessary exposure. Bank and repayment details are sensitive. Keep them inside the secure return workflow and only share what the client needs to review or approve.

Useful HMRC references

This guide is general product and filing workflow information, not tax advice or payment advice. Always check the current HMRC account and payment reference for the specific company and period.