• Increase font size
  • Default font size
  • Decrease font size
Apogee Consulting Inc

Marines Are Made of Tougher Stuff Than You or I

E-mail Print PDF

Garst

USMC Corporal Matt Garst demonstrated several things last June during a patrol in Southern Shorsurak, Afghanistan.

First, he demonstrated that metal detectors don’t always identify improvised explosive devices (IEDs)—especially when they are buried deep in the ground as improvised landmines.

Second, he demonstrated that Marines are made of tougher stuff than you or I, as the IED (comprised of three liters of explosive) detonated directly beneath Cpl. Garst’s feet and blew him, unconscious, at least 15 feet, “where he landed on his limp head and shoulders before immediately standing back up”—according to this story.

And what was Cpl. Garst’s reaction to nearly being killed? According to the story—

‘It pissed me off,’ he said. He directed his men to establish a security perimeter while letting them know in his own way that he was OK.



‘[What are you looking at?]’ he said. ‘Get on the cordon!’

The story continues—

Once EOD cleared the area, Garst led his squad the four miles back to their observation post — just hours after being ragdolled by an IED blast.



‘I wasn’t going to let anybody else take my squad back after they’d been there for me,’ he said. ‘That’s my job.’


The next day Garst awoke with a pounding headache and was as sore as he’d ever been in his life. ‘Just getting up from trying to sleep was painful,’ he said.

But he saw no reason being sore should slow him down. He popped some ibuprofen and after a day of rest, Garst was back out on patrol ….

Congratulations Corporal Matt Garst, Company L, 3rd Battalion, 3rd Marine Regiment. You are one lucky Marine.

 

Just Another Day in the Life: Embezzlement and Procurement Fraud

E-mail Print PDF

Internal_Controls

Ho, hum. One story of embezzlement and another story of procurement fraud. Just another day in the life of a government contractor….

But wait!

These two stories are not about government contractors!

As we’ve said many times on this site, not all stories of waste, fraud, and abuse take place in the government contracting arena. We believe that as much wrongful behavior takes place within the government and/or military—or within the commercial marketplace—as takes place in the Federal contracting domain. It’s just that government contractor waste, fraud, and abuse makes such a delectable sound bite for certain politicians.

Today we bring you two stories to support our assertion.

First, we link to a recent story at GovExec.com about Sheila Ann Howard, age 54, of Capitol Heights, Maryland. According to the story, Ms. Howard was charged with embezzling $149,459 from the Federal Emergency Management Agency (FEMA) over a 15-month period.

Ms. Howard has been employed by FEMA since 1990. Her current title is Human Resources Specialist, a position she has held since 2008. As part of her duties, Ms. Howard “manually inputs payments into FEMA’s Special Payroll Processing System (SPPS). SPPS … allows the establishment, adjustment, inquiry, retrieval, and deletion of certain manual payment transactions.” Here’s the criminal affidavit from which we draw the foregoing quote and other facts we are reporting herein. (Tip of the hat to GovExec.com for providing it.)

According to the complaint, FEMA’s SPPS transactions include “cash awards and special bonuses, compensatory time payments, and restored annual leave payments that cannot be processed through the National Finance Center (NFC) payroll system.” Ms. Howard allegedly used her SPPS access to process fraudulent payments that were subsequently deposited into bank accounts to which she had access.

The GovExec.com story reported that Ms. Howard, “allegedly submitted these fraudulent payments in the names of 16 former FEMA employees and one current agency employee. Law enforcement contacted seven of the former employees who, according to the complaint, said they did not receive any of the funds or recognize the accounts into which Howard allegedly deposited the money.”

Did FEMA’s internal controls catch Ms. Howard? Was there proper segregation of duties or supervisory reviews of the “manual payment transactions”? Did the banks report a pattern of suspicious activity to the proper authorities? Apparently not.

Ms. Howard’s alleged wrongdoing came to light because a former FEMA employee received a 2010 W-2 indicating wage amount(s) that didn’t seem right. According to GovExec.com –

One of the former employees, who court documents identify by the initials R.P., sent an email to FEMA about a mysterious 2010 W-2 that she received from the agency for wages totaling $9,598.50. According to the payroll system, the money was to compensate R.P. for unused annual leave when she retired in 2009. But R.P. already had been compensated for her unused leave at the time of her retirement.

