A credit control app can put your own address on a Xero reminder in two ways: by connecting to somebody's Gmail mailbox and sending as them, or by authenticating your domain and sending on its behalf. Domain authentication is the one that scales.
Slack is the easier half. Any tool that can post to an incoming webhook can put an overdue account in the channel your team already watches.
Xero holds one reminder schedule at organisation level. You can have up to five reminders in it, and Xero sets three of them up for you when you first turn the feature on. Every reminder fires against every invoice marked as sent.
Each reminder goes to the primary person on the contact plus anyone with "Include in emails" selected. The only balance control is a checkbox, Don't send reminders for amounts owing on an invoice under, and Xero applies that setting to all reminders. Xero's own setup article tells readers to search the Xero App Store for apps that allow more advanced invoice reminder options.
Those reminders leave from a Xero address with your name on them. No setting in Xero changes the sending domain.
Both approaches put your address in the From line, and to the customer they look identical. What differs is what you hand over, what happens at volume, and what breaks when somebody leaves.
Signing in authorises one mailbox DNS records authorise your domain
Signing in and granting an app access authorises one mailbox. Your domain's sending records are untouched, and the app is relaying through that account.
Domain authentication is a DNS change. You publish records that let the sending service sign mail as your domain, which is what a receiving server checks. Both routes get described as connecting your email, so the distinction is easy to miss on a pricing page.
Several tools will connect to a Gmail mailbox and send as that person, and if that is what you want, it is available. Our honest view is that it is the weaker design. You are granting access to a mailbox and borrowing its send quota to get a From line you can have another way.
The failure modes are the giveaway. Somebody moves on and the chasing quietly stops. Somebody gets phished and the attacker inherits your invoice threads. Neither happens when the sending belongs to the domain instead of to a person.
Paidnice never connects to a mailbox and never reads your inbox. On Pro plans you add your domain under Email Preferences, Paidnice returns the DNS records, and you or your IT team publish them and verify. Sending runs through SendGrid.
Paidnice's setup guide is explicit about what follows: verify your top level domain once, then set up sending addresses inside Paidnice with no further verification.
One DNS job covers [email protected], [email protected] and [email protected], with no extra mailbox licences and no second approval.
That is what makes an escalation ladder practical. A sender profile carries a From name, a From address and a reply-to, so the due-date nudge comes from Accounts, the fortnight-overdue chase comes from a named credit controller, and the late fee notice comes from a director. The customer reads it as the matter moving up the building, and nobody forwarded anything.
If the mail did not leave your mailbox, the record still has to go somewhere. Every sender profile carries a BCC field, and it takes any address you like.
Point it at your own inbox and every reminder, statement and late fee notice arrives there as it goes out. Point it at a CRM logging address instead and the same thread lands on the customer record. Pipedrive, HubSpot and Salesforce all accept mail this way, as does any system that logs by BCC.
Replies are separate and simpler. The reply-to address on the sender profile decides where a customer's answer arrives, so it can go to the person who sent it, to a shared accounts inbox, or to both.
Paidnice posts notifications into the Slack channel your team already watches, so an account that needs attention is picked up by whoever is free rather than by whoever opens the shared inbox first.
The connection is an incoming webhook, which is why the destination is a setting rather than a product decision. Microsoft Teams, Discord, Telegram and WhatsApp all accept incoming webhooks, and so do Zapier and Make for anything else you run. Our team will set it up with you.
Of the four apps below, Paidnice is the only one publishing a chat integration at all. The other three document ledger, email and payment integrations, and nothing that posts into a Slack channel.
Four apps come up most often for teams running on Google and Slack. They differ on the sending mechanism more than on the feature list.
| Tool | Authentication | At volume | Slack alerts | Price | Best for |
|---|---|---|---|---|---|
| Chaser | One mailbox login | Caution | None | £199/mo | £1m to £200m turnover |
| Paidnice | Your own domain | Safe | Yes, via webhook | £49 / US$69/mo | £500k to £10m |
| ezyCollect | Not published | Not published | None | About A$275/mo | Australia and New Zealand |
| Satago | One mailbox login | Caution | None | £25 to £45/mo | UK, on Sage 50 or Xero |
Your own domain. You publish DNS records once and the app sends as your domain. No mailbox is connected, nothing reads your inbox, and there is no per-person send limit to hit.
One mailbox login. The app signs into one person's Gmail or Outlook and sends as them. Chasing shares that account's daily send limit and its bounce reputation, it stops when that person leaves, and a compromise of that mailbox reaches your invoice threads too.
The vendor documents neither method, so we have not assumed one either way.
Prices are entry tiers checked against vendor materials in August 2026; verify current pricing before you buy.
Connecting a credit control app to a Google and Slack stack is a DNS job and two integrations. Budget an afternoon.
That last step is the one teams forget. Two systems chasing the same invoice is worse than one.
The wider buying criteria, including late fees, statements and disputes, are in credit control software for Xero. The Microsoft version of this page is credit control software for Xero, Outlook and Teams, and the DNS walkthrough is in sending Xero invoices from your own domain.
Will my Xero reminders go out from my own Gmail address?
They can, by one of two mechanisms. Some apps connect to your Gmail mailbox and send as you. Others authenticate your domain and send on its behalf. The customer sees the same From line either way.
Do I have to give an app access to my Gmail mailbox?
Only with tools built that way. Paidnice does not connect to a mailbox and does not read your inbox. It publishes DNS records against your domain and sends through SendGrid, so nothing is granted on anyone's Google account.
Does Google Workspace limit how many reminders I can send?
Google Workspace applies daily sending limits per account, and those limits apply to anything sending through that mailbox. Sending on the domain's behalf through dedicated infrastructure is not bound by one user's quota.
What happens when the person whose mailbox is connected leaves?
With a mailbox connection, chasing stops until somebody reconnects an account. With domain authentication the setup belongs to the domain, so a leaver changes who reads the replies and nothing else.
Which Xero credit control apps post alerts into Slack?
Paidnice posts to Slack over an incoming webhook, which also covers Teams, Discord, Telegram and WhatsApp. Among the others, availability varies by tier, so check which plan the integration sits on before you compare prices.
Can I still keep a copy of every reminder in my own inbox?
Yes. Put your inbox in the BCC field on the sender profile and every reminder, statement and late fee notice arrives there as it goes out. The customer cannot see it.
Paidnice takes the pain out of getting paid for thousands of businesses using Xero and QuickBooks.
Try it Now - It's FreeNo card required.
Optimize your cash flow with our suite of financial tools designed for AR professionals. Calculate DSO, aging analysis, late fees, and more.
Request an AI summary of Paidnice
