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

Why Won’t Contracting Officers Settle Questioned Direct Costs? (Part 1)

E-mail Print PDF

A couple of friends and I will be starting a podcast soon, discussing government contracting things. Looks like it will be available every two weeks. The other two participants are former contracting officers and former DAU instructors. I think the only reason they asked me to participate is for comic relief.

I’m supposed to bring “two or three topics” to each podcast. We’ll see how that goes. I may be like the SNL castmember who doesn’t return after their first season. Anyway, one of my topics for the first podcast will be the recent Department of Defense Inspector General audit report where – once again – the offer criticism of DCMA contracting officers for not doing what DoDIG thinks they should be doing. In this case, it concerns settlement of direct costs questioned by DCAA during their “incurred cost” audits (which should really be called audits of “proposals to establish final billing rates,” but we’ll get into that later in this article.)

In DoDIG Audit Report No. DODIG-2021-047 (“Evaluation of Department of Defense Contracting Officer Actions on Questioned Direct Costs”), the auditors offered a conclusion regarding whether “the actions taken by DoD contracting officers on questioned direct costs reported by the Defense Contract Audit Agency (DCAA) complied with the Federal Acquisition Regulation (FAR), DoD Instructions, and agency policy.”

Before we get into the audit report, though, you need to know that the DoD IG has a long history of sniping at DCMA contracting officers—most of which has been documented on this blog. This particular audit report noted that it was following-up on a 2017 audit report. We discussed that audit report in this article. As with the prior audit report, in this audit report the DoD IG accepted DCAA findings as being accurate, and criticized DCMA contracting officers for not addressing DCAA’s findings timely and therefore “DCMA contracting officers may have reimbursed DoD contractors up to $231.5 million in costs that may be unallowable on Government contracts in accordance with the FAR.” May have being the key phrase. The IG auditors don’t know. But it sure makes a good headline, right?

Here’s some other stuff you need to know before we get into the audit report:

Each contract has a cognizant contracting officer (often called the “procuring contracting officer” or PCO), but contract administration functions may be “assigned” (or delegated or transferred) to a Contract Administration Office (CAO). The entire post-award contract administration function, or portions of it, or “specialized services” may be assigned from the PCO to the CAO. Contract administration functions are listed in the FAR, at 42.302. There are 82 of them. In addition, DFARS 242.302 lists a few more contract administration functions.

There are certain functions that are “normally delegated” to a CAO (71 out of 82) and there are certain functions that must be delegated to a CAO. Functions that are mandatory for delegation include:

  • Negotiation of forward pricing rate agreements

  • Establish final indirect cost rates and billing rates for those contractors meeting the criteria for contracting officer determination

  • Administer Cost Accounting Standards (CAS) matters

  • Determine the adequacy of the contractor’s accounting system

Those functions must be performed by a CAO contracting officer, and not by a PCO. The rationale should be fairly obvious: those are cross-cutting issues that affect all contracts (perhaps contracts awarded by another agency) and administration of those issues requires a bigger picture than a PCO would typically get. The CAO contracting officers that handle those issues are typically called “Administrative Contracting Officers” (ACOs). But there are different flavors of ACO; some ACOs are called ACOs but others are called Divisional Administrative Contracting Officers (DACOs) and still others are called Corporate Administrative Contracting Officers (CACOs). A DACO handles cross-cutting issues for a contractor segment or division or sector (or whatever the contractor calls it) whereas a CACO handles cross-cutting issues across an entire corporation, and coordinates the activities of multiple DACOs and/or ACOs.

One thing we’ve noticed is that neither the FAR nor the DFARS actually describes the role of a DACO or ACO. The regulations are silent on what those functions do and how they differ from each other. As we will see, that gap gave the DoD IG auditors some wiggle room to create audit findings.

The DoD IG audit report states, “For DCAA incurred cost audit reports, the DCMA is generally responsible for determining whether the DoD contractor’s claimed indirect and direct costs are allowable in accordance with contract terms and FARs Subpart 31.2 and for negotiating a final indirect cost rate agreement that will be used to close the contractor’s contracts.” Now we are going to quote from the audit report because what follows is the central thesis of the DoD IG auditors:

