# EDGAR Filing Document

**Accession Number:** 0001280058
**File Stem:** 0001280058-23-000010
**Filing Date:** 2023-3
**Character Count:** 28920
**Document Hash:** f9a48b1010fcf616ab43d98447d965f9
**Contains OCR:** False
**Source Format:** 

## Filing Content

## Filing Summary
**0001280058-23-000010.hdr.sgml**: 20230309

**ACCESSION NUMBER**: 0001280058-23-000010

**CONFORMED SUBMISSION TYPE**: 8-K

**PUBLIC DOCUMENT COUNT**: 17

**CONFORMED PERIOD OF REPORT**: 20230309

**ITEM INFORMATION**: Regulation FD Disclosure

**ITEM INFORMATION**: Financial Statements and Exhibits

**FILED AS OF DATE**: 20230309

**DATE AS OF CHANGE**: 20230309

**FILER**: 

**COMPANY DATA:**
- **COMPANY CONFORMED NAME:** BLACKBAUD INC
- **CENTRAL INDEX KEY:** 0001280058
- **STANDARD INDUSTRIAL CLASSIFICATION:** SERVICES-PREPACKAGED SOFTWARE [7372]
- **IRS NUMBER:** 112617163
- **STATE OF INCORPORATION:** DE
- **FISCAL YEAR END:** 1231

**FILING VALUES:**
- **FORM TYPE:** 8-K
- **SEC ACT:** 1934 Act
- **SEC FILE NUMBER:** 001-41527
- **FILM NUMBER:** 23720800

**BUSINESS ADDRESS:**
- **STREET 1:** 65 FAIRCHILD STREET
- **CITY:** CHARLESTON
- **STATE:** SC
- **ZIP:** 29492
- **BUSINESS PHONE:** 843-216-6200

**MAIL ADDRESS:**
- **STREET 1:** 65 FAIRCHILD STREET
- **CITY:** CHARLESTON
- **STATE:** SC
- **ZIP:** 29492

?xml version="1.0" ? blkb-20230309

**UNITED STATES**

**SECURITIES AND EXCHANGE COMMISSION**

Washington, D.C. 20549

**FORM 8-K** 

**CURRENT REPORT** 

Pursuant to Section 13 or 15(d) of the Securities Exchange Act of 1934

Date of Report (Date of earliest event reported): **March 9, 2023**![blkb-20230309_g1.jpg](blkb-20230309_g1.jpg)<br>

**Blackbaud, Inc.** 

(Exact name of registrant as specified in its charter)

---

| | | |
|:---|:---|:---|
| **Delaware** | **000-50600** | **11-2617163** |
| (State or other jurisdiction of incorporation) | (Commission File Number) | (IRS Employer ID Number) |

---

**65 Fairchild Street, Charleston, South Carolina 29492** 

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(Address of principal executive offices) (Zip Code)

Registrant's telephone number, including area code: **(843) 216-6200** 

---

| | |
|:---|:---|
| **Check the appropriate box below if the Form 8-K filing is intended to simultaneously satisfy the filing obligation of the registrant under any of the following provisions:** | **Check the appropriate box below if the Form 8-K filing is intended to simultaneously satisfy the filing obligation of the registrant under any of the following provisions:** |
| **☐** | Written communications pursuant to Rule 425 under the Securities Act (17 CFR 230.425) |
| **☐** | Soliciting material pursuant to Rule 14a-12 under the Exchange Act (17 CFR 240.14a-12) |
| **☐** | Pre-commencement communications pursuant to Rule 14d-2(b) under the Exchange Act (17 CFR 240.14d-2(b)) |
| **☐** | Pre-commencement communications pursuant to Rule 13e-4(c) under the Exchange Act (17 CFR 240.13e-4(c)) |

---

---

| | | |
|:---|:---|:---|
| Securities Registered Pursuant to Section 12(b) of the Act: | Securities Registered Pursuant to Section 12(b) of the Act: | Securities Registered Pursuant to Section 12(b) of the Act: |
| <u>Title of Each Class</u> | <u>Trading Symbol(s)</u> | <u>Name of Each Exchange on which Registered</u> |
| **Common Stock, $0.001 Par Value** | **BLKB** | **Nasdaq Global Select Market** |
| **Preferred Stock Purchase Rights** | **N/A** | **Nasdaq Global Select Market** |

