schedule 14-min read

Xero and Accounting Software Invoice Emails and DMARC

DMARC AI editorial team · Last updated

How Xero sends invoice emails, what it means for DMARC alignment and your client’s policy, and what MSPs should check to reduce invoice fraud risk.

01

How do Xero invoice emails interact with DMARC?

Xero invoice emails are sent from Xero's own message service address, message-service@post.xero.com, with replies routed to the reply address in the organisation's email settings. Because the From domain is post.xero.com, DMARC checks Xero's domain, not the client's. As of November 2026, a client's DMARC policy therefore neither breaks nor protects Xero-sent invoices.

That changes the usual third-party sender advice. Most platforms that send "as" a client need SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail) set up on the client domain before DMARC (Domain-based Message Authentication, Reporting and Conformance) can reach enforcement. Xero, today, does not. This guide explains why, what Xero has said about sending from your own domain, how two other accounting platforms handle it, and what an MSP (managed service provider) should check in a client's aggregate reports. The general approach to outside senders is in how to handle third-party senders during DMARC projects, and the protocol basics are in the DMARC guide.

02

Key takeaways

  • As of November 2026, Xero sends invoices, quotes and other customer emails from message-service@post.xero.com, so DMARC is evaluated against post.xero.com, which publishes a p=reject policy.
  • Moving a client domain to p=reject does not stop Xero invoices being delivered, because the client domain is not in the From header.
  • Sending from your own domain is listed as "In development" on Xero's product ideas site, with no release date. Plan for new DNS records when it ships.
  • Invoice and mandate fraud usually exploits compromised or spoofed email, not the accounting platform. DMARC at p=reject on the client domain blocks exact-domain spoofing of the finance team.
03

How does Xero send invoice and quote emails today?

Xero sends customer emails through its own message service. The long-running request on Xero's product ideas site asks for emails to "appear as @company-name.com instead of message-service@post.xero.com", and Xero's staff responses confirm that emails come from the message service, with replies going to the reply address set in email settings.

In practice that gives each Xero email three identities that matter for authentication:

Header or field What it contains with Xero today Used by DMARC?
From address message-service@post.xero.com Yes, this is the domain DMARC protects
Reply-To The reply address from the organisation's email settings, often accounts@example.co.uk No
Envelope sender (Return-Path) Set by Xero's sending service; check a real header Only for SPF alignment with the From domain
DKIM signature Whatever Xero's sending service applies; check a real header Only if d= aligns with the From domain

The display name and the exact Return-Path can vary, so check a real message rather than assuming. Xero's email settings article on Xero Central is where the reply address is configured.

You can see the domain policy that applies with a simple lookup:

dig +short TXT _dmarc.post.xero.com

On Windows, use Resolve-DnsName -Type TXT _dmarc.post.xero.com. A lookup we ran in November 2026 returned a record with p=reject. That policy belongs to Xero and is managed by Xero; the client cannot change it.

04

Why does a client's DMARC policy not affect Xero invoices?

DMARC only applies to the domain in the visible From header. RFC 9989, the current DMARC standard, ties the policy lookup and alignment checks to that RFC5322.From domain. Since Xero's From domain is post.xero.com, receivers look up Xero's DMARC record, not the record at _dmarc.example.co.uk.

This has three consequences for MSPs:

  1. Xero is not a blocker for enforcement. A client can move from p=none to p=quarantine to p=reject without any Xero-specific SPF include or DKIM record, as long as Xero keeps its current sending model.
  2. Xero mail does not appear in the client's aggregate reports. Aggregate (RUA) reports are grouped by From domain. Xero-sent invoices are reported to Xero, not to the client.
  3. Do not add Xero to the client's SPF record "just in case". It adds DNS lookups without changing any DMARC result. RFC 7208 limits SPF evaluation to 10 DNS-querying mechanisms, so unnecessary includes cost you headroom.

If a client insists that "Xero emails fail DMARC", ask for the full headers of one message and paste them into the email header analyzer. In most cases the message either passed for post.xero.com or was not sent by Xero at all.

05

What has Xero said about sending from your own domain?

Xero has said it is building the feature but has not given a date. On 12 March 2026 the request moved to "In discovery", and on 21 October 2026 Xero changed the status to "In development", writing: "We've made meaningful progress towards enabling email sending from your own domain."

The same update says "substantial backend work is underway" and that there are "important steps we need to work through" before release. Xero also asked users whether only administrators should manage custom email domain settings and whether the same domain should be usable across several Xero organisations. Earlier, in October 2023, Xero had said the capability "requires extra steps outside of Xero for customers to enable". Read the full history on the Xero product ideas page.