R.P reported it and a review of all of Ms. Howard’s manual SPSS transactions revealed the pattern of alleged embezzlement. To make matters even worse, one of the bank accounts used to receive the allegedly wrongful payments was under the name of “O.W” who is Ms. Howard’s co-worker at FEMA. So there was (allegedly) collusion involved here as well.

Our second story was brought to our attention by the Society of Corporate Compliance and Ethics (SCCE). A routine email newsletter linked to this story at The Seattle Times, reporting that a (now) ex-Microsoft manager had been charged with three counts of wire fraud.

According to the story, Robert Curry, who had been fired by Microsoft in January 2011 and was being sued by his former employer for defrauding it of “nearly $450,000”, had been a Director of Business Development for Microsoft’s Strategic Partnerships Team. He allegedly used his position and influence to persuade “unwitting vendors to cut him checks for services that were not provided to the company.”

What?

Apparently, Mr. Curry (allegedly) persuaded suppliers to cut him checks that were to be used to purchase items from other vendors for Microsoft’s use. For example (according to The Seattle Times story)—

Curry solicited money from one vendor, a manpower firm called Pentad, purportedly to pay another vendor for audio equipment for Microsoft, the complaint said. He allegedly told Pentad's managers that he needed the checks because of Microsoft's ‘slow purchase-order system.’ The complaint says Curry told Pentad officials that they should just bill Microsoft for the reimbursement as if it was billing for manpower services, not audio equipment.



Curry also allegedly had vendors bill Microsoft for ‘bounty fees’ related to the distribution of its Bing toolbar when they had nothing to do with it, according to the charges.

What did Mr. Curry do with his allegedly ill-gotten money? According to the story, he “would then use the checks to buy personal items, including expensive audio equipment for a new home.” In addition, “he used more than $150,000 of money allegedly bilked from Microsoft to invest in a struggling Seattle audio company, according to the complaint.”

Apparently this guy had a real thing for audio equipment….

A little bit of Googling turned up some more details of the situation.

Over here we learned that—

Curry formed the company Blu Games as a false distributor of the Bing Toolbar browser plug-in and billed Microsoft, through a contractor, based on fabricated invoices. As part of the alleged scheme, Microsoft says, Curry used fraudulent business contracts and forged his supervisor’s signature.

We also learned that—

Around Nov. 10, Curry got his manager to open a $600,000 purchase order for Pentad’s new-found Bing toolbar distribution, according to the lawsuit. About a week later … Curry told Pentad that Resolution Audio and his new front company, Blu Games, had ‘generated hundreds of thousands of downloads of the Bing toolbar, and … were entitled to $183,585 and $152,200 respectively,’ … Neither company had bona fide toolbar-distribution contracts.



Pentad hand delivered both checks to Curry, and then invoiced Microsoft for a reimbursement of $450,918 plus a fee that Curry computed for $60,132…. Microsoft paid Pentad back $388,000 after discounts.



Curry allegedly upped the ante by telling Microsoft that Pentad’s purchase order needed to be increased to $3.7 million…. Along with the request, Curry submitted a distribution agreement between Pentad and Microsoft that included a forged signature of his manager, according to the lawsuit. Microsoft’s Finance Group approved the increase.

We could not determine how Curry was caught, but indications were that it was the high dollar value of the transactions that surfaced them to management’s attention.

Interestingly, one comment under The Seattle Times story had this point to add—

I have been a Microsoft vendor and their ridiculously slow payment process makes them the perfect target for this kind of scam. I don't condone the theft but I can't understand how a company like Microsoft can be so rude in dealing with their vendors. I solved my problem I now refuse to do business with them.

So to wrap this article up, let’s note that implementation of proper controls and segregation of duties—including routine reviews of manual payments and supplier purchase orders—ought to be a part of every organization’s compliance regime. But sadly, not enough organizations consider the costs of implementing such controls to be a value-added investment that pay for itself many times over, through prevention or detection of wrongdoing.

 

German Company Tripped-Up by False Claims Pays $9.1 Million to Settle

E-mail Print PDF

