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

Mistakes are Not Cost Accounting Practices

E-mail Print PDF

Back from the Society of Corporate Compliance and Ethics (SCCE) annual Compliance & Ethics Institute (CEI). From my perspective, well worth the investment of three-and-a-half days of time. The focus was not on Government contractors, per se, but there was enough related content to keep it interesting. Some of the breakout sessions were full of wonderful content—content that made one think about it and how it could be applied to the day-to-day grind of work.

One of those breakout sessions was taught by a member of the Office of the Inspector General of the Department of the Interior (DOI), Daniel Coney. He had a slide so personally impactful that I took a picture of it with my phone.

When speaking about the discretion OIGs have, he stated (paraphrasing), “Most of our cases are not criminal. We don’t go after people for making mistakes. We don’t go after people when there’s no intent to commit a crime.” Which is good news for many of us!

But then he showed a slide that contained the following sentence:

A MISTAKE REPEATED MORE THAN ONCE IS A DECISION

Whoa.

What I gleaned from that single sentence is that the more a mistake is repeated, the more it looks like intent—or, at least, like negligence.

Remember, the civil False Claims Act (as amended) has a different definition of intent than the criminal statute. To be liable, a defendant must have “knowingly” submitted a false claim; the civil statute defines “knowingly” as including either “deliberate ignorance” or “reckless disregard” for the truth. In our layperson’s interpretation, a defendant cannot claim that the false claim was the result of a mistake when the “mistake“ was the result of ignoring (or not looking for) warning signs that the mistake was being made.

But then we started thinking about cost accounting practices. Most of us know that a contractor subject to either modified or full CAS coverage has constraints over when it can make changes to its cost accounting practices. See, for example, the contract clause 52.230-2, which states (in pertinent part):

… the Contractor, in connection with this contract, shall -- Follow consistently the Contractor’s cost accounting practices in accumulating and reporting contract performance cost data concerning this contract. If any change in cost accounting practices is made for the purposes of any contract or subcontract subject to CAS requirements, the change must be applied prospectively to this contract and the Disclosure Statement must be amended accordingly. If the contract price or cost allowance of this contract is affected by such changes, adjustment shall be made in accordance with subparagraph (a)(4) or (a)(5) of this clause, as appropriate.

Similarly, the clause 52.230-4 states (in pertinent part):

… the Contractor, in connection with this contract, shall -- (i) Follow consistently the Contractor’s cost accounting practices. A change to such practices may be proposed, however, by either the Government or the Contractor, and the Contractor agrees to negotiate with the Contracting Officer the terms and conditions under which a change may be made. After the terms and conditions under which the change is to be made have been agreed to, the change must be applied prospectively to this contract, and the Disclosure Statement, if affected, must be amended accordingly.

The mechanism(s) for disclosing changes to cost accounting practice are established by yet another contract clause (52.230-6).

Finally, see FAR 30.6 (CAS Administration) provides direction to government contracting officers regarding how to administer the requirements of the foregoing contract clauses.

In summary, if you are a CAS-covered contractor, then you need to become somewhat of an expert in the clause requirements and FAR guidance. However, that will only get you so far.

Importantly, none of the foregoing clauses or the cited FAR language actually define the phrase “cost accounting practice.” The phrase is defined in the Cost Accounting Standards regulations themselves (see 48 CFR 9903.302-1) but that’s about it. In addition, you need to read certain court decisions (e.g., Perry v. Martin Marietta) to understand how the courts have interpreted the CAS language.

The tension between the CAS contract clauses, the FAR regulations, and the desires of the contracting parties have led to disagreements regarding whether or not a cost accounting practice has been changed. More to the point of this article, in our experience there is also disagreement regarding whether or not a cost accounting practice has been followed consistently.

As required by the clause language quoted above, when they execute their CAS-covered contracts, contractors agree to follow their cost accounting practices consistently. (We discussed the nuances between “disclosed” and “established” cost accounting practices in this article.) That’s the deal and, if a contractor fails to be consistent, then it may be alleged to have breached its contract. That’s not good.

But what about mistakes?

Does a simple mistake—somebody does something they’re not supposed to do—lead to a contract breach via an allegation that cost accounting practices were not followed consistently?

It depends, doesn’t it?

For a long time we argued that mistakes are not cost accounting practice. We argued that the cost accounting practice is what the contractor intends, not what some ill-trained employee actually does. But if that were literally true then a contractor would almost never have inconsistent cost accounting practices. There would need to be some type of direction from an authority figure in order to find inconsistent cost accounting practices. A smoking gun email would do it. A meeting behind closed doors would do it. But otherwise, not so much. If an employee violated policies and procedures and, as a result, the contractor treated something differently than it had told the government it was going to, that would not be an inconsistent cost accounting practice—because it would be a simple mistake.