DCMA Manual 2201-03 [“Final Indirect Cost Rates,” February, 14, 2019] requires DCMA divisional administrative contracting officers (DACOs), who are usually the primary recipients of a DCAA incurred cost audit report, to settle any questioned indirect costs and prepare the final indirect cost rate agreement. According to DCMA Manual 2201-03, DCMA administrative contracting officers (ACOs) must settle any questioned direct costs. DCMA Manual 2201-03 does not indicate whether DCMA DACOs have the authority to settle direct costs. However, the Manual does state that the DCMA DACO must coordinate and obtain settlement results from DCMA ACOs, DoD Component contracting officers, and Government agency contracting officers, who have the responsibility for settling DCAA questioned direct costs relating to one or more of their contracts. The DCMA DACO and DCMA ACO are collectively referred to in this report as DCMA contracting officers.

(Emphasis added.)

Because the regulations (and DCMA guidance) are silent on the varying roles of ACOs, DACOs, and CACOs, the IG auditors felt free to lump them all together and call them, collectively, “DCMA contracting officers.” When that happens, then an opportunity arises to criticize the “contracting officers” for not following guidance.

The issue is who has the authority to settle questioned direct costs. There is no question that an ACO or DACO or CACO must settle indirect cost rates. There is no question that an ACO must settle questioned direct costs. There is no question that a DACO (or CACO, we assume) must “coordinate” the activities of the ACOs in effectuating settlement of questioned direct costs. But do DACOs (or CACOs) have the authority to settle direct costs on their own? The guidance doesn’t say. But the IG auditors will assert that they do have that (unwritten) authority, and will then criticize them for not exercising it.

The DoD looked at DCAA audit reports and examined how DCMA “contracting officers” dispositioned or settled the audit findings. The audit report stated:

We selected 26 DCAA audit reports from a universe of 68 DCAA audit reports that each questioned over $1 million in direct costs and were reported as settled in the CAFU system by DoD contracting officers between October 2017 and September2018. The DCAA issued the 26 DCAA audit reports for settlement between February 2006 and September 2017. In total, the 26 DCAA audit reports identified $597.4 million in questioned direct costs because the auditors determined that the costs were unallowable in accordance with FAR subpart 31.2. Common reasons for the DCAA questioning the direct costs included instances where contractors did not provide sufficient supporting documentation of the costs or where DCAA auditors determined that the costs were unreasonable in accordance with FAR 31.201-3.

DCAA questioned nearly $600 million in direct costs through issuance of 26 audit reports over a nearly 11-year period. But wait! Should they have? Should those audit reports have been issued?

Let’s ask the question “should DCAA have been looking at both direct and indirect costs in the same audit?” This would seem to be a reasonable question, because of the bifurcated settlement process discussed above. Some CAO contracting officers settle indirect cost rates, and others settle questioned direct costs. Given the disparate nature and responsibilities associated with dispositioning DCAA audit findings, one might reasonably think that two audit reports would be created, addressed to the appropriate contracting officer. Such is not the case.

But should it be the case? At least one distinguished body thought so, and made that recommendation.

In the next blog article, we’ll explore the Section 809 Panel’s recommendations in this area, and continue our criticism of the DoD IG criticism of the DCMA contracting officers who, the auditors asserted, had failed to execute their (unwritten) responsibilities.

 

2021 NDAA Analysis

E-mail Print PDF
Somebody I follow asserted that 2021 didn’t actually start until January 21, 2021. I want that to be true, because January 6th belongs with 2020, doesn’t it? Regardless of your position on the matter, for defense contractors 2021 could be said to have started on January 1, 2021, which is a nice alignment with the calendar. That’s the date when the William M. (Mac) Thornberry National Defense Authorization Act (NDAA) for Fiscal Year 2021 became public law.

The 2021 NDAA became public law on that date because that’s the date Congress voted to override the President’s veto of the bill. It was President Trump’s tenth veto of a bill during his four-year term, but the first veto to be overridden by Congress. The date of the override becomes the date of the public law, or so we’re told.

For the twentieth year in a row, Bob Antonio at WIFCON.com published his invaluable analysis of the NDAA, section by section. As has become tradition here, we’ll take a look at his analysis and bring certain highlights to your attention. But if you want to know more, there is no better source than his analysis, and we encourage you to go read it.

