Coupa is a spend management platform used by mid-sized and large organisations to control buying. Requesters shop from catalogues and punchout sites, requisitions pass through approval chains, purchase orders go to suppliers, and invoices are matched before payment. For maintenance teams, it is where every spare part, tool and contractor visit gets paid for.
Technicians and planners do not live in Coupa. They live in the CMMS, and when they need a part they either wait for a buyer or learn a second system. Questions such as "is it approved yet?" and "when will it arrive?" become emails. An AI agent connected through Agentic CMMS answers those questions directly and can raise requests for the person who uses it.
What your AI agent can do with Coupa
- Turn a parts list into a request. "Create a requisition for the four filter elements and the drive belt on this job, delivered to the North site stores."
- Follow an approval. "Who is my requisition for the forklift battery waiting on?"
- Check order status. "Has the PO for the conveyor rollers been sent to the supplier, and what is the promised date?"
- Search catalogues. "Find a catalogue item for 6205 bearings and show the supplier and price."
- Review invoices. "Which invoices for maintenance contractors are on hold for a price mismatch?"
- Watch spend against budget. "How much have we spent with our compressor service provider this year?"
- Spot repeat purchases. "Which parts did the maintenance team buy more than six times in the last quarter?"
Coupa with your other systems
The part you order in Coupa is always for something. These links keep the reason attached.
- Copy the part list of a Fiix work order into a Coupa requisition, then add the PO number back to the job.
- For each planned job in HxGN EAM, check whether its materials have an approved purchase order in Coupa.
- Compare Coupa spend per supplier with the payments recorded in Oracle NetSuite.
- Post a short list of requisitions blocked for more than three days into a Microsoft Teams channel for the approvers.
Faster parts, same controls
The approval chains, budgets and catalogues in Coupa exist for good reasons. The agent does not go around them. It removes the waiting and the guesswork: technicians know the status of their parts, and buyers get complete requests with the asset and job already named.
Buyers gain as well. Requests raised through the agent arrive with the asset, the job and the delivery location already named, so fewer requisitions bounce back for missing details, and spend reports show which machines cost the most to keep running.
Each person approves their own agent, owners and admins choose which roles may raise requisitions, and every Coupa call is stored in the activity log.