Now, having seen and thought about Mr. Coney’s simple sentence, we think a reasonable person could distinguish between a simple mistake and an inconsistency in cost accounting practice based on the number of transactions that were affected.

Obviously, there’s no bright line in this line of reasoning. But we might assert (with some trepidation) the following general guidelines:

  • One transaction out of many is not an inconsistent cost accounting practice; it is a mistake.

  • One employee miscoding a transaction when many others in the same function are getting it right is not an inconsistent cost accounting practice; it is a mistake.

  • Transactions escaping controls are also mistakes, assuming the controls were reasonably designed to prevent and/or detect mistakes.

Something for CAS-covered contractors to consider, perhaps?

 

Gone But Still Here

E-mail Print PDF

 

Well, it’s time for another trip—this time to attend the 17th Annual Compliance and Ethics Institute, sponsored by the Society of Corporate Compliance and Ethics. Three-and-a-half days of workshops and keynotes and breakout sessions.

Naturally, my focus will be on compliance risks and plans related to Federal government contractors. But I will also be dabbling in other areas, such as UK and Ireland compliance regulations, establishing compliance programs for small and medium-sized businesses, and establishing a culture of compliance in the larger companies.

Yes, yes. I know. The Compliance Institute is being held in Las Vegas. Go ahead and smirk, if you must. But the fact is that, from Sunday through Wednesday, I will be attending about 20 hours of learning. Maintaining my SCCE certification requires 40 hours of CPE annually, and this is going to be a big chunk of my annual requirement. So I’m going to attend all the sessions and make sure to turn in the signed CPE forms at each one of them.

Of course, what happens after class stays in Vegas….

Seriously, though. I’m kind of over Vegas. For a long time I visited the city at least twice a year, to teach Fed Pubs classes. I kind of got all the expensive misbehaviors out of my system. My blackjack days have been over for a long time. At this point, I look forward to having a nice meal with a glass of wine and retiring early to bed.

Federal government contract compliance is what I have done for many years, and it’s nice to see that niche explored within a broader context of “compliance” as it relates to entities other than Federal contractors.

So I’m off to Vegas and, by the time you’re reading these words, I’ll be hip-deep into the SCCE’s Compliance and Ethics Institute. Which means that I won’t be writing any more blog articles until I get back.

See you then.

 

Sanders to Speak at NCMA Orange County Chapter

E-mail Print PDF

Once again I will make the journey from San Diego to Irvine in order to present to the Orange County Chapter of the NCMA. This time they let me choose my own adventure. I picked Contract Close-Outs.

First: Link to presentation details. Follow the link and you will see that I’m presenting October 17th, starting at 6:45 PM. (I’ll need that time to navigate the traffic on The 5.)

Second: Why Contract Close-Outs? I mean, could I have picked a more boring topic? Nobody cares about closing-out contracts.

Exactly.

The fact is, closing-out contracts can be very important to the financial health of any contractor. The fact is, the government cares very much about closing-out contracts and eliminating “Unliquidated Obligations” that can mess up financial statements, and keep agencies from getting “clean” audit opinions. The fact is, your backlog of physically completed but not formally closed contracts is like an anchor, holding you and your company back.

So I chose a topic that is seemingly of little importance, but which actually has a potentially significant impact on both government and contractor.

If you’re in the area, why not show up and participate in the discussion?

 

The Importance of a Company Hotline

E-mail Print PDF

Recently we came across this article, written by attorneys (and former Federal prosecutors) A. Lee Bentley III and Jason Mehta, entitled “How Contractor Fraud is Reported Shouldn’t Affect How It Gets Investigated.” The article addressed something we have pondered from time to time—i.e., how does the government choose whether to pursue available administrative remedies or civil/criminal remedies?

For example, in one article we discussed differences between allegations of defective pricing and allegations of False Claims associated with defectively priced contracts. We wrote: “Now we have a new rule: If the Federal government detects the defective pricing, then it’s a TINA matter. But if the relator detects the defective pricing, then it’s a FCA matter. Which is inconsistent and, on its face, somewhat inequitable. But that’s the way we’re seeing it these days.”

Subsequently, we questioned that new rule when we came across allegations that BAE Systems (successor to the Stewart & Stevenson FMTV contractor) was being charged with both defective pricing and violations of the FCA—with no qui tam relator in sight.