Nothing on the page specifies record types, so do not prepare DNS changes in advance. When the feature arrives, check the current Xero Central documentation for the exact records.

What should an MSP prepare for when own-domain sending arrives?

Prepare a short change process so the first client to enable it does not break DMARC. The client's domain will move into the From header, which means the client's DMARC policy suddenly applies to Xero mail and Xero will appear as a new source in the client's aggregate reports.

Questions to answer for each client before switching it on:

  • Who owns DNS? The MSP, the client, a web agency or the accountant. Someone has to publish the records Xero asks for.
  • Which records are needed? If Xero uses DKIM with a d= value on the client domain, DMARC can pass on DKIM alone. If it asks for an SPF include, check the lookup count first.
  • Which domain or subdomain? Sending invoices from the main domain puts them under the main policy. A dedicated subdomain such as invoices.example.co.uk isolates them, but customers may find it unfamiliar.
  • Who in the client can change it? Xero's own question about admin-only management suggests the setting may be widely accessible. Agree who can turn it on.
  • Is the client already at p=reject? If so, verify aligned DKIM with a test invoice before anyone sends a real one, or invoices may be rejected.
06

How do other accounting platforms handle invoice emails?

Other platforms differ, so check each one in the client's stack instead of assuming they behave like Xero. Two UK-relevant platforms document their approach clearly in their own help centres.

Platform Default From address Own-domain option What it means for the client's DMARC
Xero message-service@post.xero.com "In development" as of November 2026 No effect today
FreeAgent A FreeAgent address Yes, a custom email domain verified with DNS records Applies once a custom domain is added
Sage Accounting (UK) A Sage no-reply address that cannot be changed Not described No effect; replies go to a verified reply address

FreeAgent

FreeAgent lets a business authorise it to send from its own address. Its support article describes adding a custom domain under Settings, then publishing DNS records shown in the app: an informational TXT record and a validation key record. FreeAgent checks them before the domain is accepted.

FreeAgent says an SPF entry is generally not needed unless the domain's SPF record already ends in -all. Addresses on Gmail, Yahoo and similar consumer domains always use the default FreeAgent address. If the records are later removed, FreeAgent reverts to its default address. For MSPs, this means a FreeAgent custom domain is a sending source on the client domain and should appear in aggregate reports. Confirm in the reports that it passes DMARC through aligned DKIM before p=reject.

Sage Accounting

Sage's UK knowledge base article on email defaults states that documents go out from a Sage no-reply address that "you can't change". Replies go to the registered account email by default, and a different reply address can be set and verified with a code. Like Xero today, this model leaves the client's DMARC policy untouched.

For any other accounting or credit control tool, look for three things in its official documentation: the From address it uses, whether it offers a verified custom domain, and which DNS records that requires.

07

How does invoice fraud relate to DMARC for UK SMBs?

Invoice fraud is a payment diversion scam: the victim tries to pay a genuine supplier, and a criminal redirects the payment. UK Finance's Annual Fraud Report 2026 recorded 2,305 invoice and mandate scam cases and £41.3m in losses in 2025, with £28.0m on business accounts.

The same report says this fraud "often involves the criminal either intercepting emails or compromising an email account". The NCSC's business payment fraud guidance describes the same pattern, also called business email compromise (BEC): criminals impersonate someone you correspond with regularly and ask for money to be sent to a different account.

DMARC helps with one part of that picture. With p=reject on example.co.uk, a receiver that honours DMARC will reject a message that claims to be from accounts@example.co.uk but fails authentication. It does not stop:

  • Lookalike domains, such as example-co.uk or examp1e.co.uk.
  • A compromised mailbox, because mail from a hijacked Microsoft 365 or Google Workspace account passes DMARC.
  • Messages from a shared platform address. Every Xero customer's invoices share the same From domain, so a DMARC pass for post.xero.com proves Xero's platform sent the message, not which business did.

That last point matters for client training. A real Xero invoice and an invoice sent by an attacker with their own Xero organisation would both pass DMARC for post.xero.com. Staff should treat any change of bank details as a separate verification task, using a phone number they already hold. The wider leadership view is in business email compromise and DMARC.

Can attackers abuse the reply address?

Yes, if they gain access to the Xero organisation. The reply address in email settings decides where customer replies land, so anyone who can change it can intercept payment queries. Protect Xero logins with multi-factor authentication, keep the user list current, and review email settings during client onboarding and offboarding.

