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

Let Us Welcome Public Law 111-240, the Small Business Jobs and Credit Act of 2010

E-mail Print PDF


On September 27, 2010, the President signed into law H.R. 5297, the Small Business Jobs and Credit Act of 2010—now P.L. 111-240. The new law is long and fairly complex. Rather than recap its many provisions that affect government contractors, we are going to link to an excellent summary by the law firm Venable LLP.

Go check out Venable’s summary. What? You’re too lazy to click the link? Okay, then here is a very brief list of some of the interesting items contained in the new public law. We are quoting from Venable. You should really go review their summary, instead of reading our recap of their recap.

  • Contractors that misrepresent their size status are presumed to be liable for the amount which the government expends on a contract intended for small businesses.

  • A contractor that believes in good faith that his company is small (based on his understanding of the affiliation rules and the calculation of annual receipts during the relevant period) will be ‘deemed’ to have affirmatively, willfully, and intentionally misrepresented the company’s size status if the company is not actually small.

  • The law now requires all small businesses to recertify their size status on an annual basis through the Online Representations and Certifications Application.

  • The new law imposes new past performance and potential non-responsibility consequences on prime contractors that fail to pay their subcontractors in a timely manner.

Now, doesn’t that make you want to go check out the details of the new law? It should. Remember the sad tale of GTSI Corporation, who has seen roughly three-quarters of its annual revenue put into jeopardy based on allegations of misrepresentation of business size status. You mess with socioeconomic reporting at your risk.

That’s always been the case—but now the law has more teeth in it.

Next step will be to open FAR Cases to implement the new statute in the Code of Federal Regulations. Watch for those proposed rules.

Here is a link to the Department of Energy's recap of the new law:  http://management.energy.gov/documents/AttachmentFlash2011-6%281%29.pdf

 

 

UPDATE: DCMA Agrees with DCAA that Some Contractor Health Care Costs are Expressly Unallowable

E-mail Print PDF

Forget health care costs for a minute. Let’s first lay a bit of foundation before we get into the meat of what needs to be discussed….

In Government contract cost accounting, not all costs are created equal. Beyond the distinctions between “allowable” and “unallowable” there are also “expressly unallowable” costs as well as “directly associated unallowable costs.” We want to focus on the distinctions between costs that are merely unallowable and those costs that are “expressly unallowable.”

When submitting the final indirect cost rate proposal (also known as the annual incurred cost submission), FAR 42.703-2 discusses that a certification must accompany the proposal. The certification is formally required by the contract clause 52.242-4 (“Certification of Final Indirect Costs”). By executing the certification, the contractor represents that all costs being claimed are allowable pursuant to the applicable cost principles, and that “This proposal does not include any costs which are expressly unallowable …”

The contract clause 52.242-3 describes what happens if a contractor includes unallowable costs in its final indirect cost rate proposal, despite its certification to the contrary. Such costs are subject to penalties. The clause prescribes—

If the Contracting Officer determines that a cost submitted by the Contractor in its proposal is expressly unallowable under a cost principle in the FAR, or an executive agency supplement to the FAR, that defines the allowability of specific selected costs, the Contractor shall be assessed a penalty equal to—


(1) The amount of the disallowed cost allocated to this contract; plus

(2) Simple interest, to be computed—

(i) On the amount the Contractor was paid (whether as a progress or billing payment) in excess of the amount to which the Contractor was entitled; and

(ii) Using the applicable rate effective for each six-month interval prescribed by the Secretary of the Treasury pursuant to Pub. L. 92-41 (85 Stat. 97).


If the Contracting Officer determines that a cost submitted by the Contractor in its proposal includes a cost previously determined to be unallowable for that Contractor, then the Contractor will be assessed a penalty in an amount equal to two times the amount of the disallowed cost allocated to this contract.

(Readers wanting to dig deeper into the imposition of penalties should also look at the DCMA’s Guidance to Contracting Officers for negotiating final overhead rates. Here is a link to get you started.)

What is meant by “expressly unallowable” has been a source of disagreement between contractors and government representatives. The definitions section of FAR Part 31 states—

‘Expressly unallowable cost’ means a particular item or type of cost which, under the express provisions of an applicable law, regulation, or contract, is specifically named and stated to be unallowable.

