This feature should have been implemented years ago. What is the point of having a quote or invoice system if we can't be 100% sure emails will be delivered?
The current recommendation from support—to ask clients to safelist Xero or allow specific IPs—is not scalable or practical. For larger corporations (e.g., 1,000+ employees), working through their IT departments is often slow or unfeasible. For small businesses, the technical know-how is often lacking.
A more practical solution would be to allow us to use our own sending domain for invoices. This would let us configure DKIM and SPF authentication ourselves, eliminating the need to walk each client through technical email settings.
This approach would also shift deliverability responsibility to us, reducing Xero's support load.
It’s a win-win:
Clients reliably receive invoices.
We have full control and visibility over email deliverability.
Jonathan Fortin
supported this idea
·
This feature should have been implemented years ago. What is the point of having a quote or invoice system if we can't be 100% sure emails will be delivered?
The current recommendation from support—to ask clients to safelist Xero or allow specific IPs—is not scalable or practical. For larger corporations (e.g., 1,000+ employees), working through their IT departments is often slow or unfeasible. For small businesses, the technical know-how is often lacking.
A more practical solution would be to allow us to use our own sending domain for invoices. This would let us configure DKIM and SPF authentication ourselves, eliminating the need to walk each client through technical email settings.
This approach would also shift deliverability responsibility to us, reducing Xero's support load.
It’s a win-win:
Clients reliably receive invoices.
We have full control and visibility over email deliverability.
Fewer support tickets for Xero.