Why Collection Emails Go to Spam: A Deliverability Checklist for AR Teams

Collection emails go to spam for five common reasons: the sending domain is not authenticated with SPF, DKIM and DMARC; the From address does not match the system that actually sends the message; the email looks like invoice fraud; the sending pattern looks like a bulk blast; or the list is full of stale addresses that bounce. A reminder that lands in spam is a reminder that was never sent. Your aging report still shows it as "contacted," your collector still waits for a reply, and the invoice keeps getting older.

The bar has also moved. Since February 2024, Google has required every sender to authenticate with SPF or DKIM and keep its spam rate in Postmaster Tools below 0.3%, with stricter rules for anyone sending about 5,000 or more messages a day to personal Gmail accounts, according to Google's email sender guidelines. Yahoo publishes matching rules, and Microsoft began rejecting non-compliant high-volume mail to Outlook.com, Hotmail and Live addresses in May 2025. Your customers' AP teams sit behind filters that read the same signals.

This guide is for the controller or AR manager running a collections team of three to five people that sends hundreds of reminders a month from an ERP, a billing tool and a few personal mailboxes. It covers why reminders get filtered, what the big inbox providers now expect, a ten-point checklist you can run with IT in an afternoon, and what to do when a customer says the invoice never arrived.

Why Do Collection Emails Land in Spam?

Spam filters do not read your email the way your customer does. They score it on who sent it, whether that sender can prove it, how the message is built and how recipients have reacted to similar mail before. Collection email has a few habits that score badly on every one of those.

Your domain is not authenticated

Three DNS records tell receiving servers that a message really came from you:

• SPF lists the servers and services allowed to send mail for your domain.

• DKIM adds a cryptographic signature to each message so the receiver can check it was not altered and came from a domain you control.

• DMARC tells receivers what to do when a message fails those checks, and sends you reports on who is sending as your domain.

Most companies set these up for their main mailbox provider years ago. The gap is everything added since: the ERP that emails statements, the billing platform that sends invoices, the AR tool that sends reminders. If one of those sends as yourcompany.com and is not covered by SPF or DKIM, its mail fails authentication even though the address looks right.

The From address does not match the system that sends

A common setup is an ERP sending invoices "from" ar@yourcompany.com while the message actually leaves through the ERP vendor's servers. Google's guidelines ask high-volume senders to make the From domain align with the SPF or DKIM domain. When it does not, the message looks exactly like what spoofing looks like: one domain in the From line, someone else's servers underneath.

The message looks like invoice fraud

AP teams are trained to distrust unexpected payment emails, and their filters are tuned the same way. Fake invoices and "updated bank details" requests are a standard fraud pattern, so a real reminder that shares their features gets extra scrutiny. The features that hurt most:

• Attachments other than a plain PDF, especially zipped files or documents with macros.

• Shortened or tracking-heavy links that hide where the click goes.

• Urgent, all-caps subject lines such as "FINAL NOTICE: PAYMENT REQUIRED."

• A new sender the recipient has never replied to, writing about money.

• Any mention of changed payment instructions. If your remittance details really changed, say so by phone as well.

The sending pattern looks like a bulk blast

Many teams send most of their reminders in one burst: statements on the first business day, a reminder batch the morning after month end. Filters notice sudden spikes in volume from a sender, especially from a mailbox or domain that is usually quiet. A collector who pastes the same message to 200 customers from a personal mailbox in ten minutes looks a lot like a compromised account.

Bad addresses and bounces

Billing contacts go stale. People change roles, AP moves to a shared inbox, a customer is acquired and its domain is retired. Every reminder sent to a dead address bounces, and a high bounce rate tells providers you do not maintain your list. It also hides a bigger problem: an account that "has been emailed six times" may have been emailed zero times by a human who could pay.

What Do Gmail, Yahoo and Outlook Require From Senders?

These are the published sender policies of the three largest consumer inbox providers. They are written for consumer mailboxes, but they set the baseline every serious filter now expects, and many of your smaller customers do use personal Gmail or Outlook addresses for billing.

Requirements for every sender

Google's guidelines apply to anyone sending to Gmail, at any volume:

• SPF or DKIM on the sending domain.

• Valid forward and reverse DNS for sending servers.

• TLS for the connection.

• A spam rate below 0.3% in Postmaster Tools. Google recommends staying below 0.10%.

