Export or back up the relevant data first. Do not delete, void, unreconcile, or adjust historical transactions unless you understand the accounting impact.
Menu names can change. We link current first-party instructions so you can confirm product behavior before acting.
Identify the failure before applying a fix
An invoice or reminder appears sent in Xero, but the customer cannot find it, or Xero reports a bounce or missing email.
Record the complete message, affected organisation or company, user, date range, and last successful action. A precise symptom is more useful than trying several broad repairs at once.
Workflow map
Prove delivery without creating a second invoice
A “sent” status records the handoff, not the inbox. Work the delivery evidence in order and keep one sales transaction.
- 1
Inspect
Open the original invoice, confirm it is approved, and check the contact address and send history.
Evidence: The version actually sent, and the address it went to.
- 2
Read the bounce
Separate an invalid address from a rejection by the recipient’s mail server.
Evidence: The bounce message Xero returned to the sender.
- 3
Resend
Resend the existing invoice, or share its online link or PDF through an agreed channel.
Evidence: The delivery method recorded in the invoice history or internal notes.
- 4
Confirm
Ask the customer to confirm the invoice number, amount, and due date they received.
Evidence: The customer’s confirmation, not the send status.
Checks before changing data
- Confirm the customer email character by character.
- Check whether Xero emailed a bounce message to the sender.
- Ask the recipient to search spam, junk, quarantine, and security filtering.
Resolution path
- Inspect the invoice and contact details. Open the original invoice, verify the recipient, and review its history before sending anything again.
- Confirm the invoice is approved and the intended version was sent.
- Check the contact record for an old or misspelled address.
- Use the bounce information. If Xero reports a bounce, distinguish an invalid address from a recipient-mail-server rejection.
- Correct an invalid address before resending.
- For a valid address, have the recipient or their mail administrator allow Xero messages.
- Resend the same invoice safely. Resend the existing invoice or share its online link or PDF through an agreed channel.
- Do not create a second invoice.
- Record the alternate delivery method in the invoice history or internal notes.
- Verify delivery with the recipient. Ask the customer to confirm the invoice number, amount, and due date they received.
- Do not treat an “email sent” status as proof of inbox delivery.
- Escalate repeated domain-wide rejection to Xero and the recipient’s mail provider.
Verify the result
A disappearing error is not enough. Confirm the accounting and workflow outcome:
- The customer confirms receipt of the correct invoice.
- Only one sales transaction exists.
- Any bounce cause has been corrected or documented.
What to avoid
- Creating a replacement invoice to solve email delivery.
- Voiding the original invoice without an accounting reason.
- Sending sensitive financial information to an unverified alternative address.
When to involve product support, IT, or your accountant
Stop making changes and escalate when any of these conditions applies:
- Multiple recipients at the same domain reject Xero mail.
- The address is correct but every resend bounces.
- The invoice contains disputed or sensitive information.
Bring the exact error, screenshots, affected record IDs, timestamps, product version or region, and a description of every change already attempted. That evidence shortens the support path and reduces repeated or conflicting fixes.
Sources checked
First-party product documentation used to verify the workflow and risk notes in this guide.