---

Indicate by check mark whether the registrant is an emerging growth company as defined in Rule 405 of the Securities Act of 1933 (§230.405 of this chapter) or Rule 12b-2 of the Securities Exchange Act of 1934 (§240.12b-2 of this chapter).

Emerging growth company ☐

If an emerging growth company, indicate by check mark if the registrant has elected not to use the extended transition period for complying with any new or revised financial accounting standards provided pursuant to Section 13(a) of the Exchange Act. ☐

------

**Item 7.01. Regulation FD Disclosure.** 

Blackbaud, Inc. (the "Company") has reached a settlement with the United States Securities and Exchange Commission (the "SEC") in connection with the Company's previously disclosed 2020 security incident, in which a cybercriminal removed a copy of a subset of data from the Company's self-housed environment (the "Security Incident"). This settlement fully resolves the previously disclosed SEC investigation of the Security Incident and is further described in an SEC cease-and-desist order (the "SEC Order"). Under the terms of the SEC Order, the Company has agreed to cease-and-desist from committing or causing any violations or any future violations of Sections 17(a)(2) and (3) of the Securities Act of 1933, as amended (the "Securities Act"), and Section 13(a) of the Securities Exchange Act of 1934, as amended (the "Exchange Act"), and Rules 12b-20, 13a-13 and 13a-15(a) thereunder. No other violations of the securities laws are alleged in the SEC Order. As part of the SEC Order, the Company has also agreed to pay a civil penalty in the amount of $3,000,000. The Company has consented to the entry of the SEC Order without admitting or denying the findings of the SEC Order, other than with respect to the SEC's jurisdiction over the Company and the subject matter of the SEC Order. The SEC Order describing the settlement is furnished herewith as Exhibit 99.1 and the SEC's press release announcing this resolution is furnished herewith as Exhibit 99.2.

The information in this Form 8-K (including Exhibits 99.1 and 99.2) shall not be deemed "filed" for purposes of Section 18 of the Exchange Act or otherwise subject to the liabilities of that section, nor shall it be deemed incorporated by reference in any filing under the Securities Act or the Exchange Act, except as expressly set forth by specific reference in such a filing.

**Item 9.01. Financial Statements and Exhibits.**

(d) Exhibits

The following exhibits are filed with this current report:

---

| | |
|:---|:---|
| **Exhibit No.** | **Description** |
| <u>[99.1](exhibit991secordermar2023.htm)</u> | SEC Order |
| <u>[99.2](exhibit992secpressreleasem.htm)</u> | SEC press release dated March 9, 2023 |
| 104 | Cover Page Interactive Data File (embedded within the Inline XBRL document). |

---

------

SIGNATURES

Pursuant to the requirements of the Securities Exchange Act of 1934, the registrant has duly caused this report to be signed on its behalf by the undersigned hereunto duly authorized.

---

| | | |
|:---|:---|:---|
| | | **BLACKBAUD, INC.** |
| Date: | March 9, 2023 | /s/ Anthony W. Boor |
| | | Anthony W. Boor |
| | | Executive Vice President and Chief Financial Officer |
| | | (Principal Financial and Accounting Officer) |

---

## Exhibit 99.1

**EXHIBIT 99.1**

**UNITED STATES OF AMERICA**

**Before the**

**SECURITIES AND EXCHANGE COMMISSION**

**SECURITIES ACT OF 1933**

**Release No. 11165 / March 9, 2023**

**SECURITIES EXCHANGE ACT OF 1934**

**Release No. 97098 / March 9, 2023**

**ADMINISTRATIVE PROCEEDING**

**File No. 3-21339**

---

| | |
|:---|:---|
| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>**In the Matter of**<br>**BLACKBAUD, INC.,**<br>**Respondent.** | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**ORDER INSTITUTING CEASE-AND-DESIST PROCEEDINGS PURSUANT TO SECTION 8A OF THE SECURITIES ACT OF 1933 AND SECTION 21C OF THE SECURITIES EXCHANGE ACT OF 1934, MAKING FINDINGS, AND IMPOSING A CEASE-AND-DESIST ORDER** |

---

**&nbsp;&nbsp;&nbsp;&nbsp;**

**I.** <br>

