Emailing Invoices and Proving Delivery: What to Record
Back to blog
automation·September 11, 2026·4 min read·By Yehonatan Saadia

Emailing Invoices and Proving Delivery: What to Record

A customer says they never got the invoice. What proves it was sent, how to reduce spam filtering, and what to record so the conversation ends in a minute.

Key takeaways

  • Sending is not delivery. What proves anything is the sending system's log, not your sent folder.
  • A linked document beats an attachment: you can see when it opened, and it is not blocked as a file.
  • A wrong email address is the most common cause, and the place to check it is when the customer record is created.
  • A second channel - WhatsApp or SMS with a link - removes most of these enquiries.

"I never received the invoice" is one of the most common enquiries in any business, and from the customer's side it is almost always true: the document was sent, landed in spam or at an old address, and nobody knew. The fix is not sending it again but recording it: what was sent, to whom, when, and what the receiving server said.

This is an operational description, not advice. Your business's retention and record-keeping obligations are a question for your accountant and the official authority pages.

Why email fails

CauseHow to spot itWhat to do
Wrong or old addressA bounce from the serverValidate the address when creating the customer, not when sending
Spam filteringNo error, and no openCorrect sender configuration, sent from a recognised address
Attachment blockedAn error from the customer's serverSend a link instead of a file
Mailbox fullA bounceReach out on another channel
Corporate filteringNo error and no openAsk the customer to allowlist the address

The two rows with no error are the problem: as far as your system is concerned the send succeeded, and as far as the customer is concerned nothing arrived. That is why a log showing only "sent" is not enough.

What counts as a good record

  • Date and time of sending, from the system rather than from memory.
  • The address it went to, as it was at that moment.
  • What was sent - the document number, not just "an invoice".
  • The receiving server's response where available: delivered, rejected, or an error.
  • An open or download, if your system reports it.
  • A resend, if there was one, with its own date.

Those five together turn the conversation with a customer from an argument into a fact: "sent on the 12th to this address, opened on the 14th". If the address is wrong, it also reveals that immediately.

AttachmentDocument link
Server blockingHappensRare
Can you tell it openedNoUsually yes
Later accessThe file is theirs foreverDepends on link availability
ConvenienceOpens immediatelyOne extra click
Sending over WhatsAppAwkwardNatural

The practical recommendation: links by default, attachments when a customer asks. Corporate customers sometimes require a file for their internal systems, and that is a legitimate request.

How to reduce spam filtering

  • Send from the system rather than a personal mailbox - sending systems are configured correctly from the start.
  • Use a consistent sender address, rather than changing it every few months.
  • Do not attach large files or write a subject line that reads like marketing.
  • Confirm the domain configuration is correct - a technical subject covered in SPF, DKIM and DMARC in practice.
  • Do not send invoices through the same platform you use for marketing campaigns.

The last line gets forgotten: a mailing platform used for both marketing and documents creates a situation where a customer who unsubscribed from marketing stops receiving invoices too.

The second channel

The simplest way to eliminate this enquiry is to send the link on a channel that gets read as well. Morning, for instance, presents sending invoices over WhatsApp among its tools. What matters:

  • Send the same link, not a second document created afresh.
  • Do not include sensitive details in the message itself.
  • Record that send too, in the same place.

The full collection flow on that channel is described in collecting payments over WhatsApp.

What to do when a customer says they did not receive it

  1. Check the log for when it was sent and to which address.
  2. If the address is wrong, fix it on the customer record, not only on this send.
  3. Resend, and simultaneously use a second channel.
  4. Log the enquiry, so you can spot whether it repeats for the same customer.
  5. If it repeats across many customers, this is a general delivery problem, not an individual case.

Step five is the flag: three enquiries in one week is not coincidence but a sign that something in the sending configuration changed.

What happens when an invoice goes to the wrong customer

It happens, usually because of two similar customer records or an address copied by mistake. What matters is the order: first establish what was actually exposed - a document with another customer's details is a third party's information; then ask the recipient to delete it and record that request; then send the correct document to the correct address; and only then fix the source of the error on the customer record. The order matters because most people start at step three and forget step one, which is the part that actually carries weight.

What about customers who want paper

Some customers - usually long-standing or corporate - ask for a printed invoice. That is legitimate, and it deserves a procedure: who prints, when, and where it is sent. What matters is that the printed document is the same document in the system rather than a separate version, and that printing supplements the digital record rather than replacing it. A business running some customers on paper and some digitally discovers the gap at year end, when documents turn out to be missing from the system.

How to set this up once

The right configuration is done once and holds for years: one sending address from the system; a fixed message template with the document number in the subject; automatic sending at the moment of issue rather than as a daily task; and records kept in the system rather than in a personal mailbox. Those four together cut enquiries about undelivered documents to almost nothing, and they need no new tool - only a decision.

Sources

#invoice email#delivery#spam#records#collections#אינטגרציה

Frequently asked questions

Does sending by email count as delivery?

That has a formal side, which belongs with your accountant and legal adviser. Operationally, what holds up in a conversation with a customer is a record: when it was sent, where to, and what the server returned. A sent folder in a personal mailbox is the weakest record there is.

Should I send invoices over WhatsApp?

As an additional channel, yes - that is where they get read. What is unwise is replacing email entirely, because business customers expect a document by email for their own filing. The common solution: email as the main channel, a message with a link as backup.

A customer asks me to send to a different address each time. What now?

Update the address on the customer record once, rather than changing it on every send. An address typed by hand each time is a permanent source of errors, and it is also what produces the next complaint about a document that never arrived.

How do I know the document was opened?

It depends on the system: some report an open or download of a document sent as a link. That is a good indication rather than absolute proof - so the real value is in the combination: a send log, followed by an open marker where one exists.

Keep reading

Related service

Integrations

Make the systems you already pay for talk to each other.

Learn more

About the author

Yehonatan Saadia

Freelance automation, web & MVP developer

I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.

Work with me

Have a project like this?

Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.