💷🏛️💷 HMRC - How to complete your HMRC CT600 Company Tax Return with Chat GPT + GDS CMS Critique

Описание: 🏛️ HMRC UK Corporation Tax With Chat GPT Live Walkthrough
https://siennaai.net/6M/HMRC--2017-20...
2096f2) ⚛️🚀6M – GDS CMS by Thoughtworks – Autofill Bug in HMRC: Same Problem in 2017 Still Not Fixed in 2025 – Is the Service Being Retired Because of This Bug?
Date: 14 April 2025
Author: Nick Ray Ball

🎯 Watch as GPT-4o (ChatGPT) guides Nick Ray Ball through the full process of completing and submitting two UK Corporation Tax Returns (CT600) with zero accounting background, while working hands-free from a lying position due to physical disability.

This 5-hour unedited video is the first of its kind — a real-time showcase of how AI can be used to:
• File CT600s for two companies: Cape Villas Ltd and Sienna AI Ltd
• Navigate the HMRC system more effectively than any human support
• Document live software bugs in the government’s digital CMS
• Prove that GPT-4o is a superior assistant for tax return completion

🧠 NO accounting knowledge required
🧑‍🦽 Completed while bedbound, using just one hand
🗂️ Includes timestamps, breakdowns, and real bug reporting
📢 Ideal for: SMEs, founders, finance teams, policy experts, and digital reform advocates

📌 Key Topics Covered:
Corporation Tax Return (CT600) full walkthrough
HMRC portal setup and digital activation code process
Autofill bug documented with crash at 3:33 and 4:44
GDS CMS critique and mothership CMS proposal
Use of GPT-4o as a real-time AI co-pilot
Accessibility and tech empowerment in action

________________________________________
⚠️ Overview
While filing a short-period Corporation Tax Return for Cape Villas Ltd, we encountered a serious autofill bug in the HMRC online tax return system — a system designed and operated under the Government Digital Service (GDS) CMS, originally developed by Thoughtworks. This bug replicates the exact same issue we experienced in 2017.
"Autofill fields are consistently incorrect, often pulling unrelated numbers or identifiers — including substituting the Company Registration Number (CRN) with a Government Gateway ID."
After eight years, the bug remains unresolved, and it appears that this recurring autofill issue may be one of the core reasons HMRC has now announced it will be shutting down the online CT600 filing service by 31 March 2026.
________________________________________
🎬 Incident Timeline
• 14 April 2025 – 3:05:00 into the session video
• Filing the short-period CT600 return for 12 May – 31 May 2024
• Autofill incorrectly populated the CRN field with:
"931942218480"
...instead of the correct CRN:
"14864994"
This incorrect value is a mashup of the Government Gateway ID, proving definitively that the bug misreads form history or local autofill context, and fails to validate critical identifiers.
"This is the same bug we encountered in 2017. Eight years on, it still hasn’t been fixed — despite being incredibly simple to detect and correct."
________________________________________
💻 Systemic Flaw in GDS CMS
The issue highlights a wider structural flaw in the way the GDS CMS is maintained across departments:
"The GDS does not use a centralised 'mothership' CMS architecture. Each department's version appears to be a copy-paste implementation, meaning that fixes are not propagated system-wide."
We’ve seen the same flaw replicated in:
• The Department for Work and Pensions (DWP)
• The HMCTS / Ministry of Justice
• And now again in HMRC
In contrast, UKRI's recent improvements to their digital interface show that certain departments have fixed this bug — but rather than propagating that fix across all government services, it remains siloed.
"Instead of sharing codebase improvements across the network, each fix must be manually duplicated into every departmental CMS. That never happens — so even simple bugs like autofill errors persist indefinitely."
________________________________________
🔁 The 6M Solution: Fix Once, Fix Everywhere
Our architecture under the Sienna AI 6M mothership model proposes exactly the opposite:
"One system. One fix. Everywhere."
If a bug like this autofill error is fixed in one module (say, at UKRI), the update automatically propagates to all other instances of the CMS — including DWP, HMRC, MoJ, and future digital government portals.
That’s the power of centralised version control, dynamic APIs, and modular governance-by-design.
________________________________________
🛑 The Real Reason the Service is Closing?
HMRC's notice:
"This service is closing on 31 March 2026. You will need to use commercial software..."
leads us to ask:
"Are they shutting down this service because it’s outdated — or because no one can fix its bugs anymore?"
This isn’t just inefficient — it’s a governance-level failure. And it confirms what we’ve long suspected:
"Without a mothership CMS, the government’s digital estate is built on sand. When one part breaks, they’d rather decommission the whole system than fix a single line of code."