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

Retain Evidence

E-mail Print PDF

A recent ASBCA decision contains a reminder that contractors should retain evidence and other documentation, even stuff that might not seem to matter now—but will matter in any dispute that goes to litigation.

Strategic Technology Institute, Inc. (STi) had received its first cost-type contract from the US Navy in 2008. As required by contract terms (i.e., clause 52.216-7), STI timely submitted its proposals to establish final billing rates (commonly called an Incurred Cost Proposal or ICP) for the two years of contract performance.

Allegedly.

STi asserted that it timely submitted its ICPs; however, the government—particularly DCAA—had no record of receipt. STi (allegedly) submitted its proposals but no auditors ever showed up to audit the submissions. The situation stayed that way until 2014.

In July, 2014, “DCAA was auditing STi’s 2010 ICP, which would have been submitted in June 2011 -- three years earlier. The auditor found reference to 2008 and 2009 costs, and requested from STi copies of its 2009 and earlier ICPs. STi promptly provided the 2008 and 2009 submissions to DCAA. At this point in July 2014, the 2008 ICP had been prepared five years earlier.”

DCAA audited 2008 and 2009 and, based on that audit report, three years later the DCMA contracting officer issued a Final Decision demanding $1.1 million. The COFD was issued in November, 2018—"over nine years after the 2008 ICP was prepared, but less than four-and-a-half years after DCAA requested the ICPs from STi in July 2014.”

Before the Board, STi argued that the government’s claims were time-barred by the Contract Disputes Act’s six-year Statute of Limitations. The Board didn’t buy that argument—primarily because STi was unable to provide any evidence that it had actually submitted the proposals when the company said it had done so. Moreover, STi said that the passage of time prevented the company from actually disputing the government claim. Thus, if the Statute of Limitation argument failed, the company had nothing else to faill back on.

The argument failed.

The Board’s decision stated—

We hold that the contract required STi to submit its ICPs, and that STi has not established, by a preponderance of the evidence, that it submitted its ICP prior to July 2014. Additionally, we hold that the government did not know and had no reason to know of its claims against STi until it received the 2008 and 2009 ICPs in July 2014. Accordingly, we sustain the government’s claim, reject STi’s statute of limitation defense and deny the appeals.

The lesson here is simple: retain evidence that the proposals were submitted. Do not rely on the government agreeing with you as to when (and if) they were submitted. Obtain confirmation. Print out the confirmation and retain it in your ICP support files.

You have ICP support files, don’t you?

You are going to experience turnover in personnel. You are going to have documents sent to storage or otherwise purged. Consequently, you are going to want to have robust files related to all significant decisions made during the account “scrub” and proposal preparation process.

If you don’t have such files, you risk ending up as STi did, with no ability to dispute DCAA’s audit findings, because you simply lack the documentary evidence to disagree with them. Not a great place to be in, is it?

I remember when we went to support the government audit of our 1986 proposal to establish final billing rates. This was back in the day when general ledgers were printed out, bound, and retained. We had taken all the old general ledgers and put them in an unused room, awaiting audit. When the audit finally came (in the late 1990’s—please don’t ask why it took so long), we went to pull the 1986 general ledger to show the auditors how our ICP reconciled … only to find that somebody had “cleaned” the office by throwing out all the documents that we had carefully retained.

What did we expect was going to happen? The office was unused, and filled with papers more than a decade old. Of course somebody was going to clean up the mess! (Or so it was explained to us.)

Anyway, that made the audit support of the 1986 ICP rather challenging, to say the least.

Don’t be like STi or like the company I worked for in the late 1990’s. Retain your documents. Label them. Ensure they are not thrown away.

If you do all that, your audit will go better, I’m sure.

 

Recorded Versus Incurred Costs

E-mail Print PDF

An accrued expense refers to when a company makes purchases on credit and enters liabilities in its general ledger, acknowledging its obligations to its creditors. In accounting, it is an expense incurred but not yet paid. … An accrued liability represents an expense a business has incurred during a specific period but has yet to be billed for.” – The Corporate Finance Institute