&nbsp;&nbsp;&nbsp;&nbsp;The Securities and Exchange Commission ("Commission") deems it appropriate that cease-and-desist proceedings be, and hereby are, instituted pursuant to Section 8A of the Securities Act of 1933 ("Securities Act") and Section 21C of the Securities Exchange Act of 1934 ("Exchange Act"), against Blackbaud, Inc. ("Blackbaud" or "Respondent").

**II.** <br>

*&nbsp;&nbsp;&nbsp;&nbsp;*In anticipation of the institution of these proceedings, Respondent has submitted an Offer of Settlement (the "Offer") which the Commission has determined to accept. Solely for the purpose of these proceedings and any other proceedings brought by or on behalf of the Commission, or to which the Commission is a party, and without admitting or denying the findings herein, except as to the Commission's jurisdiction over it and the subject matter of these proceedings, which are admitted, Respondent consents to the entry of this Order Instituting Cease-and-Desist Proceedings Pursuant to Section 8A of the Securities Act of 1933 and Section 21C of the Securities Exchange Act of 1934, Making Findings, and Imposing a Cease-and-Desist Order ("Order"), as set forth below.

------

**III.** <br>

&nbsp;&nbsp;&nbsp;&nbsp;On the basis of this Order and Respondent's Offer, the Commission finds that:

**<u>Summary</u>**

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1.&nbsp;&nbsp;&nbsp;&nbsp;This matter concerns materially misleading disclosures by Blackbaud regarding a ransomware attack that resulted in the unauthorized access and exfiltration of sensitive customer information. Blackbaud provides software that non-profit organizations use to manage data about their donors, including identifying information, donation history, and financial information. On May 14, 2020, Blackbaud discovered the attack, and the company's subsequent investigation indicated the attack resulted in the unauthorized access and exfiltration of over a million files concerning over 13,000, or roughly a quarter, of the company's customers.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.&nbsp;&nbsp;&nbsp;&nbsp;On July 16, 2020, Blackbaud announced the incident on the company's website and notified the impacted customers. In the website post and notices, the company indicated that the attacker did not access any donor bank account information or social security numbers. Within days of these statements, however, the company's technology and customer relations personnel learned that these claims with respect to bank account information and social security numbers were erroneous. Nevertheless, on August 4, 2020, the company filed a Form 10-Q that discussed the incident, but omitted this material information about the scope of the attack, and misleadingly characterized the risk of exfiltration of such sensitive donor information as hypothetical. At the end of September 2020, the company disclosed for the first time that the attacker had, in fact, accessed unencrypted donor bank account information and social security numbers for certain of the impacted customers. The company also failed to maintain disclosure controls and procedures as defined in Exchange Act Rule 13a-15(e).

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.&nbsp;&nbsp;&nbsp;&nbsp;Based on the foregoing conduct, and the conduct described herein below, Blackbaud violated Sections 17(a)(2) and (3) of the Securities Act and Section 13(a) of the Exchange Act and Rules 12b-20, 13a-13, and 13a-15(a) thereunder.

**<u>Respondent</u>**

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.&nbsp;&nbsp;&nbsp;&nbsp;<u>Blackbaud, Inc.</u>, a Delaware corporation headquartered in Charleston, South Carolina, provides donor relationship management software to various non-profit organizations, including charities, higher education institutions, K-12 schools, healthcare organizations, religious organizations, and cultural organizations. Blackbaud's common stock is registered pursuant to Section 12(b) of the Exchange Act. Blackbaud's common stock trades on the NASDAQ.

**<u>Facts</u>**

*<u>May 14, 2020 Cybersecurity Incident</u>*

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.&nbsp;&nbsp;&nbsp;&nbsp;On May 14, 2020, Blackbaud's technology personnel detected unauthorized access to the company's systems, and determined the access may have begun as early as February 2020. The personnel found messages from the attacker in the company's system claiming to have

------

exfiltrated data concerning Blackbaud's customers, and subsequently demanding payment. Blackbaud's technology personnel conducted an investigation of the incident in consultation with a third-party cybersecurity firm. In addition, Blackbaud's cybersecurity personnel consulted with a third-party vendor to engage in communications with the attacker, and ultimately coordinate payment of a ransom in exchange for the attacker's promise to delete the exfiltrated data.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6.&nbsp;&nbsp;&nbsp;&nbsp;By July 16, 2020, Blackbaud understood from the information available to it that the attacker exfiltrated at least a million files. The company's technology personnel analyzed the exfiltrated file names to identify which products and customers were impacted. The company did not analyze the content of any of the exfiltrated files, and Blackbaud did not direct any of its third party vendors to do so. Based on the file name review, the company's technology personnel identified over 13,000 impacted customers and multiple impacted products, including various versions of the company's donor relationship software.