08

What should MSPs check in aggregate reports for finance email?

Focus on the sources that really send as the client domain, because Xero mail will not appear there today. Aggregate reports show every IP and service that sent mail using the client's From domain, so anything unexpected around invoice season deserves a look.

What you see in the client's reports Likely cause Action
A source labelled as Xero under the client domain Own-domain sending enabled, or a misread source Confirm in Xero settings; check DKIM d= alignment
FreeAgent or another accounting platform failing DMARC Custom domain added but DKIM records missing or removed Republish the records from the platform's settings
A credit control or reminders add-on failing alignment The tool sends as the client domain with its own signing domain Set up its documented DKIM option or move it to a subdomain
Microsoft 365 or Google Workspace passing, high volume from finance Staff sending exported invoice PDFs from their own mailbox Normal; no change needed
Unknown IPs failing SPF and DKIM with the finance address Spoofing attempts Confirms the value of enforcement; move policy forward

Check the published record first with the DMARC checker. Then look for these signals across the portfolio:

  1. New sources after a client changes accounting software. Migrations often bring a new sender with it.
  2. Alignment failures on DKIM-only senders. A platform signing with its own domain passes DKIM but fails DMARC alignment; see DMARC alignment explained.
  3. Failing volume from unknown sources around month end, which is when invoice impersonation is most convincing.
  4. Subdomains used for invoices without their own policy. RFC 9989 adds the np tag for non-existent subdomains, and the tree walk now finds the organisational domain policy without the public suffix list.

DMARC AI processes the aggregate reports and uses AI to classify sending sources, which helps spot a newly added invoicing platform across many client domains.

09

How should an MSP move a client to enforcement with accounting platforms in mind?

Move one policy step at a time and treat each accounting tool as a named item in the sender inventory. Under RFC 9989, the percentage tag is gone, so the rollout is p=none, then p=quarantine, then p=reject, with the t=y testing flag available to signal a trial.

A record for a client whose invoices come from Xero and whose staff use Microsoft 365 might end like this:

_dmarc.example.co.uk. TXT "v=DMARC1; p=reject; np=reject; rua=mailto:dmarc@example.co.uk"

Before each step, run through this checklist for the client:

  • List every finance platform: accounting, payroll, payments, credit control and statements.
  • Record the From address each one uses today, from a real message header.
  • Note which ones send as the client domain and confirm aligned DKIM for each.
  • Leave Xero out of SPF while it sends from post.xero.com.
  • Record who owns DNS and who can change sending settings in each platform.
  • Agree a payment verification process with the client's finance team.
  • Recheck when Xero releases own-domain sending.

The full rollout method is in how to move from DMARC monitoring to enforcement safely, and the vertical view is in DMARC for SaaS companies.

10

FAQ

Do I need to add Xero to my SPF record?

No, not as of November 2026. Xero sends from message-service@post.xero.com, so SPF and DMARC are evaluated for post.xero.com, not your domain. Adding a Xero include to your SPF record changes nothing in DMARC and uses up DNS lookups. Revisit this when Xero releases sending from your own domain.

Will p=reject on my domain stop Xero invoices being delivered?

No. Receivers apply the DMARC policy of the From domain, which for Xero invoices is post.xero.com. Your own policy applies only to mail that uses your domain in the From header. Xero invoices can still land in junk for other reasons, such as content or reputation, but not because of your DMARC record.

Why do Xero invoices not appear in my DMARC reports?

Aggregate reports are sent to the owner of the From domain. Xero invoices use post.xero.com, so receivers report them to Xero. If you see a Xero source under your own domain, someone may have enabled a custom sending domain, or a different tool is sending on your behalf. Check the headers of a sample message.

Can DMARC stop fake invoices that come from Xero?

No. A fake invoice sent through any Xero organisation passes DMARC for post.xero.com, because Xero really sent it. DMARC proves the platform, not the business behind it. Protect customers by verifying bank detail changes by phone, securing Xero logins and enforcing DMARC on your own domain against direct spoofing.

Does FreeAgent work differently from Xero?

Yes. FreeAgent lets a business add a custom email domain verified with DNS records shown in its settings, after which invoices are sent from the business address. That puts the client's DMARC policy in charge, so check aggregate reports for FreeAgent passing with aligned DKIM before moving to p=reject.

Related articles

Related tools

Ready to Implement?

Get authenticated mail moving in minutes: start free, book a guided demo, or talk to the team about your stack.