You measure how many invoices your team processes and how quickly they are paid. The time taken by the creditors’ mailbox is not included in any report.
However, the mailbox is for many creditor teams the biggest time-waster. Amidst the invoices, reminders, questions about payment status, supplier statements, due date notifications, amended bank details and credit notes come in. Each message requires someone to read, look up and respond. In this article, you will read about why that work is so persistent, how AI reads and classifies a creditor mailbox, what it concretely yields in aligning supplier statements, and where the boundary lies.
Why the mailbox is the most stubborn part of your creditor process
The creditors’ mailbox is obstinate because each message has a different format and still requires a response from your ERP. Peppol has structured the invoice. The questions regarding that invoice are not.
Look at a typical working week. A supplier sends a second reminder for an invoice that has already been paid. Another asks when invoice 2026-0412 will be paid, without mentioning which entity it is from. A third sends a statement with forty open items as a PDF. Among these are a credit note, a new price list, a request for a purchase order number, and a notification that the bank details have changed. No two messages follow the same template.
Each of those messages asks for the same three steps: reading what is being asked, searching for the answer in the ERP, and writing a response. That is precisely the kind of work that classical automation cannot handle, as it starts with understanding what is stated in free text. And because the work is fragmented throughout the day, nobody measures it.
There is also the risk. A reminder that goes untouched becomes a payment request. A copy that no one reconciles conceals a double payment or a missing credit note. And a changed account number among twenty status inquiries is precisely how payment fraud works.
How does AI approach that then?
How AI reads and classifies an accounts receivable mailbox
AI reads every mail and attachment, determines what is being asked, searches for the answer in your systems, and prepares a response or action for your team. The agent does not respond on his own; he carries out the research.
Specifically, every mail goes through four steps.
- Classify The agent determines the type of message: invoice, reminder, status inquiry, extract, credit note, change of details, or something else. He also recognises the supplier and the entity, even if they are not explicitly mentioned.
- Search for For a status inquiry or reminder, he checks the status of each invoice: received, under approval, blocked, scheduled for payment, or paid, along with the date.
- Present He prepares a response in your team’s tone, including the status of each invoice. If an invoice is missing from your system, this will be clearly indicated, along with a request for a copy.
- Signal A changed account number, an invoice that came in twice, or a reminder for a disputed invoice does not go to the standard flow but to a human, with explanation.
The result is that your team no longer starts with a full inbox, but with a list of prepared responses and a smaller list of messages that truly require a decision. A staff member reads the response and sends it. After a measurement period, you can decide to automatically send simple status responses; until then, nothing goes to a supplier without agreement.
The most important message in that mailbox is usually the supplier’s statement.
Supplier statements: searching for a list of differences for a day
Reconcile a supplier statement means placing every outstanding item from the supplier alongside your own accounts, and that is precisely where AI saves time. The work is not difficult, but endless.
A statement comes in as a PDF or Excel, each supplier with their own formatting. Someone in your team places it next to the supplier card in the ERP and checks line by line: is this invoice with us, for the same amount, and has it been paid? Differences usually have a handful of causes: an invoice that hasn’t arrived with you yet, a payment that is on its way, a credit note that the supplier has already processed and you have not yet, an invoice that has been booked twice.
The agent reviews the transcript, regardless of the format, and places it alongside your open items. What matches disappears from view. What differs gets a presumed cause: “invoice not received, copy requested”, “payment from 3rd October, not yet processed by supplier”, “credit note missing from our accounts”. Your colleague only assesses the differences.
At one client of JUVO, the coordination of supplier statements decreased from six to less than half an FTE. That is capacity, not a cash saving: the team dedicates that time to the differences that really matter. How you address the exceptions structurally yourself is detailed in the article about exceptions in invoice processing.
So much automated reading raises the question of where the boundary lies.
Where the border lies
The agent reads, searches and prepares; he sends nothing without agreement, books nothing and never changes supplier details. The boundary is sharpest regarding banking information.
An email notifying a new account number never receives a standard response. The agent compares the request with what he knows: sender address, usual contact person, tone, country of the bank. He prepares a verification via a contact already in your master data, and he signals that ongoing payments must wait. A human decides.
There is also a limit to what AI knows. If a supplier asks why an invoice is blocked, the agent can retrieve the status and the reason for the blockage from the ERP system. The reason why the purchaser disputes the invoice may only be found in a conversation that was never recorded. Then it is proposed that this is fair, and the question is directed to the appropriate person.
When this is (still) not worthwhile for you
A mailbox agent is only worthwhile if the volume and variation are large enough. If your creditors’ mailbox receives a handful of questions each day from a small, regular group of suppliers, then a good shared mailbox with fixed rules and a few templates is often sufficient. And if your suppliers do not pose status questions because they are paid promptly and on time, then the gain lies more in coding or matching than in the mailbox. We also tell you that if that is the answer.
What you can do tomorrow, even without us
Three statements give you insight into what your creditors’ inbox costs in one week.
Count for a week how many emails come in that are not invoices, and divide them into four groups: reminders, status inquiries, statements, and the rest. Note how long the resolution took for the statements. Also, check how many reminders were about invoices that had already been paid. That final count tells you how much work is purely caused by communication, and that is usually the easiest to eliminate.
Frequently Asked Questions about the Creditors’ Mailbox
Can AI respond to suppliers’ payment reminders?
The AI checks the status for each invoice and prepares a response: received, under approval, scheduled or paid, along with the date. A staff member reviews it and sends it out. After a monitoring period, you can have simple answers sent automatically.
How do you automatically reconcile a supplier statement?
The agent reads the statement, regardless of the format, and places each open item alongside your accounts. What corresponds disappears from view; for each discrepancy, he proposes a suspected cause. Your team only assesses the discrepancies.
What happens to an email about changed bank details?
It never goes through the standard process. The agent signals the request, compares it with known data, and prepares a verification via a trusted contact. A person decides on the amendment.
Bart has been helping companies improve their finance processes for almost twenty years. In recent years he has done so mainly with AI and process automation, from invoice processing to the close. At JUVO he leads the AI offering for finance, customer operations and logistics.
Wondering how much time your accounts payable inbox really takes today?
In a Discovery Session we look at your processes together and identify your first use case.