An illustrative build from the business track, using tools most Mumbai companies already have.
The problem
An accounts payable team receives a few hundred vendor invoices a month by email. Most match a purchase order and a goods receipt. The ones that don't take most of the team's time: wrong rates, missing PO numbers, duplicate invoices and quantity mismatches.
The agent
- Reads each invoice PDF saved to a shared folder and extracts vendor, PO number, items, quantities, rates and tax.
- Looks up the PO and goods receipt in an exported register and compares line by line.
- Sorts invoices into matched, exceptions and possible duplicates, with the reason for each exception.
- Drafts a polite query email to the vendor for each exception, in the team's tone.
- Stops. A person reviews the exceptions list and approves each email before it is sent. Nothing is posted to the accounting system by the agent.
What the team learns building it
- How to write agent instructions with clear rules and a clear stopping point
- How to test with tricky invoices: scanned copies, missing fields, a PDF with hidden instructions
- How to give the agent read access to the folder and register, and nothing else
- How to measure it: exceptions caught, false alarms and minutes saved per invoice
