Credit control software for Xero, Outlook and Teams (2026)

Contents

If your finance team lives in Microsoft 365, a credit control app has to do two things with your Xero data: send reminders that carry your own Outlook address, and put overdue accounts in the Teams channel you already watch.

Teams is an incoming webhook, and any tool that can post to one will do it. Outlook is the harder half, because there are two ways to build it and only one of them holds at volume.

Key takeaways
  • Xero's reminders leave from a Xero address, so your own address needs a connected app whichever route you take.
  • Caution Relaying through an Outlook mailbox inherits that account's Microsoft 365 sending limits and puts collections bounces against the mailbox your team uses all day.
  • Safe Domain authentication is one DNS job. Paidnice verifies the domain once, then accounts@, jeff@ and stanley@ all work with no further setup and no extra licences.
  • Copies go wherever you want the record: your own inbox, a shared mailbox, or a CRM logging address.
  • Teams alerts run over an incoming webhook, so Slack, Discord, Telegram and WhatsApp work identically.

What Xero does before you connect anything

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.

Nothing in Xero changes the sending domain, and nothing in Xero talks to Teams. Both jobs belong to a connected app.

Two ways to put your Outlook address on a reminder

To the customer these look the same. The difference shows up in your admin centre, in your send volume, and on the day the person who connected the mailbox hands in their notice.

Mailbox connection
Caution at volume

The app sends through one person's Outlook

  • You grant the app permission on that mailbox, and a Microsoft 365 admin normally has to consent for the tenant.
  • Sends count against that account's Microsoft 365 limits.
  • Bounces and complaints from a collections round land on the mailbox your team uses for everything else.
  • It is tied to one account. When that person leaves, chasing stops until somebody reconnects.
  • If that mailbox is ever compromised, whoever holds it also holds your invoice threads and can send as your collections address.
  • More sending addresses usually means more connected accounts, and often more licences.
Domain authentication
Safe at volume

The app sends on your domain's behalf

  • You publish DNS records once. No mailbox is connected and nothing reads anyone's inbox.
  • Sending runs on dedicated infrastructure, so a chasing round is not spending a mailbox quota.
  • Collections reputation sits on the sending setup rather than on your everyday mail.
  • It belongs to the domain, so it survives a leaver.
  • A compromised personal mailbox does not take your chasing with it, because sending is not attached to anyone's account.
  • Every address on the domain works once the domain is verified.
A login is not domain authentication

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 an Outlook 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 tenant-level mailbox access and borrowing a 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.

How Paidnice sends from any address on your Microsoft 365 domain

Paidnice does not connect to a mailbox and does not read your inbox. On Pro plans you add your domain under Email Preferences, Paidnice returns the DNS records, and whoever manages your DNS publishes them. 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]. Your Microsoft 365 admin is not asked to approve anything per address, and you are not buying a licence to send from a name.

💡 Paidnice insight

This is what makes an escalation ladder cheap to run. Each 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.

Where the sent copies land

If the mail did not leave Outlook, the record still has to go somewhere. Every sender profile has a BCC field that takes any address you choose.

Point it at a shared accounts mailbox and the whole team sees each reminder as it goes out. Point it at a CRM logging address and the thread lands on the customer record instead. Pipedrive, HubSpot and Salesforce all accept mail this way, as does any system that logs by BCC.

Replies are handled separately. The reply-to address on the profile decides where a customer's answer arrives, so it can land with the named sender, with a shared inbox, or with both.

How Paidnice posts overdue alerts into Microsoft Teams

Paidnice posts notifications into the Teams channel your team already has open, so an overdue account gets picked up by whoever is free, instead of sitting in one person's inbox.

The connection is an incoming webhook, so the destination is a setting rather than a product decision. Slack, Discord, Telegram and WhatsApp all accept incoming webhooks, and so do Zapier and Make for anything else in your stack. 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 others document ledger, email and payment integrations, and nothing that posts into a Teams channel.

Which Xero credit control apps cover Outlook and Teams

Four tools come up repeatedly for Microsoft-stack finance teams. Price and mechanism separate them more than features do.

ToolAuthenticationAt volumeTeams alertsPriceBest 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
ezyCollectNot publishedNot published NoneAbout A$275/moAustralia and New Zealand
Kolleno One mailbox login Caution NoneUS$650 per user/moLarger finance teams
Safe

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.

Caution

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.

Not published

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.

Check how the pricing scales before you commit. Where the price rises with each person you want to send as, an escalation ladder gets expensive fast, and the ladder is the part that moves payment dates.

How to set it up on Microsoft 365 and Teams

Connecting a credit control app to a Microsoft stack is a DNS job and two integrations. Budget an afternoon.

  1. Pick the addresses you want to send from. Three covers most teams: an accounts address, a named credit controller, and a director for the final step.
  2. Publish the DNS records. Add the domain in Email Preferences, take the records Paidnice returns, and have whoever manages your DNS publish them. Verify once they resolve.
  3. Create a sender profile per address, each with its From name, reply-to, and a BCC address if you want the record in a shared mailbox or CRM.
  4. Assign a profile to each policy so the sender escalates as the invoice ages.
  5. Add the Teams webhook and choose the channel. Then switch Xero's own reminders off so customers are not chased twice.

That last step is the one teams forget. Two systems chasing the same invoice is worse than one.

The full buying criteria, covering late fees, statements, disputes and portals, are in credit control software for Xero. The Google version of this page is credit control software for Xero, Gmail and Slack, and the DNS walkthrough is in sending Xero invoices from your own domain.

Common questions

Will my Xero reminders go out from my own Outlook address?
They can, by one of two mechanisms. Some apps connect to your Outlook mailbox and send as you. Others authenticate your domain and send on its behalf. The From line looks the same to your customer.

Does my Microsoft 365 admin have to approve anything?
For a mailbox connection, usually yes, because the app is granted permission inside your tenant. For domain authentication the work is DNS records on your domain, so nothing is granted on anyone's Microsoft account.

Will chasing hit my Microsoft 365 sending limits?
It can, if the app relays through a mailbox, because those sends count against that account's limits. Sending on the domain's behalf through dedicated infrastructure is not bound by one user's quota.

Does adding more senders cost more on a Microsoft stack?
It depends how the tool prices. Paidnice charges on invoice volume rather than per user, and Pro plans include unlimited users, so a second or third sending address costs nothing extra.

Which Xero credit control apps post alerts into Microsoft Teams?
Paidnice posts to Teams over an incoming webhook, which also covers Slack, Discord, Telegram and WhatsApp. Elsewhere availability varies by tier, so check the plan the integration sits on before comparing prices.

Do replies come back into Outlook?
Yes. The reply-to address on the sender profile decides where a customer's answer lands, so replies arrive in the Outlook mailbox you nominate even though the reminder was sent on the domain's behalf.

Denym Bird

Written by

Denym Bird

Co-founder & CEO of Paidnice

Denym is a software entrepreneur and writes about accounts receivables management for small business.

Stop chasing invoices.
Start getting paid.

Paidnice takes the pain out of getting paid for thousands of businesses using Xero and QuickBooks.

Try it Now - It's Free

No card required.

ACAcme Joinery 12 days overdue Checking policy Late fee applied Awaiting payment $4,120 $4,202
BRBrightwork Due today Reminder sent Still unpaid Final notice $1,880
CVCoverdale Due in 3 days Reminder sent Checking policy Exempt from fees Needs review Sent to your team $6,480

Try Our Free Accounts Receivable Calculators

Optimize your cash flow with our suite of financial tools designed for AR professionals. Calculate DSO, aging analysis, late fees, and more.

Explore Calculators