Following on the heels of yesterday’s story of Verizon’s FCA settlement comes today’s story about the German security firm, Securitas GmbH Werkschutz (Securitas). The U.S. Department of Justice announced on April 5, 2011, that Securitas agreed to pay the US Government €6,529,042 (US $9.1 million) to resolve allegations that it billed the U.S. Army for hours not actually worked guarding Army installations in Germany.

According to the DOJ press release, Securitas had filed claims against the Army in the U.S. Court of Federal Claims, “seeking additional compensation under one of the contracts at issue.” The press release valued the Securitas claims at $5.7 million and referenced the case Securitas GmbH Werkschutz v. United States, Nos. 07-255/6/7C (Fed. Cl.). As part of its defense, the U.S. filed counterclaims alleging fraud under the False Claims Act, “other anti-fraud provisions, and common law.”

Apparently, the U.S. counterclaims scared Securitas. In addition to paying to settle the fraud charges, Securitas also agreed to dismiss its claims against the Army, according to the press release.

The lesson here is that companies filing suit against the U.S. Government need to make sure that their own house is in order before proceeding.

 

ASBCA Decision Continues Trend of Courts Eroding DCAA’s Approach to CAS Cost Impact Calculations

E-mail Print PDF

Six years ago (in 2005) the FAR Councils published significant revisions to the “CAS Administration” portion of the FAR—specifically, FAR 30.6 and the related FAR 52.230 CAS solicitation provisions and contract clauses. The revisions were hated by industry. Promulgating comments from the time include the following summary of public input regarding the proposed rule—

One respondent stated that the proposed rule is unnecessarily complicated and does not address the major reasons that the current process does not work. Two respondents asserted the proposed rule is so detailed and prescriptive that CFAOs will be unable to exercise good business judgment and consider the unique aspects of each contractor’s business environment in settling issues. Another respondent stated that the highly prescriptive nature of this regulation will impede the expeditious and fair resolution of CAS issues. The respondent stated that CFAOs will interpret the proposed rule as significantly decreasing the flexibility regularly exercised under the current regulation. … Four respondents commented that the cost-impact calculation should not include closed contracts or years with final negotiated overhead rates.

The response of the FAR Councils to the public comments/concerns was terse: “Nonconcur.” The FAR Councils were going ahead with the rulemaking despite industry’s grave concerns. Importantly, among those industry concerns were problems with the proposed approach to calculating “increased costs in the aggregate.” As our readers will understand, that is a critical aspect of the cost impact analysis since, when a contractor makes voluntary (aka, “unilateral”) changes to its cost accounting practices, the Government is prohibited (by statute) from paying “increased costs in the aggregate” as a result. The problem was that the term lacked a precise definition in the CAS regulations and the FAR Councils had made up their own definition—in brazen defiance of the CAS Board authorizing statute, which reserved the right to interpret CAS regulations exclusively to the CAS Board.

Six years of history has shown the prescience of industry’s concerns. CAS administration issues remain among the most contentious and difficult to resolve of any issues between contractors and Government. Many—if not all—CAS-covered government contractors have a backlog of CAS issues that have lain unresolved for many years. In fact, the backlog of unresolved CAS issues has grown to such an alarming extent that, quite recently, the DOD initiated a special “Cost Recovery Initiative” to push their resolution.

Adding to the myriad problems inherent in resolving cost impacts is troubling, and wrong-headed, DCMA and DCAA guidance. The DCMA guidance was issued by the DOD Directorate of Procurement and Acquisition Policy (DPAP) in 2002 and was immediately met by a firestorm of criticism from both industry and legal practitioners. Fortunately, then DPAP Director Deirdre Lee issued subsequent guidance that helped assuage the problems her Directorate had caused. According to the supplemental guidance, Contracting Officers were not permitted to cite to the original DPAP guidance memo as support for their positions; they were required to cite to the CAS regulations themselves. (We note that the DCAA website lists the 2002 DPAP memo under “open audit guidance” but fails to list DPAP’s subsequent modification to it ….)

