TLF-Contract-Claims-Insight-75.jpg

Surviving Government Motions to Dismiss Based on the Sum Certain Requirement

A Contract Disputes Act (CDA) claim meets the mandatory “sum certain” requirement when the contractor has submitted to the contracting officer (CO) a clear and unequivocal statement that gives the CO adequate notice of the basis and amount of the claim. While the CDA provides no definition of a claim, the Federal Acquisition Regulation (FAR) § 2.101 defines a government contract “claim” as a written demand or assertion by a contracting party seeking, as a matter of right, the payment of money in a “sum certain.” This “sum certain” requirement contained within the FAR definition of a claim was considered jurisdictional until the Federal Circuit’s relatively recent decision in ECC International, LLC v. Secretary of the Army, 79 F.4th 1364 (2023). In the much publicized ECC decision, the Federal Circuit held that the “sum certain” requirement was not a jurisdictional prerequisite for a CDA claim but a mandatory claim-processing rule that claimants must follow. Since parties may raise jurisdictional issues at any time during appeals litigation, the ECC decision has practically limited the government’s “sum certain” challenges to motions for dismissal for failure to state a claim upon which relief may be granted, brought at the outset of the appeals litigation.

In ASBCA 63522, an opinion issued on February 14, 2024, the Armed Services Board of Contract Appeals (ASBCA) resolved one such motion to dismiss for a failure to state a sum certain in the contractor’s favor. The contract underlying the claim was a Blanket Purchase Agreement (BPA) issued by the U.S. Army to acquire material-handling equipment in Erbil, Iraq. The BPA permitted the Army to place individual call orders, each considered a separate contract. In its claim to the CO, the contractor sought an estimated $120,000 for the combined value of the two trucks that went missing in Syria. During the appeals litigation at ASBCA, the contractor provided a breakdown of the separate amounts sought for each vehicle, with an estimated value of $50,000 for a missing black water truck and an estimated $70,000 for a missing fuel truck. The contractor also requested $333,000 in unpaid lease payments for the two trucks between September 2017 and October 2022. Notably, the contractor submitted a single certified claim for $453,000 for the two trucks leased by the Army. The CO issued a final decision denying the entirety of the claim, and the contractor appealed the CO’s final decision at the ASBCA in a timely manner.

As noted, the contractor had packaged its claim as a single document requesting compensation under the BPA itself without identifying which call order corresponded to which leased truck. Consequently, the government raised a challenge on the basis that the contractor failed to meet the mandatory sum certain requirement. During the ASBCA litigation, the government alleged that the contractor had asserted two distinct claims under separate contracts and did not provide a sum certain for each distinct claim. Specifically, in its motion to dismiss for failure to state a claim, the government argued that the contractor sought costs arising from two vehicles leased under two separate contracts, thereby giving rise to two claims. In response to the government’s motion to dismiss, the contractor argued that its overarching claim specified a sum certain for each piece of equipment at issue – thereby satisfying the sum certain requirement.

The ASBCA began its analysis by stating that a dismissal based on a failure to state a claim is appropriate when the facts asserted in the complaint do not entitle the contractor to a remedy. The Board reminded the parties that for determining whether an appeal sufficiently stated a claim upon which relief could be granted, the primary document to be reviewed was the contractor’s claim to the CO rather than its complaint filed at the Board. The ASBCA also recognized that the sum certain requirement was mandatory but not jurisdictional and that the Board was required to decide on the merits of an appeal whether the claimant met the sum certain requirement in a particular case. In this case, the contractor submitted a single claim stating the total amount sought for two types of compensation, lease payments, and replacement costs of the two missing trucks. The ASBCA ruled that the contractor had satisfactorily provided a “sum certain” for the total amount sought. Furthermore, this amount provided an adequate notice of the basis and amount of the total claim to the government – thereby satisfying the mandatory “sum certain” requirement. However, it was unclear to the Board whether the Army leased the two missing vehicles under the same or different contracts. Therefore, the Board ruled that it lacked sufficient information to determine whether the contractor’s claim was one claim arising from the same operative facts or multiple distinct claims. Since this determination involved a factual dispute for the ASBCA to resolve on the merits, the Board denied the government’s motion to dismiss at this preliminary stage of the litigation.

It is unlikely that the issue of two or more distinct claims each not meeting the sum certain requirement was raised by the CO in his final decision denying the contractor’s claim in this case. Indeed, had the CO identified that the contractor’s overarching claim should have been multiple distinct claims, he should have required the contractor to provide a breakdown of the separate amounts sought for each distinct claim to resolve the alleged “sum certain” issue. On the contrary, the ASBCA decision indicated that the government argued for the first time on appeal that the contractor’s claim actually involved four distinct sub-claims. Therefore, while it may seem counterintuitive and inefficient that the government would raise the “sum certain” requirement for the first time during appeals litigation, contractors should nevertheless be prepared for such an eventuality, especially in cases where it is not clear whether the contractor should present one or several claims involving the same or similar operative facts.

This Federal Contract Claims Insight is provided as a general summary of the applicable law in the practice area and does not constitute legal advice. Contractors wishing to learn more are encouraged to consult the TILLIT LAW PLLC Client Portal or Contact Us to determine how the law would apply in a specific situation.

Related Insights

TLF-Contract-Claims-Insight-53.jpg

