Your invoice reminder lands in spam. Your client never sees it. The invoice sits unpaid for another two weeks. And you have no idea any of this happened.
This is one of the most frustrating problems with QuickBooks Online’s built-in reminder system - and it’s frustrating partly because it’s invisible. QuickBooks doesn’t tell you when a reminder fails to reach the inbox. There’s no bounce notification, no delivery report, no way to know whether your client ignored the reminder or never received it at all.
The root cause is straightforward: QuickBooks sends your invoice reminders from its own email infrastructure, not from you. Understanding why that matters - and what you can do about it - is what this article covers.
What your client actually sees when a reminder arrives
When QuickBooks sends an invoice reminder on your behalf, the email arrives from quickbooks@notification.intuit.com. Your business name appears in the sender field, and any replies will come to your email address - but the actual sending address your client’s spam filter evaluates is Intuit’s.
For many clients, this is fine. For a meaningful number, it isn’t.
Corporate email systems - particularly those running Microsoft 365 or Google Workspace with strict security policies - are set up to be sceptical of emails where the visible sender name doesn’t match the sending domain. An email that says it’s from “Acme Accounts” but actually originates from notification.intuit.com can trigger a spam filter flag before the content is even evaluated.
The blacklisting problem
The sending domain issue is compounded by a separate, recurring problem: Intuit’s IP addresses have repeatedly ended up on email blacklists.
The most documented instance runs through the QuickBooks community forum, where a thread titled “Intuit IPs found in Spamcop blocking list preventing vendors from sending invoices” accumulated hundreds of responses over years. The core issue: QuickBooks sends its emails through SendGrid, a third-party email delivery service, and several of the IP addresses used have appeared on SpamCop and other blocklists. When that happens, invoices and reminders sent through QuickBooks are bounced or rejected entirely at the recipient’s mail server.
One user who manages inbound email for a large number of businesses documented 145 blocked emails in a single week, all traced back to the same recurring Intuit IP addresses.
What makes this particularly frustrating is that the QuickBooks support article listing the company’s authorised sending IPs doesn’t include all the IP addresses QuickBooks actually uses. So even businesses that follow the official guidance and whitelist those IPs can still find their clients’ reminders getting blocked.
Intuit has acknowledged the problem on multiple occasions and committed to resolving it. The thread is still open and still receiving new reports. At higher volumes the problem becomes even more visible: one business owner sending 700 invoices a month reported having to release them in batches of 10 on QuickBooks’ own advice, simply to improve the chances of them getting through.
The scam problem making it worse
There’s a second layer to the domain reputation issue that’s harder to fix: scammers actively exploit the Intuit/QuickBooks email domain.
Phishing campaigns that impersonate QuickBooks invoices - fake payment requests, fake ACH remittance notifications - are common enough that security researchers track them specifically. Because they use email addresses that look like legitimate QuickBooks communications, some corporate IT departments have adopted blanket policies blocking anything from the notification.intuit.com domain.
For those clients, your genuine invoice reminder won’t reach them regardless of whether Intuit’s IPs are on a blacklist that week. The block is a policy decision, not a filter, and your client may not even know it’s in place.
What QuickBooks suggests - and why it’s not enough
QuickBooks support offers three main workarounds for the spam problem. It’s worth knowing what each one actually does.
Ask your clients to whitelist the Intuit address. The standard advice is to ask customers to add quickbooks@notification.intuit.com to their contacts or safe sender list, and to mark any emails from QuickBooks as “not spam” if they find them in their junk folder. This works if your client finds the email, recognises it as legitimate, and takes action on it. It doesn’t help if the email was silently rejected at the mail server level before it reached the inbox at all. It also requires you to contact every affected client individually, which is an ongoing task as you add new customers.
Connect a Gmail account. QuickBooks allows you to connect a Gmail account, so that invoices are sent from your Gmail address rather than the Intuit domain. For some users this improves deliverability, since emails from a Gmail address don’t carry the same domain reputation issues. The limitations are significant though: this option only works with Gmail - there is no equivalent integration for Microsoft 365 or Outlook, which is how the majority of UK businesses send email. It also applies specifically to invoice sends, and does not cover all automated reminder types.
Configure your SPF records. Businesses with their own domain can add the Intuit sending domain to their DNS SPF records, which tells recipient mail servers that QuickBooks is an authorised sender on your behalf. This is a legitimate technical fix for one part of the problem - but it requires access to your domain’s DNS settings, an understanding of SPF records, and keeping the Intuit IP list up to date. As noted above, QuickBooks’ published list of IPs is incomplete, so even a correctly configured SPF record may not cover all of QuickBooks’ actual sending infrastructure.
The thing none of these workarounds solve
All three approaches share the same underlying limitation: they’re working around the fact that the email comes from Intuit, rather than actually fixing it.
The reason reminder emails from notification.intuit.com end up in spam more often than emails from your own address isn’t random. Spam filters are built to evaluate whether an email is likely to be what it claims to be. An email that arrives from a generic third-party notification domain - shared with millions of other businesses, and with a publicly known reputation for also being used by scammers - will score worse than an email that arrives from the same domain as your website, sent from an inbox your client has corresponded with before.
The deliverability difference isn’t just about spam filters either. Even when the reminder reaches the inbox, an email from quickbooks@notification.intuit.com reads differently to one from accounts@yourcompany.com. The latter looks like a direct communication from someone the client has a relationship with. The former looks like a system notification from a piece of software. Clients are more likely to open and act on the former.
How Trove handles this
Trove integrates directly with your Gmail or Outlook inbox and sends reminders from your own email account. Each reminder lands in your client’s inbox from your actual email address - accounts@yourcompany.com, or whoever handles collections - looking exactly like an email you sent yourself.
This solves the deliverability problem at its root. There’s no shared sending domain, no third-party IP reputation to manage, no SPF configuration to maintain. Because the email comes from your own inbox, it passes through spam filters the same way any email from you would.
It also makes a meaningful difference to response rates. Trove’s data across thousands of invoices shows that reminders sent from a personal business address get paid faster than those arriving from a platform address. The same message, from the right sender, performs better.
Trove runs a free 30-day trial and takes about fifteen minutes to connect to your QuickBooks account.
