Issue 4: How Clause 2.8.5 of Schedule 2-3 applied to Volume Based Service Charges in Service Year 5
Issue 4: How Clause 2.8.5 of Schedule 2-3 applied to Volume Based Service Charges in Service Year 5
TCS contends that the meaning and effect of Clause 2.8.8 was to ensure a minimum Volume Based Service Charge for TCS in Service Year 5, to be calculated by multiplying the applicable transaction charge by 85% of Predicted Volumes. It contends that Clause 2.8.8 was not engaged unless actual volumes in Service Year 5 fell below 85% of Predicted Volumes (just as, TCS says, Clauses 2.8.4 and 2.8.5 were not engaged unless actual volumes in Services Years 1 to 4 fell outside the range 85% to 110% of Predicted Volumes). Thus if (as was in fact the case for Basics, Standard Disclosure and Enhanced Disclosure transactions) actual volumes exceeded 85% of Predicted Volumes, TCS was entitled to Volume Based Service Charges calculated by multiplying actual volumes by the applicable transaction charge. It is argued by TCS that:
As a matter of language, ‘minimum’ means minimum. On a natural and ordinary reading, the clause provided that regardless of how few transactions were actually affected in Service Year 5, TCS would be entitled, at a minimum, to Volume Based Service Charges calculated by multiplying the contractual unit charge by 85% of Predicted Volumes for that Service Year.
Moreover, paragraph 2.3.3 of Schedule2-3 provided that the Volume Based Service Charges were to be calculated by multiplying ‘the actual volume of transactions’ by the applicable Transaction Charges (i.e. the unit charges). Whilst that was said to be ‘subject to any variation to the Transaction Charges arising from the provisions in paragraph 2.8 …’ (emphasis added), it was not subject to any variation to volumes. Nothing in paragraph §2.3.3 or §2.8.8 suggests that the former ceased to apply in relation to Service Year 5.
DBS argues that in Service Year (‘SY’) 5, TCS was to be paid the applicable transaction charge (whether adjusted or not) multiplied by 85% of the Predicted Transaction Volume. It is argued by DBS that:
The wording of sub-section 2.8.8 is clear and unambiguous. The Volume Based Service Charge was to be calculated on the minimum transaction charge (85% of the predicted transactions) agreed “at the end of Service Year 4”.
Accordingly, the charge was fixed for SY5. That is consistent not just with the plain meaning of the words used, but also the fact that a reasonable observer would have understood the purpose was to provide clarity over the sums DBS would pay. The objective reason for the fix is that there was no future year in which an over or under-recovery could be clawed back.
TCS’s contention there was to be a calculation at the end of SY5 at which time the Volume Based Charge would be the higher of 85% of the predicted revenue or the actual volume times by the applicable transaction charge is wrong. Firstly, DBS point to the fact that there is no language which supports that interpretation,and say that it is contradicted by the clear language focussing on the calculation occurring at the end of SY4, at which time the actual volume for SY5 was unknown. Secondly, this would expose DBS to paying an unlimited amount of money with no possibility of recovery by adjustment in the following year. That would contradict the carefully construed Charges Variation Clause as a whole and the agreed purpose of the clause. Thirdly, TCS’s interpretation benefits only TCS, whereas the true construction is balanced and may favour TCS (if actual volume < 85%) or DBS (if actual volume > 85%).
Clause 2.1 of Schedule 2-3 requires that ‘the Authority shall pay the Service Charges to the Contractor for all operations services in each Month from the Service Commencement Date to the end of Term’. The Term (subject to any extension) was 5 years. The Service Charges shall be made up of various Charges, include ‘Volume Based Service Charges in accordance with paragraph 2.3 below’. Clause 2.3.1 sets out the table quoted above, and as also set out above, Clause 2.3.3 then requires that the Volume Based Service Charges shall be calculated each Month. For each type of transaction, the actual volume of transactions in the Month shall be multiplied by the Transaction Charges in Table 1 (during the initial 5 year Term), subject to any variation to the Transaction Charges arising from the provisions in paragraph 2.8.
Whilst cross reference to Clause 2.8 of Schedule 2-3 is made within Clause 2.3.3 of Schedule 2-3, this cross reference is made with respect to any variation to the Transaction Charges. It does not identify that Clause 2.3.3 is more widely subject to variation as a result of Clause 2.8.
Applying Clause 2.3.3 to Year 5, it would suggest that the Volume Based Service Charges shall be calculated each Month by multiplying the actual volume of transactions by the Transaction Charges (as varied by the provisions in paragraph 2.8). This would suggest that the amount of the Volume Based Service Charges will vary with actual various in volume of transactions in Year 5, as with previous years.
Notwithstanding any broader cross-reference between Clauses 2.3.3 and 2.8.8 of Schedule 2-3, it is clear that both sides contended for constructions in fact impose a further change in the manner in which the Volume Based Service Charge is calculated.
On TCS’s case, a minimum Volume Based Service Charge is calculated (by reference to 85% of the predicted volume of transactions for Year 5 multiplied by the applicable Transaction Charge). If the actual volume falls below 85% of the predicted volume, TCS is to be paid the minimum Volume Based Service Charge rather than the actual. Clause 2.8.8 is silent as to how this mechanism works on a monthly basis, or how the adjustment process works at the end of Year 5. As DBS points out, the clause does not suggest that there is some adjustment/accounting process at the end of Year 5. This is a factor which weighs against TCS’s construction.
On DBS’s case, there is, in effect, a fixed Volume Based Service Charge (again, calculated by reference to 85% of the predicted volume of transactions for Year 5 multiplied by the applicable Transaction Charge). However, this construction suffers a similar problem in that there are no express words which explain precisely how, in practice, the mechanics of the change to the ‘vanilla’ Clause 2.3.3 process actually works. Does TCS get paid accordingly to actual volumes, in accordance with Clause 2.3.3, on a monthly basis until the minimum volume is met, at which point no further payments are due? Or are the payments made in accordance with Clause 2.3.3 with an adjustment process at the end of the year to repay any sums required to be paid by 2.3.3 but which overtop the minimum Volume Based Service Charge calculated pursuant to Clause 2.8.8?
It can be seen that the interrelationship between Clause 2.3.3 and Clause 2.8.8. is poorly drafted and neither sides’ construction properly reflects a fully described and satisfactory mechanism.
However, in my judgment giving proper meaning to the word ‘minimum’ is likely to be the key to construing the intention of the parties. On DBS’s case, it is a word which is, at best, otiose and, more problematically for DBS, positively misleading in some circumstances. In circumstances where actual volumes exceed 85% of the predicted volume, the clause does not operate to provide a ‘minimum’ Volume Based Service Charge at all: indeed, it operates as a cap. It was suggested by Mr Croall in argument that the word refers to the fact that 85% is the acceptable ‘minimum’ Actual Percentage Transaction in Clause 2.8.3, but that is not what Clause 2.8.3 either expresses or implies. 85% is the bottom of the range within which there is no adjustment of the Transaction Charge. I do not regard Clause 2.8.3 as giving the word ‘minimum’ a sensible meaning within Clause 2.8.8. TCS’s submission that if the parties had intended the clause to mean what DBS contends it means, it would have most accurately used the word ‘fixed’, or no further descriptor at all, is right. In circumstances where I consider there is, in the language used, a plain indicator that TCS’s construction is preferable – in that it imbues the word ‘minimum’ with proper meaning – the fact that DBS’ construction is ‘balanced’ and might operate in either parties’ favour is not persuasive. That the adjustment is upwards only is, in fact, precisely what one would expect the implication of use of the word ‘minimum’ to be. It does not create a commercially odd outcome, insofar as relevant. Where TCS earns more, it is because it has carried out more work (and DBS has received more income).
In the circumstances, in relation to Issue 4, TCS’s construction is preferable.
- Heading
- CONTENTS
- IntroductiON
- The Factual Witnesses
- Expert Evidence
- Programming Experts
- Forensic Accounts
- The Parties Submissions
- Principles Applicable to Issues of Construction
- The Defendant’s Obligations and Responsibilities
- Clause 15
- Clause 9.5 which states
- Clause 14.5 of Schedule 2-6 which states
- The Delay and Notice Provisions
- Clause 7
- Conditions Precedent: Clauses 5 and 6
- Conditions Precedent: the authorities
- Clause 5.6
- Clause 6
- Clause 8
- Limitations of Liability
- A single or multiple caps?
- The Delay Damages cap under Clause 52.2.5
- Is TCS’s claim for loss of anticipated costs savings excluded by Clause 52?
- Compliance with Clause 5.3, Agreement and Estoppel Introduction
- Express Agreement
- Estoppel
- Introduction
- R1 B&B Delays
- Mr Britton’s First Analysis
- Mr Britton’s Second Analysis
- Conclusion on Mr Britton’s Analyses
- TCS’s submission based upon Mr Jardine’s analysis
- Responsibilities for Delay on the ‘Infrastructure’ Critical Path
- R1-D
- Compliance with Notice Provisions
- Analysis of Delays
- Up to August 2017
- From August 2017 to 19 September 2018
- Analysis
- Failed to confirm its desired functional scope of R1 Disclosure in relation to the Customer-to-Business portal and Accountable Officer’s Update Service functionality. Such confirmation was a prerequis
- Failed to make available an end-to-end test environment for the Interactive Voice Response system
- Failed to agree upon a data migration approach, without which the Claimant could not complete the build of a data migration environment so that anonymised data could be made available for testing
- Failed to ensure that relevant external stakeholders were available to participate in Final Systems Integration Testing
- Partial Termination
- TCS’s Claims
- Non-Manpower Costs
- Anticipated Cost Savings
- Summary of TCS’s Delay Claim Recovery
- DBS’s Claims
- Delay Payments
- R1-B&B Delay
- Disclosure Scotland Extension Costs – Item 1 of the Updated Schedule of Loss
- Loss of Anticipated Savings – Item 3 of the Updated Schedule of Loss
- R1-D Delay
- R0 Licence Costs – Item 4 of the Updated Schedule of Loss
- R0 Hosting and Infrastructure Costs - Item 5 of the Updated Schedule of Loss
- R0 Technology Refresh – Item 6 of the Updated Schedule of Loss
- R0 N-1 Sustainment Costs – Item 7 of the Updated Schedule of Loss
- R0 Maintenance Costs – Item 8 of the Updated Schedule of Loss
- Savings
- Introduction
- Quality-related Obligations
- Good Industry Practice and Defects
- Digital by Default Standards
- Section 71
- The Basics Portal
- Section 73
- The Barring Portal
- Section 75
- Section 76
- Barring Portal: Loss of productivity - Item 11 of the Updated Schedule of Loss
- LPF Portal
- Siebel Useability Issues
- Redaction
- Document naming, bundle creation and performance
- Adobe Licence (Item 20)
- Document Storage (Item 21)
- Other B1 Barring Quality Issues
- Scan on Demand
- Special Characters
- Letters
- Item 24 : Loss of Efficiency Claims arising out of R1 Barring Quality/Useability Issues
- N-1 Sustainment Costs
- Causation and Loss
- Exit/Service Transfer
- Identification of all services (3.2.2)
- Knowledge Transfer (3.2.6 and 3.2.7)
- Section 95
- Providing all documentation to a replacement contractor (3.2.1 and 3.2.10)
- The identification of all leases, maintenance agreement and support agreements in connection with the provision of the services (3.2.3)
- Providing any other information or assistance reasonably required by a replacement contractor (3.2.14)
- Causation and Loss
- The Security Incidents
- The Charges Variation Dispute Introduction
- Issue 1: How the amount of an ‘over-recovery of the Forecast Revenue’ (Clause 2.8.4) or ‘under-recovery of the Forecast Revenue’ (Clause 2.8.5) is to be measured
- Section 104
- Issue 4: How Clause 2.8.5 of Schedule 2-3 applied to Volume Based Service Charges in Service Year 5
- Issue 2: Whether the Predicted Volumes for Basics in Service Year 4 were 1,000,000 (TCS’s case) or 320,374 (DBS’s case)
- Conclusion on Volume Based Service Charge
- Conclusions
![HT-2020-000448 - [2024] EWHC 1185 (TCC)](https://backend.juristeca.com/files/emisores/logo_yJUntHA.png)