*<u>July 16, 2020 Customer Notices and Website Post</u>*

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7.&nbsp;&nbsp;&nbsp;&nbsp;On July 16, 2020, the company announced the incident for the first time on its website. The company also sent notices about the incident to the impacted customers. In both the customer notices and website post, the company stated "[t]he cybercriminal did not access . . . bank account information, or social security numbers."

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;8.&nbsp;&nbsp;&nbsp;&nbsp; By the end of July 2020, company personnel learned that the attacker had, in fact, accessed donor bank account information and social security numbers in an unencrypted form for a number of the impacted customers.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9.&nbsp;&nbsp;&nbsp;&nbsp;During the days following the notices and website post, Blackbaud received over a thousand communications from customers regarding the incident. A number of customers raised concerns that they had uploaded sensitive donor data—including social security numbers and bank account information—to fields that were not otherwise encrypted, or that they had included such information in attachments that were uploaded to Blackbaud's products and not encrypted.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;10.&nbsp;&nbsp;&nbsp;&nbsp;These customer concerns were prevalent enough that by July 21, 2020, five days after the website post and notices, the company's personnel had developed a script for customer service personnel that acknowledged that certain attachments and fields potentially used to store social security numbers and bank account information were, in fact, not encrypted.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;11.&nbsp;&nbsp;&nbsp;&nbsp;As a result of these customer inquiries, Blackbaud's personnel conducted further analysis of the potentially impacted products, and confirmed that certain donor bank account information and social security numbers had been accessed and exfiltrated by the attacker in an unencrypted format, contrary to the claims in the company's July 16, 2020 website post and notices. Although the company's personnel were aware of the unauthorized access and exfiltration of donor bank account numbers and social security numbers by the end of July 2020, the personnel with this information about the broader scope of the impacted data did not communicate this to Blackbaud's senior management responsible for disclosures, and the company did not have policies or procedures in place designed to ensure they do so.

------

*<u>August 4, 2020 Form 10-Q</u>*

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;12.&nbsp;&nbsp;&nbsp;&nbsp;On August 4, 2020, Blackbaud filed its Form 10-Q for the second fiscal quarter of 2020.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;13.&nbsp;&nbsp;&nbsp;&nbsp;In the days preceding the Form 10-Q filing, between July 29, 2020, and July 30, 2020, the company met with analysts and held its quarterly earnings call, during which analysts asked several questions about the cybersecurity incident, including concerning the nature of the data impacted, which the company did not answer.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;14.&nbsp;&nbsp;&nbsp;&nbsp;In Blackbaud's Form 10-Q filed on August 4, 2020, however, the company included a discussion about the scope of the incident, stating only that "the cybercriminal removed a copy of a subset of data." In that discussion, the company made no reference to the attacker removing any sensitive donor data, and in particular made no mention of the exfiltration of donor social security numbers and bank account numbers. This statement omitted the material fact that a number of customers had unencrypted bank account and social security numbers exfiltrated, in contrast to the company's unequivocal, and ultimately erroneous claims in the July 16, 2020 website post and customer notices.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;15.&nbsp;&nbsp;&nbsp;&nbsp;Moreover, in the company's discussion of its cybersecurity risks in the Form 10-Q, the company stated, "A compromise of our data security that results in ***customer or donor personal*** or payment card data being obtained by unauthorized persons ***could*** adversely affect our reputation with our customers and others, as well as our operations, results of operations, financial condition and liquidity and could result in litigation against us or the imposition of penalties." (Emphasis added). This statement omitted the material fact that such customer or donor personal data was exfiltrated by the attacker, which entailed that the risks of such an attack on the company's business were no longer hypothetical.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;16.&nbsp;&nbsp;&nbsp;&nbsp;Blackbaud's omissions of material facts about the scope of the incident and the company's cybersecurity risks in the August 4, 2020 Form 10-Q rendered the statements about the incident misleading because they perpetuated the false impression, started with the company's earlier website post and customer notices, that the incident did not result in the attacker accessing highly sensitive donor data—data at the core of the company's business as a service provider helping institutions manage donor relationships—when in fact the company's personnel learned before August 4, 2020 that such data had been accessed and exfiltrated by the attacker.

