Skip to content

How an AI Agent Answers "Has My Invoice Been Paid?" Emails

Half of AP teams lose six or more hours a month to supplier payment questions. Here is how an AI agent answers them from your ERP while people keep control.

Dragan Ristić

On this page

If your AP inbox fills up with suppliers asking "Has my invoice been paid?", an AI agent can answer most of those emails for you. It reads the question, finds the invoice in your ERP, writes back with the real status and hands anything unusual to a person. Your team stops being a help desk and goes back to paying bills on time.

This guide is for owners, controllers and AP leads at distributors and logistics companies with about 20 to 500 people. It shows what the system looks like, what data it needs, where people stay in charge and how to start small.

Why this keeps eating your team's week

MineralTree's 2024 State of AP Report surveyed more than 1,100 finance people and found that half of AP teams spend six or more hours a month on vendor payment inquiries. In a small team that is close to a full day every month, spent looking up the same kind of answer again and again.

A distributor feels this more than most. You buy from hundreds of suppliers, many of them small, and each one watches its cash closely. When a payment is late or a check crosses with an email, they write. Often they write twice.

It is also getting worse. IOFM's surveys of more than 150 AP leaders found that the share of invoices taking more than 15 days to process jumped from 5% to 25% in about six months, from summer 2025 to winter 2025 into 2026. Slower invoices mean more suppliers asking where their money is.

Why a supplier portal doesn't fix it

The usual answer is a supplier portal where vendors check status themselves. It sounds right. The problem is that most suppliers don't want to log in to one more site.

In MineralTree's 2023 survey of people at vendor companies, 88.6% said email was how they prefer to ask about a payment. Only 3.3% picked a self-service portal. So you can build the portal, and the emails keep coming.

That is why I'd start with the inbox instead. Meet suppliers where they already are and answer the email they already sent.

How the system works, step by step

Think of it as a careful new hire who only does one job and always shows their work. Here is the flow.

  • The agent watches the shared AP mailbox and picks out emails that ask about an invoice or a payment.
  • It pulls out what the supplier gave you, like the invoice number, PO number, amount or date.
  • It finds the supplier in your vendor list by email address and the invoice in your ERP.
  • It reads the status. Received, waiting for approval, on hold for a mismatch, scheduled to pay, or paid with the date, method and check or payment reference.
  • It drafts a short, plain reply with that status and, when there is one, the reason for a hold and what the supplier can send to clear it.
  • It logs the question and the answer next to the invoice, so the next person sees the history.

For a simple "paid on the 12th by ACH" answer, many teams let the agent send the reply on its own after a few weeks of testing. Anything else waits for a person to click approve.

The data it needs and the rules it follows

Most of the work before go live is cleaning data, not writing code. The agent needs read access to four things in your ERP or AP tool.

  • The vendor list with the email addresses your suppliers actually write from.
  • Open and paid invoices with their status and due dates.
  • Payment runs with dates, methods and reference numbers.
  • Hold reasons, written in words a supplier would understand.

Then you set the rules. These are the ones I'd put in from day one.

  • Only answer the supplier on record. If the sender's address isn't tied to that vendor, a person checks first.
  • Never change bank details from an email. Any request to change where money goes is sent straight to a person, who confirms it by phone using a number you already had on file.
  • Never promise a pay date that isn't already scheduled in the system.
  • Never discuss another supplier's invoices, prices or terms.
  • Hand over anything angry, legal, or about a dispute, a credit or a short payment.

The bank details rule matters a lot. Fake supplier emails asking to change payment details are a common fraud, and an agent that reads the AP inbox all day is in a good spot to flag them instead of acting on them.

What stays with your people

The agent handles the lookups. Your team keeps the judgment. That means approving invoices, solving price and quantity mismatches, deciding who gets paid early when cash is tight, handling disputes and talking to suppliers who are upset. Those are the calls that protect supplier relationships, and they need a person who knows the history.

In practice this flips the job. Instead of answering "where is my money" all morning, your AP lead reviews a short list of the emails the agent couldn't close and works on the holds behind them.

What to measure

Pick a few numbers before you start so you can tell if it works. These are the ones I'd watch.

  • Hours per month your team spends on supplier status emails, before and after.
  • How long a supplier waits for an answer, from email in to reply out.
  • The share of status emails the agent closes with no edits.
  • Repeat emails, meaning the same supplier asking about the same invoice twice.
  • Invoices stuck on hold for more than 15 days, since those drive most of the questions.

As example math, if one AP person spends six hours a month on these emails at a loaded cost of $40 an hour, that is $240 a month, or about $2,900 a year, for one person. Your numbers will differ. Use your own hours and rates. This is a model with stated assumptions, not a promise of results.

How to start small

You don't need a big project to test this.

  • Export last month's supplier emails from the AP inbox and tag the ones that ask about status.
  • Check how many you could have answered from the ERP alone. That share is your ceiling.
  • Run the agent on that same set in draft mode, with every reply waiting for approval.
  • Compare its drafts with what your team actually sent.
  • Turn on sending for the simplest answers only, and keep people on everything else.

If most of your supplier emails turn out to be about mismatches and disputes rather than status, fix the matching problem first. An agent that answers fast doesn't help much if the answer is always "on hold".

If this eats hours of your AP team's week, I build these systems with my team. You can see how an inbox agent sorted and routed email for one company in this case study, and if you want to talk through your own inbox, reach out on Work with us.

Frequently asked questions

It shouldn't, if you set one rule. The agent only answers when the sender's email address belongs to that supplier in your vendor list. Anything else goes to a person to check first.

Series: Working with a development team

Part 5 of 5
Previous

When Should an AI Support Agent Hand Off to a Human? The Rules That Work in Production

Next

Latest in this series

From the Lab, for buildersThe trust boundary pattern, the architectural decision you are already making, whether you know it or not

Keep reading