The foregoing definition is not particularly conducive to resolving disagreements between government and contractor. In practice, DCAA tends to assert that any unallowable cost is expressly unallowable; whereas contractors tend to believe that very few costs are expressly unallowable. Alcohol, charitable contributions, and amortization of goodwill are among the few areas of agreement. The other cost principles are fertile ground for dispute.

In June 2002, the Armed Services Board of Contract Appeals (ASBCA) discussed the concept of “expressly” unallowable costs in the appeal of General Dynamics (ASBCA No. 49372). Although the decision subsequently was reversed (on other grounds) on appeal, the Court’s opinion stands as the most lucid discussion of the topic. The Court opined—

We do not believe the determination of ‘express unallowability’ can turn solely on whether the contractor made a ‘good faith effort’ to comply with the particular cost principle involved, although subjective good faith is important. We think Congress intended the standard to be an objective one. The FAR and CAS definitions of ‘expressly unallowable’ point to the need to examine the particular principle involved in light of the surrounding circumstances. Moreover, since Congress adopted the ‘expressly unallowable’ standard to make it clear that a penalty should not be assessed where there were reasonable differences of opinion about the allowability of costs, we think the Government must show that it was unreasonable under all the circumstances for a person in the contractor’s position to conclude that the costs were allowable. The scope of the inquiry will vary with the clarity and complexity of the particular cost principle and the circumstances involved. Under 10 U.S.C. § 2324(e)(1)(F), for example, the ‘costs of alcoholic beverages’ are unallowable and may leave little room for debate, short of a discussion of alcohol levels. On the other hand, the analysis required under 10 U.S.C. § 2324(k) is far more complicated and the answer not necessarily obvious, particularly when a settlement agreement must be consulted. See also 10 U.S.C. § 2324(e)(1)(N), now (e)(1)(O). [Emphasis added.]

Accordingly, our position is that the “expressly unallowable” standard is a high bar and difficult for the government to impose.

The foregoing is necessary prelude for the subject of this article.

On September 24, 2010, DCMA issued this guidance to the DOD “Contracts Community”. The guidance was short and simple. It said—

  • DCAA found that some defense contractors are inappropriately charging the Government for health benefit costs for dependents that are no longer eligible for benefits under the contractors' plans.  Based on their findings, DCAA issued audit guidance on ineligible dependent health benefit costs in MRD 09-PSP-016(R). That guidance states that the costs are expressly unallowable, and therefore subject to penalties if included in a contractor's final indirect cost rate proposal.

  • We have reviewed DCAA's audit guidance and agree that the costs are expressly unallowable and subject to penalties if included in a contractor's final indirect cost rate proposal. 

  • If the ACO determines that the costs are unallowable, the ACO shall treat the costs as expressly unallowable costs.

  • As a result, we are revising the Final Overhead Instruction to ensure ACOs properly assess penalties on these costs.

We told you about DCAA’s focus on “ineligible” dependent health care costs last year, in this article. We called the audit guidance “troubling” and made some suggestions regarding what contractors might do to prepare for DCAA’s audit approach. Subsequently, we’ve learned more about this topic (mostly from contractors who have been audited) and we think it’s a tempest in a teapot. Quite simply, the amount of costs at issue just isn’t that big.

But we think the government is going to have trouble meeting the standard established by the ASBCA regarding the test for “expressly unallowable” costs—particularly with respect to the “grace periods” offered to employees who need to report changes in the eligibility of dependents.

That said, we’re also concerned by DCMA’s guidance, which continues a troubling trend of reducing the discretion of Contracting Officers in favor of centralized direction. The current DCMA guidance (link above) requires that an Administrative Contracting Officer (ACO) must generate “an affirmative statement that the ACO agreed or disagreed with each finding and recommendation made by DCAA or DCMA specialists … and whether or not the assessment of any penalties and interest is appropriate.”  We have difficulty seeing why the ACO needs to follow that direction, when there is no discretion to disagree.



 

Catch-Up Time: Bribery, False Statements, and DCAA Justice

E-mail Print PDF

 

 

We’re back from the Apogee Consulting, Inc. annual fall maintenance shut-down, and ready to catch-up on some news. Here we go—

 

