Enter your idea

Thanks for the update. This feature cannot come soon enough. To answer your questions:

1. Just Admins
2. Yes
3. Not at this time, low priority feature.

I'm so glad to hear there is progress. Spam filtering of Xero emails has gotten so bad that we have gone back to downloading the invoices from Xero so we can manually email them as attachments to our customers. For us, what's most important is that your solution works with Google Workspace as that's how our organization manages our email. Obviously Microsoft and other providers will be critical for other users. What we don't want is a situation where we have to delegate Xero as our domain mail server and/or where Xero tries to send the mail (from us) through their servers, as those will still get spam filtered. We want to configure Xero to send through our existing mail infrastructure. You can look to many CRM and similar SaaS software for examples that handle this mail integration well. Regarding your specific questions:

* Limiting the settings to Administrators seems simplest and works well for us.
* Our domain has many mailboxes, but we would be fine with using just one (sales@ourdomain) for outgoing Xero emails.
* If we had more than one Xero organization (and we might in the future), we would prefer that each could specify their own domains.

Thanks for actioning this. We were close to losing hope with Xero.

Within your Xero account would you want multiple Users to be able to manage custom email domain settings, or just Administrators?
Admin Only

Does your domain have more than one mailbox associated with it?
Yes

Would you want to use the same domain across more than one Xero organisation?
Not at this time, but would appreciate the functionality as an option.

Within your Xero account would you want multiple Users to be able to manage custom email domain settings, or just Administrators?
• Admin only

Does your domain have more than one mailbox associated with it?

• Yes, quotes should come from sales@ while invoices, statements etc accounts@ anything internal like Expenses can also be from accounts@

Would you want to use the same domain across more than one Xero organisation?

• We only have one org, so not needed for us.

I agree this should not be complicated. Unfortunately, this discussion has become unnecessarily complex and moved beyond the actual request.

**The request is simple: Each Xero organization should be able to configure its own authenticated email domain for invoices, statements, and payment reminders.**

This should be an organization-level setting, not tied globally to a user's account. Users managing multiple organizations should have separate sending addresses for each business.

**This is established industry practice, not new technology.**

Zendesk, Salesforce, HubSpot, Microsoft 365, SendGrid, and Amazon SES already support authenticated business-domain email delivery in various forms.

SPF, DKIM, DMARC, and domain verification are established standards. Configuration should involve entering the sending address, verifying domain ownership through DNS, and saving.

**Cybersecurity and customer expectations have changed.**

As an IT services provider, we train clients to identify phishing, fraudulent invoices, and suspicious financial communications. A fundamental recommendation is verifying the sender's domain before processing invoices or clicking payment links.

Yet Xero's approach creates exactly the situation we teach customers to question.

A customer expecting an invoice from a recognized business domain instead receives one from an unfamiliar Xero domain. They may delete it, report it as phishing, or delay payment.

**We should not have to choose between cybersecurity best practices and successfully delivering invoices.**

**Bad actors can potentially create legitimate Xero accounts to distribute fraudulent invoices.**

A malicious actor could create a Xero organization impersonating a legitimate business and send fraudulent invoices through Xero's infrastructure.

These emails may pass SPF, DKIM, and DMARC authentication despite being fraudulent.

**Email authentication verifies authorized sending infrastructure, not the legitimacy of the business or invoice.**

I am not suggesting Xero lacks fraud prevention controls. However, legitimate platforms can be abused before malicious activity is identified.

When legitimate and fraudulent organizations use the same platform domain, recipients have fewer ways to distinguish trusted communications.

Using verified business domains adds an identity verification layer. It does not eliminate fraud but improves security.

**This raises questions about security responsibility and potential liability.**

When Xero requires businesses to use its email infrastructure, Xero controls a critical component of financial communications.

What happens if Xero's infrastructure is compromised or fraudulent invoices are distributed through its platform? Who is responsible if security failures contribute to financial losses?

**If Xero requires customers to use its infrastructure, it must recognize the associated security responsibilities.**

Legal liability depends on applicable laws, contracts, and circumstances. Customers deserve clarity about Xero's responsibilities when using infrastructure they cannot control.

Allowing businesses to authenticate their own domains creates clearer shared responsibility. Businesses manage their domains and authentication; Xero remains responsible for securing its platform.

**Businesses should control their email identity rather than having Xero make that decision for them.**