It’s always been a bit of a pet peeve that GAAP-compliant accrual accounting is insufficient for compliance with government contract cost accounting—primarily the FAR and CAS requirements that drive “allowable” costs. Most companies that have to prepare, submit, and support an audit of their “proposal to establish final billing rates” (popularly but incorrectly called “the incurred cost submission”) know this fact.

Adjusting GAAP-compliant general ledger balances to create compliant “claimed costs” and the resulting indirect cost rates is time-consuming and, in general, subject to human error. It would be so much easier (and cheaper) to just submit the year-end balances, let an independent public accounting firm audit them, and then let the government rely on the results! But we don’t do that, do we?

Instead, we make adjustments. One of the most common adjustments is to “true-up” year end bonus/incentive compensation accruals to the amounts actually paid. For example, let’s assume the company has a 12/31 year-end (calendar and fiscal years match). Let’s say that, before the books close for the year on 12/31, the company budgets annual bonus payments at $10,000,000. But the company won’t pay that amount to its employees until next February. So it accrues the liability on the books. The company knows that it will pay, and the auditors know that the obligation to pay the bonuses is real and the bonuses are related to the current year’s results—but the company and the auditors (and the employees) know the bonuses won’t be paid for roughly 60 days. It’s a legitimate accrual of a known liability.

Because the liability was recorded, an accrued expense entry is also recorded. This is because the accrued expenses related to current period’s operations and results. In other words, the famous “matching principle” requires the expense to be matched to the revenue to which it relates. If the expense entry weren’t made, then profits for the year would be overstated.

Okay so far? I mean, this is a really simplistic view of things—but I’m trying to get across the important concepts. GAAP requires that the liability to pay bonuses be recognized, and the recording of the liability triggers the recording of an accrued expense. All based on budgeted (or estimated) values. This is fine. This is normal.

But then government contract accounting says “wait a minute!” The auditors show up and ask how much was really paid in February? It’s not exactly $10,000,000! Why not? Well, because several people left the company in January and February, forfeiting their right to collect their bonuses. The company thought it was going to pay the bonuses when it accrued them in December, but it turned out that those particular payments weren’t actually made in February. Let’s say the company paid-out $9,500,000 instead of the $10,000,000 it had accrued. In that case, government auditors expect that the company will “true-up” its claimed expenses by reducing them by $500,000.

What’s good for GAAP isn’t necessarily good for government contract cost accounting.

Shrug. It’s just the way it is. Court after court after court has accepted the notion that GAAP and FAR/CAS don’t always match up. (Though Congress directed that the CAS Board “conform” CAS to GAAP as much as possible … still waiting for any official movement on that.) So we accept it and deal with it, and continue to make those adjustments so that GAAP-compliant expense ledgers are now FAR and CAS compliant claimed costs.

A recent case at the ASBCA caused Judge O’Connell to review the differences between “incurred” and “actual” costs—or, as we would say, between “recorded” and “actual” costs. Because yes, indeed, there is a difference.

Cellular Materials International (CMI) had several cost-type contracts with the Department of Defense (DoD). As required by the Allowable Cost and Payment clause (52.216-7), CMI submitted its proposals to establish final billing rates for its Fiscal Years 2010 through 2014. As Judge O’Connell wrote—

Initially, the Defense Contract Audit Agency (DCAA) informed CMI that its proposals were low risk and would not be audited. But after receiving this notice, CMI revised its 2010-2014 proposals to add $425,000 ($85,000 per year) in general and administrative (G&A) costs for a consultant, Mr. Haydn Wadley.

(References and citations omitted, as they will be from all direct quotes from the decision.)

Let’s start there. CMI submitted its proposals, was told they would not be audited and, upon receiving that notice, decided to add in some more costs. Yeah, like that wasn’t going to raise red flag.

What were the additional costs? They were for a consultant. A consultant who just happened to be “CMI’s largest shareholder, owning up to about 39% of the shares during this period.” Um, yeah. Not suspicious; not at all—right?

