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

Why You Subcontractors Should NOT Let Your ACO Set Billing Rates for Invoices to Your Prime Contractors

E-mail Print PDF

Cash_is_King
This is going to be an important article. Which means, of course, that few will read it and even fewer will heed it. So be it.

This is going to be a controversial article. Which means, of course, that most will disagree with it and even more will simply ignore it. So be it.

Newsflash: If you are a subcontractor, if you are supporting a prime contract and submitting vouchers/invoices to the prime contractor instead of directly to the U.S. Government, then you should not—indeed, you must not—let your cognizant ACO establish the billing rates you use to prepare those invoices.

The cognizant ACO has authority to establish provisional billing rates and final billing rates only for your prime contract billings, the invoices submitted directly to your US Government customers. Your cognizant ACO lacks authority to establish provisional billing rates and final billing rates for your subcontract invoices to your prime contractors.

To be clear, you can agree to give the ACO that authority. You can execute a subcontract with a prime contractor that links your provisional and final billing rates to what the ACO does for the contractors over which s/he does have authority. You can do that, and many upon many subcontractors do so automatically, as a matter of routine. It’s the common wisdom, the way things are normally done. So of course you can choose to do that.

But you’ll be making a big mistake if you do so.

By way of background, try this article. In it we wrote:

… whenever the contractor knows that its provisional billing rates are varying, to a significant degree, from its currently anticipated final indirect rates for the year, it should request an appropriate adjustment. If the contracting officer declines to adjust the billing rates, then s/he needs to be able to justify why not—since the clause mandates that the provisional billing rates “shall be” the anticipated final rates. Bottom-line: while there may be some discretion with respect to notification, there is no discretion once notification has been made—the billing rates must be adjusted.

[Emphasis in original.]

For a little more nuance, consider reviewing this other article, in which we wrote—

So if the parties are complying with the requirements of the Allowable Cost and Payment Clause, then the difference between provisional and final billing rates should be de minimis.

That’s the theory, anyway. We’re quite certain that practice does not match theory in this area. The primary reason for the deviation between theory and practice is that many Contracting Officers apply decrement factors to contractor’s proposed provisional billing rates in order to ‘protect the Government’s interests.’ As a result of the desire to protect the Government’s interests, contractors are only approved to bill at provisional rates that are lower than the estimated final billing rates. The size of the decrements seems to depend on the individual Contracting Officer; some contractors have rather small decrements and others have rather larger decrements. The immediate impact is to reduce contractors’ cash flows, which is annoying, no doubt. But since the provisional billing rates should be synced up to final billing rates over time, the cash flow impact primarily manifests during the current performance year and, accordingly, is perceived as a temporary phenomenon and not something to get overly worked-up about. …

The fact of the matter is that provisional billing rates should closely approximate final billing rates. Imposition of a large decrement factor on a contractor risks the government being unaware of a contract’s true costs, and receiving a large ‘surprise’ when the final billing rates are negotiated. (We note for the record that too-low provisional billing rates do not relieve a contractor from having to comply with the Limitation of Cost/Limitation of Funds clause requirements.) Moreover, from the contractor’s perspective, having provisional billing rates closely approximate final billing rates means that the settlement of final rates will not have a significant impact on cash flow.

Okay. You should be up to speed now. Provisional billing rates should always closely approximate expected final billing rates, and contractors should request adjustments to provisional billing rates when those rates start to differ significantly from estimated final billing rates. The parties have six years to negotiate final billing rates, and if the parties did the right thing during contract performance (as defined by complying with the requirements of the 52.216-7 Allowable Cost and Payment Clause) then the final invoices, calculated at the negotiated final billing rates, should be relatively small.

Note that all of our previous writings on the topic elided any discussion of what happens to subcontractors that want to adjust their provisional billing rates. The closest we’ve ever come to that discussion point can be found over here, where we wrote about a subcontractor to L-3 Communications that had submitted rate adjustment vouchers, that L-3 refused to pay until DCAA had conducted an audit and had determined the subcontractor’s final billing rates. The subcontractor sued L-3 for a failure to pay its invoices (among other allegations) and won. We reported that suit and its outcome but we failed to draw any conclusions from it.

What we should have said was, based on that case, subcontractors don’t have to wait for a DCAA audit and formal rate negotiation in order to submit adjustment vouchers to their prime contract customers. Granted, that was only one case, and it was at the State level, thus its precedent-setting ability was somewhat in doubt to this non-attorney. But still, we missed that implication.

