Why invoice emails go to spam and what to check
Start by finding out whether the invoice email was sent, rejected or filtered, then identify the service that actually sent it. An invoice from accounting software can take a different route from a normal Outlook reply, even when both show your business name. This guide helps finance teams and their IT providers investigate the right route.
- Why are invoice emails going to spam?
- An invoice can reach spam because of its sending identity, authentication, message characteristics, sender reputation or the recipient’s filtering rules. But a customer reporting a missing invoice does not establish spam placement. The message may never have been generated, may have bounced or may have gone to a different address. Check the actual outcome before changing DNS or resending it.
1. Establish what happened to the missing invoice
| What you can observe | What to check | Who can help |
|---|---|---|
| There is no sending event | Was the invoice or reminder scheduled, approved and generated for this contact? | The finance team or billing-application owner |
| The platform reports a bounce or delivery issue | Keep the exact error, recipient and timestamp. Check the address and which system rejected the attempt. | The platform supplier or mail administrator |
| The customer finds it in junk or quarantine | Retain that message’s technical evidence and the filtering verdict where available. | The receiving organisation’s administrator |
| The platform says sent or delivered, but the customer cannot find it | Confirm the destination address and the platform’s definition of the status. Placement remains unconfirmed. | The sender and recipient administrators, using the same message details |
| The invoice arrived but remains unpaid | Confirm that the right person received it and follow your normal billing process. Non-payment alone is not a delivery diagnosis. | Your accounts team and the customer’s established billing contact |
If payment or a deadline is at risk, contact the customer through an established channel while the investigation runs. Avoid repeated resends to multiple addresses, which can create confusion about which invoice is current. Do not ask the customer to weaken security controls or trust changed payment details simply to complete a delivery test.
2. Identify the invoice’s actual sending route
| How the invoice is sent | What to identify | What a successful Outlook reply proves |
|---|---|---|
| Directly from an accounting platform | The platform’s sending address, reply-to address, delivery events and supported authentication options | Only that the separate Outlook message arrived |
| Through a connected business mailbox | Which mailbox is connected, whether its permission still works and the route used by this feature | Useful comparison evidence, but the application may use different content or settings |
| As a PDF or link in a staff email | The staff mailbox, actual recipient, attachment or link, and available mail trace | That one sample arrived, not that every invoice message will |
| Through an add-on or reminder service | The add-on’s sending provider and domain, even if it reads the invoice data from your accounting system | Nothing conclusive about the add-on’s sending route |
What should you check when Xero invoice emails go missing?
Check the Xero sending route before editing your business domain’s SPF record. Xero’s email settings documentation (opens in a new tab) says its standard service sends from messaging-service@post.xero.com, while you can choose the display name and reply-to address. Those are different parts of the message.
A reply-to address on your company domain does not mean that your company’s mailbox sent the invoice. If an add-on sends reminders using your mailbox instead, treat that as a separate route. Establish which service handled the affected example and give that service’s support team the relevant sending details.
For a practice using several systems, our accountancy email-deliverability page explains how client correspondence, practice reminders and invoice mail fit into one scoped investigation.
What should you check when QuickBooks invoices are not received?
Check the invoice’s delivery status and the intended recipient before assuming that it reached spam. Intuit’s undelivered-invoice guidance (opens in a new tab) notes that a delivery issue can refer to one failed recipient in a message addressed to several people. It does not necessarily mean that nobody received it.
Record which customer contact was used and ask the relevant recipient to check junk or quarantine. Intuit’s UK guidance for sales-form email (opens in a new tab) also explains how to review sending history and company email settings. Use the documentation for your product and region, since screens and available sending options can differ.
If ordinary mailbox email arrives but the QuickBooks message does not, keep those results separate. Ask the administrator or supplier to investigate the affected invoice route. Broadly allowing a supplier’s traffic is not a substitute for understanding why a particular message was blocked.
3. Compare a small set of useful examples
Choose an affected example
Record the invoice reference, sending time and time zone, actual destination, sending application and status. Keep the finance record unchanged while the technical question is investigated.
Find a comparable successful example
Use the same sending route where possible. Note differences in recipient organisation, sender address, template, links and attachments. A copy arriving in your own inbox is only evidence about that copy.
Collect the technical evidence
Use our annotated email-header guide to identify the evidence to request. Ask authorised people for the relevant sending event, bounce or original received-message headers. A forwarded message or screenshot of a spam folder can lose details needed to identify the route and filtering decision.
Test one supported explanation
Agree a controlled test with suitable recipients and the system owner. Change one relevant factor at a time and compare the received result. Do not create or duplicate live accounting transactions solely to test email.
Will SPF, DKIM or DMARC fix invoice delivery?
They may be part of the correction if the affected route is misconfigured, but they are not a universal fix. Inspect authentication on a message from that route. The visible From address, reply-to address and domains used by SPF or DKIM can differ. Microsoft’s authentication explanation (opens in a new tab) describes why an authenticated sending identity and alignment need to be considered together.
If a platform sends using a domain it owns, your team cannot repair that domain by adding records to your own. If it supports sending as your domain, use the current configuration supplied for your account and verify the result after an approved change. Do not copy a generic SPF string into DNS without reviewing the senders already authorised.
Passing authentication still does not guarantee inbox placement. For a message sent from your business mailbox, follow the relevant Microsoft 365 or Google Workspace investigation. If the issue began after a change, use the domain and provider migration checklist.
Illustrative example: a reminder fails but a personal reply arrives
A fictional consultancy sends invoice reminders through an add-on and personal replies through Microsoft 365. One customer reports a missing reminder, while a staff reply arrives. That comparison suggests a route to investigate, but does not establish the cause.
The useful next step is to identify the add-on’s sender and delivery event, then compare an original affected reminder with a successful reminder from the same service. If the evidence points to the receiving organisation, its administrator needs the exact message details. If the add-on rejected the send before delivery, the investigation stays with that application.
The result should identify what was observed, who owns the next action and how a proposed correction will be checked. This is an illustrative method, not a client result.
A focused handover includes
- The affected route and message details
- The confirmed outcome and supporting evidence
- A named owner for the next check
- The change and verification plan, if justified
When should you bring in a deliverability specialist?
Specialist help makes sense when invoice problems recur across customers, several applications are involved or your software supplier and IT provider each hold only part of the evidence. A single mistyped billing address usually belongs with the accounts team first.
Neotiqa provides a read-only email deliverability assessment with evidence, prioritised findings and a technical handover. Any implementation or ongoing monitoring is agreed separately. You work directly with Peter Black to define the systems, access and outputs before the work starts.
For the wider client-email workflow, see our guidance for accountancy practices, law firms and estate and letting agencies. The right scope depends on the messages and systems affected, rather than the industry label alone.
If the missing message is a quotation or order confirmation, our manufacturing and engineering email-deliverability page covers RFQs, document revisions, ERP sending accounts and drawing access. Keep those enquiry-to-order checks separate from the billing transaction.
Questions about missing invoices and reminders
Why do invoice emails go to spam when normal emails arrive?
The invoice may use a different sending service, domain, template or link from your normal correspondence. Identify the actual route and compare message evidence from it. One successful staff email does not establish that the invoicing route is working.
Does a sent or viewed status prove the customer received the invoice?
Check what that specific platform measures. A sent status does not by itself establish inbox placement. A viewed or open event may reflect automated scanning or image loading, so it is not conclusive proof that the intended person read the invoice.
Should I download the invoice and email it from Outlook?
That may be an agreed temporary way to contact the customer, but it changes the sending route and does not diagnose the original failure. Keep the invoice and billing record consistent, use your normal document-sharing controls and investigate the platform route separately.
Can we solve this by adding the accounting platform to SPF?
Only where its supported sending setup requires a change to a domain you control. Some platforms send from their own domain. Identify the sender and follow the current account-specific instructions before proposing a DNS change.
What should we send Neotiqa in an initial enquiry?
Describe the invoicing software, mail provider, symptom and when it began. Do not upload invoices, customer records, credentials or confidential message samples through the public form. We agree the evidence and sharing method when scoping an assessment.
Are missing invoice emails creating repeated chasing?
Tell us which system sends the invoice and what the customer has reported. We can discuss a focused assessment of the affected route.