The government may terminate a federal contract if the contractor fails to meet its contractual obligations. The contracting officer (CO), in such cases, issues a final decision terminating the contract for default and outlines the reasons for the default. In the event of a termination for default, the government is only liable to the contractor for the portion of the contract that was already performed. While the CO may exercise discretion to terminate a contract for default, such a decision is appealable to the Board of Contract Appeals or the Court of Federal Claims (COFC) pursuant to the Contract Disputes Act (CDA). The CO’s decision to terminate may be set aside by the adjudicative forum if it is arbitrary, capricious, or constitutes an abuse of the CO’s discretion. For instance, a decision to terminate for default may be arbitrary and capricious if there is a lack of nexus between the CO’s decision to terminate the contract for default and the contractor’s performance on the contract. In such situations, while the concerned adjudicative forum may lack the ability to provide injunctive relief, it may nevertheless convert the CO’s default termination to one for the government’s convenience.

more
TLF-Contract-Claims-Insight-57.jpg

Once a contractor submits a claim to the government under the Contract Disputes Act (CDA), the government is required to provide it a copy of the contracting officer’s final decision (COFD). The receipt of the COFD by the contractor is a key event in the lifecycle of a CDA claim because it triggers the beginning of the statute of limitation period to appeal the COFD at a Board of Contract Appeals (BCA) or the Court of Federal Claims (COFC). Upon receipt of the COFD, the contractor has ninety (90) days to file an appeal at a BCA or twelve (12) months to file an appeal at the COFC. Since the statute of limitations is a condition on the waiver of the government’s sovereign immunity, adjudicative forums enforce it strictly as long as the government can establish, by evidence, the date on which the contractor received the COFD. The Federal Acquisition Regulation (FAR) § 33.211(b) obligates the contracting officer (CO) to furnish to the contractor a written copy of the COFD by certified mail, return receipt requested, or by any other method that generates evidence of receipt. Notably, the CO’s obligation to furnish a copy of the COFD to the contractor applies equally to all final decisions on claims, regardless of whether the contractor or the government initiates the claim.

more
Shutterstock_530695792.jpg

To file appeals under the Contract Disputes Act (CDA), contractors are required to first submit their claims to the contracting officer (CO) for a contracting officer’s final decision (COFD). The Federal Acquisition Regulation (FAR) § 33.211(a)(4)(v) requires COs to include in their final decisions a notice detailing the contractor’s rights to appeal the COFD at the Boards or the COFC. Such notice of contractor appeal rights should include language substantially similar to the following:

“This is the final decision of the Contracting Officer. You may appeal this decision to the agency board of contract appeals. If you decide to appeal, you must, within 90 days from the date you receive this decision, mail or otherwise furnish written notice to the agency board of contract appeals and provide a copy to the Contracting Officer from whose decision this appeal is taken.”

As detailed in the appeal rights notice, the contractor has ninety (90) days to appeal the COFD to an appropriate Board of Contract Appeals or up to twelve (12) months to appeal the decision at the Court of Federal Claims (COFC). The receipt of the COFD by the contractor triggers the beginning of the CDA appeals limitations period, within which the contractor must appeal the COFD at a Board of Contract Appeals (BCA) or the Court of Federal Claims (COFC). Notably, in cases where the government issues a decision terminating a contract for default, the receipt of notification of the CO’s decision to terminate the contract begins the CDA appeals limitation period. Such a default termination notice must typically contain the contractor appeal rights language detailed above. However, the omission of the appeals rights language in the termination notice does not, by itself, negate an otherwise final decision. Additionally, the lack of such an appeal rights notice also does not stop the receipt of the COFD from triggering the CDA appeals limitation period – unless the contractor can demonstrate detrimental reliance or prejudice stemming from the omission of such notice.

more
TLF-Contract-Claims-Insight-66.jpg

Software manufacturers that provide commercial software to the government via pre-approved intermediary software vendors on the General Services Administration (GSA) Federal Supply Schedule (FSS) do not contract directly with the federal government. Due to this lack of privity of contract with the government, such software manufacturers are unable to bring direct contract claims against the government under the Contract Disputes Act (CDA). Since the software manufacturers’ end-user licensing agreement (EULA) is typically incorporated into the government contract and dictates the government’s use of the commercial software – the government’s violation of the EULA is considered a non-frivolous cause of action for a breach of contract claim. However, the Civilian Board of Contract Appeals (CBCA) refused to recognize the right of software manufacturers in such situations to bring a direct CDA claim when the intermediary GSA FSS software vendor does not sponsor their claim against the government.

In the underlying claim at issue, the software manufacturer had alleged that end users at the Food and Drug Administration (FDA) violated its EULA in 2015. The claim was not sponsored by the GSA FSS software vendor. The software manufacturer alleged that as part of FAR Part 12 acquisition of software licenses, FDA end users owed it a freestanding obligation, as they had “clicked” a box representing their agreement to the terms of the EULA. According to the software manufacturer, this freestanding obligation owed by FDA end users, created a privity of contract between the software manufacturer and the FDA. Meanwhile, the GSA and the FDA did not deny the software manufacturer’s allegations concerning the specific acts of the FDA end users leading to the alleged violations of the EULA. However, the agencies generally denied violating any legal obligations to the software manufacturer citing a lack of privity between the government and the software manufacturer, and the GSA FSS software vendor’s lack of sponsorship of the software manufacturer’s claim. The software manufacturer’s January 2019 appeal at the CBCA was dismissed by the Board for a lack of jurisdiction. The software manufacturer appealed the CBCA’s dismissal at the Federal Circuit. In March 2024, the Federal Circuit in Avue Technologies Corp. v. Secretary of Health & Human Services, 96 F.4th 1340 (Fed. Cir. 2024) (covered here) vacated and remanded for the CBCA to consider as a merits issue, whether the software manufacturer was a party to – or otherwise had enforceable rights pursuant to the “procurement contract” – defined by the Federal Circuit as the software manufacturer’s EULA in addition to the underlying GSA FSS or task order contract.

more

Surviving Government Motions to Dismiss Based on the Sum Certain Requirement

TILLIT LAW Federal Contract Claims Insights