We rectify that omission today, citing to a recent U.S. Court of Federal Claims case to support our position. We refer to U.S. Enrichment Corporation v U.S.A. Now, before we get into our analysis of the decision, please remember that we are not attorneys and you should not rely on our legal analyses. If you want a legal analysis upon which you can rely, go hire yourself a good government contracts attorney.

All that being said, we look at the July 28, 2014 decision, in which Judge Firestone granted the Government’s Partial Summary Motion to Dismiss, finding that the court lacked jurisdiction to hear the part of the case that involved USEC’s subcontract costs. Judge Firestone's reasoning in granting the Government’s Motion supports our position.

USEC filed a suit at the COFC, alleging that the Department of Energy (DOE) breached its contracts with USEC “when the government failed to reimburse certain indirect costs that USEC incurred as both a prime contractor and subcontractor while performing work at the United States Department of Energy’s … gaseous-diffusion plants (‘GDPs’) in Portsmouth, Ohio and Paducah, Kentucky.” USEC’s suit was based on “DOE’s purported failure to establish provisional and/or final indirect cost rates in a timely manner in connection with those prime and subcontracts, which allegedly resulted in USEC being under-compensated throughout performance.” Roughly 10 percent of USEC’s claimed $38 million in damages were related to its cost-reimbursement subcontracts with other prime contractors performing their own DOE contracts (also called “Captive work”). The Government argued that “the court lacks jurisdiction to entertain a suit brought directly by USEC in its capacity as a subcontractor.”

Those subcontracts, as well as USEC’s prime contracts with DOE, contained the Allowable Cost and Payment Clause (52.216-7). We have extensively discussed the requirements associated with that clause on this site. Indeed, the articles from which we quoted above go into some detail. Judge Firestone summarized many of those requirements in her decision.

With those requirements as context, Judge Firestone found that the dispute started with respect to USEC’s FY 2003 indirect cost rates. The DOE granted one rate adjustment (in May 2004) but refused to grant another, despite USEC’s June, 2004, request that it do so. And there the matter languished, for literally seven years, until 2011, when USEC finally submitted rate adjustment invoices for FY 2003 and DOE rejected them (we assume because they contained unapproved billing rates). DOE refused to let USEC adjust its FY 2004 billing rates. Eventually USEC took the DOE to court.

As noted, Judge Firestone granted the Government’s Motion. She found that—

… USEC entered into separate agreements with prime contractors to provide Captive work, those agreements are controlling. To recover additional indirect costs, USEC must comply with the mechanisms set forth in those agreements and applicable regulations. See 48 C.F.R. § 52.216–7(d)(5) (‘The completion invoice or voucher shall include settled subcontract amounts and rates. The prime contractor is responsible for settling subcontractor amounts and rates included in the completion invoice or voucher and providing status of subcontractor audits to the [C]ontracting [O]fficer upon request.’)

Judge Firestone found that the DOE lacked privity with USEC in its capacity as a subcontractor. Accordingly, she could not hear that part of USEC’s case. If USEC wanted to adjust its indirect cost rates so as to bill more (and collect more), then that matter was between it and its prime contractors. The DOE Contracting Officer was not a party to the matter, nor did s/he have authority to override the billing mechanisms found in USEC’s subcontracts. If there was a dispute, then the two contracting parties would need to work it out. Importantly, Judge Firestone cited to the 52.216-7 language that expressly provided that the prime contractor, and not the U.S. Government, was “responsible for settling subcontractor amounts and rates.” There was a regulatory basis for her position.

Therefore, it seems very clear to us that your billings to your prime contractors are a matter between you and them. The Government is not a party to your disputes nor does it have authority to set either the provisional billing rates or the final billing rates. Subcontractors need to push your prime contractors to the negotiating table and settle your final billing rates (with respect only to the individual subcontract under discussion), and you absolutely do not need to wait for DCAA or for your ACO.

Prime contractors, then can be good news for you. All those old prime contracts you can’t close because you have subcontractors whose rates have not yet been finalized? Go ahead and negotiate your final billing rates and close ‘em out.

Best get to it now.

 

Proposed Revisions to DFARS Business System Oversight Regime

E-mail Print PDF

Governor Robert Ritchie, R-FL : Now, he's going to throw a big word at you – ‘unfunded mandate.’ He's going to say if Washington lets the states do it, it's an unfunded mandate. But what he doesn't like is the federal government losing power. But I call it the ingenuity of the American people.

Moderator : President Bartlet, you have 60 seconds for a question and an answer.

President Josiah ‘Jed’ Bartlet: Well, first of all, let's clear up a couple of things. ‘Unfunded mandate’ is two words, not one big word.

