Vogon International Ltd. v The Serious Fraud Office

Factual and Procedural Background

The dispute arises from the interpretation of the charging provisions under Contract 38118B, entered into between Plaintiff and Defendant for electronic data processing services related to an investigation conducted by Defendant. Defendant, during an investigation, obtained electronic material stored on tapes containing backups from two Microsoft Exchange email servers ("the Servers"). Due to internal workload constraints, Defendant engaged Plaintiff, an external contractor, to convert these backups into an accessible format within a tight deadline.

Initially, Contract 38118 was formed for certain restoration services, which proceeded without issue. Subsequently, Contract 38118B was concluded for additional work ("the Work") involving the extraction and processing of individual PST files from the backups. Plaintiff completed the Work by the agreed deadline and invoiced Defendant a substantial sum based on a per "database" charge. Defendant disputed the invoice, contending that "database" should be construed as referring to the Servers themselves rather than each individual backup file, resulting in a significantly lower payable amount.

Both parties presented expert evidence on the technical meaning of "database" in the context, but the court found this evidence of limited assistance. The case thus turned on the proper construction of Contract 38118B and the meaning of the term "database" within it. Alternative claims by Plaintiff alleging mistake and estoppel were also pleaded but ultimately abandoned.

Legal Issues Presented

1. What is the proper construction of the term "database" in the phrase "per database" as used in Contract 38118B?
2. Whether Plaintiff is entitled to recover the invoiced amount calculated on a per backup file basis or a lesser amount calculated per Server?
3. Whether any alternative claims of unilateral mistake, lack of meeting of minds, uncertainty, ambiguity, or estoppel affect the validity or interpretation of Contract 38118B?

Arguments of the Parties

Plaintiff's Arguments

• The natural and ordinary meaning of "database" includes each individual backup file/session of email data from the MS Exchange Servers, as supported by dictionary definitions.
• The wording of the quotation and contract distinguishes between "MS Exchange Database" (referring to the Servers) and "database" (referring to individual backup files), as evidenced by the itemised charging structure.
• The commercial purpose of the contract was to provide readable data from each backup file, not merely to recreate the Servers, supporting a per backup file charging basis.
• Correspondence and prior quotations indicate that charges were contemplated on a per backup set basis.
• Alternative claims of mistake and estoppel were pleaded on the basis that Defendant either knew or ought to have known Plaintiff's intended charging basis, and Defendant accepted services beyond the scope originally authorised.

Defendant's Arguments

• The term "database" in the contract should be construed as referring to the Servers from which the backup data originated, not each individual backup file.
• Charging on a per Server basis is consistent with the contract language, the covering letter, and the commercial context.
• Expert evidence supports the view that a backup file is not a "database" in the relevant sense, as it requires restoration before it can be accessed or manipulated.
• The alternative claims of mistake and estoppel lack legal foundation and were not supported by evidence that Defendant had knowledge of any error or different intended meaning.

Table of Precedents Cited

Precedent	Rule or Principle Cited For	Application by the Court
Investors Compensation Scheme Ltd. v. West Bromwich Building Society [1998] 1 WLR 896	Guidelines for contract construction focusing on contextual and purposive interpretation.	The court applied Lord Hoffman's principles to interpret the term "database" in the contract, emphasizing context over literal dictionary meanings.

Court's Reasoning and Analysis

The court's analysis centred on the proper construction of the term "database" in Contract 38118B, particularly in the phrase "per database" used as the basis for charges. The court acknowledged that "database" lacks a single fixed meaning and depends on context. Expert evidence confirmed that a backup file is not typically regarded as a "database" because it must be restored before access or manipulation.

The court rejected Plaintiff's argument that the contract language clearly distinguished between "MS Exchange Database" (the Servers) and "database" (backup files). It found that the natural reading of the contract, the accompanying covering letter, and the commercial context pointed to "database" meaning the Servers themselves. The court noted that the breakdown of charges into three stages was not inconsistent with this interpretation, as the first stage charged a lump sum irrespective of the number of Servers.

The court also found that the commercial purpose of the contract did not dictate the charging basis and that multiple remuneration models could have applied. The court was unpersuaded by Plaintiff's alternative claims of mistake and estoppel, considering them legally unsustainable and unsupported by evidence.

Further, the court found that the conduct and contemporaneous understanding of Plaintiff's representatives did not reflect the construction they later advanced. Instead, evidence showed an opportunistic attempt by Plaintiff to inflate charges by redefining "database" to mean each backup file, exploiting Defendant's perceived commercial naivety.

Holding and Implications

The court held that the term "database" in Contract 38118B refers to the Servers, not individual backup files, and accordingly Plaintiff is entitled only to payment calculated on that basis.

The court ruled that Defendant's liability for the Work undertaken by Plaintiff is limited to £22,500 plus Value Added Tax, rejecting Plaintiff's claim for the higher invoiced amount.

No broader legal precedent was established; the decision directly affects the parties' financial obligations under Contract 38118B and clarifies the interpretation of "database" in this contractual context.