Why are my invoices ending up in clients’ spam folders?

Usually because the email is being sent from an address that doesn’t match the domain it claims to come from — e.g. an invoicing app sends “from” yourname@gmail.com but the actual sending server has no authentication for gmail.com. Modern spam filters (Gmail, Outlook, Apple Mail) flag this aggressively as a likely phishing attempt.

Can I send invoices from my Gmail address and still avoid spam?

Sending directly from Gmail is reliable because Gmail authenticates its own outgoing mail. The problem starts when an invoicing tool tries to send “as you” via gmail.com from its own servers — that fails authentication. Either send manually from Gmail (slow) or use a tool that sends from its own authenticated domain.

What trigger words cause invoice emails to be flagged?

Words like “FREE!”, “URGENT”, all-caps subject lines, multiple exclamation marks, and excessive emojis raise spam scores. Modern filters are content-aware though — a plain, polite invoice email rarely fails on content alone. Authentication and sender reputation are the dominant signals.

Why Are My Invoice Emails Going to Spam? (And How to Fix It)

Q: What are SPF, DKIM, and DMARC?

They’re DNS records on your domain that tell email providers “these servers are authorised to send mail as me.” SPF lists allowed sending IPs. DKIM cryptographically signs outgoing mail. DMARC tells receivers what to do when SPF or DKIM fails. Without them, you’re effectively anonymous — which spam filters treat as suspicious.

Q: How do I send invoices from my own domain?

You add a few DNS records (SPF, DKIM, DMARC) pointing to the sending infrastructure of your invoicing tool. Free Invoice App Pro+ walks you through this once at setup — from then on, your invoices arrive from invoices@yourbusiness.com.au with full authentication and dramatically higher inbox placement.

Quick answer

Invoice emails go to spam mostly because of missing email authentication— the sending server isn’t cryptographically tied to the “from” address. Sending an invoice that claims to be from yourname@gmail.com via a third-party invoicing tool fails this check, and modern spam filters treat that as a likely phishing attempt. The fix is to send from a domain you control (e.g. invoices@yourbusiness.com.au), with SPF, DKIM, and DMARC properly configured. Free Invoice App Pro+ sets this up for you.

Why this matters more than ever

In the last few years, Gmail, Outlook, and Apple Mail have all tightened their rules significantly. Gmail’s 2024 changes require any sender hitting their inbox at scale to be authenticated, period. The flow-on effect: a freelancer who sends one invoice a week isn’t the target of those rules, but their unauthenticated emails get caught in the same nets. Clients miss invoices, payments are delayed, and you blame yourself for not following up.

The three biggest reasons invoices land in spam

1. Mismatched “from” and sending domain

This is the dominant reason and the trickiest to diagnose without technical context. Here’s what happens:

You sign up for an invoicing tool with your email yourname@gmail.com.
The tool sends invoices “from” yourname@gmail.com.
But the actual server doing the sending is the invoicing tool’s server, not Google’s.
Gmail’s SPF/DKIM checks run against gmail.com’s authorised servers. The invoicing tool isn’t on that list.
Result: the email fails authentication and lands in spam, or gets blocked entirely.

Many invoicing tools work around this by sending from their own domain (e.g. notifications@invoicingtool.com) on your behalf, with a “Reply-To” set to yours. Better than failing auth, but your clients see an unfamiliar “from” address — and may delete the email as suspicious anyway.

2. No SPF, DKIM, or DMARC on your sending domain

If you have your own business domain (e.g. yourbusiness.com.au) but haven’t set up authentication on it, your emails are technically anonymous. Receiving servers can’t verify the email actually came from you, so they default to suspicion.

In plain English:

