QuickBooks Invoices Bounce When the Sending Domain Lacks Authentication
Gmail and Yahoo now require authenticated sending domains, and QuickBooks users who skip the setup see invoices land in spam or bounce outright.
QuickBooks users who email invoices from a custom domain keep hitting a delivery problem that has nothing to do with the invoice itself. We see the complaint arrive in the same shape each time: the message shows as sent inside QuickBooks, and the customer never receives it. The cause sits one layer down, in the domain behind the From address. The accepted fix is domain authentication, laid out in an Intuit walkthrough of the Mailchimp delivery service QuickBooks uses.
The symptoms users report
The pattern is consistent. An invoice or estimate leaves QuickBooks, and the software reports it as delivered. The customer never sees it. When a message does arrive, it often sits in the junk folder with a spoofing warning attached. Businesses that mail in volume notice first, because the largest mailbox providers grade bulk senders far more strictly than occasional ones.
How does QuickBooks send these emails?
When you send an invoice from QuickBooks, the mail does not travel from your own computer or mail server. It passes through the Mailchimp delivery platform that Intuit connected to QuickBooks. The message carries the From address you entered in your sales email settings, and it is sent on your behalf.
Mailbox providers then ask a simple question: has this domain authorized the platform to send for it? If the answer is no, the message gets filtered. Invoices, estimates, statements, and payment reminders all travel this same path, so one weak domain can affect every customer email you send from the software.
The rules that changed in February 2024
The accepted answer points to a policy shift at the two biggest providers. As of February 2024, Gmail and Yahoo require custom authentication and a published DMARC record from anyone sending more than 5,000 messages to their users within 24 hours. DMARC, short for Domain-based Message Authentication, Reporting and Conformance, is a public record that tells receiving servers what to do when a message fails its checks.
Senders below that threshold are not bound by the mandate. The filtering logic still reaches them. An unauthenticated domain is simply trusted less, and invoices pay the price.
The accepted fix, step by step
The solution is to authenticate the domain, and the order matters. First you verify the domain, which proves you are allowed to send from it. Then you authenticate it, which publishes the records that authorize the delivery platform to send on your behalf. Have the login for the company where your domain is registered ready before you start.
Two routes exist for the record work. The quicker one uses a service called Entri, built for exactly this purpose. You sign in with your registrar credentials, and the records are written for you. The manual route has you copy each value from the setup screen and paste it into the DNS settings at your registrar. The walkthrough suggests keeping two browser tabs open, one for setup and one for your registrar. Records take a little time to be recognized after you save them, so a short wait before retesting is normal.
Does a free Gmail or Yahoo address still work?
No, and the accepted answer is blunt about it. Authentication can only be added to a domain you or your business owns. Free mailbox services such as Gmail and Yahoo cannot be authenticated through the delivery platform at all, because you do not control their domains. The recommended move is to switch your From address to a private domain, such as the one behind your website or your work email. That single change, followed by verification and authentication, is what restores dependable delivery.
One record still to add: DMARC
SPF and DKIM, the two underlying checks, are handled during authentication. DMARC is separate. It is a small text record you publish alongside the others, and it tells receivers what to do when a message claims to come from you but fails those checks. Without it, you meet the letter of authentication but not the new Gmail and Yahoo requirements for volume senders. The accepted guidance is to complete both.
The bottom line for invoice delivery
If your invoices are vanishing, look at the domain in your From address before you look at QuickBooks itself. A custom domain that has been verified, authenticated, and given a DMARC record clears checks that free addresses cannot. The setup is a one-time job, and the payoff is mail that arrives where it should.