- Yes. The SRM, whether SAP Ariba, Coupa or another, stays the system of record: vendor master, supplier status and the processes that read from them.
- The agent works in front of it, on the part SRMs store but do not do: talking to suppliers who will not log in, reading each document, checking it against your requirements and chasing what is missing.
- A person approves every supplier and every exception. Only then is the approved status written to the SRM.
- You can start without integrations: the agent works from your mailboxes and spreadsheets and your team updates the SRM from the validated file. Write-back comes once access is in place.
- Suppliers who prefer the portal can keep using it. The agent covers the ones who answer by email.
Can an AI agent work on top of SAP Ariba or Coupa?
Yes, and that is the point. Replacing an SRM is a multi-year project with its own risks, and most teams that have one are not looking to remove it. What they want is for the work around it to stop depending on people chasing suppliers and reading PDFs. An agent layer keeps the SRM as the system of record and does that work in front of it, with a person approving every supplier before anything is written back.
What an SRM does well, and where the work stays manual
An SRM is good at records and process: one supplier master, a registration portal, workflow steps, document storage and the link to sourcing, contracts and payments. What it does not do is the judgment in the middle. It stores the certificate of insurance; someone still has to open it and see that the limit is below the requirement. It sends a reminder; someone still has to read the reply and work out which document is still missing. And it only works for suppliers who log in.
What stays in the SRM and what the agent does
| Part of the work | SRM | Agent |
|---|---|---|
| Supplier record, vendor master, status | Yes | No. Writes the approved status back, once connected |
| Supplier portal and registration forms | Yes | No. Offers email to suppliers who do not use the portal |
| Workflow routing and approval steps | Yes | Prepares the approval pack a person decides on |
| Storing documents | Yes | Files them with the checks that were run |
| Chasing suppliers for missing documents | Reminders, if configured | Follows up in the thread, naming exactly what is missing |
| Reading each document against the requirement | Usually a person | Checks issuer, holder, limits, scope, expiry and consistency |
| Sanctions and registry checks | Through add-ons or a person | Screens the entity and owners; matches go to a person |
| Expiry watch and recertification | Date fields, if filled in | Reads dates from the documents and requests renewals |
This describes how SRMs usually handle each step, not a review of a specific product or configuration. Check against your own setup.
How the two work together
A request starts where it starts today
A new supplier raised in the SRM, a requester email, or a line in a spreadsheet. The agent picks it up with the requirement set your policy assigns to that category, country and spend.
The agent collects and checks
It asks the supplier by email, reads the replies and attachments, checks each document and chases only what is missing. Suppliers who complete the SRM portal are not asked twice.
A person approves
The approver gets one pack in Microsoft Teams or Slack: what was checked, against which source, what passed, what is unclear, and a recommendation.
The SRM is updated
Once connected, the agent writes the approved status and data to the vendor master. Until then, your team updates it from the validated file. The file, the thread and the decision are kept together for the audit.
Integration: what is needed and when
To start, the agent needs access to the mailboxes where supplier documents arrive and to your requirement set, which can be a spreadsheet. That is enough for a diagnostic on your own data and for the first weeks of a pilot. Writing approved statuses back to the SRM needs access to it, granted and reviewed by your IT team. Nora's tools include the SAP vendor master and Coupa; for other systems, what can be written and how is confirmed during scoping.
What happens to the supplier portal
It stays for the suppliers who use it. Many buyers find that a share of suppliers never complete the portal and email the documents instead, and someone uploads them on their behalf. The agent covers those suppliers by email and checks their documents the same way as those that came through the portal, so the policy is applied regardless of the channel. The guide to supplier management without a new portal shows what that exchange looks like.
Questions to ask before adding an agent layer
- Which part of supplier onboarding takes most of our team's time today: chasing, reading, or deciding?
- What share of our suppliers complete the portal on their own, and what happens with the rest?
- Is our requirement set written down by category, country and spend, or does it live in people's heads?
- Who can grant read and write access to the vendor master, and what review does that need?
- Who approves suppliers today, and which exceptions need a second approver?
- What evidence would an auditor ask us for today, and where would we find it?
For the wider choice between a suite module, a specialized tool and an agent, see the supplier onboarding software comparison.
Limits
- The agent is not a system of record. The SRM or ERP keeps the vendor master.
- Write-back needs access to the SRM. Until then, your team updates it from the validated file.
- Suppliers are reached by email. Microsoft Teams or Slack are for your own team.
- It checks the documents suppliers provide. It does not audit sites or certify compliance.
- A person approves every supplier and every exception.
To see the approval pack and the systems Nora works in, read her profile or the supplier onboarding use case. To scope a pilot on top of your SRM, book a call.
Frequently asked questions
Does this replace SAP Ariba or Coupa?
No. The SRM stays the system of record and the vendor master. The agent does the collection, document checks and screening before a supplier is approved, and writes the approved result into the SRM once connected.
Which systems does the agent connect to?
Nora's tools include the SAP vendor master and Coupa, Gmail or Outlook, Slack, sanctions lists and tax registries. Which systems it writes to depends on the access your IT team grants, and is confirmed during scoping.
Do we need an integration project to start?
No. A diagnostic and the start of a pilot run from your mailboxes and spreadsheets, without integrations. Your team updates the SRM from the validated file until write-back is connected.
What happens to suppliers who already use our portal?
Nothing changes for them. The agent covers the suppliers who answer by email instead, and checks the documents regardless of the channel they arrived through.
Who approves the supplier?
A named person, always. The agent prepares the approval pack and cannot approve a supplier. Potential sanctions matches and scores above your threshold always go to a person.
Keep reading
This article is for information and is not legal advice. Practices and references are for the United States; check what applies to your contracts and your state.