Skip to main content

BLACKBAUD INC

For the period ended Sep 30, 2024. Filed Oct 30, 2024.

View on SEC.gov

About this filing

A company's report for each of its first three quarters. The financial statements are not audited. It shows how the business has moved since the last annual report, and what management says changed.

Sep 30, 2024 · Filed Oct 30, 2024

BLKB$54.12-3.0%Stored close · as of Nov 6, 2026

What changed in Risk Factors?

Read the current filing

Previous report: 10-Q

Period ended 2024-06-30; filed 2024-07-31.

0001280058-24-000057

Item 1A. Risk factors

Current report: 10-Q

Period ended 2024-09-30; filed 2024-10-30.

0001280058-24-000065

Item 1A. Risk factors

The baseline is this issuer’s latest earlier reporting period of the same form that was filed before the current report. A previous 10-Q is a different quarter, not a year-over-year comparison. Amendments are excluded.

Compared 33 previous paragraphs and 17 current paragraphs.

9 unchanged; 7 reworded; 0 added; 16 removed; 1 previous and 1 current paragraphs rearranged.

Tables are not compared: 4 previous and 2 current tables excluded. Dates, whitespace, punctuation and numbering changes are ignored; changes to financial figures remain significant.

A changed paragraph is not evidence that risk increased or decreased. An unchanged paragraph does not establish that risk stayed the same.

Removed paragraphs (16)

Previous report

Defects, delays or interruptions in our cloud solutions, hosting services and payment services, including those caused by our vendors, partners or other third parties (such as the CrowdStrike Event described below), could diminish demand for these services and subject us to substantial liability.

Previous report

We utilize data center hosting facilities to provide cloud solutions to a significant number of our subscription customers, hosting services to our on-premise license customers and transactional payment services. Any damage to, or failure of, these systems or services generally could result in, and have resulted in (as described below), interruptions in service to our customers, notwithstanding any business continuity or disaster recovery agreements or arrangements that may be in place. Our executive offices and some of our data centers are located in areas that are vulnerable to the effects of climate change and could be subject to increased interruptions as a result of the severity and increased frequency of extreme weather events such as hurricanes, wildfires, floods, heat waves, or power shortages. Furthermore, because our cloud solutions, hosting service offerings and payment services are complex and incorporate a variety of computer hardware and software systems, our services have in the past developed, and may again develop, errors or defects, whether of our own creation or caused by third parties, that have, and could again, result in unanticipated downtime or other problems for our customers and us. Internet-based services sometimes contain undetected errors when first introduced or when new versions or enhancements are released. We have from time to time found defects in our web-based services and new errors might again be detected in the future. In addition, our customers might use our Internet-based offerings in unanticipated ways that cause a disruption in service for other customers attempting to access their data.

Previous report

For example, on July 19, 2024, CrowdStrike Holdings, Inc. (“CrowdStrike”), which provides cybersecurity services to millions of Microsoft Windows systems worldwide, including to certain Windows systems operated by Blackbaud, implemented a software update to its Falcon sensor software that was flawed and caused Falcon to crash, thereby causing widespread crashes of Windows systems into which it was integrated, including certain Windows systems used by us and certain of our customers (the “CrowdStrike Event”). As a result, some of our customers were unable to access certain of our services and solutions, including our payments processing solutions. We are still evaluating the actual and potential impact of the CrowdStrike Event on Blackbaud, both directly and indirectly due to the impact on our customers.

Previous report

Because our customers use our services for important aspects of their businesses, any defects, delays or disruptions in service or other performance problems with our services, such as the CrowdStrike Event, could hurt our reputation, damage our customers' businesses and result in liability for the Company. For example, customers could elect to cancel their service, delay or withhold payment to us, not purchase from us in the future or make claims against us, which could result in an increase in our provision for credit losses, an increase in collection cycles for accounts receivable, loss of revenue or the expense and risk of litigation. Any of these could materially harm our business, reputation, financial condition and results of operations.

Previous report

Financial Risks

Previous report

We significantly increased our leverage in connection with acquisition of EVERFI and stock repurchases, and may increase our leverage in the future in connection with additional acquisitions, Security Incident costs or other business purposes, which could adversely impact our business and financial performance.

Previous report

The degree to which we are leveraged could have adverse effects on our business, including the following:

Previous report

