How to Send Invoices from Your Own Email Address

Why invoices from yourbusiness.com.au get paid faster than the same invoice from Gmail — and how to set it up in under 15 minutes.

Quick answer

Sending invoices from your own email domain (e.g. invoices@yourbusiness.com.au) instead of a generic free address or your invoicing app’s shared sender massively improves deliverability and reduces the chance of an invoice landing in spam. Setup takes about 15 minutes: own a domain, add SPF and DKIM DNS records, and verify in your invoicing app’s settings. After that, every invoice email arrives as if you sent it personally from your business address.

Why this matters

Email deliverability sounds technical but the impact is purely commercial:

  • Invoices land in the inbox. Custom-domain emails pass SPF, DKIM, and DMARC checks for your domain, which is what mail servers use to decide spam vs. inbox. Generic free-tool senders fail one or more of these checks at scale.
  • Clients pay faster. An email from jane@janesmithdesign.com.au arrives, is recognised, and gets actioned. An email from a Gmail address with the invoicing platform’s domain in the From header is more likely to be ignored or forwarded to a procurement queue that takes a week.
  • The brand is consistent. If your website is yourbusiness.com.au, your invoices should be too. Clients (or their bookkeepers) notice the mismatch.
  • Reply-To works as expected. When the client clicks Reply, the email goes to you, not to a shared support address routed somewhere.

What “sending from your own domain” actually means

A few things to get straight, because most invoicing tools blur the line:

  • Free tier on most tools: the email arrives showing your name, but the underlying sender is the platform. The From header shows “noreply@theapp.com on behalf of Your Name” or similar.
  • Custom sending domain: the email is genuinely sent from your domain. The From header is invoices@yourbusiness.com.au with no “on behalf of”. SPF/DKIM checks pass for your domain, not the platform’s.
  • SMTP relay: a related but heavier option where you connect your existing Gmail/Outlook account directly. Useful if you want sent invoices to appear in your normal Sent folder.

The custom sending domain option is the right answer for most sole traders — cleanest setup, best deliverability, easy to manage.

The setup, step by step

The flow is the same across most invoicing tools:

  1. Own a domain. If your business is “Jane Smith Design”, register janesmithdesign.com.au with an auDA registrar (Crazy Domains, VentraIP, and others all offer .com.au registrations from around $15/year).
  2. Decide on your sending address. Common choices: invoices@,hello@, billing@, or your name jane@. invoices@ is the clearest signal of what the email contains.
  3. In your invoicing tool, add the domain and copy the SPF, DKIM, and (sometimes) DMARC records it generates for you.
  4. Open your DNS provider (the registrar where you bought the domain) and add the records. Usually one TXT for SPF, two CNAME for DKIM, sometimes one TXT for DMARC. The tool gives you the exact values.
  5. Verify in the tool. Most invoicing apps check the records and confirm verification within a few minutes. DNS can sometimes take up to 24 hours but usually propagates much faster.
  6. Send a test invoice to yourself from a different email account. Check the From, the Reply-To, and that it lands in the inbox.

The DNS records, explained

Three records do all the work. You don’t need to deeply understand them, but it helps to know what each one does:

  • SPF (Sender Policy Framework). A TXT record listing which servers are allowed to send email as your domain. Without SPF, anyone can spoof you, and mail servers know it.
  • DKIM (DomainKeys Identified Mail). Cryptographic signature attached to outgoing emails. Mail servers verify the signature to confirm the email genuinely came from your domain and wasn’t tampered with in transit.
  • DMARC (Domain-based Message Authentication). Tells receiving mail servers what to do when SPF or DKIM fails: deliver anyway, quarantine, or reject. Strongly recommended once you’re set up.

Full deliverability explanation in why are my invoice emails going to spam.

What changes after setup

Once your custom sending domain is live:

  • Invoice emails arrive with From: invoices@yourbusiness.com.au.
  • Clients see your domain in every part of the email — From, Reply-To, message headers.
  • Replies go to you. You can configure where: a Gmail forward, a shared inbox, your normal business email.
  • Spam rates drop sharply. The biggest single deliverability lever for sole traders.
  • Branding stays consistent across your website, business cards, and outgoing invoices.

Common setup mistakes

  • Adding the SPF/DKIM records to the wrong domain. If you have multiple domains, make sure you’re editing the DNS for the one you’ll be sending from.
  • Including the domain twice in the record value. Some DNS UIs append your domain automatically; others expect you to type the full record. Check the verify step error message.
  • Forgetting to wait for DNS propagation. Most edits propagate in minutes but can take up to 24 hours. If a verify fails, wait an hour and retry.
  • Setting up DMARC too aggressively. Start with p=none (monitor only). Move to p=quarantine once you’ve confirmed all your legitimate email passes. Going straight to p=reject can bounce real mail.

Does this replace my email account?

No. A custom sending domain in your invoicing tool only handles outbound invoice email. To receive replies and use the address for general business email, you still need a regular email account on the domain (Google Workspace, Microsoft 365, or your registrar’s included email). Two common setups:

  • Pure invoicing. Use invoices@ as a send-only sending address. Replies forward to your existing personal Gmail. Cheapest, no extra mailbox.
  • Full business email. Set up Google Workspace ($8.40/user/month) on the domain and use jane@ as your business email everywhere — including for invoices. Most professional setup; pays for itself if you do any client work.

Pricing context

Custom sending domains are a paid-tier feature on every invoicing platform that supports them — the platform has to pay for the email-sending infrastructure and the deliverability monitoring. Free Invoice App includes custom sending domains on Pro+ alongside per-service T&Cs, expense tracking, and scheduled send. Compare with Xero’s and MYOB’s pricing in Free Invoice App vs Xero and Free Invoice App vs MYOB.

How Free Invoice App handles this

On Pro+, you add a custom sending domain by pasting your domain into a setup screen and copying the three DNS records into your registrar. Free Invoice App verifies the records and switches outbound email to your domain. Every invoice from then on arrives as if you sent it yourself from invoices@yourbusiness.com.au. Pricing details on the pricing page, or create a free account first and upgrade once you’re ready.

Frequently asked questions

Why don’t my invoice emails come from my own address?

Most tools use a shared sending domain so they can authenticate the email. To send from your own domain, you need to configure a custom sending domain on the paid tier.

What’s a custom sending domain?

A setup that lets the invoicing platform send email as if it came from your own domain — passes SPF/DKIM checks, lands in the inbox.

Does sending from my own domain reduce spam?

Yes — significantly. Generic shared domains used by free tools regularly fail authentication checks.

How do I set up a custom sending domain?

Add a few DNS records (SPF TXT, DKIM CNAMEs, optional DMARC TXT) on your registrar. Setup takes 10–15 minutes; propagation within an hour.

Do I need my own domain to use this feature?

Yes — a .com.au domain costs around $15/year. You can use it for both your website and your invoice email.

Skip the copy/paste. Send a real invoice in 60 seconds.

Free Invoice App turns this template into an ATO-ready PDF you can email instantly. Free to start.