GSA’s Transactional Data Reporting Rule Ushers in a New Era

Merle M. DeLancey Jr.Justin Chiarodo, and Philip Beshara

Last month, the General Services Administration (“GSA”) finalized a rule marking what the agency describes as the most significant development to its Schedules program in over two decades. The rule completely changes how GSA will analyze vendor pricing for products and services.

Under the rule, vendors will eventually be required to submit monthly transactional data reports with information related to orders and prices under certain GSA Schedule contracts and other vehicles. Along with the implementation of the new Transactional Data Reporting (“TDR”) requirement, GSA will relieve vendors from two preexisting compliance burdens—eliminating the Commercial Sales Practices (“CSP”) and Price Reductions Clause (“PRC”) reporting requirements when vendors begin submitting transactional data.

While vendors should welcome the relief provided from the elimination of two burdensome regulations, the shift to TDR will not be without cost and risk; and, the eventual efficiencies promised by GSA remain to be seen. Indeed, the impact of the change will likely extend beyond compliance burdens, with potential effects varying from the nature of False Claims Act suits to the potential publication of competitive information.

We summarize these and other key takeaways from the new rule below, and answer questions important to vendors as GSA rolls out this significant development. Continue reading “GSA’s Transactional Data Reporting Rule Ushers in a New Era”

Department of Labor Issues Final Rule Updating Sex Discrimination Guidelines

Merle M. DeLancey Jr. and Lyndsay A. Gorton

On June 15, 2016, the Department of Labor (“DOL”) Office of Federal Contract Compliance Programs (“OFCCP”) issued a final rule updating its 1970 sex discrimination guidelines. The final rule, available here, enforces Executive Order 11246, which prohibits federal contractors and subcontractors from employment discrimination based on race, color, religion, sex, sexual orientation, gender identity, or national origin. The rule applies to companies that have federal government contracts of $10,000 or more and will be effective on August 15, 2016. Continue reading “Department of Labor Issues Final Rule Updating Sex Discrimination Guidelines”

Supreme Court Affirms Small Business Preference Requirement in Veterans Affairs Contracts in Kingdomware Technologies, Inc. v. United States

Merle M. DeLancey Jr. and Lyndsay A. Gorton

On June 16, 2016, the Supreme Court issued a decision in Kingdomware Technologies, Inc. v. United States, available here, holding that the Veterans Benefits, Health Care, and Information Technology Act of 2006 (the “Veterans Act of 2006”) requires the Department of Veterans Affairs (“VA”) to conduct a “Rule of Two” analysis before a contract award. The unanimous decision, authored by Justice Clarence Thomas, holds that the Veterans Act of 2006 “unambiguously requires” the VA to use the Rule of Two before awarding a contract under competitive procedures even when the VA will otherwise meet its annual minimum small business contracting goals.

Kingdomware Technologies, Inc. is a veteran-owned small business (“VOSB”) that filed suit after unsuccessfully bidding for a VA emergency-notification services contract that was eventually awarded to a non-VOSB via the Federal Supply Schedule (“FSS”). In its protest to the Government Accountability Office, and subsequent suits in the Federal Circuit, Kingdomware argued that the VA violated the Veterans Act of 2006 by failing to award the contract to a VOSB because it did not award the contract based on the mandatory Rule of Two provision. The Rule of Two states that the VA “shall award” contracts to VOSBs when there is a “reasonable expectation” that two VOSBs will submit bids “at a fair and reasonable price that offers the best value to the United States.” Continue reading “Supreme Court Affirms Small Business Preference Requirement in Veterans Affairs Contracts in Kingdomware Technologies, Inc. v. United States

We Just Received a Government Subpoena. Now What?

Merle M. DeLancey Jr., Steven J. Roman, James R. Murray, and Christian N. Curran

If you are a multi-million dollar company and receive a subpoena for your documents and records, you simply send it to the legal department. But what if you are a smaller healthcare provider? Responding to a government subpoena can be daunting, especially if it is your first one, and you may not have the personnel or resources to respond without a significant disruption to your business. Does the subpoena mean you or your company is about to be charged with a crime? Do you have to submit original records? Will the government insist on the production of all documents within the often broadly worded scope of a subpoena? How do you deal with electronic information on your computer system? How do you protect patient confidentiality? Will your insurance help with the costs of complying with the subpoena? What can you do to ensure the company is prepared ahead of time?

Step One: Issue a Document Hold Notice and Consult Counsel

The first thing you should do when you receive a government subpoena is issue a written notice to your employees to protect and maintain any documents and records that may be encompassed by the subpoena. As part of that process, you will also need to suspend any records destruction practices that you currently have in place. The failure to produce or preserve potentially relevant documents and information can result in significant exposure. Courts have regularly penalized companies and individuals who fail to produce or preserve potentially relevant materials. It is important to send the notice out as soon as possible and to thoroughly document its distribution. You should also simultaneously consult with counsel to review the subpoena and ensure that you are taking all necessary steps to preserve information. Continue reading “We Just Received a Government Subpoena. Now What?”