•Requiring us to dedicate a substantial portion of our cash flow from operations to payments on our indebtedness, thereby reducing the availability of our cash flow to fund working capital, capital expenditures, acquisitions, dividends, stock repurchases and other general corporate purposes;

Previous report

•Increasing the amount of interest we pay, particularly if interest rates increase;

Previous report

•Limiting our flexibility in planning for, or reacting to, changes in our business and the industries in which we operate;

Previous report

•Restricting us from making additional strategic acquisitions or exploiting business opportunities;

Previous report

•Reducing our currently available borrowing capacity or limiting our ability to borrow additional funds; and

Previous report

•Decreasing our ability to compete effectively or operate successfully under adverse economic and industry conditions.

Previous report

If we incur additional debt, these risks may intensify. Our ability to meet our debt service obligations will depend upon our future performance, which will be subject to the financial, business and other factors affecting our operations, many of which are beyond our control.

Previous report

In addition, additional leverage could impact our ability to meet certain financial and other covenants contained in our 2024 Credit Facilities, which increased our total borrowing capacity from $1.1 billion to $1.5 billion. (See Note 7 to our unaudited, condensed consolidated financial statements included in this report for a more detailed description of our 2024 Credit Facilities.) There can be no assurance that we will be able to remain in compliance with the covenants to which we are now subject or may be subject in the future and, if we fail to do so, that we will be able to obtain waivers from our lenders or amend the covenants.

Previous report

In the event of a default under our 2024 Credit Facilities, we could be required to immediately repay all outstanding borrowings, which we might not be able to do and which would materially negatively affect our business, operations and financial condition.
Reworded paragraphs (7)

Previous wording

We are supplementing Item 1A. Risk Factors in our Annual Report on Form 10-K for the year ended December 31, 2023, as filed with the Securities and Exchange Commission on February 21, 2024 (the “Annual Report”). The following risk factors should be read in conjunction with the risk factors set forth in that Annual Report.

Current wording

We are supplementing Item 1A. Risk Factors in our Annual Report on Form 10-K for the year ended December 31, 2023, as filed with the Securities and Exchange Commission on February 21, 2024 (the “Annual Report”). The following risk factor should be read in conjunction with the risk factors set forth in that Annual Report.

Previous wording

As previously disclosed, on July 16, 2020, we contacted certain customers to inform them about the Security Incident, including that in May 2020 we discovered and stopped a ransomware attack. Prior to our successfully preventing the cybercriminal from blocking our system access and fully encrypting files, and ultimately expelling them from our system with no significant disruption to our operations, the cybercriminal removed a copy of a subset of data from our self-hosted environment that affected over 13,000 customers. Based on the nature of the incident, our research and third party (including law enforcement) investigation we believe that no data went beyond the cybercriminal, was or will be misused, or will be disseminated or otherwise made available publicly. However, our investigation into the Security Incident remains ongoing and may provide additional information.

Current wording

As previously disclosed, on July 16, 2020, we contacted certain customers to inform them about the Security Incident, including that in May 2020 we discovered and stopped a ransomware attack. Prior to our successfully preventing the cybercriminal from blocking our system access and fully encrypting files, and ultimately expelling them from our system with no significant disruption to our operations, the cybercriminal removed a copy of a subset of data from our self-hosted environment that affected over 13,000 customers. Based on the nature of the incident, our research and third party (including law enforcement) investigation we believe that no data went beyond the cybercriminal, was or will be misused, or will be disseminated or otherwise made available publicly.

Previous wording