*<u>September 29, 2020 Form 8-K</u>*

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;17.&nbsp;&nbsp;&nbsp;&nbsp;On September 29, 2020, Blackbaud furnished a Form 8-K concerning the incident. The company acknowledged for the first time that "the cybercriminal may have accessed some unencrypted fields intended for bank account information, social security numbers, usernames and/or passwords." At or around that time, the company also sent supplemental notices to customers that Blackbaud believed had such sensitive donor information accessed and exfiltrated.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;18.&nbsp;&nbsp;&nbsp;&nbsp;During the relevant period, Blackbaud offered and sold stock to its employees through an Equity and Incentive Compensation Plan for which a Form S-8 was filed with the Commission on June 16, 2016.

------

*<u>Blackbaud's Disclosure Control and Procedures Failures</u>*

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;19.&nbsp;&nbsp;&nbsp;&nbsp;Exchange Act Rule 13a-15(a) requires issuers such as Blackbaud to "maintain disclosure controls and procedures (as defined in paragraph (e) of this section)." Paragraph (e) defines disclosure controls and procedures to include, among other things, "controls and other procedures of an issuer that are designed to ensure that information required to be disclosed by the issuer in the reports that it files or submits under the [Exchange] Act . . . is recorded, processed, summarized and reported, within the time periods specified in the Commission's rules and forms." Under the rule, "[d]isclosure controls and procedures include, without limitation, controls and procedures designed to ensure that information required to be disclosed by an issuer in the reports that it files or submits under the [Exchange] Act is accumulated and communicated to the issuer's management . . . as appropriate to allow timely decisions regarding required disclosure."

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;20.&nbsp;&nbsp;&nbsp;&nbsp;Blackbaud's primary business includes providing software that allows its customers to manage data, including sensitive financial and personal data, concerning their donors. Nevertheless, during the relevant time frame, Blackbaud did not have disclosure controls and procedures related to the disclosure of cybersecurity risks or incidents, including incidents involving the exposure of sensitive donor information.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;21.&nbsp;&nbsp;&nbsp;&nbsp;As described above, certain of the company's technical and customer response personnel learned shortly after the July 16, 2020 customer notices and website post that, contrary to the representations therein, the attacker accessed and exfiltrated sensitive donor information including banking information and social security numbers that certain customers had included in unencrypted attachments and fields.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;22.&nbsp;&nbsp;&nbsp;&nbsp;Nevertheless, the company's senior management responsible for the company's disclosures were not made aware of these facts prior to the company filing its Form 10-Q on August 4, 2020, or indeed until several weeks later, nor were there controls or procedures designed to ensure that such information was communicated to senior management. The company did not have controls or procedures designed to ensure that information relevant to cybersecurity incidents and risks were communicated to the company's senior management and other disclosure personnel. As a result, relevant information related to the incident was never assessed from a disclosure perspective.

**<u>Violations</u>**

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;23.&nbsp;&nbsp;&nbsp;&nbsp;As a result of the conduct described above, Blackbaud violated Sections 17(a)(2) and (3) of the Securities Act, which prohibit any person from directly or indirectly obtaining money or property by means of any untrue statement of a material fact or any omission to state a material fact necessary in order to make the statements made, in light of the circumstances under which they were made, not misleading, or engaging in any transaction, practice, or course of business which operates or would operate as a fraud or deceit upon the purchaser, in the offer or sale of securities. A violation of these provisions does not require scienter and may rest on a finding of negligence. *See Aaron v. SEC*, 446 U.S. 680, 701-02 (1980).