1. We previously reported the sordid little tale of two former Staff Sergeants in the U.S. Army, stationed at a Forward Operating Base in Afghanistan, who accepted bribes and falsified documents in order to facilitate theft of fuel by a government contractor. Our prior story reported that (former) Staff Sergeant Michael Dugger (age 27) had pleaded guilty to one count of receiving a bribe as a public official, but that his alleged co-conspirator, (former) Staff Sergeant Stevan Ringo (age 26), had turned-in a plea of not guilty. Well that’s changed.

On September 24, 2010, the Department of Justice announced that Ringo had decided to plead guilty to one count of bribery. Ringo, like Dugger, now faces up to 15 years in prison plus monetary fines. As the DOJ reported—

Ringo was stationed at Forward Operating Base (FOB) Shank, a U.S. Army installation in the Logar Province of Eastern Afghanistan. FOB Shank supports U.S. military operations in Afghanistan in various ways, including through fuel receipt and redistribution. More specifically, the Army stores large quantities of fuel at FOB Shank and redistributes that fuel to installations in the surrounding area through government contractors. Ringo’s responsibilities at FOB Shank included supervision of that fuel redistribution process.

In his guilty plea, Ringo admitted that between December 2009 and February 2010, he accepted more than $400,000 in cash payments from a government contractor in exchange for creating and submitting fraudulent paperwork permitting that contractor to steal fuel from FOB Shank. The total value of the fuel stolen in the course of the scheme was nearly $1.5 million.

2. We have reported (several times) on compliance implications associated with falsely certifying business socioeconomic status. For example, in this article we reported on a firm that settled allegations it improperly reported the extent to which minority and disadvantaged business enterprises were performing work on its public construction contract, and in another article we reported the story of an Alaska Native Corporation (ANC) that was alleged not to qualify for status as an SBA 8(a) business. Here’s a story about affiliated companies that falsely claimed to be HUBZone business entities.

According to this DOJ announcement—

CSI Engineering and CSI Design Build, located in Beltsville, Md., and their president, Debdas Ghosal, have agreed to pay the United States $200,000 to settle claims that they used false statements to obtain contracts from several government agencies. … The United States alleged that CSI Design Build falsely represented to the SBA and other government agencies that it maintained its principal office in a designated HUBZone location in Maryland. According to the government, CSI Design Build actually operated as part of CSI Engineering, which was not located in a HUBZone. Both companies are owned by Debdas Ghosal. Despite not qualifying for the HUBZone program, CSI Design Build was awarded contracts that had been set aside for qualified HUBZone companies based upon the false statements it made to the SBA and the contracting agencies. The company obtained HUBZone contracts from the Army, the Department of Labor, the Department of Homeland Security and the Smithsonian Institution.

As the DOJ release notes—

Under the HUBZone program, companies that maintain their principal office in a designated area and employ 35 percent of their workforce from that area, among other requirements, can apply to the Small Business Administration (SBA) for certification as a HUBZone small business company. HUBZone companies can then use this certification when bidding on government contracts. In certain cases, government agencies will restrict competition for a contract to HUBZone-certified companies.

It was not made clear how the $200,000 settlement was reached. So we are left to wonder whether it was based on the number of false statements made, the number of false claims submitted under contracts tainted by the false statements, or whether it had something to do with profits made under the fraudulently obtained contracts. It would be helpful to us—and we believe to our readers as well—if the DOJ would clarify whether the settlement made such improper business practices unprofitable, or not.

3. If you’ve seen our presentation on the “DOD Oversight Wars” you know that one of the great unanswered questions of 2009 was why then DCAA Director April Stephenson never fired any of the audit agency executives who were accused of such infractions as allowing audit scope to be influenced by buying commands (and/or contractors), changing audit findings, and whistle-blower retaliation. Clearly, taking action would have appeased the agency’s critics and might have helped her keep her job. We’ve seen speculation that her hands were tied by agency counsel, who forbade her from taking any action while investigations were open against the individuals (who after all were entitled to the protections of their civil service positions). But we’ve never seen anything definitive, and it has remained one of the mysteries of the situation.

So we were very interested in this recent report by Robert Brodsky at GovExec.com, in which he noted a one-line September 27, 2010 memo to DCAA employees, stating that, “in light of the investigations at DCAA,” Ms. Susan Barajas was “no longer an active DCAA employee.” According to the article, Ms. Barajas was the Deputy Director of the Western Region, and was implicated in some of the shenanigans cited by the GAO in the two audit quality reports it issued, which were subsequently confirmed by the DOD Inspector General. As the article noted—

