- Industry
- Procure AI
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Accounts Payable Lead
- Code
- CUS-05
It answers the purchase-to-pay mailbox for client teams and their suppliers, separating every question in the latest email (an invoice not received, a match exception, a missing PO number, a remittance request) and answering each from the email guide and the documents in the ERP. It sends routine replies itself, sets the ticket status and pending reminder, and holds anything sensitive, such as a bank-detail change, for a person.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the ERP's purchasing and accounts payable modules: the invoices, POs, match status and scheduled payments named, and the sender's registered contact in the supplier master..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Accounts Payable Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the helpdesk: it sends the reply on the ticket and sets its status, tags and pending reminder. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The P2P mailbox guide: reply templates for invoice status, PO-number requirements, e-invoicing submission per country, remittance copies and match exceptions, the no-PO-no-pay rule, attachment handling and service levels.
Reads from
the ERP's purchasing and accounts payable modules: the invoices, POs, match status and scheduled payments named, and the sender's registered contact in the supplier master.
Acts in
the helpdesk: it sends the reply on the ticket and sets its status, tags and pending reminder.
Hands back
An object with subject, body (the email reply), answered (a list of the questions answered), unanswered (a list, each with question and owner), fraud_flag (true or false), ticket_status (open, pending or solved) and remind_on (YYYY-MM-DD or null).
Asks a person when
The reply falls outside invoice status, PO number required, remittance copy, e-invoicing how-to, the sender is not a registered contact, the email asks to change bank details, or the thread disputes a short payment, a deduction or a late-payment penalty.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Reply due within (business hours) | 8 | A reply later than this is flagged as late. |
| Replies it may send itself | invoice status, PO number required, remittance copy, e-invoicing how-to | Comma-separated. Replies in other categories are drafts for a person. |
| Remind a pending sender after (days) | 3 | When the reply asks the sender for something, such as a corrected invoice, the ticket is set to pending and reminded after this long. |
| Close a pending ticket after (days) | 10 | A pending ticket with no reply is closed after this long. |
| Accept PDF invoices by email | Off | When off, a supplier who emails a PDF invoice is told to submit it through the e-invoicing network instead. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Answer every question in the latest email, in the order asked, and say plainly which one it cannot answer and who will.
- Send without a person only replies in invoice status, PO number required, remittance copy, e-invoicing how-to; everything else is a draft for the Accounts Payable Lead.
- Never send payment, remittance or bank information to an address that is not the supplier's registered contact in the supplier master.
- Treat any email asking to change bank details, especially with a bank letter attached, as a possible fraud attempt: do not act, reply only with the portal's verified change process, and flag it.
- Apply no-PO-no-pay: an invoice without a valid PO number is returned to the supplier asking for it, never forced into match.
- When off is false, redirect emailed invoices to the e-invoicing network with the country's submission steps.
- When the reply asks the sender for something, set the ticket to pending, remind after 3 days and close after 10 days; flag a reply as late after 8 business hours.
See the Email Support Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.