Surprising nobody who reads this blog, DCAA auditors questioned the additional costs. All of them. Apparently, another $86,119 of other G&A expenses were questioned as well. (The decision doesn’t address them.)

The Contracting Officer issued a final decision, unilaterally establishing the final indirect cost rates at rates that included a disallowance of $511,119.

CMI appealed and, during discovery—

… it produced to the government various documents, including 31 canceled checks, that resulted in the government agreeing that CMI had made $219,583.23 in payments to Mr. Wadley and that these payments were allowable costs. The parties were also able to resolve the portion of the dispute that did not relate to Mr. Wadley, which amounted to an additional $86,119.

Leaving $205,416.57 still in dispute before the Board.

CMI believed that it had supported the majority of the costs still in dispute. To that end—

… CMI has provided the government 27 promissory notes executed each month from October 2012 to December 2014 in which CMI promised to pay Mr. Wadley the amount of $7,083.33, for a total amount of $191,249.91. The notes do not provide for interim payments or contain a date for repayment, other than to state that they are payable five days after demand. As an explanation, Les Gonda, President and Chief Executive Officer of CMI, and Mr. Wadley, in a joint affidavit, state that Mr. Wadley did this ‘due to his belief in the future potential of CMI’. Mr. Wadley has not demanded payment … CMI also represented to the government that it issued checks to Mr. Wadley totaling $14,166.66 in December 2011 and September 2012 that remain uncashed.

As noted above, Judge O’Connell had to delve into the meaning of FAR 51.216-7(d). He wrote—

The contractor is required to submit a final indirect cost rate proposal. FAR 52.216-7(d)(2)(i). The rates it proposes ‘shall be based on the Contractor’s actual cost experience for that period.’ FAR 52.216-7(d)(2)(ii) (emphasis added). The government contends that ‘actual cost experience’ is synonymous with ‘actually paid’ and because CMI has not made any payments on the promissory notes, these costs are not allowable.

FAR 31.0013 provides that ‘actual costs means... amounts determined on the basis of costs incurred, as distinguished from forecasted costs...’ The FAR does not provide further guidance as to when a cost may be considered to have been incurred and when it is merely forecasted.

The Judge cited several legal decisions. As part of his analysis, Judge O’Connell noted that the Federal Circuit had cited to Black’s Law Dictionary. (“The Federal Circuit cited Black’s Law Dictionary to define incur as meaning “to suffer ‘a liability or expense.’”)

Citing to a case involving a petition for damages under the Vaccine Act, Judge O’Connell quoted the following—

[i]n ordinary usage, ... to ‘incur’ expenses means to pay or become liable for them. In one common usage, a person becomes liable for yet-to-arise expenses at the time of undertaking an obligation to pay those expenses if and when they arise. See Liability, Black’s Law Dictionary (10th ed. 2014) (defining liability as the state ‘of being legally obligated or accountable,’ through civil or criminal penalties).

Judge O’Connell also wrote—

In UMC Electronics Co. v. United States, 43 Fed. Cl. 776 (1999), aff’d 249 F.3d 1337 (Fed. Cir. 2001), the Court of Federal Claims considered the meaning of actual costs in the context of fraud counterclaims filed by the government. In that case, the contractor represented that its claim was based on actual costs. The court found, however, that the claim was based on purchase orders to subcontractors so that it sought, for example, payment for materials that the contractor never received and for which it never received invoices. Relying on the FAR 31.001 definition of ‘actual costs’ discussed above, the court held that a cost is incurred ‘when a person becomes legally bound to pay.’ The court recognized that at some future date the contractor might become liable for some of the unbilled costs, but rejected the contention that such a future cost could be considered an actual cost.

These decisions illustrate the fact intensive nature of determining when costs are incurred. Collectively, they demonstrate that a future expense must be more than merely likely or probable to be an incurred cost. …

