XML 31 R19.htm IDEA: XBRL DOCUMENT
v3.24.2.u1

Commitments And Contingencies | 9 Months Ended
--- | ---
Jun. 30, 2024
Commitments and Contingencies Disclosure [Abstract] |
Commitments And Contingencies | COMMITMENTS AND CONTINGENCIES Litigation We are subject to audits, investigations, and reviews relating to compliance with the laws and regulations that govern our role as a contractor to agencies and departments of federal, state, local, and foreign governments. Adverse findings could lead to criminal, civil, or administrative proceedings, and we could be faced with penalties, fines, suspension, or debarment. Adverse findings could also have a material adverse effect on us because of our reliance on government contracts. We are subject to periodic audits by federal, state, local, and foreign governments for taxes. We are also involved in various claims, arbitrations, and lawsuits arising in the normal conduct of our business. These include but are not limited to bid protests, employment matters, contractual disputes, and charges before administrative agencies. Except for the matters described below for which we cannot predict the outcome, we do not believe the outcome of any existing matter would likely have a material adverse effect on our consolidated financial position, results of operations, or cash flows. We evaluate, on a regular basis, developments in our litigation matters and establish or make adjustments to our accruals as appropriate. A liability is accrued if a loss is probable and the amount of such loss can be reasonably estimated. If the risk of loss is probable, but the amount cannot be reasonably estimated, or the risk of loss is only reasonably possible, a potential liability will be disclosed but not accrued, if material. Due to the inherent uncertainty in the outcome of litigation, our estimates and assessments may prove to be incomplete or inaccurate and could be impacted by unanticipated events and circumstances, adverse outcomes, or other future determinations. MOVEit Cybersecurity Incident Litigation As the Company has previously disclosed, on May 31, 2023, Progress Software Corporation, the developer of MOVEit (“MOVEit”), a file transfer application used by many organizations to transfer data, announced a critical zero-day vulnerability in the application that allowed unauthorized third parties to access its customers’ MOVEit environments. Maximus uses MOVEit for internal and external file sharing purposes, including to share data with government customers related to Maximus's services in support of certain government programs. Based on its review of the impacted files to date, the Company has provided notices to individuals whose personal information, including social security numbers, protected health information, and/or other personal information, may have been included in the impacted files. On August 1, 2023, a purported class action was filed against Maximus Federal Services, Inc. (a wholly-owned subsidiary of Maximus, Inc.) in the U.S. District Court for the Eastern District of Virginia arising out of the MOVEit cybersecurity incident – Bishop v. Maximus Federal Services, Case No. 1:23-cv-01019 (U.S. Dist. Ct. E. D. VA). The plaintiff, who purports to represent a nationwide class of individuals, alleges, among other things, that the Company’s negligence resulted in the compromise of the plaintiff’s personally identifiable information and protected health information. Since August 1, 2023, approximately eleven additional cases arising out of the MOVEit cybersecurity incident have been filed in federal courts against Maximus, Inc. and its subsidiaries. These cases each allege substantially similar allegations on behalf of putative nationwide classes and on behalf of various putative state subclasses. Three plaintiffs have subsequently dismissed their claims voluntarily. On October 4, 2023, the United States Judicial Panel on Multidistrict Litigation granted a Motion to Transfer that created a Multidistrict Litigation (“MDL”) in the District of Massachusetts for all cases in federal court related to the MOVEit cybersecurity incident, including cases filed against Maximus and other defendants, including Progress Software Corporation, the creator of MOVEit. All of the cases against Maximus, Inc. and its subsidiaries initially filed in federal courts outside of the District of Massachusetts that are related to the MOVEit cybersecurity incident have now been transferred to the MDL under the caption In re: MOVEit Customer Data Security Breach Litigation and are currently stayed pending the filing of consolidated amended compliant(s). The plaintiffs in Bishop and the other cases against the company in the MDL seek damages to be proved at trial. On September 6, 2023, an individual action was filed in state court in the Florida Circuit Court for the 7th Judicial Circuit, Volusia County: Taylor v. Maximus Federal Services, Case No. 2023-12349 (Fla. Cir. Ct., 7th Jud. Cir., Volusia Cnty.), also arising out of the MOVEit cybersecurity incident. The plaintiff alleges, among other things, that the Company’s negligence resulted in the compromise of the plaintiff’s personally identifiable information and protected health information. Since September 6, 2023, approximately eight additional individual actions have been filed against Maximus, Inc. and its subsidiaries in Florida state courts, one of which has been dismissed. The Taylor matter pending in Volusia County, Florida has been stayed. The remaining seven matters pending in Florida’s state courts are pending in Miami-Dade County court. Each of the actions pending in Florida courts raise substantially similar allegations and legal claims. The plaintiffs in these individual actions seek damages to be proved at trial. On October 27, 2023, a purported class action was filed in state court in Marion Superior Court in Marion County, Indiana, against Maximus Health Services, Inc. (a wholly owned subsidiary of Maximus, Inc.): Solis Garcia v. Maximus Health Services, Inc., Case No. 49D12-2310-CT-042115 (Ind. Super. Ct., Marion Cnty.), again arising out of the MOVEit cybersecurity incident. The plaintiff, who purports to represent a class comprised of Indiana residents, alleges, among other things, that the Company’s negligence resulted in the compromise of the plaintiff’s personally identifiable information and protected health information. The plaintiff seeks damages to be proved at trial. The Company has removed this case to federal court in the Southern District of Indiana and it has been transferred to the MDL. The Company is not able to determine or predict the ultimate outcome of any of these proceedings or reasonably provide an estimate or range of the possible outcome or loss, if any. Census Project – Civil Investigation Demand (“CID”) In 2021, Maximus received a CID from the U.S. Department of Justice (“DOJ”) pursuant to the False Claims Act seeking records pertaining to the Census project. The CID requested the production of documents related to the Company’s compliance with telephone call quality assurance scoring and reporting requirements. The Company is cooperating with the DOJ in its investigation and providing responses and information on an ongoing basis. As of June 30, 2024, the Company has reserve d $4.0 million i n connection with this matter. While it is reasonably possible that losses exceeding the amount accrued may be incurred, it is not possible at this time to estimate the additional possible loss in excess of the amount already accrued.

X
- References No definition available. + Details
Name: | us-gaap_CommitmentsAndContingenciesDisclosureAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure for commitments and contingencies. + References Reference 1: http://www.xbrl.org/2009/role/commonPracticeRef -Topic 405 -SubTopic 30 -Name Accounting Standards Codification -Publisher FASB -URI https://asc.fasb.org/405-30/tableOfContent Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Topic 440 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 4 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org/1943274/2147482648/440-10-50-4 Reference 3: http://www.xbrl.org/2009/role/commonPracticeRef -Topic 450 -Name Accounting Standards Codification -Publisher FASB -URI https://asc.fasb.org/450/tableOfContent Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Topic 954 -SubTopic 440 -Name Accounting Standards Codification -Section 50 -Paragraph 1 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org/1943274/2147478522/954-440-50-1 Reference 5: http://www.xbrl.org/2003/role/disclosureRef -Topic 440 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 4 -Subparagraph (c) -Publisher FASB -URI https://asc.fasb.org/1943274/2147482648/440-10-50-4 Reference 6: http://fasb.org/us-gaap/role/ref/legacyRef -Topic 440 -Name Accounting Standards Codification -Publisher FASB -URI https://asc.fasb.org/440/tableOfContent + Details
Name: | us-gaap_CommitmentsAndContingenciesDisclosureTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration