IT SYSTEM ERROR
Background
36. It is also clear that IT system, or software,
error has been another significant source of overpayments. According
to the National Audit Office, the administration of payments "suffered
from the serious problems with the computer systems during the
introduction of tax credits in April 2003", which "both
delayed the processing of claims and led to incorrect payments
being made".[58]
The NAO told us that software errors resulted in overpayments
of £184 million in 2003-04 and 2004-05, and that HMRC was
"continuing to investigate the reasons for other incorrect
payments caused by system miscalculations."[59]
The Comptroller and Auditor General's standard report on Inland
Revenue's 2004-05 accounts summarised the cost of writing off
overpayments arising from software error as follows:
In my 2003-04 report I noted that certain software
errors had resulted in overpayments calculated as £94 million
in 2003-04 of which the Department had written-off overpayments
of less than £300 totalling some £37 million. I also
noted that the Department expected further write-offs in respect
of the balance of £57 million. In addition, the Department
calculated and wrote off other overpayments of some £2 million
that it considered had been caused by software errors. The Department
calculated that [these] software errors
resulted in further
incorrect payments in 2004-05 of £7.9 million. Various other
incorrect payments have also resulted from other system miscalculations.[60]
37. In recognition of these difficulties, the Paymaster
General undertook, in her Written Ministerial Statement of 26
May 2005, that HMRC would "improve the speed with which it
identifies IT system problems and processing errors so that they
can be resolved more quickly."[61]
Difficulties with the IT system
38. At the time the new tax credits regime was set
up, it was intended that its administration would be wholly IT-based.
It is evident that the administrative process currently requires
significant human intervention. For example, when we visited the
TCO in Preston, we heard that only about 25% of all claims went
straight through the automated system without the need for manual
intervention. About 80% of new claims required intervention; about
30%-35% of claims for renewal required intervention. The Public
and Commercial Services Union (PCS) told us that the Government:
initially intended that the 'rapid data capture'
process (the conversion of written information from application
forms into electronic data) would handle around 90% of claims
without further need for human intervention. Our estimate is that
only 10% of the information is captured by this method.[62]
39. HMRC is involved in ongoing work to improve the
IT system. In October 2005, Sir David told us that HMRC had:
been trying to stabiliseand I think have been
successfulthe IT system. It is still potentially fragile
and, therefore, every time we have to do something, I approach
it in the spirit that we do not want to lose any progress that
we have made in stability.[63]
More recently, Sir David told the Committee of Public
Accounts that HMRC still did not feel it knew "enough about
the system to be clear of its resilience
it is a very complicated
system".[64] In
the course of the present inquiry, the Paymaster General updated
us on the performance of the system:
IT performance has been significantly improved
a significant new software release was introduced without a hitch
in November. Largely invisible to people outside, this will deliver
real improvements in operational performance. In total there have
been 300 improvements made to the system since April 2005.[65]
40. We received evidence from both PCS and the voluntary
sector that the IT system was continuing to cause difficulties
both for staff and claimants. PCS acknowledged an improvement
in "identification of IT system problems", but felt
that the resolution of processing errors had not similarly improved:
The computer system is not user friendly and continues
to be often unavailable at key times
Our members report
continuing problems with the interface between the [tax credits]
computer system and treatment of data that HMRC operatives are
forwarding for inclusion (such as a claimants' change of circumstances).[66]
41. Representatives from the voluntary sector referred
to many examples, generally involving the tax credits helpline,
where claimants had been disadvantaged by what appeared to be
software erroralthough, from the perspective of helpline
users, it is often difficult to tell whether it is official error
or software error which is the problem. A recurring theme was
the IT system's lack of flexibility, and the difficulty of correcting
a mistake once it had been (erroneously) entered into the systemstaff
may accept that information is wrong, but still be unable to correct
the information.[67]
The system also appears to lose claimants' records periodically,
as a representative from a Citizens Advice Bureau explained:
I used to think [the problem] was a lot administration,
a little bit computer, but I personally now believe it is a lot
computer and a little bit administration, particularly with this
issue of losing clients. There are two times of year where a lot
of clients drop off the system, particularly around the beginning
of October
I was led to believe they could not get them
back on the system. I am now told that about a quarter go back
but they cannot tell you why, but the others are all left with
manual payments
one of the suggestions at a meeting was
a to change people's national insurance numbers because that way
you could put them back on the system with a new national insurance
number.[68]
42. Mr Field mentioned an example of a claimant he
knew of who, when completing an application form, had put a line
through a section of the form to be filled in by claimants with
disabled childrento indicate that this section was not
relevant to her. Her form was read electronically as indicating
that she did have a disabled child.[69]
The Chartered Institute of Taxation (CIOT) commented on the fact
that the IT system had, on occasion, produced award notices containing
internally inconsistent informationfor example, where the
number of children has differed in different parts of the notice.[70]
The CIOT considered that the IT system should operate in such
a way that "errors like these are isolated for checking,
or are just never possible in the first place".[71]
43. The Paymaster General rejected PCS's statement
that the IT system was often not available at key times:
The computer has downtime in order for it to have
the software put on to it
I have no information
that the computer was repeatedly going down. The only incident
I can find in all of the last 12 months is that there was a period
of maybe two hours, and I cannot remember when it was, when the
system did not perform as it should have done. This idea that
it is repeatedly not available and you cannot get access I disagree
with.[72]
Terms of settlement between HMRC and EDS
44. The tax credits IT system went live in April
2003, under a contract with Electronic Data Services (EDS). This
contract ended on 30 June 2004 and was replaced by a contract
with Cap Gemini.[73]
On 22 November 2005, the Paymaster General announced that HMRC
had reached a settlement with EDS:
the aggregate settlement is £71.25 million
including an up-front payment and payments of additional amounts
over time. Details of the settlement are commercially sensitive
and therefore bound by a legal confidentiality agreement as is
normal in agreements of this nature.[74]
The Paymaster General had earlier stated that, as
at 31 August 2005, the "identifiable costs" paid to
EDS and, subsequently, Cap Gemini for running the IT system were
£236 million, exclusive of VAT.[75]
Between 2002-03 and 2004-05, the Department spent £19.7 million
on IT consultants in relation to tax credits.[76]
45. HMRC has so far received £47 million from
EDS; Sir David told us that the payment has "had the effect
of being as if it was £47 million cash", but was "funded
in different ways through different streams".[77]
£24.25 million remains outstanding. Since the Paymaster General's
November announcement, further details of the settlement have
emerged. Subsequent to our 19 April hearing with Sir David, the
Committee of Public Accounts reported to the House that "staged
payments of up to £26.5 million are contingent on EDS winning
new business with the United Kingdom Government
there is
however no guarantee that EDS will win sufficient new business
to trigger payment of the full amount".[78]
Prior to our 19 April hearing, however, the substance of the Committee
of Public Accounts' report to the House was leaked to the media.
We therefore discussed with Sir David the conditions attaching
to the payment of the remaining £24.25 million.
46. Owing to the confidentiality agreement which
formed part of the HMRC-EDS settlement, Sir David felt constrained
in what he was able to tell us about the terms of the settlement.
By way of context, he explained that the cost of taking EDS to
court over the matter was estimated at £20 million and expected
to take two years.[79]
In reaching the settlement, HMRC considered it had a choice:
we could have settled for a lower sum of money and
been certain or [taken] this mechanism [of staged payments contingent
on EDS winning new business with the UK Government] against the
threat that we did not reach a full and final settlement. There
will only be full and final settlement with EDS when we are paid
the £71,250,000.[80]
Prior to agreeing the settlement, HMRC had inspected
EDS's order book and found that it "many, many times covered"
the amount of the contingent payments. Sir David said he would
be "extraordinarily disappointed if EDS did not honour this
obligation to pay the remaining amount of money".[81]
47. We raised with Sir David the propriety of making
part of the HMRC settlement contingent on EDS's future business
with other departments of the UK Government. He stressed that
nothing HMRC had done was meant "to influence in any way
any decision [by] anybody in government to procure services from
EDS".[82] He also
contended that the terms of the settlement would not in fact influence
any decision by government as to whether to award a contract to
EDS, on the basis that:
[government] departments are under an obligation
under EU law to make value for money declarations in terms of
contract procurement
You are asking, 'When you come to
make a value for money consideration in the National Health Service,
would you factor into your calculation that there was a benefit
for HMRC?' Answer, no.[83]
48. We also questioned Sir David about who in Government
made the decision to accept the settlement with EDS. He described
the situation as follows:
we went specifically to the Treasury and to
the NAO, who went all through this in great detail
this
is an accounting officer deal. This is an accounting officer [that
is, Sir David himself] who is responsible
We talked at
the working level to the Treasury, but this was a matter for us
to determine what we thought was in the best interests of [HMRC]
I did not seek ministerial approval
The decision
to accept this deal was the decision of the Commissioners of the
Revenue. It has nothing to do with the Treasury.[84]
Our conclusions
49. On the basis of the evidence we have received,
the rate of error within the IT system seems to us to have been
significant. Just
as HMRC appears to have attempted no complete analysis of the
contribution made by official error to overpayments, so we have
seen nothing from the Department attempting to assess the contribution
made by IT system error. Again, it seems obvious to us that HMRC
must acquire a thorough understanding of the problems which have
arisen if it is to succeed in improving the administration of
the tax credits regime. We recommend that the Government undertake
a complete analysis of the incidence of IT system error and the
extent to which it causes or contributes to overpayments, and
that it publishes that analysis.
50. The settlement of £71.25 million agreed
by HMRC and EDS appears to have provided for staged payments of
up to £26.5 million which are contingent on EDS winning new
business with the United Kingdom Government. It
is clear that the IT system which EDS delivered for the running
of new tax credits was unsatisfactory in a number of respects.
We have grave concerns about the wisdom of an agreement which
then makes the payment of compensation to the affected government
department by the provider of the unsatisfactory service contingent
on that provider winning other contracts with government. Our
concern is not that we believe the contingent payments will influence
future decisions by government departments to award contracts,
but that it will be impossible to be sure that they have not.
The agreement has the appearance of impropriety, if not the fact.
51. We also
draw the attention of the House to the confidentiality agreement
which formed part of this settlement, and which so constrained
the Chairman of HMRC in his ability to respond to our questioning.
We are extremely concerned that HMRC appears to be claiming to
have effectively 'contracted out' of its obligation to be publicly
accountable for its administration and expenditure, by virtue
of having entered a private contract. The existence of such a
confidentiality requirement also makes it impossible for the House
to assess what happened in this particular case, and to seek to
draw broader lessons from it about the problematic area of government
IT contracts. We recommend that the Government ensure that this
particular settlement does not indicate the start of a trend on
the part of public bodies towards agreeing such confidentiality
requirements. We further recommend that the procurement, design,
project management and delivery of the tax credits process and
systems be independently examined by the National Audit Office,
regardless of this agreement.
9