It is undisputed that more than nine years after execution of the first note, Mr. Wadley has not demanded payment, and that the notes require Mr. Wadley to make a demand before payment is due. Even if the Board were to assume that there is a ‘near-certain future prospect’ that Mr. Wadley will demand payment, he has refrained from doing so. CMI’s liability to pay has not attached because Mr. Wadley has not taken the action necessary to trigger CMI’s obligation. Or, to use the Court of Federal Claims’ formulation, CMI is not legally bound to pay until Mr. Wadley demands payment. Accordingly, for purposes of FAR 31.001 and 52.216-7(d)(2)(ii), the Board holds that the consulting costs at issue are not incurred costs but are best described as ‘forecasted costs.’ Thus, the contracting officer correctly determined that these costs are not allowable.

In this case, the Board found that CMI had not incurred costs and it was not permitted to claim those costs as allowable expenses for government contract accounting purposes—even though it had (we assume) accrued them as liabilities on its balance sheet.

Whether or not one agrees with this decision, it is striking that no discussion of accrual accounting requirements under GAAP was made. There was no discussion of the validity of accrual accounting entries with respect to what costs have been “incurred” for government contract accounting purposes.

We noted that CMI was represented by the company’s CEO and not by a law firm well-versed in government contract disputes. Did the choice of representation affect the outcome? We couldn’t say.

However, we will venture the opinion that this case continues the worrisome trend of judges and lawyers trying to parse accounting concepts without the benefit of the opinions of actual accountants in the courtroom. In this case, we think the additional input would have been beneficial to the Board.

 

Global Fraud Resolution

E-mail Print PDF

With not much happening in terms of regulatory changes or DCAA audit guidance updates—and with nothing happening at the CAS Board—we have scaled back the frequency of blog articles. When we do post, it is likely to be about a Department of Justice settlement. Even then, we try to restrict those articles to something that may be informative, something that may impart a lesson learned to our readers.

Today, as we wind up 2021, we have another DoJ settlement and (hopefully) another lesson for our readers.

On December 22, 2012, the Department of Justice announced that it had reached a “global resolution” of both civil and criminal matters with the contractor, Balfour Beatty Communities, LLC (BBC), an entity that was described as “one of the largest providers of privatized military housing to the U.S. Armed Forces.” (BBC operated 55 military housing communities for three different services, according to the DoJ press release.) The resolution involved BBC pleading guilty to one count of major fraud against the United States (18 U.S.C. § 1031)(a)(1)). In addition, BBC agreed to pay “over $33.6 million in criminal fines and over $31.8 million in restitution to the U.S. military, serve three years of probation, and engage an independent compliance monitor for a period of three years.”

But wait. There’s more. “Separately, BBC also entered into a False Claims Act settlement with the United States to resolve its civil liability for $35.2 million. The amounts paid under the civil settlement will be credited against the amounts owed under BBC’s criminal plea.”

So basically, almost $66 million. Not a small settlement, not at all.

What had BBC done to warrant such a significant payment?

According to the press release, BBC employees falsely claimed that the company had met contractual performance objectives in order to obtain quarterly (or semi-annual) performance incentive fees. The relevant contractual objectives related to timely performance of maintenance services and resident satisfaction with BBC’s management. “BBC employees altered or manipulated data in property management software and destroyed and falsified resident comment cards to falsely inflate these metrics and, ultimately, to fraudulently induce the service branches to pay performance incentive fees which BBC had not earned.”

In addition, “the military service branches were provided an inaccurate assessment of the state of BBC’s military housing communities and were unable to assess, and potentially correct, BBC’s performance.”

The size of the fine was affected by a number of factors, “including the nature and seriousness of the offense, the pervasiveness of the misconduct among BBC’s employees and at multiple military installations, and the state of BBC’s compliance program and the progress of its remediation, including the fact that BBC’s compliance program and internal controls [had] not been fully implemented or tested to demonstrate that they would prevent and detect similar misconduct in the future.”

Finally, the announcement stated that two BBC employees had been individually charged with offenses related to the scheme, and both had pleaded guilty earlier this year.

What lessons can be learned from this?