------

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;24.&nbsp;&nbsp;&nbsp;&nbsp;In addition, Blackbaud violated Section 13(a) of the Exchange Act and Rule 13a-13 thereunder, which require issuers of a security registered pursuant to Section 12 of the Exchange Act to file with the Commission quarterly reports in conformity with the Commission's rules and regulations. Blackbaud also violated Rule 12b-20 of the Exchange Act, which, among other things, requires such issuers to include in quarterly reports filed with the Commission any material information necessary to make the required statements in the filing not misleading.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;25.&nbsp;&nbsp;&nbsp;&nbsp;In addition, Blackbaud violated Exchange Act Rule 13a-15(a), which requires most issuers such as Blackbaud with a security registered pursuant to Section 12 of the Exchange Act to maintain disclosure controls and procedures designed to ensure that information required to be disclosed by an issuer in reports it files or submits under the Exchange Act is recorded, processed, summarized, and reported within the time periods specified in the Commission's rules and forms.

**IV.** <br>

**&nbsp;&nbsp;&nbsp;&nbsp;**In view of the foregoing, the Commission deems it appropriate and in the public interest to impose the sanctions agreed to in Respondent Blackbaud's Offer.

**&nbsp;&nbsp;&nbsp;&nbsp;**Accordingly, it is hereby ORDERED that**:**

&nbsp;&nbsp;&nbsp;&nbsp;A.&nbsp;&nbsp;&nbsp;&nbsp;Pursuant to Section 8A of the Securities Act and Section 21C of the Exchange Act, Respondent cease and desist from committing or causing any violations and any future violations of Sections 17(a)(2) and (3) of the Securities Act and Section 13(a) of the Exchange Act and Rules 12b-20, 13a-13, and 13a-15 thereunder.

&nbsp;&nbsp;&nbsp;&nbsp;B.&nbsp;&nbsp;&nbsp;&nbsp;Respondent shall, within 14 days of the entry of this Order, pay a civil money penalty in the amount of $3,000,000 to the Securities and Exchange Commission for transfer to the general fund of the United States Treasury, subject to Exchange Act Section 21F(g)(3). If timely payment is not made, additional interest shall accrue pursuant to 31 U.S.C. § 3717.

Payment must be made in one of the following ways:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(1)&nbsp;&nbsp;&nbsp;&nbsp;Respondent may transmit payment electronically to the Commission, which will provide detailed ACH transfer/Fedwire instructions upon request;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(2)&nbsp;&nbsp;&nbsp;&nbsp;Respondent may make direct payment from a bank account via Pay.gov through the SEC website at <u>http://www.sec.gov/about/offices/ofm.htm</u>; or

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(3)&nbsp;&nbsp;&nbsp;&nbsp;Respondent may pay by certified check, bank cashier's check, or United States postal money order, made payable to the Securities and Exchange Commission and hand-delivered or mailed to:

Enterprise Services Center

Accounts Receivable Branch

HQ Bldg., Room 181, AMZ-341

6500 South MacArthur Boulevard

------

Oklahoma City, OK 73169

Payments by check or money order must be accompanied by a cover letter identifying Blackbaud as a Respondent in these proceedings, and the file number of these proceedings; a copy of the cover letter and check or money order must be sent to David Hirsch, Division of Enforcement, Securities and Exchange Commission, 100 F Street, N.E., Washington, District of Columbia 20549.

&nbsp;&nbsp;&nbsp;&nbsp;C.&nbsp;&nbsp;&nbsp;&nbsp;Amounts ordered to be paid as civil money penalties pursuant to this Order shall be treated as penalties paid to the government for all purposes, including all tax purposes. To preserve the deterrent effect of the civil penalty, Respondent agrees that in any Related Investor Action, it shall not argue that it is entitled to, nor shall it benefit by, offset or reduction of any award of compensatory damages by the amount of any part of Respondent's payment of a civil penalty in this action ("Penalty Offset"). If the court in any Related Investor Action grants such a Penalty Offset, Respondent agrees that it shall, within 30 days after entry of a final order granting the Penalty Offset, notify the Commission's counsel in this action and pay the amount of the Penalty Offset to the Securities and Exchange Commission. Such a payment shall not be deemed an additional civil penalty and shall not be deemed to change the amount of the civil penalty imposed in this proceeding. For purposes of this paragraph, a "Related Investor Action" means a private damages action brought against Respondent by or on behalf of one or more investors based on substantially the same facts as alleged in the Order instituted by the Commission in this proceeding.

&nbsp;&nbsp;&nbsp;&nbsp;By the Commission.

Vanessa A. Countryman

Secretary

## Exhibit 99.2

**EXHIBIT 99.2**

![image.jpg](image.jpg)

<br>