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

DOD Walks Away from Use of Performance-Based Payments

E-mail Print PDF

bureaucrats

This one hits close to home, folks.

If you are a site member, you know we’ve published two technical articles, and made several speeches and presentations, on the subject of Performance-Based Payments (PBPs). Suffice to say, we are sensitive to anything that impacts use of PBPs.

Coming almost unnoticed out of the Federal Acquisition Streamlining Act (FASA) of 1994, PBPs became the DOD’s “preferred method” for providing contract financing payments for competitively awarded firm, fixed-price acquisitions of noncommercial goods and services in March, 2000. (See Federal Acquisition Circular 97-16.) Almost immediately, DOD policymakers became enamored of PBPs and sought to implement them on a majority of qualifying acquisitions within five years—a goal that was achieved within 12 months!

Without rehashing our previous writings, let’s simply say that PBPs were created because of a couple of reasons that made a whole lot of sense at the time—and which continue to make sense to us today. The PBP rationale includes:

  • The DOD found the prior contract financing method (customary progress payments based on contractor costs incurred) to be both difficult to understand and burdensome to administer.

  • Reduction in “non-value-added cost-based oversight”.

  • Emphasized schedule and technical progress.

  • Reinforced roles of government program managers and reduced roles of accountants and auditors.

  • Lowered barriers that prevented commercial contractors from entering the DOD marketplace, thus increasing competition while allowing DOD to access leading-edge commercial technology.

Importantly, implementation of PBPs tied contractor financing payments to measurable program performance. No longer did a contractor receive financing payments simply for spending money; the contractor actually needed to make tangible progress towards completion.

In our articles, we speculated about the linkage between PBPs and the termination of the A-12 Avenger II stealth attack fighter program in 1991. Then Secretary of Defense Dick Cheney terminated the program for default after payment of more than $2 billion in cost-based progress payments. More than 20 years later, that T4D action is still being litigated and the Pentagon is still trying to recover its “progress” payments from the two prime contractors involved.

Regarding the impact of PBP usage on contract oversight, we wrote in December, 2005 (in Contract Management magazine)—

Reductions to administrative burdens associated with cost-based billings. Since PBP trigger events are a ‘yes-or-no’ technical decision, there are no associated costs to review. For instance, compliance with FAR Part 31 cost principles or the Cost Accounting Standards is not a requirement for PBP payment requests. The contractor does not need to develop a government-specific accounting or billing system that is subject to audit and adequacy determination. The substantial resources normally devoted to complying with government-unique accounting rules can be applied elsewhere.

Despite the seemingly unassailable rationale for use, there is one DOD constituency who has, from the beginning, resisted use of PBPs and fought them at every turn. Can you guess that DOD stakeholder?

If you answered “DCAA” then you win a prize!