As an IT services provider, I implement SPF, DKIM, DMARC, and phishing prevention for clients. Yet Xero limits our ability to apply those same controls to financial communications.

**The requested solution is straightforward:**

1. Configure a sending address for each organization.
2. Verify domain ownership through DNS.
3. Support SPF, DKIM, and DMARC alignment.
4. Automatically use the correct authenticated domain.
5. Retain Xero's default email service as an option.

We are not asking Xero to become an email hosting provider, only to support an established capability.

**I would appreciate direct answers from Xero:**

1. Does Xero support authenticated outgoing domains per organization?
2. If not, is this planned, and when?
3. If not planned, what is the justification?
4. What responsibility does Xero accept if its infrastructure or security controls fail and contribute to financial losses?

I am not looking for forwarding instructions, Outlook workarounds, or third-party automation.

**This is not simply branding. It is a cybersecurity, deliverability, and accountability issue.**

Why is authenticated, organization-specific email identity not considered a fundamental requirement for a modern financial platform?

I would appreciate a direct response from Xero's product development team addressing this request rather than continuing to complicate an established industry practice.

Within your Xero account would you want multiple Users to be able to manage custom email domain settings, or just Administrators? - Just administrators.

Does your domain have more than one mailbox associated with it? - Yes

Would you want to use the same domain across more than one Xero organisation? Possibly

1)Within your Xero account would you want multiple Users to be able to manage custom email domain settings, or just Administrators?
- only admin for us, though I do understand why a larger team might want to allow an IT person or 3rd party contractor to manage email settings without accessing financial details.

2) Does your domain have more than one mailbox associated with it?
- per person and role-based
- we would send from one role-based company email
- can provide valid SMTP info if needed, or Google Workspace integration

3) Would you want to use the same domain across more than one Xero organisation?
- Yes, our American and Canadian companies use the same domain

+1 to what Jonathan said: "what we need is a way to authenticate our domain with DNS records (DKIM, SPF) so we can simply choose our own service to send the emails. Any mid-sized business who need this stuff can set this up in 5 minutes with their IT company."

Beyond that, just let me use my own SMTP! No DNS required. Works with any service.
- Google Workspace with an app password
- AWS
- SMTP2GO (or any 3rd party SMTP)
- literally any email service that offers password-based SMTP

Just let us fill in the fields and we're golden.

Finally! Good news.

1. Administrator only
2. Yes, per person and shared mailboxes
3. No, one domain per Xero organisation only.

Yes I agree with Perry,

Questions are a bit strange.

1) Obviously admin
2) Yes, of course. I mean, any mid-sized business has more than one email address.
3) No, the setting has to be at the company level. If I separated my business in different organisation, there's a 95% chance they are different company - using different email.

But, really, what we need is a way to authenticate our domain with DNS records (DKIM, SPF) so we can simply choose our own service to send the emails.

Any mid-sized business who need this stuff can set this up in 5 minutes with their IT company.

While I'm cautiously optimistic about this update, I'm not convinced this will happen in my lifetime. The questions being asked are part of the reason why, and it kind of shows that Xero doesn't seem to grasp the problem at hand.

The domain authentication would apply to any number of emails being used. It's simply authorizing Xero to send an email through our mail server and nothing more. It has nothing to do with the number of email addresses used, and it has nothing to do with the number of people who might send emails. That's a completely separate issue that's a new feature and shouldn't be involved in this.

The fix here is literally a day's work for a reasonably good programmer to implement. It is not complicated, but once again Xero is overthinking it. Stop doing that.

If a Xero account has more than one company, then the domain setting should live at the company level, not the account level. That is, If I have Company X and Company Y, and they have different domain names, then there should be a setting for each one. Put this in the company settings and make it editable by admins only.

Number of email addresses is irrelevant. That's a separate question/feature.

Thank you for at last applying yourselves to something useful which people have been asking for for years, instead of more AI guff which nobody asked for.

Within your Xero account would you want multiple Users to be able to manage custom email domain settings, or just Administrators?

Adminstrators only

Does your domain have more than one mailbox associated with it?
Yes. It would be good to be able to use different sender addresses with different template sets, to maintain brand identity.

Would you want to use the same domain across more than one Xero organisation?
Potentially, yes!

Thank you for providing an update - this is something we have wanted for a very long time and is a critical step towards having Xero as a one solution platform.

