Recover an undelivered customer invoice with a clear owner, a traceable resend and evidence that separates delivery from payment.
An invoice can be correct, issued and still absent from the customer’s accounts payable queue. Resending it repeatedly does not explain whether the address is wrong, the sender system failed or only one recipient was affected.
An invoice delivery failure workflow treats that problem as a recovery case around the original invoice—not as permission to create another charge. This guide gives B2B billing and accounts receivable teams a diagnosis matrix, a case register and a controlled handoff back to collections.
Keep invoice, delivery and collection states separate
Track three questions independently: is the invoice valid and posted, what happened to each delivery attempt, and what balance remains unpaid? A failed email alone does not establish that the invoice amount, accounting record or agreed payment terms should change.
Use your contract, billing policy and applicable requirements to decide whether delivery affects a due date or requires another channel. Escalate that decision to the authorized finance or contract owner; do not reset dates simply to clear a delivery exception.
The controls below are a recommended operating design, not a universal accounting or legal requirement. Regulated electronic invoicing, tax-document corrections, payment disputes and debt-collection rules need their own procedures. For the surrounding lifecycle, see the accounts receivable workflow.
A status is evidence of one event, not the whole outcome
“Sent” may establish only that the application submitted a message. “Delivered” does not necessarily prove that the billing contact saw the invoice or approved payment. For example, Microsoft’s Exchange Online message trace FAQ explains that a message sent to Junk Email or quarantine can have a Delivered status. Use the meaning documented by your actual provider rather than treating labels as interchangeable.
Likewise, an invoice marked viewed is not a payment receipt. Close the delivery case using defined delivery evidence, and leave the receivable open until the accounting system records the appropriate payment or authorized adjustment.
Open one recovery case against the original invoice
Billing owns intake when an application reports failure, a bounce arrives or the customer says the invoice is missing. First check the invoice, its current balance and prior communication. If it has already been paid, coordinate with cash application before sending another payment request.
Record one parent case per invoice and separate child rows for each attempt and recipient. Preserve the original document and identifiers. Multiple notifications about the same failure should update that case rather than create competing resend tasks.
- Invoice identity: issuing entity, customer account, invoice number, issue date, currency, amount, original document reference and current balance.
- Delivery identity: attempt time and time zone, channel, sender, intended To/Cc recipients, message or provider reference and available status/error evidence.
- Recovery decision: classification, owner, verified contact or technical correction, authorization where needed, next action and next review time.
- Closure evidence: authorized resend reference, resulting status, customer acknowledgment if required, unresolved recipients and collections handoff.
Limit access to customer contact details and supporting correspondence under your company’s permissions and retention policy. Retain enough evidence to reproduce the decision without scattering unnecessary copies of invoice attachments.
Diagnose before choosing a resend
Do not assume an invoice-wide failure identifies the bad recipient. Intuit’s undelivered invoice guidance explains that a message sent to several recipients can show an undeliverable invoice status when only one recipient failed, without identifying which one. Investigate the available event details and confirm the billing destination before acting.
| Observed problem | Decision owner | Evidence and action | Exit condition |
|---|---|---|---|
| Missing or invalid billing address | Billing, with the customer account owner | Confirm the authorized destination through an established customer contact; record who verified it and correct the controlled contact record. | Verified destination and authorized resend of the original invoice. |
| Temporary mail failure or queued attempt | Messaging administrator, with billing tracking the case | Inspect the provider’s status and retry behavior. Set a review time; avoid manual resends while an automatic retry may still run. | Provider outcome reviewed, or an approved alternative route assigned. |
| Sender configuration or permission failure | System administrator | Retain the error and support reference. Use the approved technical support process; billing does not improvise sender/security changes. | Administrator confirms recovery and billing verifies the next authorized attempt. |
| Some recipients may have received it | Billing | Review recipients separately and ask the designated AP contact whether the invoice is already in its queue. Preserve uncertain outcomes as unknown. | Required billing recipient confirmed; remaining recipient exceptions have a documented disposition. |
| Server accepted the message, customer cannot find it | Billing and customer AP contact | Check the agreed address, spam/quarantine or portal route using an approved communication channel. Agree a traceable resend or alternative. | Evidence meets the company’s delivery standard; otherwise keep an owner and review date. |
| Customer received it but rejects the amount or supporting documents | AR, contract owner and authorized finance reviewer | Transfer the substantive issue to dispute/correction review. Do not label it a transport failure or silently alter the invoice. | Linked dispute case accepted by its owner, with delivery evidence retained. |
Temporary and permanent failures need different handling. Salesforce’s bounce-handling documentation distinguishes temporary failures from permanent ones such as a nonexistent address. Apply the classification your messaging service supplies; there is no single retry interval appropriate to every provider and contract.
Authorize one traceable retransmission
Once the cause is understood, billing checks the current invoice version, recipient and balance again. For an unchanged valid invoice, use the existing system’s supported resend or download-and-send process. Make clear that it is a copy of the same invoice, not a new request to pay twice.
Record the case reference, destination, document/version reference, sender, authorization and next attempt identifier. If the customer’s agreed channel is a portal, record its submission and acknowledgment references rather than relying on the email log.
A changed recipient is not authorization to change bank details. Verify any requested change to payment instructions through the separate approved control. If the amount, tax treatment, customer entity or other financial substance is wrong, stop delivery recovery and obtain the appropriate correction review before releasing a revised document.
Use the recovery sequence Identified → Classified → Correction authorized → Retransmitted → Evidence reviewed → Delivery case closed. Reopen the case when a later failure arrives or the required recipient remains unconfirmed. Reapprove the decision if the document, destination or agreed channel materially changes.
Worked example: one failed recipient, one receivable
This is an illustrative example, not a customer result. A service company issues a valid $4,800 invoice and sends it to three customer contacts. The invoicing screen shows an undeliverable status. Two addresses may have succeeded, but the aggregate flag does not establish which person received it.
- Billing opens a delivery case linked to the original $4,800 invoice and preserves the attempt and error evidence. It does not create a second invoice.
- The account owner confirms through an established customer contact that the required AP mailbox has changed. Billing checks whether AP already has the invoice and records the response and verified replacement address.
- Billing updates the authorized contact record and makes one recorded resend of the unchanged invoice to the agreed destination. The message identifies it as a copy of the original invoice.
- The AP contact acknowledges receipt into its processing queue. Billing records that evidence, closes delivery recovery under company policy and returns follow-up to AR.
The accounting record still contains one $4,800 charge, less any properly recorded receipts or adjustments. Acknowledgment does not prove acceptance of every line or settlement. If AP now disputes the service, AR opens or links a dispute case rather than reopening endless email resends.
Close delivery recovery without losing the cash follow-up
The billing reviewer checks that the original invoice identity is preserved, the required recipient/channel meets the delivery standard, prior failures remain visible and any unresolved recipient has a decision owner. A successful send button alone is not enough if the case required customer confirmation.
Then hand AR the current balance, delivery evidence, any approved due-date decision, customer response and next follow-up date. The dunning process handles subsequent reminders and escalation. If reminders were paused during investigation, record who may resume them and when; do not leave a silent indefinite hold.
For review, distinguish open delivery cases, cases awaiting technical action and invoices back in ordinary collections. Count duplicate failure notifications only once at case level. Define the population and timestamps before reporting resolution time; do not treat an improved delivery metric as proven cash collection improvement.
Where Workhint fits
Workhint’s Workflow Engine describes routing approvals to defined roles and requiring details, files or notes before work advances. Those building blocks are relevant to a proposed recovery case in which billing supplies the invoice reference, an administrator supplies technical findings and a reviewer checks closure evidence.
The Workflow Automation Software solution describes configurable forms, stages, owners and next actions for multi-step work. The implementation question is how to coordinate that handoff around your existing invoice and messaging systems. These pages do not establish native bounce detection, an email-delivery guarantee, automatic ERP posting or a ready-made integration. Keep invoice balances and financial corrections in the accounting system and accountable finance roles.
Frequently asked questions
Should we issue a new invoice when the email bounces?
Not merely because delivery failed. Investigate and retransmit the unchanged valid document through the supported process. A substantive invoice error needs a separate authorized correction procedure.
Does resending automatically change the due date?
No automatic rule is assumed here. The authorized owner must assess the contract, applicable requirements and billing policy, document any approved change and communicate it consistently.
Can a delivery case close before payment arrives?
Yes, if the documented delivery criteria are met and AR accepts the follow-up. Delivery recovery and collection are different cases with different completion evidence.
What if delivery remains uncertain?
Keep the outcome unknown, assign a named owner and review time, and agree the next authorized channel with the customer. Do not convert uncertainty into a success flag or generate another charge.

Leave a Reply