If there is one particular topic we have covered thoroughly on this site, it would have to be the DFARS Business System Administration rules. We railed against it when it was first promulgated as a proposed rule; we railed against it when it became a final DFARS rule. We reported on DCAA and DCMA implementation and interpretation, and we reported on DOD Inspector General criticism of DCAA’s inability to fulfill its oversight responsibilities. You want to see those articles, just type “business system” into the keyword search feature on the front page.

More recently, we warned readers of a rumored sea change in the DCAA Business System oversight role, wherein DCAA would stop auditing contractors’ business systems altogether. We thought that would be a brilliant idea, writing “Consequently, it's likely that contractors are going to be required to spend more of their limited indirect funds to pay for external CPAs to review their business systems, a review that will be mandated by DOD and paid for through increased prices for goods and services.”

Indeed, that is what the proposed DFARS rule revisions would entail.

Published July 15, 2014, the proposed DFARS rule revisions would purport to “ensure appropriate contractor accountability for adequate contractor business systems.” It would accomplish that objective by—

… proposing to amend the DFARS to entrust contractors with the capability to demonstrate compliance with DFARS system criteria for contractors' accounting systems, estimating systems, and material management and accounting systems, based on contractors' self-evaluations and audits by independent Certified Public Accountants (CPAs) of their choosing. Government auditors will perform overviews of the results of contractor self-evaluations and CPA audits.

Let’s be clear. DCAA would no longer audit three of the six DFARS business systems. Those three systems are Estimating, Accounting, and Maternal Management and Accounting (MMAS). Instead, contractor’s would be “entrusted” with their own evaluations, augmented by periodic reviews by independent CPA firms.

Let’s be even clearer:

  • For the three systems noted above, contractors must conduct annual self-assessments and report the results of those self-assessments to the cognizant ACO and to DCAA. The annual self-assessments must be completed within six months of the end of the contractor’s fiscal year and must be signed-off by a contractor executive.

  • In year one, and once every three years thereafter (unless the cognizant ACO directs a more frequent assessment) the contractor will engage an independent CPA firm to perform an external assessment of the three systems in accordance with GAGAS. As part of the external report, the contractor must provide the cognizant ACO and DCAA with the CPA's audit strategy, risk assessment, and audit plan (program), upon completion. The CPA firm must provide its working papers for government inspection.

  • DCAA may review the annual self-certifications or the triennial independent CPA reports, and may provide its findings to the cognizant ACO.

  • The contractor’s failure to submit either the annual self-certification or the triennial independent CPA report will constitute a “significant” deficiency and will lead to payment withholds.

  • The new rule does not apply to small businesses.

The proposed rule has drawn intense scrutiny from many sources. The attorneys at Wiley Rein opined—

For contractors, the ability to potentially accelerate approval of their business systems may be attractive. Nonetheless, the proposed rule imposes significant new mandatory requirements on covered contractors to report their annual business system assessments, engage independent CPAs to provide audit plans and perform audits, and produce documentation regarding audits and assessments. Since these contractor and CPA reports are subject to DCAA review, it remains to be seen how long DCAA takes to review the reports and whether DCAA will accept CPA audits or review them so critically that the anticipated efficiencies are lost.

Attorneys at McKenna Long & Aldridge wrote—

The purposes of the proposed rule appear to be to relieve DCAA of business system audit responsibilities it has been unable to meet, and to require that contractors disclose to the government internal documentation supporting contractor’s business systems that the government is often unable to obtain in connection with system reviews. It remains to be seen whether DOD will seek to impose the same or similar reporting requirements in connection with the purchasing, earned value management, and property management systems that DCMA currently reviews.

What do we think?

Well, we think that if contractors’ business systems truly are the “first line of defense against fraud, waste, and abuse,” as every civil servant seems to think and has so testified, then it is a damning indictment that DCAA lacks sufficient resources to perform timely audits on those business systems. The phrase “inherently governmental function” springs to mind. And now that government oversight, for which the taxpayers have paid and paid and paid, is going to be outsourced. Will DCAA downsize as a result of its suddenly reduced workload? Doubtful. So there will be no reduction in government oversight costs, while the contractors will be required to pay for the oversight that was previously performed by DCAA.

Tell us that won’t raise contractors’ costs and prices. Tell us the taxpayers won’t pay more. Go on. We’re waiting.

But more fundamentally, we believe this rule is anti-small business. We believe this rule will harm small businesses. “How is that,” you may say, since the proposed rule clearly exempts small businesses. Well, here’s how: If DCAA is not going to perform business system reviews and large businesses will perform their own reviews, then what are small businesses going to do? That’s right: nothing. So they will not have approved business systems and will be at a competitive disadvantage. They won’t be able to win that big contract that moves them from small to large business.