Medicare Advantage Program Enforcement: Increased Publicity May Lead to Increased Scrutiny

Merle M. DeLancey Jr. and Lyndsay A. Gorton

On May 19, 2015, the chairman of the Senate Judiciary Committee, Senator Charles E. Grassley (R-IA), requested information from United States Attorney General Loretta Lynch and Andrew M. Slavitt, Acting Administrator for Centers for Medicare and Medicaid Services (CMS) regarding how the agencies are working together and separately to prevent Medicare Advantage fraud. Senator Grassley’s letters rely on April 2015 investigative findings issued by the Center for Public Integrity for his assertion that there is “an increasing number of lawsuits against insurance companies” for Medicare Advantage fraud, and the Government Accountability Office’s (GAO) 2015 Annual Report, which suggests that CMS “could save billions of dollars by improving the accuracy of its payments to Medicare Advantage programs. . . .” To ensure that CMS has the appropriate “safeguards” in place to prevent fraud, Senator Grassley requested answers to the following questions by June 3, 2015:

  1. What steps has the Department of Justice (DOJ) taken, and is currently taking, to ensure that insurance companies are not fraudulently altering risk scores?
  2. Is DOJ working in conjunction with CMS to investigate risk score fraud? If not, why not?
  3. In the past five years, how many Medicare Advantage risk score fraud investigations has DOJ conducted? Of the investigations, how many have resulted in criminal and/or civil sanction?

Senator Grassley’s letters were sent only weeks after CMS issued its 2016 Rate Announcement and Call Letter on April 6, 2015. After accepting and reviewing comments on its Advance Notice and Draft Call Letter, which estimated a 0.95 percent decrease in revenue for plan providers, the April 6 announcement estimated a 3.25 percent increase in revenue based on finalized 2016 rates. Neither the Attorney General nor CMS has responded to Senator Grassley’s requests. Continue reading “Medicare Advantage Program Enforcement: Increased Publicity May Lead to Increased Scrutiny”

Responding to a Warrant—What to Do if Your Company Is Subject to a Fraud Investigation

Merle M. DeLancey Jr., Steven J. Roman, and Philip E. Beshara

This is the scenario: you are an executive or manager at a government contractor. It’s Friday morning. You are hoping to leave early and get a jump on the weekend. Then, the receptionist buzzes you and says, “There are men and women out here wearing FBI windbreakers and they want to execute a search warrant.” You wonder, “Can I tell the agents they cannot come in?” Your company does not have in-house counsel. You can call your attorney, but his or her office is across town and the FBI agents say they are not going to wait. “What should I do?”

This may sound like an unlikely scenario, but such government investigations happen all of the time around the country and are rarely expected. In recent years, prosecutors and agents from the Department of Justice (DOJ) and Inspector General Offices have brought charges of procurement fraud and corruption against over 100 defendants, including officers and employees of companies of all sizes. In September 2014, DOJ’s Criminal Division announced that it would be “stepping up” its investigation and prosecution of criminal violations of the False Claims Act, using a team of senior federal prosecutors dedicated exclusively to procurement fraud. DOJ’s announcement cited the use of search warrants as one of the significant investigative tools at prosecutors’ disposal. In addition to their increased exposure to law enforcement authorities, small businesses should expect greater scrutiny of their contracting dollars, an initiative that has received bipartisan support in Congress. In March, the House Small Business Committee approved a measure calling for a sweeping examination into abuses in small business contracting, and the Small Business Administration recently proposed a rule for harsher penalties relating to small business subcontracting limitations. Continue reading “Responding to a Warrant—What to Do if Your Company Is Subject to a Fraud Investigation”

New Anti-Trafficking Regulations Finalized for Government Contractors

Merle M. DeLancey Jr., Daniel A. Broderick, and Philip E. Beshara

On January 29, 2015, the Department of Defense, General Services Administration, and National Aeronautics and Space Administration published a final rule, effective March 2, 2015, implementing extensive new prohibitions and compliance requirements to the Federal Acquisition Regulation (FAR). The changes, mandated by President Obama’s December 2012 Executive Order (E.O. 13627) and the FY 2013 National Defense Authorization Act, raise across-the-board compliance concerns for government contractors—especially those that regularly employ foreign nationals.

New Restrictions and Requirements

The rule, amending FAR Subpart 22.17 and Contract Clause 52.222-50, will prohibit contractors and subcontractors from denying employees identity or immigration documents; using misleading or fraudulent recruitment practices; charging employees recruitment fees; using recruiters that do not comply with local labor laws of the country recruited from; and providing or arranging housing that fails to meet the host country’s housing and safety standards. The regulations also generally require contractors and subcontractors to pay for or provide transportation of foreign workers back to their home country at the end of their employment if they were brought to the work-country for the purpose of working on a U.S. Government contract or subcontract; or if the work-country is the U.S., they are not a U.S. national, and transportation is required under existing temporary worker programs or pursuant to a written agreement with the employee.

