---
title: "The customer says the invoice never arrived: checking facts without conflict"
canonical: https://www.billabex.com/en/blog/customer-says-invoice-never-arrived/
lang: en
alternate: https://www.billabex.com/fr/blog/client-affirme-facture-non-recue.md
updated: 2026-10-06
index: https://www.billabex.com/llms.txt
---

# The customer says the invoice never arrived: checking facts without conflict

“We never received that invoice.” The reply can describe several problems: the document never left your system, the message reached a poorly monitored inbox, an attachment was missing or accounts payable never took responsibility for processing it. Immediately replying “But we sent it” can close the conversation before anyone identifies the actual obstacle to getting the invoice approved and paid by the customer.

Start by defining what needs to be established. Identify the invoice, check its delivery path and help the appropriate contact process it. If the conversation becomes a dispute about the debt or its due date, examine the contractual evidence and applicable requirements separately. An email's technical status cannot resolve all those questions on its own, even when it appears reassuring in the sending dashboard.

## Ask what the customer is actually missing

Invite the contact to clarify: can they find no message, is the invoice attachment missing, or is the document absent from their accounting system? These answers point to different actions. Repeating the original send might help in the first case, fail again in the second and leave the underlying approval process entirely unchanged in the third. A precise question can avoid several unnecessary exchanges.

Check the complete reference, issuer, date and amount before resending a document. A customer handling multiple entities may be searching for the wrong invoice. The agreed billing address may also differ from the salesperson's address used during negotiations. If the [accounts payable contact has left](https://www.billabex.com/en/blog/accounts-payable-contact-left-payment-route/), first identify the current process without assuming that every historical attachment was passed to the replacement colleague.

A useful question is: “To help you process invoice X from the named company, can you confirm that this is the correct receiving address and that no separate submission is required?” You are establishing the destination and action needed, rather than asking the customer to acknowledge having read something they may never have seen or been responsible for processing.

## Distinguish server acceptance from arrival in the right inbox

SendGrid explains that a Delivered event follows the receiving server's acceptance with a `250 OK` response. That server may subsequently place the message outside the main inbox, queue it or apply further filtering. Technical acceptance therefore does not prove that the appropriate contact has the document in front of them. [SendGrid, delivered email missing from the inbox](https://support.sendgrid.com/hc/en-us/articles/4408443310619-Email-Delivered-But-Not-Appearing-in-Inbox).

Ask your team for the available evidence: exact destination address, sending date, message reference, any error response and the file actually transmitted. If a rejection is recorded, resolve its cause before sending another payment reminder. If the server accepted the message, use that information to assist the search without concluding that the customer is dishonest when they cannot locate the document in their own working environment.

The [collections audit trail](https://www.billabex.com/en/blog/collections-audit-trail-automation/) can reconstruct the path, but its entries must be interpreted at the right level. A sending attempt, server acceptance and human reply are different events. Their appearance in one history does not make them equivalent or establish that the correct invoice was attached to the message the recipient eventually opened or forwarded to a colleague.

## An open event does not settle the conversation

Apple states that Protect Mail Activity downloads remote content in the background regardless of whether the recipient interacts with the message. A signal based on that loading can therefore occur without a person reading the email. [Apple, Mail Privacy Protection, version dated 12 December 2025](https://www.apple.com/legal/privacy/data/en/mail-privacy-protection/).

Avoid saying “We know you opened the invoice” based only on a counter. Even an actual opening of the message does not establish that its attachment was read, its details were correct or accounts payable entered it into the payment process. Ask instead for an observable action: locate the document, confirm its identity or explain what prevents the team from taking responsibility for processing it.

That discipline helps internal communication too. A salesperson may have opened and forwarded the message while the accountant is still searching for the attachment. The counter cannot reconstruct that whole chain. A targeted response from the team handling the invoice provides information more directly useful to the next collection action than an interpretation of one isolated engagement event in a dashboard.

## A simulation shows why the final step matters

Consider twenty fictitious invoices of €2,000 each, sent through an email process in which that delivery method remains applicable. Three sends are rejected. Seventeen are accepted by receiving servers. After checking with customers, five of those seventeen documents are found in mailboxes that do not process invoices, while twelve have been identified by the team responsible for taking them through the payment workflow.

Technical acceptance represents **17 ÷ 20 = 85% of sends**, covering €34,000 in invoices. Confirmed operational receipt represents **12 ÷ 20 = 60%**, covering €24,000. The difference is five invoices and €10,000. These numbers describe only the simulation; they are not market rates, results from a customer study or performance measures for any email or collections provider.

The five misrouted cases need the receiving process corrected; the three rejected sends need their delivery problem resolved. The twelve processing confirmations are not payments, so cash received may still be zero at that point. Measuring those stages separately supports an appropriate action and prevents technically accepted documents from being presented as secured liquidity in a management update about expected receipts.

## Resend the right evidence without creating another inconsistent demand

Where the original invoice is correct, send an identifiable copy and explain that it is the previously issued document. Preserve the complete reference. Do not create another invoice merely to make a resend visible. If the original contains an error in the customer, amount or tax treatment, have accounting address the correction instead of silently modifying the file used in the conversation.

Check the documents required by the customer's process. An invoice may be available but blocked by a [missing purchase order](https://www.billabex.com/en/blog/missing-purchase-order-blocked-invoice/). Resending the PDF alone will not solve that problem. Provide the relevant supporting document or identify who can supply it, then request confirmation that the file can now be processed rather than assuming another send has resolved the customer's stated difficulty.

France's tax authority explains that an ordinary emailed PDF is not an electronic invoice under the reform: the latter contains structured data and travels through an approved platform. Where an operation is subject to that obligation under its scope and timetable, inspect the platform's delivery path; an informational email does not replace it. [DGFiP, emailed invoices, updated 16 January 2026](https://www.impots.gouv.fr/professionnel/questions/est-ce-quune-facture-envoyee-par-mail-est-une-facture-electronique).

## Resume follow-up with facts and a specific next step

A response might say: “We located the original transmission to the agreed address on the 14th. To help processing, we are providing the invoice copy and associated purchase order again. Could you confirm that accounts payable has taken them in hand and identify any document still missing?” Adapt this illustrative wording after verifying the facts and the applicable submission channel for the particular customer and invoice.

Do not automatically promise a new due date starting from the resend. If the customer disputes the deadline or underlying obligation, assemble the contract, evidence of delivery or performance and the chronology. Article 1353 of the French Civil Code addresses proof by the party claiming an obligation and the party claiming discharge. It does not make an open counter sufficient evidence of the entire receivable. [Civil Code, article 1353](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032042341).

The [follow-up conversations in Billabex](https://www.billabex.com/en/product/follow-ups-conversations/) help place the customer's reply in the context of the case. The objective remains concrete: the right document, in the right place, with a contact who understands what needs checking. The discussion about receipt then becomes an investigation that supports payment, backed by the evidence available and a clear understanding of what each piece of evidence does and does not establish.

## Sources

- [SendGrid, delivered email missing from the inbox](https://support.sendgrid.com/hc/en-us/articles/4408443310619-Email-Delivered-But-Not-Appearing-in-Inbox).
- [Apple, Mail Privacy Protection, 12 December 2025](https://www.apple.com/legal/privacy/data/en/mail-privacy-protection/).
- [DGFiP, emailed invoices, 16 January 2026](https://www.impots.gouv.fr/professionnel/questions/est-ce-quune-facture-envoyee-par-mail-est-une-facture-electronique).
- [French Civil Code, article 1353](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032042341).