At a time when more and more RFPs required approved business systems, small businesses won’t have them. FAR 16.603 requires that a contractor must have an adequate accounting system in order to be awarded a cost-type contract. How are small businesses going to obtain a determination that their system is adequate when DCAA won’t be performing audits anymore? Are small businesses supposed to have the same financial resources as large businesses? We don’t think so. As a result, we very much suspect small businesses will be unable to win awards of cost-type contracts—including SBIR Phase 2 contracts.

Where are the independent CPA firms going to come from? You know, the ones with GAGAS compliance training and government contract expertise. Sure, they exist. But contractors will not be able to use their external auditor for such work and the other firms will be vying for the remediation work (where the money is), so who will be left to perform the assessment work?

Which firm will agree to the potential liability associated with a system approval that the DCAA subsequently finds to be deficient? Which firm will agree to turn over its working papers for DCAA review? Again, they exist. But there will not be very many of them and they will charge contractors dearly for the work. And the contractors will pass those charges back to DOD via indirect rate increases.

Clearly, something needs to be done. But this proposal either goes too far or doesn’t go far enough. DOD needs to remove DCAA completely from the picture and simply rely on the work of the independent CPAs. Failing that, DOD needs to completely revamp DCAA so the audit agency can actually perform quality audits that are useful to COs, and issue them timely.

Or perhaps it’s time to rethink this unworkable and quite frankly punitive business systems oversight regime. You know, go back to the drawing board and start fresh. We would advocate that approach.