First, many contractors have award-fee contracts or incentive-fee contracts that require a contractor’s self-assessment. Other contracts make the self-assessment optional. In either case, contractors must be clear that their self-assessments are legal documents, subject (at a minimum) to the False Statements Act. And, as this case clearly shows, false statements (or documents) may lead to allegations of violations of the False Claims Act (or the Major Fraud Act). Therefore, contractors must take care to ensure that their self-assessments are factually correct to the best of their ability. There is a natural, human, tendency to puffery in such things—but that tendency must be tempered with the knowledge that an intent to deceive could have catastrophic consequences for the company that far exceed the award or incentive fees earned. Those consequences could (and, in this case, did) extend to individual employees.

Second, note that, once again, a contractor was heavily fined for an inadequate compliance program and associated internal controls. Contractors who have accepted contracts that contain FAR clause 52.213-13 (“Contractor Code of Business Ethics and Conduct”) are urged to read it closely and to take its requirements seriously. The money you save by implementing a robust compliance program and associated internal controls may be sufficient to repay your investment, several times over.

Link to DoJ’s charges is here.

Link to BBC’s plea agreement is right here.

This is likely the last 2021 blog article. We wish for you peace and prosperity in 2022!

 

Compliance with Labor Law Stuff

E-mail Print PDF

I’m always surprised when government contractor personnel don’t want to cooperate with auditors’ requests for information. What did they expect was going to happen when they accepted that government contract?

To be clear, though, there are boundaries that should be enforced. Government auditors aren’t entitled to everything. They are, however, entitled to request and review most things. Knowing those boundaries is a key part of what every compliance practitioner needs to know. The other aspect of knowing those boundaries is explaining them to employees—often executives—who don’t know and probably don’t care, and most certainly do not want to provide to the auditors what they have requested.

They signed the contract but they didn’t read the fine print, the part in Section I where those pesky “clauses incorporated by reference” are listed. Too bad because, if they’d known what they were signing up for, they might not have signed. Or—more likely—they would have signed anyway, because revenue. But at least they would have had a clue.

Now, either during performance or perhaps after performance is complete, a government audit is happening. Auditors are requesting information, and they (quite reasonably) expect the company to provide the information requested. But somebody doesn’t want to provide the information. Why? Maybe they’re too busy right now, overwhelmed with all the other stuff they need to be doing. Or maybe they see the audit request as being unreasonable, over-the-line, beyond the pale. Government overreach. They’re just objecting based on principle.

Or maybe they have something to hide.

There’s very often no way to tell what’s really going on. Nobody can read minds. (Or, if you can read minds, then you are definitely in the wrong line of work.) But what’s often forgotten in the internal debate over what can and should be provided to the auditors is the point that the auditors can’t read minds either. They don’t know why the company won’t provide what they’ve requested—and they often default to the worst position: the company won’t provide the information because there is something to hide.

We were reminded of the rules about what can and should be provided versus what should not be provided by this news brief issued by the Department of Labor. As you can see (if you follow the link), the Department of Labor Administrative Law Judges have ordered a government contractor to provide information and documents related to a review of the contractor’s affirmative action program.

As we reviewed the case, it seems that this issue has been in play since 2013. Yes, that’s right. For eight years, a government contractor has disputed the Department of Labor’s right to review its affirmative action plans.

Anyway, after eight years of dispute (and eight years of paying attorney fees), the government contractor was told in no uncertain terms to comply “upon penalty of debarment and contract termination.” That would be quite a hit to the company’s revenue, we believe. Not a great hill to die on, in our view.

The DoL Judge found that the contractor “violated 41 C.F.R. § 60-1.12(c)(2) by failing to provide its written affirmative action programs and supporting data upon request, and that Defendant did not have good cause to excuse the violation.” This was after the contractor had argued that the audit requests were “unconstitutional under the Fourth Amendment because OFCCP has failed to articulate a basis for having selected any of [the contractor’s] facilities for compliance review according to a neutral administrative plan. [The contractor] further argues that the number of document requests is unreasonably burdensome….”

Yeah, no.