DCMA’s problems have been exacerbated by largely unwarranted criticism with politicians such as Senator Claire McCaskill (who recently said in a hearing, “contracting officers lose objectivity because they get too friendly with the contractors they oversee and build connections with the companies as business partners, and therefore lighten up on tough independent supervision."). The criticism has resulted in an excessively risk-adverse culture where nearly every significant administrative contracting officer (ACO) decision has to be reviewed by a Board of Review—and often by multiple Review Boards. Any failure to rubber stamp a DCAA audit finding—no matter how incorrect it may be—is subject to a lengthy bureaucratic “dispute resolution process” that puts the ACO squarely in the cross-hairs of his or her headquarters. The only smart move at DCMA these days, with respect to controversy between DCAA and the contractor, is to delay or defer any decision that might engender criticism. Thus: the smartest action for a career ACO to take is no action.

DCAA’s actions in the CAS administration process create even more problems than DCMA’s inaction. Let’s dig into this aspect a little bit.

DCAA’s guidance to its auditors implementing the 2005 FAR Part 30 revisions was issued via MRD 05-PAC-041(R), dated June 6, 2005. That audit guidance is still the agency’s official policy, and still listed under “open audit guidance” on the DCAA website. Looking at that audit guidance, one thing seems clear—the 2005 FAR revisions were driven by DCAA’s view of the world. In support of that assertion, note the following comment in the MRD’s Summary section—

The significant revisions to FAR Part 30 pertain to the process for determining and resolving the cost impact on CAS-covered contracts and subcontracts when a contractor makes a change to a cost accounting practice or fails to comply with CAS. Substantive changes have also been made to FAR Part 30 by adding definitions of pertinent terms and delineating the processes for administering cost accounting changes and noncompliances. The revised FAR Part 30 provides the process of calculating and resolving cost impacts. The 5-step process for calculating cost impacts provided in the audit guidance issued in February 2000, and incorporated in CAM 8-503, reflects the concept of calculating cost impacts promulgated by this revision to FAR Part 30.

In other words, DCAA’s “5-step process for calculating cost impacts”—issued in 2002—was so attuned to the FAR Council’s future “significant revisions”—issued in 2005—that no significant revision to DCAA’s audit procedures was required to implement the FAR procedural revisions in that complex area.

Without digging too deep into the hole, DCAA’s five-step process is summarized as follows:

  1. Compute increased/decreased cost estimates and/or accumulations for all affected CAS-covered contracts and subcontracts.

  2. Combine impacts by contract type (flexibly priced and fixed-price).

  3. Net the impacts within each contract type together (including impacts to profit/fee/incentives) to determine increased or decreased costs paid by the Government for each contract type.

  4. Determine the increased costs paid by the Government in the aggregate by combining across contract groups the increased/decreased costs paid by the Government for both contract groups, as determined in step 3.

  5. Settle the impact.

As we’ve noted before, DCAA’s audit guidance is problematic. Among the many problems is that it treats impacts from voluntary/unilateral changes the same as it treats impacts from noncompliances. It also has problems with the definition of “affected” CAS-covered contract and tells auditors to look at future impacts on contracts that haven’t yet been awarded to the contractor, as well as to impacts of contracts that have been long completed and closed, when determining the cost impact of CAS administration issues on “affected” CAS-covered contracts.

In March 2006, the U.S. Court of Federal Claims dealt a body blow to the DCAA’s audit guidance. Judge Allegra, writing for the Court, found that cost increases on one contract type could be reduced or offset by cost decreases to another contract type. The Court found that—

Notably, there is no hint in the preamble that this regulation requires a contractor to reimburse the government fully for increased costs under a cost reimbursement contract if the same CAS violation had the effect of decreasing costs in other fixed-price contracts. Such an interpretation of 48 C.F.R. § 9903.306(b), indeed, seemingly would violate the aggregation principle of 41 U.S.C. § 422(h), rendering the regulation suspect. … Fortunately, that is not a problem here, as defendant’s interpretation of the regulations is – in a word – wrong. …

Based upon … the plain wording of the statute and FAR provisions at issue, defendant [the government] is incorrect in suggesting that decreased costs associated with other fixed-price contracts it had with Lockheed cannot have the effect of diminishing or even eliminating the cost increases associated with the noncompliance of the CAS in question. Were defendant correct, a contractor that used a computer only to service government contracts might still end up owing the government increased costs for a CAS violation, even if, rather than using that computer in a flexibly-priced contract as forecasted, the contractor instead used the computer entirely for other fixed-priced government contracts. This result, of course, would be anomalous and provide the government with a windfall. More importantly, it is precisely the result that Congress sought to avoid in admonishing that – “[i]n no case shall the Government recover costs greater than the increased cost . . . to the Government, in the aggregate, on the relevant contracts subject to the price adjustment.” 41 U.S.C. § 422(h)…

(Ironically, the Judge used the DCAA’s own audit guidance to support his decision.)

More recently, in June 2010, the U.S. Court of Appeals (Federal Circuit) ruled that DCAA’s interpretation of what contracts were “affected” CAS-covered contacts was—in a word—wrong. As we reported at the time—

… the Appellate Court upheld the ASBCA’s finding that a contract that has been repriced using the changed cost accounting practices should not be included in a contractor’s cost impact analysis.  Once the contract’s estimated cost and/or price had been renegotiated to include the cost impact, it was no longer an “affected contract” and was properly excluded from the various cost impact analyses negotiated between the CFAO and the contractor.

Even more recently, in March 2011, the Armed Services Board of Contract Appeals (ASBCA) handed the Raytheon Company an important victory and, in the process, further eroded the government’s problematic interpretations of the CAS administration process.

Here’s a summary of the decision by the attorney who represented Raytheon, Paul Pompeo of the firm Arnold & Porter.

Here’s a link to the actual ASBCA decision—ASBCA No. 56701 (which you won’t find on the ASBCA site at this time).

A quick summary of the case: Raytheon changed its method for calculating the “actuarial value of assets” (AVA) for one of its pension plans. The result of this voluntary (or unilateral) change was to immediately decrease the amount of pension plan costs the company measured and recorded, and priced and billed. To be clear: pension costs decreased on both flexibly priced and fixed-price contracts.

Raytheon submitted a cost impact analysis (a “Gross Dollar Magnitude” or GDM analysis) that showed no increased cost to the Government because Raytheon set-off the cost decreases on FFP contracts against the (larger) cost decreases on its flexibly priced contracts. (Readers should note that cost decreases on FFP contract types are treated as “cost increases” to the government in the cost impact calculation.)

Naturally, DCAA had a problem with Raytheon’s methodology.

As Mr. Pompeo wrote—

The Defense Contract Management Agency (DCMA) made a claim for over US$40 million plus interest from Raytheon—the amount by which the government calculated that the pension costs, incorporated into Raytheon’s existing fixed-price contracts, exceeded the actual costs incurred under the new AVA method. The government excluded from its calculation, however, the over US$57 million by which its pension contribution costs would decrease on flexibly priced contracts. The government argued that actual pension costs would be recovered under flexibly priced contracts, thus, there should only be an adjustment to fixed-price contracts. The government further argued that Raytheon would have an opportunity to charge the same pension costs under the current fixed-price contracts on some future contracts.

So the government wanted Raytheon to fork over $40 million related to “increased costs” on the FFP contracts but it was fine keeping the $57 million in decreased costs—costs that Raytheon would not be billing to the government—on the flexibly priced contracts. DCAA justified its position because those decreased costs eventually would be billed on future contracts. (Note that position was consistent with the “problematic” audit guidance discussed above.)

Consistent with DCMA’s risk-adverse culture that encouraged ACO’s to “rubber-stamp” DCAA findings, Raytheon’s Corporate Administrative Contracting Officer (“CACO”) “adopted the findings and conclusions of the DCAA audit report, and demanded payment by Raytheon of $40,689,388 with compound interest from 27 January 2005 as a price adjustment for increased costs to the government, in the aggregate ….”

Fortunately, the ASBCA found “no merit” to the government’s arguments. It offset the cost increases on the FFP contracts with the cost decreases on the flexibly priced contracts, and found that Raytheon owed the government nothing. Moreover, it expressly dismissed the government’s notion that future contracts should be taken into consideration in the contractor’s cost impact analysis as being “entirely speculative,” and said that “the price adjustment for consideration here is limited to the CAS-covered contracts in effect at the time the accounting change was made.”

As Mr. Pompeo wrote—

For years, the question of what constitutes ‘increased costs in the aggregate’ under the CAS has escaped precise definition. There has also been uncertainty about what constitutes an ‘affected contract’ for purposes of contract price adjustments under the CAS. In addition, the government has been applying its newly created theory of impact on future fixed-price contracts in the determination of increased costs in the aggregate to other contractors. The ASBCA’s holding establishes a straightforward rule that the determination of ‘increased costs in the aggregate’ means all CAS-covered contracts, but only those in existence at the time of the change in cost accounting practice—there cannot be consideration of future contracts that postdate the change.

For years, the government has consistently misinterpreted the CAS Board regulations regarding how to determine “increased costs in the aggregate” for purposes of ensuring that there are no overpayments on CAS-covered contracts when a contractor voluntarily changes its cost accounting practices. The government’s misinterpretation has created chaos and led to a huge backlog of CAS-related issues and disputes. Fortunately, the Courts are helping to correct the misinterpretations and, generally, providing relatively clear guidance that CAS practitioners can follow.

Unfortunately, such corrections come at a very high price and take years to be issued. Meanwhile, DCAA and DCMA continue to add to the backlog of unresolved issues.

 

Verizon Pays $93.5 Million to Resolve False Claim Suit

E-mail Print PDF

Sword_of_Damocles

On April 5, 2011, several related things happened, according to this article at the Legal Times blog.

  • A qui tam suit alleging violations of the False Claims Act was unsealed in U.S. District Court in Washington, D.C.

  • The Department of Justice announced its intention to intervene in the whistleblower’s suit.

  • Verizon and the DOJ entered into a settlement agreement, wherein Verizon agreed to pay $93.5 million, but denied any wrongdoing.

Looking at the original qui tam complaint via the link helpfully provided by the article, we noted that the allegations concerned MCI/Worldcom, which was acquired by Verizon in 2006, and invoices submitted to the General Services Administration (GSA) under the telecommunications contracts FTS2001 and FTS2001 Bridge. According to the complaint—

MCI overcharged the United States by submitting invoices for payment to the United States for certain surcharges including certain federal, state and local taxes that it is prohibited from charging the United States under Federal Acquisition Regulations (FAR) and the FTS2001 Contract.

Specifically, the relator, Mr. Shea (a former Deloitte telecommunications consultant), alleged that Verizon violated FAR 52.229-04, which was incorporated into Verizon’s GSA contracts. Despite the limitations of that contract clause (and other related contract language), Mr. Shea alleged that Verizon billed the GSA for “Federal Regulatory Fee surcharges, state sales, excise and utility taxes; and surcharges [including] public utility commission fees; … state “deaf taxes;” state and local gross receipts taxes; business license fees; 911 taxes; … ad valorem taxes…”

The settlement agreement states—

This Agreement represents a compromise to avoid continued litigation and associated risks and is neither an admission of liability by Verizon nor a concession by the United States that its claims are not well founded.

Interestingly, while Verizon asserted that it was entering into the settlement agreement in order to“avoid .. risks,” the settlement agreement—by its express terms—does not eliminate Verizon’s risks associated with criminal liability or suspension/debarment proceedings. So we have difficulty fathoming what risks Verizon thought it was mitigating ….

Here’s a link to the official DOJ announcement. It’s not every day that that the government’s attorneys reap nearly $100 million in contractor payments, but the announcement is (deliberately?) understated. The most strident statement is the following—

‘A government contract is not a blank check,’ said U.S. Attorney Ronald C. Machen Jr. ‘Contractors who overbill the government will be aggressively pursued and required to make the taxpayers whole. This $93 million recovery should make contractors realize that we are firmly committed to ensuring the integrity of corporate billing practices with respect to government programs.’

Well, yes. We contractors do realize that billing practices are rather important, and that the False Claims Act always looms, like the Sword of Damocles, over our heads. Thanks for the reminder.

And thanks to Verizon, for the object lesson that government contractor compliance failures tend to be on the very expensive side, such that investments in compliance mechanisms and internal controls tend to pay for themselves.

 


Page 207 of 279

Newsflash

Effective January 1, 2019, Nick Sanders has been named as Editor of two reference books published by LexisNexis. The first book is Matthew Bender’s Accounting for Government Contracts: The Federal Acquisition Regulation. The second book is Matthew Bender’s Accounting for Government Contracts: The Cost Accounting Standards. Nick replaces Darrell Oyer, who has edited those books for many years.