If you feel the same way we do about this proposed rule, you may wish to submit written comments to the DAR Council for consideration. Not that we expect the DAR Council to actually listen to the public input (they didn’t listen the last time, when many (including Apogee Consulting, Inc.) told them their original plan was not going to work, because DCAA lacked sufficient resources to execute its role. But still. We have to keep trying to help the bureaucrats even if our efforts will prove futile.

You can submit comments on DFARS Case 2012-D042 before September 15, 2014 as follows:

Regulations.gov: http://www.regulations.gov. Submit comments via the Federal eRulemaking portal by inserting “DFARS Case 2012-D042” under the heading “Enter keyword or ID” and selecting “Search.” Select the link “Submit a Comment” that corresponds with “DFARS Case 2012-D042.” Follow the instructions provided at the “Submit a Comment” screen. Please include your name, company name (if any), and “DFARS Case 2012-D042” on your attached document. Follow the instructions for submitting comments.Show citation box

Email: This e-mail address is being protected from spambots. You need JavaScript enabled to view it . Include DFARS Case 2012-D042 in the subject line of the message.

Fax: 571-372-6094.

Mail: Defense Acquisition Regulations System, Attn: Mr. Mark Gomersall, OUSD(AT&L)DPAP(DARS), Room 3B941, 3060 Defense Pentagon, Washington, DC 20301-3060.

 

Goodbye GAGAS?

E-mail Print PDF

ChangeWe used to write letters to the Director, DCAA every year and publish them on this website. We wrote two before we were advised to cease the practice. Why? Well, because (1) the Director, DCAA, was not going to read our words, and (2) the Director, DCAA, was not going to direct DCAA based on the words of some blogger who never even worked for DCAA. We were told it was an exercise in futility.

Plus, you know, it struck certain people as being more than slightly arrogant. Who were we at Apogee Consulting, Inc., to tell a member of the Senior Executive Service, whose appointment was vetted (if not pushed) by powerful members of Congress and approved at the highest levels of the Defense Department?

So we stopped writing annual open letters to the Director, DCAA after the second one.

Truly, we were trying to be helpful. Our belief was that the Director, DCAA, wasn't getting the full and correct story from the auditors in the trenches; the ones actually doing the work and interacting with contractors. Our belief was that if the Director, DCAA, actually knew the effect audit guidance was having on the defense acquisition system, that audit guidance would be revised.

Okay, we were naïve. Sure, we get that. But please believe our intentions were pure and free of the normal levels of sarcasm and snark one encounters in our blog.

The two open letters are still on the blog. You can find 'em, if you are so inclined.

We were reminded of our naïve and perhaps patronizing advice to the Director, DCAA, when we noticed how many DCAA activities are being designed to avoid compliance with GAGAS. We think that's kind of a good thing … almost like the Director, DCAA, finally got around to reading our advice and nodded, and then made it happen.

What advice , you may ask?

In our first letter, written in December, 2009, we suggested the following to the Director, DCAA:

… consider whether all DCAA audits need to be subject to GAGAS. Reasonable people will disagree with GAO's stringent definition of 'independence' under GAGAS, but you can avoid the issue altogether if you make certain audits subject to GAGAS while others are not. There is precedent for this change: the AICPA has Consulting Standards that differ from Auditing Standards. Since DCAA performs both financial advisory services and audits, it would seem to make sense to apportion each type of audit into GAGAS-compliant and non-GAGAS-compliant groupings. And, by the way, DCMA really wants DCAA to participate in the process as an advisor; it wants your audits to offer value-added advice and to support the acquisition process. Contractors want to hear from auditors as well; they want to know where they need to improve and what should be done to fix system deficiencies. Your auditors can't do this if GAO will allege they've compromised 'independence' whenever this happens-so change the rules of the game to eliminate the issue altogether.

In our second letter, we expressed disappointment that the audit agency hadn't moved forward on our suggestion. But in the roughly 30 months since that second letter was published, we've come to see that, indeed, DCAA has decided to split out GAGAS-compliant audits from procedures that do not have to comply with GAGAS. Sometimes DCAA explicitly notes in its audit program that the procedures do not have to comply with GAGAS, and other times we have to infer it from the fact that the output of the procedures is not an audit report but is, instead, a Memorandum.

Look, we are not going to claim any special credit for this sea-change in approach to performing audits. But nonetheless, we smile a secret little smile when we see it happening. It's a good step forward and we are happy to see the change in approach.

The fact that it will reduce the audit agency's exposure to allegations of GAGAS non-compliances is simply a byproduct of the strategic management decision, we are quite sure.

 

How to Ace a Walkthrough

E-mail Print PDF

Keep_Calm_and_Ace_the_Test
When you are audited by the Defense Contract Audit Agency, you will likely have to do a walkthrough as part of your support efforts. A walkthrough is a step in the audit process in which the auditor gains an understanding of what s/he is auditing (though paradoxically walkthroughs can take place prior to the official start of the audit).

In our view, a walkthrough is a piece of performance art in which the contractor explains what was submitted to the government and why it is adequate and/or compliant. The value of the walkthrough varies depending on what is being audited. Regardless of the value to either auditor or auditee, walkthroughs are fast becoming a mandatory audit process step; so you may as well get really good at doing them.

Let us help you with that.

A DCAA walkthrough should not be confused with a Sarbanes-Oxley Section 404 walkthrough, which is intended to accomplish AS5 objectives in a cost-effective manner. (Those AS5 objectives include, for example, gaining an understanding of the process flow and related controls.) No. The DCAA walkthrough is a rather unique audit step, and inserted into many audit programs only in the past year or so. The irony is that DCAA stole the original notion from the US Air Force.

In the mid to late 2000's, the US Air Force was criticized by the Government Accountability Office (GAO) for failing to negotiate a final price for Undefinitized Contract Actions (UCAs) within 180 days, as required by statute, In response to the GAO's criticism, in early 2010 the USAF implemented changes to the UCA definitization process. Those changes were intended to speed things up. As we reported, the USAF believed one root cause of the delays was that its personnel simply did not understand what they were looking at (and subsequently negotiating). Accordingly, the USAF acquisition brass directed that "for all sole source contract actions greater than $50 million and any UCA greater than $1 million, contracting officers shall schedule a proposal kick-off meeting." The kick-off meeting was to include all stakeholders, to include the Air Force and contactor, DCAA auditors, DCMA functional specialists and, "at the prime contractor's discretion," major subcontractors.

The kick-off meeting wasn't the sole fix to the perceived problem. The USAF direction also stated: "… after proposal submittal and preliminary review … the contracting officer shall require the contractor to provide a proposal walk-through for the Government to ensure an understanding of the proposal composition, validate or revisit the definitization/award schedule, and establish action items for any obvious data omissions." Thus was created a formal process that included proposal kick-off discussions (to ensure that the stakeholders were aligned on exactly what the contractor team would be proposing), government proposal review upon receipt, and a subsequent walkthrough to ensure that what was being proposed was what had been agreed-upon and to answer any questions the government customers may have had-all with a goal of eliminating wasteful iterations and streamlining the negotiation process, so that UCAs could be definitized more quickly.

A couple of months later, DCAA issued MRD 10-PSP-016, which directed auditors to attend the proposal kick-off meeting and walk-through, so as "to obtain an understanding of the contractor's proposal, including supporting data. The contractor should also identify the contractor personnel responsible for the underlying data and estimates. DCAA will require access to these individuals during the audit process. … During these meetings, the auditor should identify any apparent proposal inadequacies. If data omissions are so significant as to render the proposal inadequate for analysis, the auditor should recommend that the Contracting Officer reject the proposal."

Apparently that worked out so well for DCAA that having a walkthrough became SOP for every proposal it audited. (Note that at roughly the same time, DCAA was reducing the number of contractor priced proposals it would agree to audit.) To aid its auditors in evaluating proposal adequacy, DCAA created a Proposal Adequacy Checklist. We note for the record that the DCAA Checklist seemed to go a bit overboard with respect to helping auditors identify "significant" data omissions that would "render the proposal inadequate for analysis." We published some choice words about it when originally issued. Regardless of our feelings on the matter, the DAR Council thought DCAA was onto something good, and so it took the Proposal Adequacy Checklist and made it a regulatory requirement. And as we subsequently wrote, Checklists of various sorts and types have become the new norm for DCAA these days. (Which is fine if the auditors have sufficient training, experience, and professional judgment to tailor those Checklists to fit the contractor's circumstances. Unfortunately, experience has shown they lack the capability to do so. But perhaps we digress.)

DCAA has taken the original proposal walkthrough and subsequently enshrined it into a number of audit programs. At this point, pretty much anytime the auditors need to "gain an understanding" of what they are auditing (which is pretty much all the time as far as we can tell), the contractor is supposed to create a dog and pony show, call it a "walkthrough," and then perform like trained monkeys for the benefit of its auditors-who will judge whether or not the performance was acceptable.

Consider for a moment the auditor as a critic. We think that metaphor works on a number of levels.

But you want to know about walkthroughs and when to expect them. You should expect to put on a lot of them. Many audit programs now call for walkthroughs to be performed. For example, in the 10100 audit of a contractor's annual proposal to finalize billing rates (aka "Incurred Cost Proposal") Step 14 states, "Coordinate with contractor and obtain a walk-through of the incurred cost proposal to gain an understanding of the basis of the proposal, the related supporting documentation, and the relevant policies/procedures and processes related to significant cost elements." Step 15 of that same audit program directs the auditor(s) to—

Obtain and document an understanding the contractor's incurred cost proposal and its processes for developing the proposal using the framework on WP B-2. Obtain and document an understanding of the underlying processes related to those specific incurred cost areas (e.g., the basis of the costs and from where the numbers/amounts are derived). A major portion of this understanding may be obtained during a walk-through of the contractor's proposal.

(Editorial Note: Normally we would expect the contractor's year-end Trial Balance and General Ledger to be the basis for costs claimed in its proposal, but we suppose it's nice for the auditors to hear that assumption confirmed, year after year after year.)

Importantly, the 10100 walkthrough is supposed to take place prior to the official entrance conference, because it is supposed to aid the auditor(s) in determining whether or not the contractor's proposal is adequate for audit. (Of course, there is an official Checklist to help the auditor(s) make that determination.) In our experience, this can cause confusion because the effort involved in supporting the walkthrough may, in many instances, be similar to (or even more intense than) the effort involved in supporting the audit and responding to auditor RFIs.

There is a similar requirement with respect to audits of contractor proposals to establish Forward Pricing Rates (FPRPs). Okay. It makes some sense that a proposal to establish final billing rates and a proposal to establish Forward Pricing Rates would be treated in a fashion similar to other priced proposals submitted for government review and negotiation. If you have a walkthrough requirement for one subset of proposals, why not require it for the entire universe? We get that, at least to some extent. But walkthroughs are cropping-up in other audits, which we find somewhat surprising. It appears that DCAA is expecting walkthroughs whenever its auditors are testing a contractor's "assertion."

In the MAAR 13 (Purchase Existence and Consumption) audit, Step 4 tells auditors to use a walkthrough to gain an understanding of the contractor's internal controls. There is a similar audit step in the MAAR 6 Floorcheck audit program. In the 19100 audit program to determine the compliance of cost accounting practices disclosed in a contractor's initial CASB Disclosure Statement, there is also a step that implies the contractor will conduct a walkthrough of its Disclosure Statement. There is a similar step in the audit program for evaluating CAS compliance of a revision to its Disclosure Statement. (As we recently wrote, we have a hard time understanding exactly what the contractor will be demonstrating in its Disclosure Statement walkthroughs. The document would very much seem to speak for itself. But perhaps we digress once again.)

The point being: contractors will be performing more and more of these performances called "walkthroughs," so we think we ought to share our experience and suggest some practices that have seemed to work out well for us and our clients.

The most important thing we have to share is that these walkthroughs are, indeed, performances. We like that analogy a lot. Like all good performances, they require a cast of performers and a script. And rehearsals. You need as many rehearsals as necessary to get the performance ready for the audience.

Every performance needs a director (or conductor if the orchestral performance analogy works better for you.) Somebody needs to be responsible and accountable and in charge for assigning roles and making sure the actors know their lines, and that they can deliver those lines crisply and professionally. That director/conductor is the person who points to the actors so that they know their cues (i.e., when to speak and when to listen).

Who is your director going to be? Will it be the DCAA audit liaison? Or perhaps the process owner? Or maybe the Executive in charge of whatever is being audited? Doesn't matter, but you need one leader and no more. Too many chefs in the kitchen leads to confusion. And all the other players need to accept the direction they receive. Some of those players will be stars and others will be minor "spear-carriers," but everybody needs to know their lines and their cues, and then keep their eyes on the director in case things go south during the performance.

Where does the script come from? In those cases where the DCAA (or DFARS) has helpfully mandated use of a Checklist, we think that's a great place to start. You will want to hit all key points in the Checklist, so as to assist the auditors in checking-off the points for which they have gained an understanding. If there is no applicable Checklist, download the audit program and tie the walkthrough script to the audit objectives and key audit steps. If all else fails, consider asking the auditors what they are looking for. Truth is, most of the time they will have no idea what they expect to see; but in other cases they may well have specific questions and/or objectives in mind, and they should be willing to communicate those to you.

PowerPoint skills will be very helpful in preparing an artistically accomplished performance. They say pictures are worth a thousand words; and while that's not necessarily true, it is true that a process flow diagram is worth quite a bit in a walkthrough.

You are going to want to have a sign in sheet and your auditors will want a copy of that. It memorializes who was there and will be useful if, at the audit end, the draft report exhibits errors that stem from a lack of listening (or comprehension) at the time of the walkthrough. In other words, you will want to memorialize not only what was said, but also who heard it.

One of the "better practices" is to actually videotape the walkthrough so that, in the unfortunate event of litigation, you have documentary evidence of who said what to whom. We have had attorneys veto that idea, under the notion that such evidence could also document any (inadvertent) misstatements of fact that the contractor made. We vehemently disagree with that overly conservative viewpoint and urge readers to tell those overly cautious attorneys to stuff it. Which is more likely-that your personnel will make a misstatement of fact after two or three dry runs to shake out the bugs and that nobody will correct that misstatement during the walkthrough, or that DCAA will subsequently claim that you never said what you clearly told the auditors during the walkthrough? We know where we stand on that question.

If you treat the walkthrough like a performance in front of a live audience, if you have a script and have assigned the roles, if your personnel know their roles and know to take their cues from the director, if you have assigned the right director, if you have put in the necessary time and effort to get this right … then you'll do fine. You will ace the walkthrough.

But there is one aspect that has recently come up in walkthroughs that's got a number of folks concerned. It stems from DCAA having to consider FRAUD during their procedures, and not knowing how to do it. The venerable DOD IG Handbook of Fraud Indicators recently was withdrawn, and DCAA has had to adjust its approach. Auditors are being encouraged to "brainstorm" where fraud might be found and to address that possibility in audit procedures. Consequently, it is becoming a recurring requirement to have management made an assertion regarding its (lack of) knowledge of any fraud during the walkthroughs. Moreover, management needs to discuss what anti-fraud and anti-corruption processes it has deployed in the area being audited. This is one area that legitimately terrifies the attorneys, because there may be instances of fraud that are known to some but not to others. For example, there may be a qui tam FCA suit that has just been unsealed or for which a criminal investigation is ongoing. Or an employee may have been terminated for corruption and a contractor disclosure is being prepared at the time of the walkthrough. Point being: the assertion regarding fraud needs to be factually accurate but it is difficult to ensure that the person making the assertion has all the facts. Our advice is to get your legal folks to draft that part of the walkthrough. Make them part of the performance. Give them a starring role! They will feel as if they are truly adding value to the business. It will be a win/win.

Walkthroughs can work for you in the sense that they give you an opportunity to teach the auditors about what they will be auditing. You can get in front of vulnerable areas and can create opportunities to connect with the auditors. These are all good things. The pros, unfortunately, are partially offset by the cons. It takes a lot of work by a number of people, all working together in a cross-functional team, to ace a walkthrough.

But it can be done. And if it leads to a positive audit outcome, then it is clearly worth the effort of doing it right.

 

Changes to DCAA Disclosure Statement Adequacy Reviews

E-mail Print PDF

A recently published Memorandum for Regional Directors (MRD) announces what most of us have known for some time: DCAA is exiting the business of reviewing contractors' CASB Disclosure Statements for adequacy. Instead, that responsibility is moving over to DCMA, because Administrative Contracting Officers over there have so much free time on their hands.

As we all know, DCAA lacks sufficient resources to perform its audit workload; never mind the fact that the FAR Council keeps adding to that workload (even though public comments from folks such as Apogee Consulting, Inc. try to apprise them of that fact). So of course it makes perfect sense for the audit agency to descope its workload wherever possible, in order to focus on more important audits that generate questioned costs that can be reported to Congress each year.

In fairness and in the name of accuracy, we have to report that DCAA will still be evaluating the adequacy of contractors' Disclosure Statements. However, that evaluation will not be part of the audit scope.

What?

No, really.

Here, let us quote from the MRD:

We no longer will evaluate adequacy as part of the scope of any Disclosure Statement audit (Activity Code 19100). Instead, audit teams will review the submission for adequacy prior to accepting the engagement. The objective of a Disclosure Statement audit will be solely to determine whether the disclosed practices comply with Cost Accounting Standards (CAS). …

As part of determining whether to accept the engagement, the audit team will review whether the contractor's submission is adequate by:

  • determining whether the contractor followed the Disclosure Statement form instructions (see Conformity of Disclosure Statement with General Instructions tool);

  • determining whether contractor disclosures are consistent (see Internal Consistency of Disclosed Practices in a Disclosure Statement tool); and

  • gaining a thorough understanding of the basis of the described practices, usually during the contractor's walkthrough of the submission.

Note that DCAA has created some "tools" to help auditors with their adequacy submission. We checked and those tools are not currently available to the public on the DCAA website. So we don't know their format or content. But we suspect the new tools will be much like other DCAA tools. In other words, we expect more checklists that help auditors do their jobs without the necessity of using professional judgment.

Importantly, the auditors are directed to use their tools and understanding to determine whether the contractor's Disclosure Statement is "current, accurate, and complete." That's kind of amusing, really, because you can't find that phrase anywhere in the CAS Board regulations. DCAA kind of just made it up and then decided it was the sine qua non of Disclosure Statements.

So the auditors will use their tools and understanding to evaluate Disclosure Statement adequacy and to prepare a Memo to the Cognizant Federal Agency Official (CFAO) documenting their evaluation.

Yes, you read that correctly. Even though the adequacy evaluation is out of scope, the evaluation process will result in yet another Memo being issued. (** SIGH **) The Memo, whose conclusions will be based on out-of-scope procedures guided by "black box" tools whose inner workings are not fit for public knowledge, guided by a goal that cannot be found in the CAS Board regulations, will result in a recommendation to the cognizant Contracting Officer regarding the adequacy of the Disclosure Statement.

Only if DCAA and the CFAO reach an agreement on adequacy will the actual CAS compliance review actually begin. Yes, you read that correctly. All of the foregoing procedures are simply a precursor to the real DCAA review. (Although in fairness the MRD does say that the compliance review can continue so long as an agreement is reached on adequacy before the end of the review.)

We wish we were making this up.

But we are not.

What if the auditors and the CFAO disagree on the adequacy of the contractor's Disclosure Statement?

Well, the presumption in the MRD is that the auditors and CFAO will agree. If they agree the Disclosure Statement is adequate, then the review proceeds. If they agree it is inadequate, then the contractor will resubmit its Disclosure Statement and "the audit team will reassess the contractor's revised submission for adequacy." There is no guidance regarding what to do if the CFAO thinks the Disclosure Statement is adequate but the auditors do not.

Perhaps another Review Board?

And what about the notion that the auditors will participate in a "walkthough" of the Disclosure Statement? According to the MRD, the contractor is supposed to describe its intended cost accounting practices and provide "policies and procedures" that support those practices. Certainly, a couple of Cost Accounting Standards do require specified policies and procedures (e.g., describing direct versus indirect costs), but we are unaware of any CAS Board regulations that require all disclosed cost accounting practices to be supported with written policies and procedures. Indeed, the CAS Board regulations use the phrase "established or disclosed" to highlight the fact that what matters is the actual practices themselves and not words on a page.

Moreover, we are unaware of any requirement that contractors must participate in a nebulous "walkthrough" exercise in order to support a DCAA audit of a Disclosure Statement. While we generally applaud the notion that auditors must understand what they are auditing, we also subscribe to the time-honored notion that "the document speaks for itself". Obviously there is a balance between making the auditors happy and indulging in a non-value-added exercise simply to check-off a box on the audit program, but we have become disenchanted with "walkthroughs" and will be devoting an article to this recent DCAA fad in the near future.

We realize that our analysis of the recent revision to DCAA audit guidance has exhibited our usual restraint and subtlety. So let's bottom-line our assessment: Not the best audit guidance we've seen.

Indeed, it's kind of a hot mess, isn't it?

 


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