How it worksManaged service · governance
How our managed AI agent service works, and how it is governed
Corpogents is a managed service. We map the process with your team, deploy an agent into your systems and run it for you, under controls your auditors can read. This page sets out how that works, and what we commit to on every deployment.
Free · 30 minutes. You leave knowing whether an agent fits your process.
- 01DemoFree30 minutes, on sample dataYou get A straight answer on fit, and what Map would cover.
- 02Map3 to 4 weeksFixed scope, real documentsYou get A rule catalogue your controller edits, a business case in your numbers and a dated plan.
- 03DeployRead-onlyA parallel run on your real documentsYou get A live agent, an approver group and a log from day one.
- Go-liveYour sign-offYour controller decides, on evidence, not on a date
- 04RunManagedMonitored by us, approved by youYou get A monthly report of what the agent did and what it escalated.
01In short
What is a managed AI agent service?
A managed AI agent service means the provider builds the agent, connects it to your systems, runs it in production and keeps improving it, instead of handing over software for your team to operate. With Corpogents it starts with a demo, then a fixed-scope Map engagement, then one agent live in SAP, with your team approving every consequential action.
| Starts with | A free demo on sample data, 30 minutes |
|---|---|
| Then | Map: fixed-scope, usually 3 to 4 weeks |
| First agent | Connects read-only, stages drafts once your controller signs off |
| A person approves | Every posting, payment and customer message |
02The stages
Map, Deploy, Run
The demo is free and shows an agent on sample documents. Everything after it is a decision you make on evidence, one stage at a time.
Map
- What happens
- We sit with the people who run the process today and follow real documents through it. We measure volumes and exception patterns from your SAP data, collect your approval rules and your audit checklist, and agree with you how success will be measured before anything is configured.
- What you get
- A process map, a rule catalogue your controller reviews and edits, a business case in your own numbers, and a dated deployment plan. You keep all of it, including if you decide not to deploy.
- What we need from you
- A process owner, a finance controller to agree the rules, and an IT contact for access. A few working sessions each.
Deploy
- What happens
- Your IT team creates a user for the agent with the permissions we specify, and it connects read-only. We configure the agent with the rules from Map: tolerances, approval limits, tax treatments, document series. Then it works your real documents alongside your team, and you compare its answers with theirs before it stages anything in SAP.
- How go-live is decided
- On evidence. The agent starts staging drafts when its answers match what your team would have done, closely enough for your controller to sign off.
- What you get
- A live agent, an approver group that knows the queue, and a log of every decision from the first day.
Run
- What happens
- We monitor every run, handle the agent’s side of the exceptions, update rules when suppliers, prices or tax rules change, and send you a monthly report of what the agent did and what it escalated.
- What stays with you
- Every approval, every rule change (signed off by your controller), and the decision to widen the agent’s permissions or add the next agent.
Documents followed through the process
- INV-20418Supplier invoice · scanned PDF
- PO-4410Purchase order · SAP
- GRN-8821Goods receipt · stores
Received · Matched · Approved · Posted
Controller’s checklist
- Approval limits by entity
- Tolerances on price and quantity
- Tax treatments and document series
- Exception patterns from your SAP data
- How success is measured agreed with you
| Document | Your team | Agent | Result |
|---|---|---|---|
| INV-20418 | Post | Post | Match |
| INV-7731 | Hold | Hold | Match |
| INV-20422 | Post | Hold | Reviewed |
| RE-0193 | Post | Post | Match |
Documents worked, by week
Worked by the agent Escalated to a person
Escalated to your team
- Price above toleranceAP
- No goods receipt yetAP
- New vendor bank detailsAP
Each one with the reason and the evidence attached.
03Responsibilities
Who does what
Corpogents runs the agent. Your team keeps every decision that matters, and the amber mark shows where.
| Activity | Corpogents | Your team |
|---|---|---|
| Process mapping | Leads the sessions, measures volumes and exceptions | Provides the process owner and real documents |
| SAP access | Specifies the permissions the agent needs | IT creates, controls and can revoke the agent’s user |
| Rules and tolerances | Configures them from your checklist | Controller approves them, and every later change |
| Daily operation | The agent reads, checks and prepares | Approves, releases and handles exceptions |
| Monitoring and tuning | Watches every run, fixes and improves | Reviews the monthly report |
| Wider permissions or a new agent | Recommends, with the evidence | Decides |
04Governance
Autonomy is a dial you set
Each agent runs at a setting you choose, process by process. It starts at the lowest setting and moves only when you move it.
Set by your controller, process by process. Select a setting to see what the agent may do.
Setting 1 of 3
Watch
Reads and reports. It flags issues and builds worklists, and changes nothing anywhere. Every agent can start here.
What moves at this setting
- Read
- Check
- Flag
- Draft
- Post
The agent does this A person decides here
Nothing is written anywhere. Your team acts on the worklist.
Setting 2 of 3
Prepare
Drafts the work: a staged invoice, a sales order, a reminder letter, a reply. A named person approves each one before it goes anywhere. Most agents run here.
What moves at this setting
- Read
- Check
- Draft
- Approve
- Post
The agent does this A person decides here
A named person approves each draft before it goes anywhere.
Setting 3 of 3
Act within a mandate
For a few defined steps, the agent acts on its own inside limits you write down. Three agents can act inside a mandate you write: Procurement sends RFQs, reminders and counter-offers to your approved vendors up to your target price, Outbound Sales sends first emails to the market you approved, and Service SLA puts a late thread on its owner’s worklist. Each mandate is logged and can be withdrawn at any time.
What moves at this setting
- Read
- Check
- Draft
- Act in mandate
- Post or pay
The agent does this A person decides here
Each mandate is written down, logged and can be withdrawn.
Some things never move off the dial. Postings to your books, payments and messages to your customers always wait for a person.
05Commitments
Our governance and security commitments
This list holds on every deployment. If you need something that isn’t here, ask us, and we’ll answer in writing.
- 01
Read-only by default. A new agent can read. It writes nothing until you decide it should.
- 02
Drafts, not postings. Where an agent writes to your ERP, it stages drafts. People approve, post and release.
- 03
A person on money and customers. Payments, postings and customer messages always need a named person’s approval.
- 04
A complete record. Every read, check, draft, hold, approval and override is logged with who, what, when and the reason. Your auditors can review it.
- 05
Rules you can read. Tolerances, approval limits and tax treatments are settings your controllers can see and change, and each change is recorded.
- 06
Separation of duties where your controls need it. The person who sets the rules can be kept apart from the people who approve transactions.
- 07
Run in the Corpogents cloud. Agents run in the Corpogents cloud and connect to your SAP through a user your IT team creates and can revoke, with only the permissions you grant.
- 08
We never train models on your data.
- 09
Data protection. Data from your systems is processed under a data processing agreement. We apply encryption in transit and at rest, access controls and least privilege, and we handle personal data in line with the data protection law that applies to you, including the GDPR where it applies.
- 10
A security overview on request, written for your IT and risk teams.
06FAQ
Questions from IT, risk and finance
What happens if the agent gets something wrong?
It is caught at the draft, because a person approves every posting, payment and customer message. The correction is logged with the reason and kept as a suggestion for the next similar case. If it should become a rule, the change goes to your controller first. Your data never trains a model.
Can we switch an agent off?
Yes, at any time. Your IT team can revoke its access, and because the agent stages drafts rather than running your process inside a separate system, your team can carry on in SAP exactly as before.
Who owns the rules and the configuration?
The rules come from your own controls and your controller signs them off. Changes are made at your request or with your approval, and each one is recorded.
Can you work with our IT security review?
Yes. We provide a security overview and a data processing agreement, and we’ll answer your questionnaire in writing.
How long does Map take?
Usually 3 to 4 weeks. It is a fixed-scope engagement: a few working sessions with the people who run the process and real documents followed end to end. It ends with a rule catalogue your controller reviews and edits, a business case in your own numbers and a dated plan.
Who from our side needs to be involved?
Three people, for a few sessions each: a process owner who knows the work, a finance controller who agrees the rules and signs off go-live, and an IT contact who creates the agent’s SAP user. After go-live, your approvers work the queue as part of their day.
Do we need to change SAP?
No. The agent works with your existing document series, approval stages and master data. It connects through a user your IT team creates and can revoke, reads what it needs and stages drafts that your team approves in the normal way.
What happens after go-live?
We run the agent as a managed service. We monitor every run, handle the agent’s side of the exceptions, update rules when suppliers, prices or tax rules change, and send a monthly report of what it did and what it escalated. Any rule change goes to your controller first.
NextBook a demo
See the controls working on a real process
In the demo we show an agent at work, then open the approval queue and the audit log so your finance and IT leads can see exactly what is recorded.
Free · 30 minutes. Bring your controller, and IT if they’d like to see the audit trail.