• Messages formatted to the email standard (RFC 5322), with no impersonation of Gmail addresses.

Google also advises using the same From address for messages of the same type. Receipts, promotions and alerts each get their own address. For AR, that means one consistent collections address, not five collectors' personal mailboxes plus a no-reply.

Yahoo's sender best practices set the same floor: authenticate with SPF or DKIM, keep complaints low and keep DNS records valid.

Extra requirements for high-volume senders

Senders who reach roughly 5,000 messages a day to personal Gmail accounts must also:

• Set up both SPF and DKIM.

• Publish a DMARC record. A policy of "none" is accepted.

• Align the From domain with the SPF or DKIM domain.

• Offer one-click unsubscribe on marketing and subscribed messages.

Two details in Google's sender guidelines FAQ matter for a finance team. First, all mail from the same primary domain counts toward the 5,000, so your marketing newsletter, product notifications and AR reminders are added together. Second, once a domain crosses that line it is permanently treated as a bulk sender. A collections team that never sends 5,000 messages can still inherit bulk-sender rules from the rest of the company. The FAQ also says one-click unsubscribe is required only for marketing and promotional messages, so a payment reminder does not need one.

Google says enforcement has been stepping up since November 2025, and mail that does not meet the requirements may be rejected outright rather than delivered to spam. Yahoo asks bulk senders for the same SPF, DKIM, DMARC and alignment setup and a complaint rate below 0.3%. For Outlook.com, Hotmail and Live addresses, Microsoft has applied similar requirements to senders of 5,000 or more emails a day since May 5, 2025, and rejects non-compliant messages instead of filtering them to junk.

What this means for B2B collections

Many of your larger customers receive mail on Google Workspace or Microsoft 365 business accounts, which run their own filtering on top of the same authentication signals. You do not need to memorize any provider's thresholds. You need every system that sends as your domain to pass SPF, DKIM and DMARC, and you need a sending pattern and content style that does not look like fraud.

The 10-Point Deliverability Checklist for AR Teams

Run this once with whoever manages your DNS and email, then repeat the monitoring items monthly. Most of it takes an afternoon.

Start with the inventory

Check 1 is the one teams skip, and it causes most failures. Ask each collector what they send and from where. You will usually find at least one surprise: a statement run from an old accounting add-on, a billing tool set up by a former controller, or a collector forwarding reminders from a personal account. Each one either gets authenticated or gets retired.

Move DMARC from "none" to enforcement slowly

A DMARC policy of "none" only reports. Once the reports show every legitimate system passing, IT can move to "quarantine" and later "reject," which tells receivers to filter mail that pretends to be you. Moving too early blocks your own tools, so wait until a full month of reports is clean.

Write reminders that look like what they are

The best deliverability fix in your templates is also the best collections fix: say exactly what is owed. A subject line like "Invoice 10482 from [Your Company]: $4,180 due Oct 30" gets opened, passes filters and is easy for AP to match. Our guide to a past-due invoice email sequence covers what each message should say, and our follow-up cadence guide covers when to send it.

How Do You Know If Your Reminders Are Being Filtered?

Filtering is silent. Nobody tells you a message went to spam, so you have to look for the signs.

Signs in your own data

• Replies have dropped on accounts that used to answer.

• "We never got it" keeps coming up, especially from customers on the same email provider.

• Promises arrive only after a phone call, never after an email.

• Bounce or rejection notices mention authentication, policy or reputation.

If several of these show up together, treat the email channel as broken until you prove otherwise. Our piece on ghosted invoices covers what silence usually means; filtering is one of the causes most teams never check.

A 15-minute placement test

Create a free Gmail address and a free Outlook.com address. Send yourself one real reminder from each system that emails customers. Check whether each lands in the inbox, the promotions tab or spam, and open the message headers to confirm SPF, DKIM and DMARC all pass. Repeat after any change to a sending tool. It is a rough test, but it catches the most common failures in minutes.

Watch the numbers providers watch

Google Postmaster Tools shows your domain's spam rate and authentication results for mail sent to Gmail users. Low volume can leave gaps in the data, but if your domain sends enough to register, it is the closest view you get of how Gmail sees you.

What Should You Do When a Customer Says They Never Got the Invoice?

Treat it as a fact to check, not an excuse to argue. It is one of the most common reasons in our list of late payment excuses, and sometimes it is true.