It is not clear whether the investigations Fitzgerald referred to in his memo on Barajas' departure are related to the 2008 GAO report, but if they are, the deputy regional director would be the first DCAA career employee to face substantive disciplinary action as a result of the findings.

As is the case with almost all GovExec.com articles about the troubled Defense audit agency, the comments were brutal. That said, a couple of them caught our eye. Here they are, unedited and unverified:

“The agency wide memo from Director Fitzgerald sounds great but why is that many within DCAA are saying that Barajas was allowed to retire at age 55 with her full pension. DCAA allowed her to remain on the payroll for two years after all these findings came to light and then retire with her full pension and no penalty for leaving early. Why were these facts not reported? This woman went after little people and showed no mercy, yet she was allowed to hang around for over two years and then collect her six figure pension. Just goes to show you how there are different rules for different people within DCAA. But hey at least we got rid of one bad egg. Why not ask the Western Regional Director who was her boss to leave or do we have to wait ten years until he is 55? We have many more who need to call it a career.”

“In an old school, good-old-boy Agency, 2 women are made the scapegoats and forced out.”

“It seems to me her departure is being percieved as a sort of chemo-therapy. We're not sure which was worse, the cure or the disease. The director is limited in what he can do, not so much the political appointees; the Secretary of Defense could have taken an interest in correcting this agency a long time ago. He still has a chance to clear out the Executive Steering Committee and give the director a chance to make positive changes.

At some point the agency is going to have evolve into a federal agency, follow the law, provide a service to tax payers, and a good start could be adhering to a code of ethics - real philisophical ethics, not the auditor ethics that are being ignored anyway. It doesn't take much time to see the left hand has no concept of the right hand. Contridiction exists in practically everything we do - and we look like a joke.”

We have much more to write about—but we’ll save additional topics for another day.





 

GTSI Suspended for Problems with Small Business Set-Asides

E-mail Print PDF

Small Business Administration

On October 4, 2010, FederalTimes.com carried a small story, which reported that GTSI Corporation had been suspended by the General Services Administration (GSA) from receiving future awards from the Federal government. GTSI is a mid-size reseller of computer software and other IT-related applications (including systems integration services), based in Northern Virginia (near Dulles Airport). Reportedly, the GSA alleged that—

… the evidence shows that GTSI was an active participant in a scheme that resulted in contracts set-aside for small businesses being awarded to ineligible contractors and with contracts not being performed in accordance with applicable law, regulations and contract terms …

A copy of the suspension letter was posted on-line by GovExec.com—you can find it here. The letter alleges that GTSI, who did not qualify as a small business, was a subcontractor on a Department of Homeland Security (DHS) contract that was set-aside for small business bids. The letter alleges that—

There is evidence that GTSI’s prime contractors had little to no involvement in the performance of the contracts, in direct contravention of applicable laws and regulations regarding the award of small business contracts. The evidence shows that GTSI was an active participant in a scheme that resulted in contracts set-aside for small businesses being awarded to ineligible contractors, and with contracts not being performed in accordance with applicable law, regulations, and contact terms.

In order to allow the prime contractors to appear eligible … GTSI actively engaged in conduct concealing the extent of its involvement as a subcontractor …. [including such actions as] GTSI created invoices and placed the letterhead of the prime contractor on the invoice … so the invoice would appear to have been created by the prime contractor rather than by GTSI.

This is a big deal for GTSI. As the FederalTimes article notes, “Last year, some 72 percent of GTSI's $762 million in sales came from the Defense Department and other federal agencies, according to its most recent annual report.” It is such a big deal, that it reportedly cratered an upcoming acquisition of GTSI by Eyak Technologies, LLC—who is an Alaska Native Corporation (ANC). The FederalTimes article reports that, “Eyak … said in a statement … that it was withdrawing its $7.50 per share cash proposal ‘in order to carefully evaluate the effect of the SBA's action upon GTSI.’”

GTSI’s future, then, is threatened on two fronts—the termination of an upcoming acquisition, and potential loss of nearly three-quarters of its annual revenue. For its part, the company asserted that it did nothing wrong. As reported by the FederalTimes article—

‘Until tonight, no government agency had made an allegation that GTSI had violated any law or regulations regarding this matter,’ [GTSI CEO Scott] Friedlander wrote. ‘Please be assured that we will fight to restore our good name.’