To date, we have received approximately 260 specific requests from customers for reimbursement of expenses incurred by them related to the Security Incident, all of which have been fully resolved and closed or are inactive and are considered by us to have been abandoned by the customers. We have also received approximately 400 reservations of the right to seek expense recovery in the future from customers or their attorneys in the U.S., U.K. and Canada related to the Security Incident, none of which resulted in claims submitted to us and are considered by us to have been abandoned by the customers. We have also received notices of proposed claims on behalf of a number of U.K. data subjects, which we are reviewing. In addition, insurance companies representing various customers’ interests through subrogation claims have contacted us, and certain insurance companies have filed subrogation claims in court, of which three cases remain active and unresolved. In addition, presently, we are a defendant in putative consumer class action cases in U.S. federal courts (most of which have been consolidated under multi district litigation to a single federal court) and in Canadian courts alleging harm from the Security Incident. The plaintiffs in these cases, who generally purport to represent various classes of individual constituents of our customers, generally claim to have been harmed by alleged actions and/or omissions by us in connection with the Security Incident and assert a variety of common law and statutory claims seeking monetary damages, injunctive relief, costs and attorneys’ fees, and other related relief. On May 14, 2024, the Court issued a memorandum opinion and order (1) denying the multi district litigation plaintiffs' motion for class certification because of the plaintiffs' failure to meet their burden of proof as to ascertainability, (2) granting our motion to exclude the multi district litigation plaintiffs' expert on the issue of ascertainability, and (3) denying the multi district litigation plaintiffs' motion to exclude our expert on the issue of ascertainability. Further, the Court denied as moot all other pending motions. On May 28, 2024, the plaintiffs filed a petition for permission to appeal under Rule 23(f) of the Federal Rules of Civil Procedure with the Fourth Circuit Court of Appeals (the “Fourth Circuit”) and we subsequently filed an opposition to such petition. On July 30, 2024, the Fourth Circuit denied the plaintiffs' petition. This litigation remains ongoing. We are subject to pending governmental actions or investigations by the U.S. Department of Health and Human Services, the Office of the Australian Information Commissioner and the Office of the Privacy Commissioner of Canada. (See Note 9 to our unaudited, condensed consolidated financial statements included in this report for a more detailed description of the Security Incident and related matters.)

Current wording

To date, we have received approximately 260 specific requests from customers for reimbursement of expenses incurred by them related to the Security Incident, all of which have been fully resolved and closed or are inactive and are considered by us to have been abandoned by the customers. We have also received approximately 400 reservations of the right to seek expense recovery in the future from customers or their attorneys in the U.S., U.K. and Canada related to the Security Incident, none of which resulted in claims submitted to us and are considered by us to have been abandoned by the customers. We have also received notices of proposed claims on behalf of a number of U.K. data subjects, which we are reviewing. In addition, insurance companies representing various customers’ interests through subrogation claims have contacted us, and certain insurance companies have filed subrogation claims in court, of which two cases remain active and unresolved. In addition, presently, we are a defendant in putative consumer class action cases in U.S. federal courts (most of which have been consolidated under multi district litigation to a single federal court) and in Canadian courts alleging harm from the Security Incident. The plaintiffs in these cases, who generally purport to represent various classes of individual constituents of our customers, generally claim to have been harmed by alleged actions and/or omissions by us in connection with the Security Incident and assert a variety of common law and statutory claims seeking monetary damages, injunctive relief, costs and attorneys’ fees, and other related relief. On May 14, 2024, the Court issued a memorandum opinion and order (1) denying the multi district litigation plaintiffs' motion for class certification because of the plaintiffs' failure to meet their burden of proof as to ascertainability, (2) granting our motion to exclude the multi district litigation plaintiffs' expert on the issue of ascertainability, and (3) denying the multi district litigation plaintiffs' motion to exclude our expert on the issue of ascertainability. Further, the Court denied as moot all other pending motions. On May 28, 2024, the plaintiffs filed a petition for permission to appeal under Rule 23(f) of the Federal Rules of Civil Procedure with the Fourth Circuit Court of Appeals (the “Fourth Circuit”), and we subsequently filed an opposition to such petition. On July 30, 2024, the Fourth Circuit denied the plaintiffs' petition. This litigation remains ongoing. We are subject to pending governmental actions or investigations by the U.S. Department of Health and Human Services, the Office of the Australian Information Commissioner and the Office of the Privacy Commissioner of Canada. (See Note 9 to our unaudited, condensed consolidated financial statements included in this report for a more detailed description of the Security Incident and related matters.)

Previous wording

As previously disclosed, on June 13, 2024, we agreed to a Final Judgment and Permanent Injunction with the Attorney General of the State of California (the "Final Judgment") relating to the Security Incident. This settlement fully resolved the last remaining U.S. state attorney general investigation into the Security Incident. Under the terms of the settlement, we agreed to comply with applicable laws; not to make misleading statements related to our data protection, privacy, security, confidentiality, integrity, breach notification requirements, and similar matters; and to implement and improve certain cybersecurity programs and tools. The terms of the settlement with California are generally consistent with those to which we agreed in settling with the other 49 state Attorneys General and the District of Columbia on October 5, 2023, as discussed below. As part of the settlement, we also agreed to pay a total of $6.8 million to the State of California. This amount was fully accrued as a contingent liability in the Company's financial statements as of March 31, 2024 and June 30, 2024, and subsequently paid in the third quarter of 2024. By agreeing to the Final Judgment, Blackbaud has denied wrongdoing or liability of any kind. Nothing contained in the Final Judgment is intended to be, and shall not in any event be construed or deemed to be, an admission or concession or evidence of any liability or wrongdoing whatsoever on the part of Blackbaud or any fact or violation of law, rule, or regulation. For more information, see the Final Judgment and Permanent Injunction of the State of California, County of San Diego that was furnished as Exhibit 99.1 to our Current Report on Form 8-K filed with the SEC on June 14, 2024.