1. Admin only, to keep the control in place.

2. We have multiple mailboxes on our domain but would want to send it from our accounts@domain.com email.

3. Yes, a different email for each different organisation to keep things very separate (as each organisation is a different legal entity).

We have different accounts emails for each organisation on each domain, it would be great that they have accounts@org1.com sending emails from org 1 and accounts@org2.com sending emails, chasers and invoices from org 2.

This is a very important issue for us and I'm sure many other users so would be helpful to have regular updates.

Thank you for finally providing an update.

1. Admin only

2. Strange question. We'd setup authentication (DKIM) on the whole domain. It would be helpful to be able to set the from and reply-to addresses in various locations (e.g. email templates), with a default value configured on the Xero org.

3. Potentially. Please add support for this. I've had issues in the past with Atlassian services when I couldn't authenticate my domain with different products of theirs as they used the same DKIM DNS names (but different values). Suggest adding some form of Xero org ID into the DKIM DNS record name.

Finally, please can you keep us updated on a regular schedule, e.g. every 2 weeks. Without that we have no way of knowing if this is actually progressing again or being ignored. Thanks.

1. Admin only.

2. We have multiple mailboxes, but we would only send Quotes/Invoices via one mailbox. However, it would be a different mailbox from the one the user is logged in to in Xero, so we need some flexibility. E.g. I'm logged into Xero as tom@, but invoices might be sent from admin@.

3. We only have one Xero organisation.

1. Who should manage custom email domain settings?
Admin only

2. Does your domain have more than one mailbox?
Yes, but we'd only need one email address at our domain for Xero to send from. I would like the ability to choose what email address that is rather than it using the email address of the Xero user logged in, so all invoices/statements no matter which Xero user sends them come from a consistent email address e.g. accounts@mydomain.com

3. Would you want to use the same domain across more than one Xero organisation?
Not needed for us now. But I can see that would be useful for others, and perhaps us in future.

Setup suggestion: 1) Administrator enters domain and sending email address in Xero. 2) Xero presents some DNS records for SPF and DKIM records to customer. 3) Customer enters those DNS records on their domain to authorise Xero to send mail from customer's domain. 4) Xero validates the DNS records.

We've built a similar setup for our Stantia CRM system utilising SendGrid API which provides the email sending as well as DKIM-related process.

1. Admin only
2. Yes. More importantly, we trade under three different brands, and it would be better if we could register more than one domain.
3. We only have one Xero organization at the moment, but this could change so the provisional answer would be yes.

1. Who should manage custom email domain settings?
Administrators only. Custom domain configuration is not a day-to-day user function and should sit in the settings at the Xero account/organisation level, restricted to Admins.

2. Does your domain have more than one mailbox?
Yes. Private domains often have multiple mailboxes (we use Office 365). To be clear, we’re not asking for an Office 365 integration. We simply want the ability to send from our domain through an SMTP relay service such as SMTP2Go, which already handles SPF, DKIM and DMARC compliance on our behalf.

3. Would you use the same domain across more than one Xero organisation?
Yes. We’d like to use the same domain across our Xero organisations. We also expect many other Xero customers will want the flexibility to set a different domain per organisation, so both options should be supported.

1. Just Admins - Why on earth do you have to ask this??
2. Odd question - But - One sending account, accounts@domain.com - But multiple receiving accounts.
3. One domain per organisation.

@Adam Romain - I do not understand why you would assume that larger companies do not use cloud email. Even if it were the case, even small companies suffer from the same issue of invoices being marked as spam.

We have an annual turnover of nearly £1m. We choose to use Google workspace, albeit with our own domain name, as it suits our 24/365 operation. After 40 years in IT, I am quite capable of following instructions on how to setup DKIM and SPF.

However, evan small companies, using cloud email, deserve to have an email system that does not predispose their invoices to being marked as SPAM.

1. Admin only
2. Yes and I would like the ability to register which email address is being used for which template rather than the current using the email of the logged in person.
3. Not personally but maybe some people will.

1. Admins only.

2. We run multiple brand names from the one company, so the ability to configure and use different domains/emails per Xero template would be needed.

3. We don't need to use the same domain across more than one Xero organisation, although we have a client who would as they have a group, 6 companies worldwide (each country it's one Xero account) but use the same domain for all countries.