A couple of days later, Robert Brodsky reported further details on GTSI’s problems at GovExec.com. He reported—

The allegations against GTSI stem from a contract awarded two years ago. In September 2008, a joint venture company known as MultiMaxArray was awarded a $165 million delivery order on Homeland Security's FirstSource information technology contract. FirstSource was a 100 percent small business set-aside contract reserved for companies with fewer than 150 employees.

Days after the award, Wildflower International Ltd., an IT firm that promotes itself as New Mexico's largest woman-owned small business, filed a protest … arguing MultiMaxArray was not eligible for the contract. …

Among Wildflower's arguments was MultiMaxArray was little more than a front company and most, if not all, the work was to be performed by GTSI, a company that, based on its size, was ineligible for the FirstSource contract. …

The protest filing said GTSI had ‘taken control’ of MultiMaxArray, which at the time of the delivery order, had ceased to exist due to a merger months earlier with Harris Technical Services Corp., Wildflower said.

‘GTSI apparently designs the systems necessary to satisfy a FirstSource delivery order, selects the computer hardware and software configurations, negotiates pricing with the vendors, prepares the MultiMaxArray proposal and then performs all of the necessary services to install, maintain and provide technical support and training for the DHS user,’ the protest document said. The protest further claimed that during the kick-off meeting for the contract, several GTSI employees represented the prime contractor to discuss performance of the delivery order. Ultimately, MultiMaxArray decided not to fight the protest and the contract was terminated.

Tellingly, Brodsky noted that, “This is not the first time GTSI has been in trouble with the government. In June 2005, the SBA inspector general recommended the government permanently debar GTSI for misrepresenting itself as a small business on a Navy IT hardware contract.” However (as Brodsky noted), “after reviewing the recommendation, the SBA's Office of General Counsel decided it did not have the authority to debar GTSI since it was not an SBA contract in question.”

Finally, Brodsky noted that this is not an isolated incident. He reported that, “The SBA IG also is investigating GTSI's actions in regard to its conduct as a subcontractor on other set-aside contracts, including those awarded to ANCs.”



 

DCAA Stomps on Ray of Hope Offered by DFARS Class Deviation

E-mail Print PDF

We recently wrote about a “ray of hope” offered by the August 17, 2010 DFARS Class Deviation issued by the Honorable Shay Assad, Director, Defense Procurement and Acquisition Policy. The Class Deviation deleted the words “for contractors with approved billing systems” from DFARS language discussing DCAA’s authority to “authorize direct submission of interim vouchers for provisional payment to the [DOD] disbursing office.” In other words, whether or not DCAA authorized a contractor to directly submit its invoices to DFAS was no longer tied to the adequacy of the contractor’s billing system.

We thought this was great news, especially given DCAA official position on the matter (as expressed in the DCAA Contract Audit Manual), which was: “It is Agency policy to obtain the maximum contractor participation in the direct submission (direct billing) of interim vouchers program.” Great news, we thought, because now DCAA could follow its policy and restore the direct billing authority for all the contractors where that authority had been withdrawn based on inadequate or unaudited business systems (which, by the way, were not necessarily the contractors’ billing systems).

We thought it was also great news for the audit agency, because it could redeploy its scarce audit resources away from this non-valued-added activity toward areas with more risk and vulnerability for waste, fraud, and abuse. Given that the contractors were only submitting “interim vouchers for provisional payment,” the risk of overpayment was minimal. After all, those vouchers and contract costs were going to be reviewed again during the audits of the contractors’ incurred costs. Redundant audits made no sense, especially when DCAA was so under-resourced it could only audit 65% of the audits it was required to perform (by its own admission).

This was great news. Hallelujah! Or so we thought.

But we were wrong.

DCAA issued Memorandum for Regional Directors MRD 10-PPD-022(R) on August 26, 2010, in order to clarify that DCAA’s policy of denying contractors direct billing authority based on inadequate or unaudited business systems was unaffected by the Class Deviation. The MRD stated—

This deviation does not impact current DCAA policy for authorizing contractors direct billing authority (CAM 6-1007). Auditors should continue to use existing policy for authorizing contractors direct billing authority and the additional guidance provided in MRD 09-PPD-006(R), dated April 15, 2009.

Now it seemed to us that the intent of the Class Deviation was exactly aimed at impacting the current DCAA policy. But DCAA not only disagreed with our interpretation of the intent of the Class Deviation, it also asserted that the Class Deviation was issued at its request! The MRD reported—

