An invoice arrives by email. The agent reads the supplier, amount, dates and line items, then looks for the matching purchase order. If they agree, it sends an approval request to the right person in Slack or Teams. If they do not, it says what does not match.
Approved bills are prepared for entry in your accounting system. Payment itself stays with your people: the agent does not release money, and a human approves every payment run. If an invoice has no purchase order, the agent does not guess. It asks the person who normally orders from that supplier, or routes it to whoever you name. That small step keeps unmatched bills from sitting unseen, and it is the kind of rule we set with you during the blueprint stage.
On the sales side, the agent watches for overdue invoices and sends reminders that grow firmer with each step. You set the schedule and the wording, and it stops as soon as payment is recorded. These choices are written into the blueprint.
Gather a sample of recent invoices, including the awkward ones: credit notes, partial deliveries, PDFs with odd layouts. Those show us where a human check should stay. It is not a fit if purchase orders are rare and approvals happen by conversation, because there is nothing to match against yet. Measure it by invoices approved without chasing, mismatches caught, and days between a due date and a reminder.
It retries, then alerts your team with the details so nothing slips through.