Nonetheless, the DefenseOne.com article (link in the first sentence) seems to resurrect and support our initial theory. Stated simply: the government’s investigation methodology and selection of legal remedy often depends on the manner in which it learns of the alleged violation(s). The authors wrote:

The traditional way to blow the whistle is to report internally up the chain and—if that does not work—the whistleblower could report suspected wrongdoing to federal contracting officers or to Defense Department hotline numbers. When the allegations are raised up the chain, a series of investigative procedures are initiated and DOD scrutinizes the allegations with appropriate vigor. DOD has contractual rights under the Federal Acquisition Regulations to investigate these allegations, inspect the premises, review documents, and root out fraud. These administrative remedies have been a resounding success when DOD learns of instances of fraud. …

[But] when the government learns about the suspected fraud through a qui tam suit, the DOJ will initiate the investigation. The investigation is given the imprimatur of a “federal case” and the stakes are automatically elevated as the default remedy for a False Claims Act case is not recoupment, but rather civil penalties (recoupment plus extra money as a penalty). In addition to the investigative steps described above, the mere fact that a whistleblower files a False Claims Act suit often results in official DOJ interviews, subpoenas and meetings.

If this hypothesis is true, if the manner in which the government learns of the allegations of wrongdoing affects both the investigatory approach and the potential legal remedies, then wouldn’t you really want employees reporting their concerns to the company hotline? And if it came to that, wouldn’t you really want employees reporting their concerns to the DOD Hotline? Those are the better options, right? Because, according to the article (and our experience) when an employee resorts to filing a qui tam lawsuit under the False Claims Act, then the company will be in for a long and very expensive legal journey.

And if all that is true, then doesn’t that mean you really need to focus on making your company hotline as accessible to employees as possible? We mean, you want employees to use the hotline, right? So you need to make the entire process as user-friendly as possible. Otherwise, you risk having employees use other, less attractive means to have their concerns addressed.

What does that look like? Well, we touched on the topic in an article we published about 18 months ago. We wrote—

Allegations received via internal hotline should be logged. Then they should be investigated. The findings of the investigation should be summarized and the matter should be dispositioned by an independent party in accordance with applicable laws, regulations, and company procedures. Then – and this must always happen – the company must ‘close the loop’ by reporting back the disposition to the employee who made the original hotline allegations. (Obviously if the original reporter was anonymous, that’s not going to happen.)

Employees who call the company hotline to report concerns are not whistle-blowers; they are concerned employees. But you can quickly convert them into whistle-blowers by ignoring their concerns or failing to report back to them the findings of your investigation. And—as we’ve reported—you cannot retaliate against any employee who avails themselves of any fraud reporting mechanism.

In fact—as that last article noted—you are required by DFARS contract clause 252.203-7002 to inform your employees, in writing, of their whistleblower rights. Of course, we are quite confident that defense contractors with that clause in their contracts have already done so. Right?

Thus, focusing on making your company hotline an attractive and user-friendly option for employees with concerns starts with education. You need to tell them about it. For certain defense contractors, you need to tell them about it in writing. But for the rest, perhaps an email blast will be sufficient. Let them know that you want them to use the hotline when appropriate. Obviously, reporting up the chain of command is preferable; but often that approach is problematic for one reason or another. So the company hotline is the best next option.

  • Let employees know that it’s okay to use the hotline; that they will not be retaliated against. Rather, they will be protected.

  • Let employees know that their concerns will be taken seriously and that the concerns will be investigated impartially, perhaps by an outside party.

  • Let employees know that they will be hearing back from somebody with the results of those investigations.

  • Make sure that the company hotline number is prominently posted. Make it easy to dial. Make sure reports are logged.

Because the alternatives are much less pleasant.

 

Palantir’s Victory is Complete

E-mail Print PDF

Use this site’s search feature (hint: it’s over there on the far right of the home page) and type in “Palantir.” You’ll see that we’ve written several articles either about (or perhaps only mentioning) that Silicon Valley Company. We’re going to assume you’ve seen those articles and so we won’t be linking to them in this one.

Anyway, the title says it all.

The Palantir story is the story of how the DoD views innovation. Truly, it doesn’t want it. What we mean to say is, if you are a defense contractor that can offer a small innovation that marginally improves performance or marginally decreases costs, then that’s great and those innovations will be accepted gratefully. But if you are not a defense contractor and you offer a disruptive innovation that dramatically changes the paradigm, then forget it. DoD doesn’t want you or your product.