Current wording

On June 13, 2024, we agreed to a Final Judgment and Permanent Injunction with the Attorney General of the State of California (the "California Judgment") relating to the Security Incident. This settlement fully resolved the last remaining U.S. state attorney general investigation into the Security Incident. Under the terms of the settlement, we agreed to comply with applicable laws; not to make misleading statements related to our data protection, privacy, security, confidentiality, integrity, breach notification requirements, and similar matters; and to implement and improve certain cybersecurity programs and tools. The terms of the settlement with California are generally consistent with those to which we agreed in settling with the other 49 state Attorneys General and the District of Columbia on October 5, 2023, as discussed below. As part of the settlement, we also agreed to pay a total of $6.8 million to the State of California. This amount was fully accrued as a contingent liability in the Company's financial statements as of March 31, 2024 and June 30, 2024, and subsequently paid in the third quarter of 2024. Nothing contained in the California Judgment is intended to be, and shall not in any event be construed or deemed to be, an admission or concession or evidence of any liability or wrongdoing whatsoever on the part of Blackbaud or any fact or violation of law, rule, or regulation. For more information, see the Final Judgment and Permanent Injunction of the State of California, County of San Diego that was furnished as Exhibit 99.1 to our Current Report on Form 8-K filed with the SEC on June 14, 2024.

Previous wording

As noted above, the terms of the Final Judgment, FTC Order, the Attorneys General Administrative Orders and our settlement with the SEC require that we implement and maintain certain processes and programs and comply with certain legal requirements related to cybersecurity and data protection. Any future regulatory investigation or litigation settlements may also contain such requirements. Effectively implementing, monitoring and updating these requirements is expected to be expensive and time-consuming over an extended period. Our failure to do so in accordance with the terms of our agreements with FTC, the Attorneys General and with the SEC, and possibly others, could expose us to additional material liability under the terms of the Administrative Orders, the SEC settlement, or otherwise.

Current wording

As noted above, the terms of the California Judgment, FTC Order, the Attorneys General Administrative Orders and our settlement with the SEC require that we implement and maintain certain processes and programs and comply with certain legal requirements related to cybersecurity and data protection. Any future regulatory investigation or litigation settlements may also contain such requirements. Effectively implementing, monitoring and updating these requirements has been, and is expected to be over an extended period of time, expensive and time-consuming. Our failure to do so in accordance with the terms of our agreements with FTC, the Attorneys General and with the SEC, and possibly others, could expose us to additional material liability under the terms of the Administrative Orders, the SEC settlement, or otherwise.

Previous wording

We may be named as a party in additional lawsuits, other claims may be asserted by or on behalf of our customers or their constituents, and we may be subject to additional governmental inquires, requests or investigations. Responding to and resolving these current and any future lawsuits, claims and/or investigations could result in material remedial and other expenses that will not be covered by insurance. It is reasonably possible that our estimated or actual losses may change in the near term for those matters and be materially in excess of the amounts accrued. Certain governmental authorities are seeking to impose undertakings, injunctive relief, consent decrees, or other civil or criminal penalties, which could, among other things, materially increase our data security costs or otherwise require us to alter how we operate our business. Although we intend to defend ourselves vigorously against the claims asserted against us, we cannot predict the potential outcomes, cost and expenses associated with current and any future claims, lawsuits, inquiries and investigations.

Current wording

We may be named as a party in additional lawsuits, other claims may be asserted by or on behalf of our customers or their constituents, and we may be subject to additional governmental inquires, requests or investigations. Responding to and resolving these current and any future lawsuits, claims and/or investigations could result in material remedial and other expenses that will not be covered by insurance. It is reasonably possible that our estimated or actual losses may change in the near term for those matters and be materially in excess of the amounts accrued. Certain governmental authorities have imposed, and others may in the future impose, undertakings, injunctive relief, consent decrees, or other civil or criminal penalties, which have materially increased our data security costs or otherwise required us to alter how we operate our business, and could further do so in the future. Although we intend to defend ourselves vigorously against the claims asserted against us, we cannot predict the potential outcomes, cost and expenses associated with current and any future claims, lawsuits, inquiries and investigations.

