Enter your idea

Using our own domain, with SPF/DKIM when sending really needs to be implemented.

We've had months of client's invoices not being received or put into spam without us knowing, only when we chased missing payments did we find this out was the norm. Severly affected our cashflow as you can imagine.

We've given up sending any correspondence through Xero now and had to resort to printing the invoice or statement as a PDF then manually emailing it, then marking it as send in Xero. Made a big difference to our cashflow, but also costs us a few more hours each week in manual work, not helpful.

We face constant issues getting invoice emails seen by our clients. This is not a huge undertaking. Most outfits are used to adding SPF/DKIM records for things like Shopify, Zendesk, and other platforms that have supported this for some time. This is the only platform in our stack that forces email from a domain other than ours. We will HAPPILY beta test this if you decide to implement it.

The requirement is slightly different - people want to connect their domains, not just send from their own email.

Emails sent from the Xero domain are not properly identified and therefore likely to be treated as spam by the large platforms (Google, Microsoft).

It concerns me that Xero doesn't appear to understand the requirement fully, let alone recognise the priority that needs to be given to it.

I guess they are concentrating their "development" efforts on popular sounding (but useless) features like Jax they can use as argument to increase prices by 10% every three months... It's time a competitor enters the market to shake up the duopoly of Quickbooks & Xero... they lost every incentive for innovation. Just milking customers.

It's a joke that every startup dashboard/client portal/B2B app around can support this as table stakes, yet a mature accounting product can't figure it out in 12 years. This should be embarrassing for you.

Hi @Kelly Munro, is there somewhere we, as users, are able to see the ideas that are in progress and on the backlog?

There are a number of critical requirements that I follow which don't appear to have been prioritised and that cause much frustration with users. Maybe if we had visibility of the priorities it would help.

I know from my perspective I would have prioritised, this, the user roles, mass deletion of unused contacts and multiple email addresses for contacts above the AI functionality that has been added.

Clearly it's more important to spend their developer time on features like this "JAX" icon which has appeared, which nobody asked for and I suspect few people want. That way they can say "we've got AI".

Why has this still not been addressed? It is really unprofessional and is a security issue to not have this capability.

This is still desperately needed.

It's surprising that Xero hasn't integrated this feature into their core code, especially since their message-service@post.xero.com email is currently being exploited to send spam with malicious payloads. The code I developed interacts with Xero's API when invoices are authorised. It requests the PDF, attaches it, and includes a link in the email with text that closely resembles the standard Xero template. The email is then sent using an App Registration in your Microsoft 365 tenant.

The process is straightforward. Anyone interested in using it will need to have Microsoft 365 (business, not personal). While I still need to write the web server setup guide, the setup for Xero and M365 is already complete. The setup is simple, and I've reviewed the AI-generated code thoroughly; everything looks fine (I have extensive experience with open-source projects).

I used AI to create the software to test its feasibility and effectiveness. As with all software, there are no guarantees it will be bug-free (please refer to any software's terms and conditions). However, after extensive testing, I am confident enough to release it to the community.

What can be more important than your users avoid their quotes & invoices being caught up in spam filters?

Would you explain exactly what is more important? All I have ever seen is an almost identical load of fluff about some mythical "Other Stuff" being more important

Xero, please listen to your users and implement requests that they ask for.

This has been requested for years and you are ignoring these requests, A couple of companies have jumped in and are offering a paid for service that does what users have been asking the core system to do for years.

I wrote a very simple web app that solves the issue simply using AI, I have tested and I'm offering this to the community at no charge.

Xero please feel free to let me know if you would like to implement the code into your core system, its written in ASP.NET Core 8 C#.

For any other Xero users please feel free to reach out with your contact details and I will be more than happy to share the compiled code and install instructions. You will need a hosting package that supports ASP.NET Core 8 (most providers do), I'm happy to assist with the hosting if needed otherwise you can use your own provider.

For the time being I have only written this to send emails via an App Registration in Microsoft 365, If anyone wants this for Google Enterprise please let me know as it should be a simple change or addition in the code.

@Richard Fincher:

Submit a support request. Every time you have a problem, comment on that thread. They seem to be obligated to reply. You will get unsatisfying answers but if you ask to escalate the problem eventually you seem to get to people who can do something. That has been my experience with other issues.

Squeaky wheel...

This conversation is starting to sound a bit like a car-dealer talking up a car's Bluetooth and Air-con features whilst ignoring the fact that one of the wheels is missing. I think we need to know the name of the responsible individual decision maker here. At present, we're (occasionally) being replied to by a gate-keeper.

"Clients are insisting we block the address (we are their IT), but that will block our own invoices."

Yup. 100% this is the problem Xero is ignoring. They told me I should tell our clients who have blocked Xero emails for the same reason, that they should unblock them. That's not an acceptable solution. I shouldn't have to go to all my clients and ask them to allow phishing emails through because a small percentage of emails from the same address might be our legitimate invoices.

This needs to be addressed ASAP. It's clearly not hard since there are third party services who have figured this out. Come on, Xero. Divert an afternoon's worth of programming time to this. That's all it takes.

A client got the below today from Xero, clearly spam / fraud.

Clients are insisting we block the address (we are their IT), but that will block our own invoices.

From: messaging-service@post.xero.com <messaging-service@post.xero.com> on behalf of T͏e͏s͏l͏a͏ Recruitment Team <messaging-service@post.xero.com>
Sent: 27 June 2025 08:59
To: ***************************************
Subject: Social Media Manager Opportunity at Tesla

If when have to pay for a third-party resolution for these emails to be sent out correctly, will Xero be refunding us the amount since they are unable to accommodate such as simple and popular request?

Microsoft will no longer support Basic Authentication after September 2025. Wordpress websites may no longer rely on PHP for enquiry forms. A plugin like WP SMTP Pro is required for Microsoft 365 email. Domains without the SPF, DKIM and DMARC records setup correctly will already have an unreliable email services.

It is vital that my company has access to this feature as your system limits the number of email contacts.

SMTP has got to be one of the simplest, most widely available solutions in the world. It would take xero 1 day to build and make everyone happy.

Not buying the excuses. This is low hanging fruit, guys.

Off to make.com to hack my own solution. Grr.