If required by law or under the contract, contractors and subcontractors must provide a written work document to employees in a language the employee understands. The rule further requires that the document contain, at minimum, details about work description, wages, the prohibition on recruitment fees, work location(s), living accommodations and associated costs, time off, round-trip transportation arrangements, grievance process, and the content of applicable trafficking laws and regulations. Continue reading “New Anti-Trafficking Regulations Finalized for Government Contractors”

Guidelines for Contractors Considering Giving Gifts to Government Customers

Merle M. DeLancey Jr. and Christian N. Curran

As the holiday season approaches, companies may consider giving gifts to their government customers. But companies should be aware of the legal limits imposed on gift giving, which could result in serious penalties if ignored. Generally, federal government employees may not solicit or accept gifts or any other thing of value from prohibited sources. See generally, 5 C.F.R. Part 2635, Standards of Ethical Conduct for Employees of the Executive Branch. A prohibited source is defined as a person or company seeking official action by, doing business with, or seeking to do business with the employee’s agency, or a person or company regulated by the employee’s agency or that has interests that may be substantially affected by the employee’s official duties.

There are exclusions under the definition of “gift” that allow for some leeway in giving. Snacks or light refreshments (e.g., coffee and doughnuts at a seminar, but not as part of a meal) are excluded from the definition of gift. Items of little intrinsic value such as greeting cards are also excluded. Further, anything that a government employee pays “market value” for is not considered a gift. Market value can have varying meanings, but generally is considered face value, what the contractor paid for it, or the open market equivalent, depending on the item. Continue reading “Guidelines for Contractors Considering Giving Gifts to Government Customers”

What Service Contractors Need to Know About the Executive Order Raising the Minimum Wage

 

Merle M. DeLancey Jr. and Stephanie M. Harden

Starting January 1, 2015, a minimum wage of $10.10 per hour will apply to certain federal government contracts issued or awarded after that date. This alert provides key details about this new minimum wage that service contractors need to know.

Which Contracts Are Covered?

On February 12, 2014, President Obama signed Executive Order 13658, which instructed the Secretary of Labor to raise the minimum wage on federal construction and service contracts to $10.10 per hour beginning in 2015 and, beginning in January 2016, to an amount set by the Secretary on an annual basis. The Department of Labor issued a final rule implementing this new minimum wage in October 2014. See 79 Fed. Reg. 60,633 (Oct. 7, 2014).

The Department of Labor’s final rule generally extends to the following four categories of “contracts” and “contract-like instruments”:

  1. Procurement contracts for construction services covered by the Davis-Bacon Act (DBA);
    2. Service contracts covered by the Service Contract Act (SCA);
    3. Concession contracts, including any concession contract excluded from the SCA by the Department of Labor’s regulations at 29 C.F.R. § 4.133(b); and
    4. Contracts in connection with federal property or lands related to offering services for federal employees, their dependents, or the general public.

Continue reading “What Service Contractors Need to Know About the Executive Order Raising the Minimum Wage”

Does Your State Contract Prohibit Offshore Outsourcing?

Merle M. DeLancey Jr.

So your company has been diligently trying to comply with state and federal government contracting regulations. You pay your service employees in accordance with the Service Contract Act, you file your EEO-1s and VETS 100s, you monitor state campaign contributions, and you follow all of the additional requirements in your compliance plan. You think your company is “golden.” Right? Maybe. Are you “offshoring” services under your contract, or the data related to your state and/or Medicaid government contracts? This easily overlooked issue has been percolating to the top of the list for government agencies, state attorneys general, and perhaps, qui tam plaintiffs’ attorneys.

Offshoring, or “the import from abroad of goods or services that were previously produced domestically,”[1] is a major part of today’s business landscape, and government contracting at both federal and state levels is no exception. The issue of offshore outsourcing of services first drew attention in the world of government contracts in 2004, when the media reported that call centers in India were answering customer service calls from Food Stamp recipients.[2] The controversy faded from the public spotlight, but in response to public outcry some states passed legislation or issued executive orders prohibiting or limiting the practice.

A recent (April 11, 2014) report[3] from the Department of Health and Human Services (DHHS) Office of the Inspector General (OIG) resurfaced the issue of offshoring restrictions in the context of Medicaid contracts. The report reminded contractors that offshoring prohibitions and limitations remain in full force today, and government contractors need to be aware of them. Government contractors must review each individual state contract to ensure compliance with any offshore outsourcing prohibition or restriction. Running afoul of an offshore outsourcing prohibition could have serious consequences. Noncompliance could expose a contractor to suspension, debarment, or even liability under the state’s version of the False Claims Act under the theory that the contractor implicitly certified compliance with a material term of the contract.[4] Continue reading “Does Your State Contract Prohibit Offshore Outsourcing?”

Exit mobile version
%%footer%%