An invoice that lands in a client's spam folder doesn't just get paid late. It can go unpaid entirely while both sides assume the other dropped the ball. For a small service business, that becomes a cash-flow problem.
One possible cause is failed email authentication: receiving servers cannot confirm that a sending system is authorized to use your domain. That is what SPF, DKIM, and DMARC are for. This guide covers what each one does, what Gmail and Yahoo expect from senders, and how to roll authentication out across every tool that sends email for you while checking that legitimate messages still authenticate.
The Real Problem: Too Many Tools Sending as You
Consider the different places a small business may send email from. Invoices come from accounting software. Appointment reminders come from a booking tool. Newsletters come from a marketing platform. Website forms send notifications. Your team replies from their own mailboxes. Each of these systems may send mail that says it is from your domain.
Receiving servers have to decide whether to trust each of those messages. If one tool hasn't been set up to authenticate as your domain, its messages can look the same as a spoofed email from a stranger. An invoicing tool configured separately from your business mailbox is one place to investigate.
What SPF, DKIM, and DMARC Actually Do
- SPF (Sender Policy Framework) is a DNS record listing the servers allowed to send mail for a domain. It is checked against the envelope sender, also called the return-path domain. This is a technical address that is often different from the "From" address your client sees.
- DKIM (DomainKeys Identified Mail) adds a cryptographic signature tied to a domain. Receiving servers use it to verify the signing domain and the integrity of the signed message content.
- DMARC (Domain-based Message Authentication, Reporting & Conformance) connects those checks to the visible From address. A message passes DMARC when SPF or DKIM passes and the domain that passed aligns with the From domain. You don't need both to pass for DMARC to pass. Your DMARC policy then tells receivers what to do with mail that fails, and it can send you reports.
A passing authentication result alone does not establish alignment. Your invoicing tool might pass SPF using its own domain. If that domain is not aligned with yours, SPF alone will not satisfy DMARC. An aligned, passing DKIM signature can still make the message pass. Relaxed alignment permits domains sharing the same organizational domain; strict alignment requires an exact match. Google explains this alignment requirement in its email sender guidelines.
What Gmail and Yahoo Expect From Senders
The Gmail rules people talk about apply to mail sent to personal Gmail accounts. They are not about whether you use Gmail yourself. According to Google's sender guidelines:
- All senders to personal Gmail accounts must set up SPF or DKIM for their sending domain.
- Bulk senders, meaning those sending roughly 5,000 or more messages a day to personal Gmail accounts, need both SPF and DKIM plus a DMARC record. A DMARC policy of
p=noneis acceptable, and the From domain must align with SPF or DKIM.
Yahoo publishes similar baseline and bulk-sender expectations in its sender best practices. Even below bulk volume, configuring all three is a sensible target: Google recommends SPF, DKIM, and DMARC, and Yahoo strongly recommends DMARC for all senders.
Both providers also recommend keeping different types of email separate. Google advises against mixing promotional content into transactional messages such as receipts, and Yahoo recommends separating email types. In practice, keep promotional content out of your invoices.
On unsubscribe links: one-click unsubscribe is part of the bulk-sender expectations for marketing and subscribed messages. It is not a blanket requirement to put an unsubscribe link on every invoice. Transactional messages are a different category.
One expectation to set clearly: authentication improves how much receivers trust your mail, but it does not guarantee inbox delivery. Google states this directly in its guidelines. Content, sending patterns, and recipient engagement still matter.
A Safe Rollout Workflow
Copying a generic DNS record and publishing a strict DMARC policy before testing can block legitimate booking confirmations or invoices. Here is a safer order of operations.
Step 1: Inventory every tool that sends as your domain
Before touching DNS, list every system that sends email using your business domain in the From address. Give each one an owner, someone responsible for its settings, and a record of what you tested.
| Sending tool | What it sends | Owner | SPF / DKIM set up? | Test result (header check) |
|---|---|---|---|---|
| Business mailbox | Day-to-day replies, quotes | |||
| Invoicing / accounting software | Invoices, payment reminders, receipts | |||
| CRM | Follow-ups, sequences | |||
| Booking / scheduling tool | Confirmations, reminders | |||
| Marketing platform | Newsletters, promotions | |||
| Website forms | Form notifications, auto-replies |
Use the blank columns as a working checklist: record the owner, setup status, test date, and header results for each tool you actually use.
Step 2: Configure SPF and DKIM per tool, using each vendor's instructions
Check each sending platform's current documentation for its supported authentication setup. Follow the vendor's current instructions rather than a generic recipe. Two SPF constraints catch people out, both documented in Google's SPF overview:
- One SPF record per domain. Adding a second SPF record for a new tool breaks SPF. New senders get merged into the existing record.
- A limit of 10 DNS lookups. Include mechanisms and their nested references can consume this allowance. Have your provider check the complete lookup chain rather than counting only the visible include statements.
Where a tool supports DKIM signing with your own domain, use it. Then check that its signing domain aligns with your visible From domain.
Step 3: Test every tool and check the headers
Send a real message from each tool to a test inbox and open the full original message or header view in your mail client. Look for SPF, DKIM, and DMARC results, and confirm the passing domain aligns with your From address. Write the result into your inventory. A setup screen that says "verified" isn't the same as a passing header.
Step 4: Publish DMARC at p=none and watch
Google recommends setting up SPF and DKIM first, waiting about 48 hours, and then adding DMARC with a none policy, as described in its DMARC setup guide. At p=none, you request no quarantine or rejection based on your DMARC policy. Receivers can still filter or reject mail under their own rules. Configure an authorized aggregate-report destination with the rua tag and review reports from participating receivers to find missed senders; publishing p=none alone does not set up reporting.
Step 5: Tighten only after every legitimate source passes
Once reports show your real sending tools passing consistently, move gradually toward quarantine and then reject, following the same Google guidance. Moving to a strict policy before you have verified every sender is how real invoices end up blocked.
Sent, Delivered, Inboxed, Opened: Know What You're Measuring
When a client says they never got the invoice, "but the system says it was sent" doesn't settle anything. There are different stages, and each one tells you something different:
- Sent or accepted by your sending provider: the message entered the sending system. Check that vendor's status definitions; this alone does not show that the recipient's server accepted it.
- Accepted by the receiving server: a delivery event may confirm this handoff. It does not establish inbox placement.
- Inbox placement: whether it landed in the inbox, spam, or a filtered tab. Sending tools usually can't see this.
- Tracked open: a signal from the tracking mechanism, not proof of human reading or payment action. Treat it as an imperfect indicator.
Build payment follow-up around this. If an invoice shows as delivered but stays unpaid, follow up through a second channel, such as a phone call or a message from a team member's mailbox. Don't just resend the same email to the same spam folder.
What Authentication Won't Protect You From
DMARC at an enforcing policy makes it much harder for someone to send mail using your exact domain in the From address. That matters for invoice fraud. But it has limits:
- Display-name spoofing: a stranger's address with your business name as the display name.
- Lookalike domains: a domain one character off from yours.
- Account takeover: if someone gets into a real mailbox on your domain, messages sent through that account can still pass authentication.
Tell clients how you handle payment-detail changes, and confirm any request to change bank details through a separate channel. Authentication is one layer of protection. These domain-level limits are explained in the DMARC specification.
Frequently Asked Questions
How do I know if my invoices are landing in spam?
Send test invoices from your actual invoicing tool to a few test inboxes at different providers, check where they land, and inspect the headers for SPF, DKIM, and DMARC results. Then ask a few regular clients whether recent invoices arrived in their inbox.
Do the Gmail rules apply to me if I don't use Gmail?
Yes, if your clients use personal Gmail addresses. The requirements are about mail sent to Gmail recipients, regardless of which provider you send from.
Can I set this up myself?
Often, yes. Most sending tools document their SPF and DKIM steps. The harder part is coordination: making sure every tool is accounted for, that SPF stays within one record and 10 lookups, and that DMARC isn't tightened too early.
If everything passes, will my invoices always reach the inbox?
No. Authentication improves trust, but providers still weigh content, sending patterns, and recipient behavior. Keep invoices clean, transactional, and free of promotional material.
Do invoices need an unsubscribe link?
One-click unsubscribe is expected for marketing and subscribed messages from bulk senders. It is not a blanket requirement for transactional emails like invoices.
The Takeaway
An unauthenticated or misaligned sending tool is one possible reason invoices land in spam. Check it before assuming the message wording is the problem. Fixing that is less about one DNS change and more about knowing every tool that sends as you, testing each one, and tightening policy only once everything legitimate passes.
If your invoices, reminders, and follow-ups run through several connected systems, mapping that workflow end to end is a good place to start. That kind of workflow audit and system integration is what our business automation work focuses on.
Illustrative Context

