CPA newsletter deliverability checklist

Most deliverability guides treat all senders the same: configure SPF, publish DMARC, watch your spam rate. That advice is correct and incomplete. A CPA firm sending a January 28 newsletter on the day IRS e-file opens has three deliverability problems no SaaS company has: a content vocabulary that overlaps with phishing kits, a calendar that compresses 60% of annual sends into 12 weeks, and a regulator (the FTC) that, since June 2023, treats tax preparers under the same Safeguards Rule that governs banks.

The general 2024–2025 sender rules are covered in the newsletter deliverability hub: SPF, DKIM, DMARC alignment, RFC 8058 one-click unsubscribe, the 5,000-message daily threshold, and the 0.10% spam-rate ceiling. This page is the industry-applied version — what an accounting firm has to add on top, where the timing changes, and which compliance obligations cross into the deliverability layer.

How does tax-season volume change the 5,000-per-day threshold?

Short answer: A weekly Q1 cadence to 1,800 clients hits 5,000/day inside Gmail’s personal-account counting if 60% of the list is on Gmail and a single send fans out across multiple subdomains. Once tripped — even once — the firm is permanently a bulk sender per Google’s FAQ.

The Google Workspace Admin Help FAQ defines a bulk sender as one that “sends close to 5,000 messages or more to personal Gmail accounts within a 24-hour period” and adds: “Senders who meet the above criteria at least once are permanently considered bulk senders.” The number sounds high until you map it to a CPA firm’s actual Q1 calendar. A firm with 1,800 client households, weekly cadence from January 28 through April 15, 60% Gmail penetration on the individual-filer list, and an additional 1,200 transactional sends per week (engagement letters, e-file confirmations, K-1 ready notifications) clears 5,000 messages in a single day during the March 10 entity-deadline week.

Two facts compound the problem. First, the threshold is per primary domain, not per subdomain — a firm sending newsletters from news.firm.com and tax notifications from notify.firm.com still has both volumes counted against firm.com. Second, “permanently bulk” means the post-April lull does not reset the classification. A firm tripping the threshold once in March is held to bulk-sender authentication for the rest of the year, including the quiet May–July window. The corollary: build for bulk-sender compliance year-round, not just during Q1.

Will IRS-coded language land my newsletter in spam?

Short answer: “IRS,” “refund,” and “audit” in the body of an authenticated newsletter from an engaged sender land in the inbox. The deliverability cost is in subject lines that mirror phishing patterns — ALL CAPS, dollar amounts, urgent verbs, sender names containing “IRS” or “Treasury.”

The IRS Dirty Dozen phishing list documents the exact language patterns spammers use to impersonate the IRS. Gmail and Microsoft train their Bayesian filters on the same dataset. The result: subject lines like “URGENT: Action Required on Your IRS Refund” trigger the same pattern recognition, regardless of who sent them. The fix is not avoiding tax vocabulary — it is writing subject lines that read like a CPA, not like a scam: “What the OBBBA passthrough rules mean for your S-corp,” not “IMPORTANT: $14,500 in OBBBA savings.”

Sibling page on accounting newsletter subject lines covers the open-rate side; this page covers the spam-folder side. The two share roughly 70% of their guidance — an authenticated sender writing professional subject lines clears both filters at once.

How does Circular 230 retention interact with newsletter archival?

Short answer: A general-audience newsletter is not Treasury Circular 230 §10.31 “written advice.” The retention obligation attaches the moment a newsletter contains client-specific guidance — tying a recommendation to a named client’s entity election, AGI band, or filing status.

Treasury Department Circular 230 §10.37 governs written advice on Federal tax matters. Generic guidance — “the OBBBA permanently extends the §199A deduction at 23%” sent to a 1,500-client list — is not §10.37 advice. A segmented send that recommends to specific clients that they take a specific action by a specific date crosses into individualized advice. The deliverability question that follows: where is the archive of record?

ESP archives (Mailchimp, Beehiiv, ConvertKit) are not designed for tax-record retention. The right answer for accounting firms: keep general-audience content in the ESP and route any client-specific written advice through the firm’s engagement-letter process and secure portal, where the §6107 four-year preparer record-retention obligation already governs storage. Cross-contaminating the two creates a deliverability problem (ESP archives become evidence) and a compliance problem (the firm cannot enforce §10.37 contemporaneous documentation through a marketing-list provider).

What does the FTC Safeguards Rule add for tax preparers?

Short answer: The June 2023 amendments to 16 CFR 314 (the Safeguards Rule) apply to tax preparers as “financial institutions.” A newsletter that contains personally identifiable tax information must be encrypted in transit. A general-audience newsletter is unaffected; a client-specific tax preview is.

The FTC’s 2023 Safeguards Rule update added a breach-notification requirement (notice to the FTC within 30 days for unauthorized acquisition of unencrypted customer information affecting 500+ consumers) and explicitly listed tax preparation services in the covered category. For deliverability purposes the implication is narrow but binding: client-segmented tax content carries an encryption-in-transit obligation that opportunistic TLS may not satisfy. Practical separation — general newsletters in the ESP, anything client-specific in the secure portal — resolves both the encryption requirement and the §10.37 archive question with the same architectural decision.