We suspect the reason for the above behavior is grounded in bureaucracy and career management. Major programs have Program Executive Offices. Major programs have Strategic Program Offices or Special Program Offices. Those various offices are staffed by military service members and civilian employees, each of whom has a career to manage. If you put their programs at risk, then you also put many careers at risk. Or so we suspect. You may have your own notions of how things work, including how lobbyists and politicians influence program decisions.

In fact, at least one Industry Association offers training entitled “How Washington Works® -- Navigating the DOD” which is a “fast-paced” two-day course covering “the three principal DOD decision-making support systems and how they are used by the Army, Navy, Air Force, Marine Corps, and USSOCOM to provide an integrated approach to strategic planning, capabilities needs assessment, systems acquisition, and program and budget development.” We have not taken the course, so our assertions are simply speculation. Those who have taken the course may well have better notions about the system than we do.

But back to Palantir’s story. In 2016, Palantir filed suit against the US Army, alleging that it was violating statutes and regulations in its acquisition plan for the “Distributed Common Ground System-Army Increment 2.” The first bid protest, at GAO, did not go Palantir’s way. But Palantir was successful at its second bid protest, when Court of Federal Claims Judge Horn told the Army to do better market research to determine whether or not its needs could be met by commercial items (e.g., Palantir’s products), as required by the Federal Acquisition Streamlining Act (FASA). Judge Horn also issued a rare permanent injunction preventing the Army from awarding the DCGS-Increment 2 contract until it had done so.

Meanwhile, Palantir and Raytheon were partnering. Perhaps Raytheon saw the writing on the wall and thought that half a loaf was better than nothing. Or perhaps Palantir realized that Raytheon already knew How Washington Works® and could smooth any Army concerns about using an outside-The-Beltway contractor. In any case, that approach seeming promising to both companies—so promising, that General Dynamics (another DCGS-2 bidder) filed its own bid protest at the GAO when it learned that the partnership was going to win the $876 million contract award. But that protest was denied.

So the Palantir/Raytheon team won the DCGS-2 contract. But that didn’t stop the government from appealing the COFC decision and injunction. Recently the Court of Appeals, Federal Circuit, ruled on the government’s appeal, affirming the COFC decision.

The respected law firm of Arnold Porter published a client advisory article, written by Nathaniel Castellano, Charles Blanchard, and Dominique Casimir. In that article, the Palantir decision is described as being possibly “one of the most significant procurement precedents of the decade.” What makes the decision so important, according to the attorney authors is that it –

… breathed new life into the government's obligations under the Federal Acquisition Streamlining Act (FASA) to prioritize, to the maximum extent practicable, the acquisition of commercial and nondevelopmental solutions. Weaning agencies off their historic preference for developmental solutions is critical now more than ever, as it is readily apparent that maintaining the United States' technological and battlefield superiority depends on its ability to harness technologies from the commercial sector and become a more commercial-friendly business partner. The decision will have the practical impact of requiring agencies to more carefully document their market research. Palantir will also provide useful leverage for companies seeking to eliminate (whether by negotiation or protest) solicitation provisions that are not accommodating to commercial vendors.

In other words, the decision creates gaping holes in the barriers that have historically prevented non-traditional defense contractors from successfully selling their goods and services to the DoD. It requires DoD acquisition folks to perform more robust market research, seeking to identify commercial sources with already-developed solutions. It requires that, if they are available, those commercial sources be given preference over funding development of new solutions by traditional sources. As such, it’s kind of a big deal.

The Arnold Porter article noted “Technology Network (TechNet), an association of chief executive officers and senior executives of leading technology companies from across the nation, submitted an amicus curiae brief in support of Palantir. TechNet argued that the Army's approach to DCGS is product of a DoD culture predisposed to favor full development of government-unique solutions instead of relying on the commercial and nondevelopmental solutions that FASA directs agencies to favor.”

The Federal Circuit agreed with Palantir and the Court of Federal Claims, finding (in a unanimous decision) that “the Army did not rationally use its market research results to determine whether there are available commercial items that: ‘(A) meet the agency's requirements; (B) could be modified to meet the agency's requirements; or (C) could meet the agency's requirements if those requirements were modified to a reasonable extent.’” The Court also found that the Army’s decision to focus on developing a new solution, rather than exploring whether a commercial solution might be available, was “arbitrary and capricious.”

For several years now, we have documented the entrenched DoD bureaucracy’s fight against true innovation, using the Palantir story as the poster child for that fight. We are very happy to now report that Palantir won on all fronts, and that its victory might pave the way for other innovative commercial firms to enter into the defense marketplace.

 


Page 42 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.