SPF (Sender Policy Framework): a DNS record listing which servers are allowed to send email as you. Without it, anyone can spoof your domain.
DKIM (DomainKeys Identified Mail): a cryptographic signature attached to every outgoing email. Receiving servers verify the signature against your DNS record. This proves the email wasn’t tampered with.
DMARC (Domain-based Message Authentication, Reporting and Conformance):tells receivers what to do when SPF or DKIM fails — reject, quarantine, or just log. Required by Gmail and Outlook at scale.

You don’t need to understand the protocols. You just need them set up correctly. A good invoicing tool tells you exactly which DNS records to add and verifies the setup before activating sending from your domain.

3. Generic free email addresses

Even when authentication is fine, an invoice from a Gmail or Hotmail address looks less trustworthy than one from your own business domain. Some corporate email gateways (the kind that protect bigger companies) downgrade trust for unknown free-address senders, especially when the email contains a PDF attachment with payment details — the exact pattern of a typical phishing attack.

A custom domain doesn’t just authenticate — it signals legitimacy.

Smaller factors worth knowing

PDF attachments. Heavy PDFs (10MB+) raise spam scores. Most invoices should be well under 1MB — if yours aren’t, your tool is embedding images at full resolution.
Trigger words in subject lines. “FREE!”, “URGENT”, all-caps, multiple exclamation marks. Modern filters are content-aware — a normal invoice email rarely fails on words alone.
Suspicious links. Shortened URLs (bit.ly), redirects, and unfamiliar payment portals can flag emails. A direct link to a payment page on a recognised processor is safer.
Cold sender reputation. A brand new domain sending email for the first time has zero reputation. Some quarantining of the first few sends is normal — it settles after a week or two.

The clean fix: a custom sending domain

The right architecture for invoice email:

You own a domain (yourbusiness.com.au).
You add a few DNS records pointing to your invoicing tool’s sending infrastructure.
Your invoicing tool sends invoices “from” invoices@yourbusiness.com.au with valid SPF and DKIM signatures.
Recipients see a clean, business-domain sender. Spam filters wave it through.

This setup also unlocks reply-handling: when a client replies to your invoice email, it lands in your real inbox (no more chasing replies through a generic notifications@ address).

What if you don’t own a domain yet?

Buy one. A .com.au domain costs around $15–$30/year through any Australian registrar (Crazy Domains, VentraIP, Netregistry, etc.). It’s a one-time setup that pays for itself in faster-paid invoices alone, and it lets you have a proper business email like hello@yourbusiness.com.au separate from your personal Gmail.

If you’re just starting out and not ready to buy a domain, the next-best option is to send invoices from your invoicing tool’s authenticated domain rather than spoofing your Gmail — you lose the branding but gain deliverability.

How Free Invoice App handles this

On the Starter and Pro plans, Free Invoice App sends invoices from our own authenticated domain with full SPF/DKIM/DMARC. Your email is set as the Reply-To, so client replies land in your inbox. This already outperforms most ad-hoc invoicing setups.

On Free Invoice App Pro+, you can add your own business domain. We walk you through the DNS records, verify the setup, and from that point onwards every invoice you send appears in clients’ inboxes from invoices@yourbusiness.com.au — fully authenticated, branded, and reply-ready. Get started free on Starter, upgrade to Pro+ when deliverability becomes business-critical.

Frequently asked questions

Why are invoices ending up in clients’ spam folders?

Usually because the email’s “from” address doesn’t match an authenticated sending domain. Modern spam filters flag this aggressively.

What are SPF, DKIM, and DMARC?

DNS records that authorise specific servers to send mail as your domain. Without them, you’re anonymous to receiving servers.

Can I send invoices from Gmail and avoid spam?

Sending directly from Gmail works, but having a third-party tool send “as you” via gmail.com fails authentication.

How do I send invoices from my own domain?

Add SPF/DKIM/DMARC records pointing to your invoicing tool’s servers. Free Invoice App Pro+ guides you through this once at setup.

What words trigger spam filters?

“FREE!”, “URGENT”, all-caps, multiple exclamation marks. Content is a small factor; authentication is the dominant one.