The most relevant section for compliance folks would be Section 806. In that Section, Congress directed significant changes to the contractor business system administration regime. Well, we think they’re significant. You be the judge. Anyway, Congress make revisions to the 2011 NDAA language that first established the contractor business system administration rules, replacing the term “significant deficiency” with “material weakness” to better align audit/review findings with other audits/reviews of internal controls, thus reducing confusion among practitioners and (hopefully) reducing confusion among those who have to deal with audit/review reports and findings.

We’ve spent a decade dealing with “significant deficiencies” and most of us have learned that a significant deficiency inexorably leads to a contractor business system being determined to be inadequate. During that decade, contractors have argued (largely unsuccessfully) with auditors and contracting officers about whether or not a deficient is actually “significant” or not. So what’s changing?

Here’s the official definition of “material weakness” from the NDAA:

The term `material weakness' means a deficiency or combination of deficiencies in the internal control over information in contractor business systems, such that there is a reasonable possibility that a material misstatement of such information will not be prevented, or detected and corrected, on a timely basis. For purposes of this paragraph, a reasonable possibility exists when the likelihood of an event occurring--

(A) is probable; or

(B) is more than remote but less than likely.

The linkage to the more traditional audits/reviews of contractor internal controls should be obvious. But let’s break that definition down a bit more:

  • A single deficiency or a combination of deficiencies

  • In internal control over information in contractor business systems

  • Leading to a reasonable possibility

  • That a material misstatement

  • Will not be prevented

  • Or detected and corrected

  • On a timely basis

  • Where “reasonable possibility” cannot mean a remote possibility

Points likely to lead to a disagreement include: (1) What is a “material misstatement” and (2) what is a “timely basis”. With respect to “material misstatement” we have fairly recent DCAA guidance on how to quantify materiality. While that guidance only applies (formally) to contractor’s incurred costs, informally most people (including DCAA leadership) agree it can—and should be—applied more broadly. We see no reason that the materiality guidance could not be extended to DCAA audits of contractor business systems. As for DCMA, there is materiality guidance found in FAR Part 30, which is applicable to CAS cost impact proposal analysis and related determinations. Again, there is no reason that materiality guidance couldn’t be extended to DCMA reviews of contractor business systems. We very much hope it will be.

Which leaves “timely basis.” What does that mean in the context of government contracting? We don’t have much in the way of authoritative answers, and the correct answer will probably depend on the context. For example, with respect to calculating indirect cost rates, we would hazard the position that “timely” means “before the end of the contractor’s fiscal year.” But with respect to complying with Limitation of Cost/Limitation of Funds requirements, “timely” could well mean something else. There are other contexts to consider as well, including Truthful Cost or Pricing Data requirements (aka “TINA”). So we’ll just have to wait and see what the contracting parties make of it.

Getting back to the NDAA, Congress continues to play with the increase in the TINA threshold. Section 814 formally increased the threshold at which certified cost or pricing data must be submitted to “a standard $2.0 million threshold for application of the requirements of the Truthful Cost or Pricing Data statute (commonly known as the Truth in Negotiations Act) with respect to subcontracts and price adjustments.” (Of course, this is the value assuming no exception applies.)

There are dozens of other Sections to be reviewed, but most of those are pointed at the Department of Defense in general, and we expect any impacts to contractors will be primarily indirect in nature. The two above are the ones that struck us as being most worthy of discussion. That being said, you shouldn’t rely on our judgment; you should follow the link we provided and do your own research.

 

2020 Hindsight

E-mail Print PDF

The last article in 2020 will be a bit introspective.

Let’s start with the numbers: in 2020 Apogee Consulting, Inc. published 73 articles (74 if you count this one). That’s a serious increase from 2019’s count of 51 articles published. Seventy-three didn’t seem like a lot to me; there were long periods where nothing much was published. Most of those fallow periods were the result of client work: I co-instructed a week-long class in Northern England last January, and (as always) the editing of two LexisNexis reference books takes hundreds of hours. But client work wasn’t the sole reason: after the November election it became harder to write about government stuff. That is not a political observation; it is a personal one. It became harder for me to write blog articles. Nothing I saw or learned seemed to spark the need to write about it. Still, I managed some production. Not as much as I intended, but as much as I could.

So: 2020 sucked for a lot of people on any number of levels. But let’s look at Apogee Consulting Inc.’s numbers:

  • 73 articles published on this website (74 if you count this one). This article will be number 1,348 in the News Archive. If you assume the average article is 800 words (which is a reasonable assumption over the 10-year period even though the later articles tend to average 1,000 words or more), the math says that’s more than one million words devoted to this stuff.

  • 2 textbooks edited for Thompson Reuters/LexisNexis (one on FAR and the other on CAS)

  • 1 class co-instructed with Don Acquisition in Northern England (“Introduction to FAR and DFARS”)

  • 1 six-week class for San Diego State University’s World Campus migrated to a Canvas/Zoom environment and taught (“Financial Management of Government Contracts”)

  • Participated in a panel discussion on “Commercial Item Myths” with Brent Calhoon (of Baker Tilly) and Ryan O’Connell (of DoD’s Commercial Item Group)

  • Co-Led a workshop on “CPSR Preparation” with Luis Avila (of KMPG)

  • 1 article published in the Government Contracts Costs, Pricing and Accounting Report (“Explaining the DFARS Ground and Flight Risk Clause”)

  • 1 comment letter to the CASB written (it will be submitted this week and I’ll post it on the website)

  • 2 new clients brought on, in addition to supporting other long-term clients at various levels

I cannot say that 2020 sucked for Apogee Consulting, Inc., at least from a business perspective.

Looking at the government contracting environment, obviously the big news was COVID-19 and the response to the pandemic. Certain small business contractors availed themselves of the CARES Act Section 1102 Paycheck Protection Program, while other contractors used the CARES Act Section 3610 contractor paid leave provisions. In 2021, I expect that contractors will begin submitting Section 3610 reimbursement requests (if they haven’t done so already) and we’ll be hearing stories about audits of those requests.

For those who want a quick primer on all the COVID-19 related legislation and the provisions that impact government contractors, DCAA has developed a handy chart to aid its auditors. The chart lists legislation, regulations, and other government guidance. It also has an FAQ section that anybody who has COVID-19 related costs should read.

With respect to other DCAA audit guidance, 2020 once again saw very few actual MRDs being published on the website. We very much suspect that the majority of DCAA guidance is being published internally, on the audit agency’s intranet. That makes it harder to understand where DCAA is coming from and to prepare for upcoming audits, but that’s how we see it.

In 2020, DCAA also flirted with reorganizing its audit staff to focus on defective pricing audits and business system audits. We say “flirted” because, according to what we’ve been told, the reorganized Regional Business System expert teams have been (or soon will be) disestablished, so that the Branches can resume their traditional roles of auditing contractor business systems. Was it the Coronavirus impact—or some other agency politics—that led to the quick course correction? We couldn’t say. But having experienced business system audits under both the “center of excellence” and traditional Branch-led audit approaches, we prefer the latter. There is less “ramping up” learning required.

2020 was a busy year for the CAS Board, if only by comparison to the prior decade’s inactivity. A Staff Discussion Paper was issued, as well as an Advance Notice of Proposed Rulemaking. However—and as we’ve noted several times on this blog—not much seems to happen without an active industry member contributing to the process. The Board has been without an industry member for nearly a year now, and has been moving forward based on inertia, in my view. I don’t expect much from the Board in 2021. You can decide whether the forecasted lack of activity stems from a lack of industry membership or the fact that a new administration is (as I write this) coming into town with its own set of priorities.

2021 may be the year that commercial items become what they were intended to be, 25 years ago when the last significant acquisition reforms took place. There are a couple of proposed rules that could, if implemented as drafted, significantly change the landscape. I’ll be watching for those.

We are all placing a lot of hope in 2021. And it’s not just about acquisition reform or precedent-setting judicial decisions. Each one of us has suffered personal or business setbacks in 2020, and we are all hoping that 2021 puts us back on course.

So here’s to putting 2020 behind us, and moving forward into a better year.

 

Re: CASB 2020–02

E-mail Print PDF

Apogee Consulting, Inc.

P.O. Box 759

Poway, CA 92074

(949) 705-9773

www.apogeeconsulting.biz

January 2, 2021

Mr. Mathew Blum

Office of Federal Procurement Policy

725 17th Street NW,

Washington, DC

20503

Re: CASB 2020–02

Advanced Notice of Proposed Rulemaking

Conformance of the Cost Accounting Standards

to Generally Accepted Accounting Principles for

Operating Revenue and Lease Accounting

Dear Mr. Blum,

This letter provides comments in response to the subject Advanced Notice of Proposed Rulemaking (ANPRM) published in the Federal Register November 5, 2020. The proposed rule discusses potential changes to the definition of “operating revenue” and the treatment of certain leases. I understand that, in promulgating the ANPRM, the CAS Board is implementing the direction of Congress as provided by Section 820 of Public Law 114-328, which directed the CAS Board to conform CAS to GAAP to the maximum extent practicable.

Apogee Consulting, Inc., is a boutique consultancy focused on the administrative needs of government contractors. Our clientele includes both large and small contractors, selling to diverse Federal agencies including the Department of Defense, the Department of Energy, and the Federal Transportation Administration.

That being said, I provide these comments as an individual. My opinions are my own and do not reflect those of any client or other entity.

  1. Operating Revenue

The Board proposes “to rely on a definition of operating revenue that is more closely aligned to GAAP.” In doing so, the Board further proposes to modify the GAAP definition to be inserted at 9904.403-50(c)(1)(2) so as to restrict the calculation of operating revenue to only fee earned “for management contracts under which the contractor essentially acts as an agent of the Government in the erection or operation of Government-owned facilities.” The rationale provided for this limitation is that “government-owned, contractor operated (GOCO) facilities ‘receive little or no benefits from home office activities’; and, without the limitation to fee, some contractors would be ‘forced to make greater allocations to GOCO’s than would be reimbursed to them under the terms of some GOCO contracts.’”

I appreciate the Board’s concerns in this area, and I agree that contractors should not be “forced” to allocate home office costs for which they will not receive reimbursement. That being said, the modification of the GAAP definition of “operating revenue” with respect to CAS 403-50(c) is unnecessary. The existing Cost Accounting Standards and regulations have sufficient flexibility to accommodate the GAAP definition—without modification—while protecting the contracting parties from having to make excess home office allocations to certain segments.

  1. Residual expenses are those home office expenses that are not otherwise allocable to segments. If a beneficial or causal relationship between home office expenses and segments could be established, then such expenses already would have been allocated to segments either directly to the segment, pursuant to 403-40(a)(1), or via an allocation base specified by 403-40(b)(1) – (b)(5). These home office allocations correspond to a contractor’s Disclosure Statement (CASB DS-1) at Part VIII, 8.3.1 (“Directly Allocated”) and 8.3.2 (“Homogeneous Expense Pools”). Thus, by definition, residual expenses are those home office expenses that are not susceptible to being allocated on a beneficial or causal basis; if they could be so allocated, then CAS 403-4(a)(1) requires that they must be. Consequently, the notion that some GOCO segments would receive excess allocations, based on a beneficial analysis of those allocations, seems to be contradicted by the very definition of residual home office expenses.

  1. Standard 403 already protects the Government from home office allocations where a segment receives little or no benefit from a particular home office function or activity.

  1. 403-50(a)(2) states that “Where the expense of a given function is to be allocated by means of a particular allocation base, all segments shall be included in the base unless … [a]ny excluded segment did not receive significant benefits from, or contribute significantly to the cause of the expense to be allocated …”

  2. 403-40(c)(3) states that “Where a particular segment receives significantly more or less benefit from residual expenses than would be reflected by the allocation of such expenses pursuant to paragraph (c) (1) or (2) of this subsection … the Government and the contractor may agree to a special allocation of residual expenses to such segment commensurate with the benefits received.”

  3. 403-50(d) establishes rules for determining when a segment has received significantly less benefit in relation to other segments. In particular, 403-50(d)(2) identifies segments that may require special allocation as being “foreign subsidiaries, GOCO's, domestic subsidiaries with less than a majority ownership, and joint ventures.” (Emphasis added.)

Therefore, the notion that contractors would be “forced to make greater allocations to GOCO’s than would be reimbursed to them under the terms of some GOCO contracts” seems to be unfounded. To the extent that a GOCO (or other segment) received less benefit from a home office activity or function than would be commensurate with the normal allocation of residual home office expenses, the contractor and the government should agree on a special allocation, as provided by 403-40(c)(3).

In addition to the foregoing, I note that the issue of excess residual home office allocations has been exacerbated by the Board’s failure to modify the thresholds at which the three-factor allocation formula found at 403-50(c) must be used. If the thresholds had been raised—for example, to take into account the impact of cumulative inflation experienced since original promulgation in 1972, which has been estimated to be more than 600 percent—then fewer contractors would be forced to use the three-factor allocation formula found at 403-50(c)(1), which includes the current definition of “operating revenue.” Thus, one simple fix to address the Board’s concern with potentially excessive residual home office allocations is to raise the 403-40(c)(2) thresholds to levels more appropriate for the twenty-first century.

2. Should changes to cost accounting practices to conform Operating Revenue to ASC 606 be considered to be a required change, a unilateral change, or desirable change?

In the ANPRM, the Board stated “The Board believes that the definition in GAAP is essentially equivalent to the CAS definition….” If the two definitions are essentially equivalent, it is difficult to envision what changes to contractor cost accounting practice might flow from the revision of the definition of Operating Revenue in Standard 403.

The Board may be asking a broader question—i.e., will any contractor changes to cost accounting practice made as a result of conforming CAS and GAAP be required changes, unilateral changes, or desirable changes? If that is the question, I suggest it should be the subject of a separate Staff Discussion Paper. It is not clear why the Board would be asking such far-reaching questions in an ANPRM, rather than in an SDP. Nonetheless, I will attempt to respond to the question.

As a threshold matter, the Board should be aware that the CAS contract clauses found in 9903.201-4 (dated JUL 2011) appear to be obsolete when compared to the FAR contract clauses 52.230-2 through 52.230-5 (dated JUN 2020). This is based on a comparison of the clauses found at www.acquisition.gov, which is the official regulatory repository for the U.S. Government. This is an issue that the Board may wish to address in a future rule-making action.

To address the Board’s question, when a contractor changes a cost accounting practice solely because of changes to GAAP requirements (absent any changes to a Standard), that would seem to be a unilateral change (i.e., “a change in cost accounting practice from one compliant practice to another compliant practice that a contractor with a CAS-covered contract(s) elects to make that has not been deemed desirable by the cognizant Federal agency official and for which the Government will pay no aggregate increased costs.”) I believe this is the case because a required change is defined as “a change in cost accounting practice that a contractor is required to make in order to comply with applicable Standards, modifications, or interpretations thereto,” or “a prospective change to a disclosed or established cost accounting practice when the cognizant Federal agency official determines that the former practice was in compliance with applicable CAS and the change is necessary for the contractor to remain in compliance [with CAS].” Since CAS is not changing—i.e., there is no change to an applicable Standard or interpretation thereto—then it seems clear that any change in cost accounting practice solely driven by changes in GAAP requirements do not meet the definition of a required change. They must therefore be unilateral changes.

Some unilateral changes may be found to be desirable changes (i.e., “a compliant change to a contractor's established or disclosed cost accounting practices that the cognizant Federal agency official finds is desirable and not detrimental to the Government and is therefore not subject to the no increased cost prohibition provisions of CAS-covered contracts affected by the change.”) But the determination and finding that a unilateral change is a desirable change is solely within the discretion of the cognizant Federal agency official and is to be decided based on the individual facts and circumstances of the change. The Board need not provide any further direction.

There are two use cases where the Board’s question poses a challenge. First, when conformance with GAAP results in a change or modification to an existing Standard that compels a contractor to then make a change in cost accounting practice. Second, when conformance with GAAP results in an elimination of a Standard, such that a contractor must now comply solely with GAAP—and that situation compels a contractor to then make a change in cost accounting practice. The second case seems probable if CASB Case 20-001 (the SDP regarding potential elimination of Standard 404 and/or 411) results in the elimination of one Standard or both.

    1. In the first case, the requirements of an existing Standard have been modified. Therefore, any contractor change in cost accounting practice that becomes necessary in order to comply with the modified Standard would seem to meet the definition of a required change. Consequently, the parties would need to negotiate an equitable adjustment as required by 9903.201-4(a)(4) and the contract’s Changes clause.

b. In the second case, there is no modification to an existing Standard; indeed, a Standard will be eliminated in its entirety. If the contractor must now change a cost accounting practice in order to comply with GAAP, then it follows that it was the requirements of the original Standard that compelled the contractor’s original cost accounting practice. In other words, the original cost accounting practice was required to comply with CAS. With the elimination of the Standard, the contractor must now comply with GAAP. (See 48 CFR 31.201-2(a): “A cost is allowable only when the cost complies with all of the following requirements … (3) Standards promulgated by the CAS Board, if applicable, otherwise, generally accepted accounting principles and practices appropriate to the circumstances.”) (Emphasis added.)

The elimination of a Standard that compels a contractor to make a change to cost accounting practice in order to comply with GAAP would seem to be a required change. Although the change in this use case does not meet the exact regulatory definition of “required change,” it was the contractor’s original cost accounting practice that was required to comply with the Standard. The requirements of the Standard distorted what the contractor’s cost accounting practice would otherwise have been. Therefore, if the elimination of that distortion requires a change in cost accounting practice in order to comply with GAAP, then that change should be treated as a required change, just as in the first use case.

3. Lease Accounting

I have no comment on the Board’s proposed clarification that right-of-use leases are neither tangible nor intangible capital assets for purposes of complying with CAS requirements. In its ANPRM, the Board wrote “Before right-of-use assets are considered for inclusion on balance sheets, the Board would need to further analyze the impact of these changes.” I would encourage the Board to proceed with its analysis. Conformance of CAS and GAAP may require some flexibility on the Board’s part with respect to traditional US-GAAP accounting treatment, and it is important to understand consequences associated with any changes that may come from conformance.

I am pleased to see the Board address these (and other) issues. However, in this comment letter I have also tried to point out other related areas that seem overripe for the Board’s attention. Among those issues are: (1) increase of the thresholds at 9904.403-40(c)(2) to address (if nothing else) actual inflation experienced since they were first promulgated, and (2) analysis and comparison of the 2020 FAR CAS-related clauses with the 2011 clauses found in the CAS regulations. Both of these areas would seem to be “low-hanging fruit” that would be worthy of the Board’s attention.

Thank you for considering these comments to the Advance Notice of Proposed Rulemaking.

Sincerely,

Nicholas Sanders

President and Principal Consultant

Apogee Consulting, Inc.

 

Government Furnished Property Problems

E-mail Print PDF

FAR Table 15-2 establishes the standard format for providing certified cost or pricing data. It lists the types of cost or pricing information and how that information should be organized. As part of the Table, the first page of a contractor’s proposal is discussed. In that section, the instructions state that the contractor must identify “whether you will require the use of Government property in the performance of the contract, and, if so, what property.”

We don’t know whether FAR Table 15-2 was part of the BGT Holdings, LLC (BGT) proposal to the U.S. Navy to “construct and deliver a gas turbine generator.” We only know that BGT was awarded an $8.25 million fixed-price contract in 2014 to do so. The contract identified at least two Government Furnished Equipment (GFE) items: an exhaust collector and engine mounts. Those items were to be provided by the Navy so that BGT wouldn’t need to source them.

Presumably, when the Navy and BGT agreed on the contract price, both parties knew that certain items were going to be provided to BGT as GFE. Presumably, the agreed-upon price was lower than it otherwise would have been, because BGT didn’t include costs associated with GFE in its proposal. Those are big presumptions; however, they seem reasonable because that’s how GFE normally works.

Another big presumption (on BGT’s part) was the presumption that the GFE would show up on time, and in working condition. The contractor was going to base its price (and schedule) on that presumption. And if the GFE didn’t show up on time (or in working condition) then BGT was going to have a problem.

Another big presumption (on BGT’s part) was that the Navy was not going to hold the contractor hostage. Very few people would expect the Navy to withhold the GFE and refuse to provide it “unless BGT provided a ‘cost savings’ to the Navy, i.e., a decrease in the contract price commensurate with the amount BGT would save by not having to procure the exhaust collector and engine mounts on its own.” Yet, that was exactly the behavior that BGT alleged it experienced during contract performance.

Allegedly, when BGT refused to provide a cost savings, it was told that “that the exhaust collector and engine mounts had been reallocated as fleet assets and would no longer be made available to BGT.” BGT then purchased those items (at a cost of $610,775) and submitted a request for equitable adjustment to the contract price to the Navy contracting officer. The REA was denied and BGT filed an appeal at the Court of Federal Claims, citing five grounds for relief.

The Court of Federal Claims dismissed BGT’s first three counts and BGT appealed to the Federal Circuit, which vacated and remanded on two of the three counts. We want to discuss the appellate decision because it has important information for contractors that deal with Government Furnished Property (or Government Furnished Equipment). Sometimes, a prime contractor will offer to procure and provide certain items to a subcontractor, and this decision would be relevant to those transactions as well. So let’s discuss.

The three Judges that heard the case and concurred with the decision (which was written by Judge Bryson) summarized their reasoning thusly:

The most straightforward claim in BGT’s amended complaint is that the Navy breached the government property clause, 48 C.F.R. § 52.245-1, by failing to provide an equitable adjustment after it withheld the GFE items it had agreed to deliver under the contract. While the Navy was entitled to withdraw GFE under the government property clause, it was not free to do so without consequence.

Further, by refusing to provide an equitable adjustment when the Government Property clause in the contract provided for one, the Navy had breached the contract. The government disagreed but the Court was not persuaded.

The government argues that BGT’s claim under subsection (d)(2)(i) [of the Government Property clause] is untenable because the contracting officer was required only to ‘consider BGT’s request for an equitable adjustment—not to grant the adjustment to BGT.’ Under the government’s theory, the phrase ‘shall consider’ gave the contracting officer discretion to grant or deny an equitable adjustment and imposed no duty to grant an adjustment even if BGT could prove financial loss due to the government’s withdrawal of the exhaust collector and engine mounts. We reject the government’s interpretation of the term ‘shall consider’ because it would produce absurd results under the government property clause.

…

It is dubious, to say the least, that the drafters of the FAR’s government property clause, 48 C.F.R. § 52.245-1, envisioned that the government would essentially have an unfettered right to withdraw promised GFE from a contract without consequence. The correct interpretation of ‘shall consider’ in this contract setting does not give the government absolute discretion, but instead holds the government to a duty of good faith and reasonableness. … Moreover, the FAR demands that the contracting officer exercise impartiality, fairness, and equitable treatment when considering requests for equitable adjustments. The government’s interpretation of ‘shall consider’ would invite subversion of that responsibility.

(Internal citations omitted.)

BGT also argued that it was entitled to an equitable adjustment under the contract’s Changes clause, wholly apart from the language of the contract’s Government Property clause. The Appellate Court did not rule on the merits of that argument, but it did vacate the Court of Federal Claim’s decision and remand for another trial, in which the Court of Federal Claims will “determine whether BGT pleaded facts sufficient to support its ratification theory and, if so, whether BGT can prove that the contracting officer ratified the withdrawal of the exhaust collector and engine mounts.” The Appellate Court also remanded to the Court of Federal Claims to determine whether BGT’s third count was supported by facts.

In summary, this is a puzzling case. The Navy awarded an $8.25 million fixed-price contract and, in doing so, had to find that the contract price was fair and reasonable. That contract price was based on certain items being provided by the Government to the contractor. It is unclear why the Navy would ask for a second price decrease during performance for those same items. (Which is what BGT alleged to have happened.)

More generally, contractors and subcontractors who rely on GFP/GFE and customer-furnished property to perform their contracts are taking risks. They should be aware of those risks and have risk mitigation plans in place. They should be alert to possible contract changes related to the GFP/GFE and be prepared to submit requests for equitable adjustment when they believe their contract had been changed because of delayed or faulty GFP/GFE.

We will have to see how BGT fares back at the Court of Federal Claims. Hopefully, the parties have had enough litigation and will be able to settle this dispute outside of a decision on the merits. But if that’s not the case, then the Federal Circuit has provided the Court of Federal Claims with a roadmap to resolve the matter.

 


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