Settings and activity
2 results found
-
458 votes
Hi team, we appreciate the on-going support and feedback we're receiving on this idea and pleased to be able to share this update. Our product team are actively exploring how we can best solve for the needs raised here, although at this time are unable to provide any set timeframes.
They are very much aware of the appetite from our community on this, and as part of their exploration have reached out some users here as they gather insights.
For the time being we'll shift to In discovery and I'll return as soon as there is more on this to share.
An error occurred while saving the comment 
Austin Smith
supported this idea
·
-
534 votes
Thanks so much for sharing your feedback on this idea, community. We appreciate that having to manually select attachments on every invoice can feel a little fiddly. We get that you want a smoother workflow, that saves you time.
As noted by others in the idea, one option for now would be to add standard files, like your terms and conditions, directly to your invoice template. That way, they'll be included automatically when you send out your invoices.
To confirm how this functionality currently works - this is based on the user and driven by the last invoice that was sent. Where you have files attached, and you had selected to include files as an attachment when emailing the invoice, the next invoice you send with file attachments should have this selected by default.
A caveat to this is when you are working in incognito mode, or refresh your browser…
Austin Smith
supported this idea
·
Thirteen years. This request opened in 2013. The last substantive staff response came in May, "in discovery," no timeframe. That was months ago and there has been nothing since.
I want to address the thing that seems to be blocking this internally, because I suspect the product team is scoping the hard version of the feature when the community is asking for the easy one.
Nobody in this thread is asking Xero to relay through our SMTP servers. I understand why that is a non starter. You would be holding tenant credentials, breaking every time a password rotates or 2FA changes, absorbing async delivery failures you cannot diagnose, losing bounce and open telemetry, and hitting per user send caps on Google Workspace and Microsoft 365. Fine. Decline that version. I would decline it too.
What we are asking for is domain authentication, and it is a materially different piece of engineering:
1. I add my domain in Xero, mycompany.com.
2. Xero generates a DKIM keypair and shows me a selector record to publish, either a CNAME pointing at a Xero hosted key or a TXT record with the public key.
3. I publish that record, plus an SPF include if required, at my DNS provider.
4. Xero validates it.
5. Xero keeps sending from Xero's own infrastructure, Xero's IPs, Xero's queue, Xero's bounce handling, Xero's telemetry. Nothing about your sending architecture changes.
The only difference is that the outbound message is DKIM signed with d=mycompany.com instead of d=post.xero.com, and the From header reads accounting@mycompany.com.
That is it. The signature now aligns with the From domain, DMARC passes on the alignment check, and my invoice lands in the inbox instead of the junk folder.
Every serious transactional sender already does this. SendGrid, Postmark, Mailgun, Amazon SES, Stripe, DocuSign, Zoho. It is not exotic. It is the baseline expectation for any platform sending mail on a customer's behalf in 2026.
The objections I can anticipate, and my responses:
Reputation risk. Yes, tenant domains introduce abuse surface. But you already have that problem in a worse form. There is documented abuse in the wild right now of scammers using Xero's invoicing to send phishing that passes SPF, DKIM and DMARC fully aligned on post.xero.com, because your shared domain is the trusted one. Moving signing to tenant domains contains blast radius rather than expanding it. When a bad actor burns a domain under this model, they burn their own, not the one every paying customer depends on.
Support cost. Real. DNS is where customers get confused. It is also a solved onboarding problem with a validation button and a clear error state, and it is a cost every one of your competitors has already decided is worth paying.
Low demand. This thread is thirteen years old with continuous engagement and multiple merged duplicates. That is not low demand, that is sustained demand that has been outlasted.
Here is where I am. I run a small services company. I invoice organizations that check email on shared admin accounts with aggressive filtering, and several of them have systems that reject or quarantine mail from an address that is not the vendor's actual domain. I have had to follow up individually to ask whether an invoice arrived. That is not a minor inconvenience, that is unpaid receivables and it makes my business look unprofessional because of a platform decision I did not make and cannot work around.
I came to Xero from Zoho Books. Zoho has supported exactly this for years. Add the domain, publish SPF and DKIM, validate, done, and if your domain is not authenticated it transparently falls back to their own sending address. It is a solved problem, shipped, by a competitor at a lower price point.
I am not threatening to leave for effect. I am telling you that I am currently evaluating what it costs me to migrate back, and that the answer is getting smaller the longer this sits at "in discovery." I would rather stay. I would rather this thread get a real update with a real quarter attached to it.