A five-step response

1. Confirm the address the invoice went to, and ask who should receive it now.

2. Resend from your standard AR address with the invoice number and amount in the subject line.

3. Ask AP to add your AR address to their safe senders so future invoices arrive.

4. Offer a second route, such as your customer portal or a copy sent to a second named contact.

5. Call to confirm receipt and get a payment date while you have them.

Fix the record, not just the invoice

If the address was wrong, update it in the ERP before the next statement run. If the address was right but the mail was filtered, take the case to IT with the message headers. One customer's complaint is often the first visible sign of a problem that affects every customer on the same provider.

Should Your Collections Process Rely on Email Alone?

No. Email is cheap and easy to send at volume, which is exactly why filters are strict with it. Even with perfect authentication, some reminders will be filtered, some will be skimmed and some will sit in a shared AP inbox nobody owns. A process that only emails cannot tell the difference between "they ignored it" and "they never saw it."

Add channels that confirm contact

A phone call or a text tells you within minutes whether you reached a person. Our comparison of dunning emails and AI calls looks at how the channels differ, and can AI call customers to collect overdue invoices covers how voice works in practice. If you are comparing tools, our guide to overdue invoice follow-up software lists what to look for. As we argue in your AR problem is a follow-up problem, coverage of every account every week matters more than the perfect template.

Where Kate fits

Kate, Abivo's AI collections agent, works from your ERP data and contacts customers by call, text and email on a cadence you set per account or segment. One message covers all of an account's open invoices, with the PO, job or billing period named, so AP can match it quickly. Kate logs promises to pay, lets you pause a single invoice, and hands disputes and sensitive conversations to a named owner on your team. When an email goes unanswered, a call or text follows, so silence becomes a signal to act on instead of a gap in the record.

OFS Group went from four collectors to one, recovered $842,518 in four months and cut DSO by more than 30 days with Kate. You can read the OFS case study, compare options in our guide to the best collections software for AR teams, or see where follow-up fits in what to automate first in AR.

Related guides for AR teams: how to resolve invoice disputes, how to track promises to pay and how to keep the right AP contact on every account.

Frequently Asked Questions

Why do my invoice emails go to spam?

The most common causes are a sending system that is not covered by your SPF or DKIM records, a From address that does not match the system sending the mail, attachments or links that look like invoice fraud, sudden bursts of volume, and stale addresses that bounce. Test a real reminder from each system to a Gmail and an Outlook address and check the headers for SPF, DKIM and DMARC results.

Do payment reminders need an unsubscribe link?

Google's sender FAQ says one-click unsubscribe is required only for marketing and promotional messages, not transactional ones. A reminder about an invoice the customer owes is a transactional message. Keep reminders free of promotional content so they stay in that category.

Do the Gmail bulk sender rules apply to a small AR team?

They can. Google counts all mail from the same primary domain toward the roughly 5,000 messages a day threshold, and once a domain crosses it, it is treated as a bulk sender permanently. If your marketing team sends large campaigns from your main domain, your AR reminders may already fall under the stricter rules.

Should collectors send reminders from their personal mailbox?

Use one consistent AR address for scheduled reminders and statements, and let collectors reply personally once a conversation starts. A shared address builds a steady sender reputation, is easy for customers to allowlist and keeps the history in one place when a collector is out.

How often should we check email deliverability?

Run the full checklist once, again whenever you add or change a system that emails customers, and check bounces, DMARC reports and Postmaster Tools monthly. Treat a cluster of "we never got it" replies as a trigger to test immediately.

Practical Takeaways

• A reminder in spam was never sent. Check delivery before you judge a customer's silence.

• Inventory every system that emails customers and make sure each one passes SPF, DKIM and DMARC for your domain.

• Send from one consistent AR address with plain subject lines that name the invoice and amount.

• Use PDF attachments or one link on your own domain, and avoid zips, macros and short links.

• Fix bounces within the week and update the contact in your ERP, not just on the invoice.

• Remember that marketing volume counts against your domain. AR may inherit bulk-sender rules.

• Do not rely on email alone. Add calls and texts so you know when you have reached a person, and escalate the accounts that still do not respond with our guide on when to escalate an invoice.

Want every account contacted every week, by call, text and email, without adding collectors? Get started with Abivo.