The deviation was issued to address a DoDIG interpretation of the subject DFARS language. The DoDIG has interpreted that the DFARS language requires that a comprehensive evaluation of the billing system internal controls is required for all contractors to participate in the direct billing program. We determined that conducting such reviews at smaller contractors would not be a prudent use of audit resources or taxpayer dollars. DCAA currently performs other audit procedures tailored to the risk to the Government when authorizing nonmajor contractors to direct bill. Therefore, we requested the DFARS class deviation to allow DCAA to use its existing policies and procedures for authorizing the direct submission of interim vouchers for provisional payment to the disbursing office.

So according to DCAA, the Class Deviation applies only to “nonmajor” contractors, such as small businesses. The “major” contractors will continue to suffer delays in cash receipts.

First, we question DCAA’s interpretation. We don’t care what DCAA intended the Class Deviation to do; all we have to go on is what it says. The “plain language” of the Class Deviation removes the linkage between direct billing authority and business system adequacy. Period. The Class Deviation does not contain any express language that would limit its application only to businesses of a certain size or class. While it may be true that the intent was to make the Class Deviation applicable only to small businesses, that’s not what the regulation says—either before or after the deletion of the language.

Granted, DCAA has the authority to authorize or not authorize direct billing authority, and it can do so based on whatever rationale it wants to cook up. But at least its actions should be consistent with its own published policy, or so it seems to us.

Second, we note that, based on the date of the MRD, it should have been published on the DCAA website already. The website says it includes all audit guidance “open as of August 31, 2010”—but you can’t find this particular one listed there. DCAA has told contractors that it publishes all releasable open audit guidance every month, but this particular MRD somehow slipped through the cracks. We have to ask whether DCAA is trying to slip its flawed interpretation under the radar?

This is not the first time that DCAA has delayed, for whatever reason, publishing audit guidance for inspection by the public. Given the Obama Administration’s push for openness and transparency, we would have thought that DCAA would be eager to share all of its audit guidance with the public in a timely fashion. And just like our thoughts about the DFARS Class Deviation, we would have been wrong.

Perhaps we are overreacting to the situation. It wouldn’t be the first time! But here’s how we see it: DCAA is interpreting the current DFARS language (after implementation of the Class Deviation) in a manner that appears to be arbitrary, capricious, and self-serving. It appears to be interpreting the DFARS language in a manner that is inconsistent with its own policy statements and in a manner that actually harms its own self-interest, as it cannot redeploy audit resources to more fruitful areas as it should.

DCAA reports to DOD Comptroller Hale in a separate vertical from that of DCMA. But given that the Class Deviation was issued by the DOD Procurement and Acquisition Policy Directorate, one might think it would carry some weight with the DOD auditors. Can DCAA simply ignore promulgations it disagrees with—or reinterpret them in ways it finds more palatable? Or is this situation something akin to insubordination? We don’t know, but (frankly) nothing DCAA says or does surprises us anymore.

Finally, President Obama has issued an Open Government Directive, and that Directive applies to all Executive Agencies and Departments—including the DOD and its auditors, the DCAA. That Directive states—

Agencies shall respect the presumption of openness by publishing information online (in addition to any other planned or mandated publication methods) and by preserving and maintaining electronic information, consistent with the Federal Records Act and other applicable law and policy. Timely publication of information is an essential component of transparency. Delays should not be viewed as an inevitable and insurmountable consequence of high demand.

Given that DCAA is not publishing its audit guidance timely, one has to ask whether it is meeting the expectations established by the President’s Directive. Or is DCAA treating that Directive with the same strategy it has applied to the DFARS Class Deviation?

But perhaps that’s not all … Dare we say it?

Yeah, let’s go there …

By apparently ignoring the requirements of the Open Government Directive, is DCAA being insubordinate to the lawful orders of the Commander-in-Chief? In a time of war?

Okay, we admit it—we are definitely overreacting to the situation. But we’re concerned, and we’re asking tough (rhetorical) questions. If DCAA wants to email us an official response, we’ll be happy to post it here. And we’ll post it timely, too.

And you too can post your thoughts on this site. Every member can post comments here, and you are welcome to do so. Agree, disagree, or have a story to share? Feel free to leave a comment.



 


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