DCAA has never accepted PBPs, perhaps recognizing that the more PBPs are used, the less there is a need for DCAA to perform “non-value-added cost-based oversight” such as detailed reviews of progress payment requests. Here’s a challenge: go look at DCAA’s website (http://www.dcaa.mil) under “standard audit programs” and find the standard audit program associated with PBPs.

Go on. We’ll wait right here.

You couldn’t find one, could you? Despite decade of usage, DCAA still doesn’t acknowledge them.

Okay, we hear you saying, “But why should DCAA have an audit program for something they aren’t supposed to audit?” That would make sense except for the fact that many Contracting Officers want DCAA to audit contractors’ use of PBPs even though they really shouldn’t be doing so. So when a Contracting Officer asks DCAA to audit some aspect of PBPs, there is no audit guidance to guide the auditors.

And now it looks like DCAA has won its fight against PBPs.

We warned readers about the September 14, 2010 Memo from Dr. Ash Carter (USD, AT&L). That memo included the following tactic—

Reverse a decade of practice and restore DOD’s preference for using customary progress payments based on cost incurred, with other contract financing options being agreed-upon only with a commensurate reduction in contractor profit, based on increased cash flow.

We said at the time—

we are disappointed to see the end of DOD’s regulatory preference for Performance-Based Payments and the return of customary progress payments. The debacle of the A-12 program taught many that progress payments had little to do with actually making progress, and everything to do with the ability to spend money. It looks to us like that lesson has been forgotten.

On April 29, 2011, the Honorable Shay Assad, Director of DOD’s Defense Procurement and Acquisition Policy (DPAP), issued a memo that officially ended DOD’s preference for PBPs. The memo said—

As a matter of practice, for new contract awards, the basis for negotiations for fixed-price contracts shall be the use of customary progress payments. … After agreement on price, or contract award in the case of competitive acquisitions, the contractor shall have the flexibility to propose PBPs for the Government’s consideration. This will allow the contracting officer to determine the reasonableness of the consideration being offered by the contractor for a more favorable payment structure.

Why does DOD want to walk away from PBPs? Because (in the words of the memo)—

PBPs offer the contractor improved cash flow as compared to customary progress payments. … This difference in the time value of money produces a PBP price that is lower than that warranted with customary progress payments, and yet is a better financial arrangement for the contractor.

So Mr. Assad is basically saying that since contractors will drop their price in return for a promise of accelerated cash flow, the DOD needs to approach contract negotiations in such a manner as to capture that price reduction. Which is fine, insofar as it goes. But when one looks at the barriers DOD is putting into place when a contractor would want to propose use of PBPs, one comes to the conclusion that DOD really doesn’t want to use them.


The memo says—

the contractor should be instructed that if PBPs are desired, a proposed PBP schedule should be submitted which includes all PBP events, completion criteria and event values along with the contractor’s expected expenditure profile. … The contracting officer must clearly identify the consideration received in the post negotiation clearance document whenever a payment schedule more favorable to the contractor than customary progress payments is negotiated. … The negotiated consideration must be specifically approved by the clearance official or one level above the contracting officer, whichever is higher.

What’s the problem with the foregoing?” we hear you asking.

Well, consider that PBPs are only used on firm, fixed-price contracts. That contractor effort described above is quite often going to be a direct-charged effort. Which means that either the contractor eats the cost of that effort from its expected profit, or it bids that effort into its firm, fixed-price. So the submitted price will be higher than it otherwise would be, because of the mandatory effort now required to use PBPs.

Moreover, when customary progress payments are used, there is an administrative cost on both sides of the contract. (Elimination of those administrative costs was one of the primary benefits associated with use of PBPs.) Those costs are going right back into future contractor bids, because the contractor must now assume that only customary cost-based progress payments are going to be used.

Finally, the DOD is once again setting itself up for a repeat of the A-12 debacle. We’ve already noted the return of fixed-price development contracts. Now comes the return to cost-based progress payments on such contracts. Those two “return to what didn’t work before” trends are exactly what led to that multi-billion dollar poster child for DOD waste of taxpayer funds.

So nice job, Mr. Assad. You managed to reverse one of the more important innovations of Clinton-era acquisition reform. You’ve opened the door for contractors to increase their offer prices at a time when the DOD (and indeed the entire Federal government) is focused on lowering those very prices. And you’ve managed to recreate the environment that led to one of the worst DOD weapon system “train wrecks” in history.

Oh, and we forgot to mention that now we’ve got a nice conflict between the Assad guidance and the requirements of FAR 31.1001, which establishes the policy of the United States that “Performance-based payments are the preferred Government financing method when the contracting officer finds them practical, and the contractor agrees to their use.” (Emphasis added.) We have to ask whether DOD has submitted a request to the FAR Councils for a FAR Deviation, as required by FAR Subpart 1.4?

 

CWC Hears Suggestions on Improving Wartime Contracting

E-mail Print PDF

CWC Hearing20110425_Panel_1

We almost entitled this article, “CWC Hears Good Suggestions from Reasonable People, is Bewildered”—but somehow we refrained from non value-added snark. Seriously, we hope the CWC Commissioners were listening intently when Jacques Gansler was speaking during the CWC hearing on April 25, 2011.

Who’s Jacques Gansler?” we hear you asking. Well, children, the Honorable Dr. Gansler was the Under Secretary for Defense (Acquisition, Technology, and Logistics) from 1997 to 2001, and is largely credited (in our minds, at least) with making some of the key improvements to DOD acquisition management during his tenure. Since then, he’s Chaired a couple of important Commissions on behalf of the DOD, and his 1989 book, Affording Defense, is still worth reading today.

What we liked about Dr. Gansler’s testimony before the CWC was that it was informed based on his years of experience at the helm of DOD during the period of post-FASA transformation. It was reasonable, it was nuanced, and his criticism of the CWC’s recommendations was delivered a heck of a lot more diplomatically that we would have been able to do. (See our rant on the same topic, here.)

Dr. Gansler’s testimony was so well-done that we want to ignore the testimony of the GAO guy, the DOD IG guy, and the two SIGAR guys, and simply focus on what Dr. Gansler had to say. We shall quote as follows—

  • The first time I testified before your Commission, in September 2010, the focus of our discussion was the government’s acquisition workforce. Today, I will emphasize this same topic, as I believe that people are the key to success. In fact, in both studies I will discuss today, three threads exist: the acquisition workforce, the leadership of that workforce, and the contractors they manage. At heart, these studies recognize the importance of contractors as partners in achieving the Department’s mission, and identify ways to ensure the government is strategically positioned to operate within this enduring business model, by empowering its acquisition workforce and by creating positive incentives for its contractors to achieve higher and higher performance at lower and lower costs.

  • In a world where more than 50 percent of the ‘total force’ in Iraq and Afghanistan is contractors, contracting has an impact that cannot be a secondary consideration: it must be front and center—embedded in military planning, education, and training; and led and managed by a cadre of civilian and military professionals. … the acquisition workforce is pivotal if we are to solve these challenges. … DoD has an extremely dedicated corps of acquisition people. The problem is they are understaffed, overworked, under-trained, under-supported, and, I would argue, most importantly, under-valued. A combination of acquisition workforce reductions and spending increases has taken its toll. Particularly alarming, and of great concern to us, was the fact that, despite about a seven-fold workload increase from the 1990s to present, and the greater complexity and urgency of contracting in the intense contingency environment, the civilian and military contracting workforce has been declining.

  • contractors are important force multipliers. We cannot forget their value. They enable military personnel to focus on mission-essential tasks. Over time, each of the Services has outsourced tasks previously performed by personnel in uniform. Outsourcing tasks that are not inherently governmental has significantly increased overall military effectiveness, and it has done so at significant savings to the taxpayer. To add to the contractor value proposition: these resources come to the Department ready-trained, and can be flexibly engaged and released to address surge needs, as they come and go. [Emphasis in original.]

  • DoD has an enduring need for more well-trained, motivated, and experienced government contracting personnel. Without those baseline resources, the Department cannot meet the wartime need. To put this in perspective, at the time of our Commission’s analysis, there were about 270,000 contractors in the Iraq and Afghanistan theater—more than half the total force. Yet, the Army was not ‘training (including exercises) or educating as we fight;’ that is, incorporating the reality of contractors. Beyond training, of course, the Department needs experienced government people to manage contractors and to conduct the inherently-governmental functions. [Emphasis in original.]

  • The [Defense Science Board’s] task force also found that the Department’s good intentions to improve competition for services have led to unintended, adverse consequences. While one of the benefits of competition is lower prices, strategies favoring low price over best value, or fixed-price over time-and-materials contracts, may create more problems than they solve. Not only might the government be jeopardizing its ability to get the best solution, it might actually be increasing prices: a fixed-price contract in the services arena in particular it may lead to higher costs, as contractors accommodate additional risk associated with this contract type. Similarly, the recent trend to award service contracts (or even goods) on the basis of ‘Low Bid, Technically Acceptable,’ often results in lower quality and higher long-term costs (compared to ‘Best Value’ awards). Or, as another example, requiring competition on all awards has significantly reduced the incentive to submit new ideas as unsolicited proposals. And while the bid protest process is a hallmark of our competitive procurement system, we can significantly hamper desired results if we permit, without penalty, protest actions lacking substance.

  • By using a commercial approach, including commercial terms and conditions, the government could tap premium talent and proven goods from firms that would otherwise be deterred by the government’s standard approach to acquisition. We are now 17 years beyond the 1994 passage of the Federal Acquisition Streamlining Act, and faced with the reality that application of FAR Part 12 principles has been problematic for services: only 18 percent of DoD’s services are sourced using commercial practices. The entry barriers remain the same: concerns over intellectual property and data rights, cost-accounting requirements, profit and overhead policies—to name just a few.

  • Within the acquisition community, DoD currently lacks program managers with strong experience in portfolio-specific services, and new hires with contracting experience in these areas also lag. The functional personnel managing large service contracts lie outside the acquisition community. (These are the Contracting Officer’s Representatives (CORs) with the substantive knowledge of the area under contract.) This means they are not subject to relevant defense acquisition workforce training. Even within the acquisition community, a robust shared body of knowledge for services contracting is lacking. While the Defense Acquisition University (DAU) does have a Services Acquisition Center of Excellence, its staff represents a tiny portion (about 1 percent) of the overall DAU faculty numbers; and there are few services-based case studies being taught—despite the fact that services constitute the majority of DoD’s buys. And, while training is minimal, so too are the career opportunities: the current culture and incentives drive good people to product acquisition programs—or to avoid acquisition altogether.

  • [The CWC’s Second Interim Report to Congress] covers incredibly salient topics. On first blush, it appears to do so through a lens that, from the very outset, is aimed at minimizing the important role contractors play: the subtitle ‘Correcting over-reliance on contractors in contingency operations’ conveys an impression that DoD should reduce the role of contractors. In reality, contractors play an essential role in contingency operations. The government’s focus should not be on decreasing contractors, but instead on ensuring they are performing appropriate functions, and then properly managing them. As I have previously stated, contractor services can offer significant savings (e.g., the Congressional Budget Office found contractors could perform weapon system maintenance for 90 percent less than organic performance of this function), provide a flexible means to address support needs, and offer immediate support through ready-trained individuals. So, while your main title rightly identifies risk as a considerable issue, the subtitle is open to misinterpretation. [Emphasis in original.] My opinion on the title reflects my general comments on your second interim report, which fall into two areas of concern regarding contractors (1) too great an emphasis on punishments and (2) an absence of value recognition.

  • the focus on punishments, like suspension and debarment, comes at the expense of incentives. Missing is a discussion of creating incentives to reward outstanding performance, such as awarding contractors with follow-on work, if they achieve higher performance at lower costs. Your second interim report contains an entire section on competition policy improvements, urging increased competition. This gave me pause: what is the purpose of forcing competition, regardless of the results achieved? I strongly believe in the value of competition (to get higher performance at lower costs); but if the threat of future competition is enough to get those desired results, then competition should not always be mandated. Rather, it should be required if the desired results are not achieved. The incentive for achieving desired results is the follow-on award. [Emphasis in original.]

  • I encourage your Commission to seek out a balance in your final report, which is due this summer. A balanced discussion of the two issues I raise—reward and recognition, over punishment and sub-optimization—will go a long way toward creating the systemic improvements our troops deserve. We cannot discount that contractors are an important force multiplier; instead, we must build the capability and infrastructure to manage this reality. Clearly, there are many important actions (legislative, regulatory, policy, practices, and so forth) where your Commission can play a valuable role. In any of these actions, I see the key issues as getting the right people (government and industry) and in creating positive incentives for these individuals to get what the warfighters need, when they are needed—with outstanding performance and at low cost. This can be done; and it must be done. The men and women serving our nation in harm’s way deserve no less. [Emphasis in original.]

Amen, brother! We hope the CWC Commissioners will listen to this voice of reason ….

 

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.

 

Yet Another Defense Contractor Defrauds DOD

E-mail Print PDF

Yeah. Just after we got through reminding our readers that as much fraud, waste and abuse takes place in the government and commercial sectors as takes place in the government marketplace comes a story about yet another defense contractor who pleaded guilty to some egregious wrongdoing.

Let’s add Staff Gasket Manufacturing Corporation, of Bergen County, New Jersey, to the list of especially stupid defense contractors that already includes such notables as Kustom Products, Inc. of Coos Bay, Orgeon—who allegedly sold the DOD counterfeit “Jesus Nuts” (the little doodads that secure the main rotors of helicopters to the aircraft)—and Rocky Mountain Instruments, who exported sensitive technical data to overseas manufacturers so it could be the low bidder to its DOD prime contractors.

Before we get into Staff Gasket’s wrongdoing, let’s state up front that the FAR is a complicated and complex beast, and that it’s unreasonable to expect anybody to have mastery of its entire panoply of regulations and contract clauses—especially when the judiciary has a tendency to reinterpret those regulations and clauses in a counter-intuitive way, and when the FAR Councils have a tendency to issue Federal Acquisition Circulars revising the regulations every month or so. Compared to much of the FAR, Part 25 (“Foreign Acquisition”) is a fairly arcane piece of work, covering such fun topics as the Buy American Act, the Trade Agreements Act, customs/duties, prohibited sources, and other similar things that make the life of acquisition professionals so much fun.

And let’s not forget that the Part 25 solicitation and contract clauses establish compliance criteria that contractors violate at their own risk….

Staff Gasket Manufacturing Corporation was one such contractor. Let’s get back to its story, and that of the company’s President, Eric Helf, age 38. According to the linked story, Staff Gasket pleaded guilty to wire fraud and a violation of U.S. export control laws, while Helf pleaded guilty to conspiracy to commit wire fraud in connection with the company’s “scheme”.

What was the scheme?

According to the story—

From August 2004 through March 2006, Staff Gasket — which was previously located in Englewood — won bids and entered into contracts with the U.S. Department of Defense to provide replacement parts for equipment to be used in military operations, including lock pins for HH-60 helicopters

The problem was, those contracts required that the equipment had to be manufactured in the United States, to exact (and sensitive) specifications. Staff Gasket decided to cut corners by procuring parts from manufactures outside the U.S., including those located in China. The story reported that Staff Gasket made “fraudulent statements in its bids, saying ‘it was the manufacturer of these parts and the parts would be manufactured in accordance’ with the specifications required [by contract].”

Instead, Staff Gasket “would ‘purchase similar and less expensive parts from other manufacturers, including foreign manufacturers located in China, or unauthorized distributors that did not meet the DoD requirements.’” The story reported—

The company and others operating under its direction would also direct that certain production and packaging of foreign-manufactured parts be disguised so the true manufacturer was hidden, making it look like Staff Gasket had built the parts … Some parts would be ‘non-conforming’ ….

When questioned about the process used to build certain parts, Staff Gasket would allegedly submit false information back to the government.

Staff Gasket caused the DoD to lose about $751,091 in connection with the fraudulent contracts, authorities said.

We have previously discussed the issue of counterfeit parts in contractors’ supply chains. While it is surely possible that a company might unknowingly acquire counterfeit parts, prime contractors also need to be on the lookout for subcontractors and suppliers that knowingly source parts from uncontrolled (and unmonitored) sources, who do so in order to lower their bid prices through such unlawful means.

If the bid price is too good to be true, it very well may be.

 

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.

 


Page 205 of 278

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.