Previous wording

Significant management time and Company resources have been, and are expected to continue to be, devoted to the Security Incident. For example, for the three and six months ended June 30, 2024, we incurred net pre-tax expenses of $1.8 million and $12.1 million, respectively, related to the Security Incident, which included $1.8 million and $5.1 million, respectively, for ongoing legal fees and additional accruals for loss contingencies of $0.0 million and $7.0 million, respectively. During the six months ended June 30, 2024, we had cash outlays of $5.8 million related to the Security Incident for ongoing legal fees. For full year 2023, we currently expect pre-tax expenses of approximately $5.0 million to $10.0 million and cash outlays of approximately $8.0 million to $13.0 million for ongoing legal fees related to the Security Incident. Although we carry insurance against certain losses related to the Security Incident, we exceeded the limit of that insurance coverage in the first quarter of 2022. As a result, we will be responsible for all expenses or other losses (including penalties, fines or other judgments) or all types of claims that may arise in connection with the Security Incident, which could materially and adversely affect our liquidity and results of operations. (See Note 9 to our unaudited, condensed consolidated financial statements in this report.) If any such fines or penalties were great enough that we could not pay them through funds generated from operating activities and/or cause a default under the 2024 Credit Facilities, we may be forced to renegotiate or obtain a waiver under the 2024 Credit Facilities and/or seek additional debt or equity financing. Such renegotiation or financing may not be available on acceptable terms, or at all. In these circumstances, if we were unable to obtain sufficient financing, we may not be able to meet our obligations as they come due.

Current wording

contingencies of $6.8 million. During the nine months ended September 30, 2024, we had cash outlays of $15.1 million related to the Security Incident for ongoing legal fees and the $6.8 million paid during the third quarter of 2024 related to our settlement with the Attorney General of the State of California. For full year 2023, we currently expect pre-tax expenses of approximately $5.0 million to $10.0 million and cash outlays of approximately $8.0 million to $13.0 million for ongoing legal fees related to the Security Incident. Although we carry insurance against certain losses related to the Security Incident, we exceeded the limit of that insurance coverage in the first quarter of 2022. As a result, we will be responsible for all expenses or other losses (including penalties, fines or other judgments) or all types of claims that may arise in connection with the Security Incident, which could materially and adversely affect our liquidity and results of operations. (See Note 9 to our unaudited, condensed consolidated financial statements in this report.) If any such fines, penalties or judgments were great enough that we could not pay them through funds generated from operating activities and/or cause a default under the 2024 Credit Facilities, we may be forced to renegotiate or obtain a waiver under the 2024 Credit Facilities and/or seek additional debt or equity financing. Such renegotiation or financing may not be available on acceptable terms, or at all. In these circumstances, if we were unable to obtain sufficient financing, we may not be able to meet our obligations as they come due.
Rearranged current paragraphs (1)

Current report — wording carried from elsewhere

Significant management time and Company resources have been, and are expected to continue to be, devoted to the Security Incident. For example, for the nine months ended September 30, 2024, we incurred net pre-tax expenses of $12.8 million related to the Security Incident, which included $6.0 million for ongoing legal fees and additional accruals for loss
Rearranged previous paragraphs (1)

Previous report — wording carried elsewhere

We incurred a substantial amount of indebtedness in connection with acquisitions, including our acquisition of EVERFI, Inc. (as described in Note 3 in our most recently filed Annual Report on Form 10-K). As a result of this indebtedness and other borrowings, including our borrowings in March 2024 to fund the ASR Transaction, our interest payment obligations have increased. In addition, we have been named as a party in various lawsuits in connection with the Security Incident, claims have been asserted by or on behalf of our customers or their constituents, and we are subject to various governmental inquires, requests or investigations. Responding to and resolving these current and any future lawsuits, claims and/or investigations could result in material remedial and other expenses. Although we intend to defend ourselves vigorously against the claims asserted against us, we cannot predict the potential outcomes, cost and expenses associated with current and any future claims, lawsuits, inquiries and investigations, which could require that we incur additional indebtedness to fund. (See Note 9 to our unaudited, condensed consolidated financial statements in this report for additional information regarding the Security Incident.)