Defendant [the contractor], through its officers, directors, partners, representatives and agents, jointly and individually, shall provide all information Plaintiff [the Department of Labor] requested in the scheduling letters that were identified in the administrative complaints filed in these consolidated cases. Defendant shall provide the information to Plaintiff’s representatives no later than 4:00 PM on the business day next following the thirtieth calendar day after this Order becomes final under the law.

Should Defendant fail to comply with the Order set forth above, Plaintiff is directed to take all administrative steps necessary to terminate all existing Government contracts held by Defendant, jointly and individually, and to debar Defendant from receiving and participating in any future Government contracts for a period of at least three years or until Defendant complies with the provisions of EO 11246, the VEVRAA, the Rehabilitation Act, and 41 C.F.R. Chapter 60, whichever period is longer.

The next time some executive in your company wants to dispute the government’s right to request, receive, and review documents for which it clearly has the authority to request, receive, and review, we suggest you mention this little lesson.

 

Criminal Conspiracy to Illegally Restrain Wages?

E-mail Print PDF

On December 9, 2021, the Department of Justice reported that a criminal complaint against an individual executive of Raytheon Technologies’ subsidiary, Pratt & Whitney, had been unsealed. As most readers know, Pratt & Whitney is a huge manufacturer of various airplane engines (2017 revenues in excess of $16 billion), with a long history as a U.S. defense contractor.

According to the criminal complaint, a (now former) Pratt & Whitney Director of Global Engineering Sourcing, participated in “a long-running conspiracy with managers and executives of several outsource engineering suppliers (Suppliers) to restrict the hiring and recruiting of engineers and other skilled laborers among their respective companies.” The complaint alleged that Mahesh Patel “enforced this agreement while serving as an intermediary between conspiring Suppliers.”

The DOJ announcement provided some details of the allegations, as follows—

Patel upheld a conspiracy among aerospace companies [the Suppliers] not to hire or recruit one another’s employees. At times, Patel confronted and berated Suppliers who cheated on the agreement, often at the direct behest of another Supplier, and threatened to punish nonconforming Suppliers by taking away valuable access to projects. In addition, as the complaint alleges, Patel and co-conspirators recognized the mutual financial benefit of this agreement — namely, reducing the rise in labor costs that would occur when aerospace workers were free to find new employment in a competitive environment.

Reading between the lines a bit, it seems that Patel felt pressure to hold down the labor costs of providers of outsourced engineering services. Was that cost-control pressure (if it existed) exerted on him from above, or was it created in his mind in order to justify his value-add to the company? We (obviously) don’t know, but we assume it will come out in the trial.

Speaking of the trial, the DOJ announcement stated that Patel was charged with “conspiracy in restraint of trade.” Our (non-legal) understanding of the allegation is that Patel has been charged with a violation of the Sherman (Anti-Trust) Act.

Patel was arrested. Yes, that’s what happens when somebody is charged with a criminal complaint. Patel was arrested and he appeared before a Judge. After his appearance, Patel “was released on conditions including travel restrictions and a $100,000 appearance bond.” The DOJ press release stated—

The maximum penalty for conspiracy to restrain trade under the Sherman Antitrust Act is 10 years of imprisonment and a fine of $1 million for individuals. The maximum fine may be increased to twice the gain derived from the crime or twice the loss suffered by the victims of the crime if either amount is greater than the statutory maximum fine.

So, yes, individuals can and will be charged when the Federal government believes that circumstances warrant doing so. It’s not always the companies that are on the hook, and issues are not always solvable by monetary settlement alone.

And speaking of companies … the DOJ announcement added the following sentences:

“The charges are the result of an ongoing federal antitrust investigation into market allocation in the aerospace engineering services industry … The charge against Patel is the first in this ongoing federal antitrust investigation.”

So, yeah, other aerospace companies doing business in the Northeast might want to perform a bit of diligence in this area, to make sure that they themselves are not exposed to allegations of Sherman Act violations. We’re just sayin’ ….

Reminder: A criminal complaint is merely an allegation, and all defendants are presumed innocent until proven guilty beyond a reasonable doubt in a court of law.

 


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