Process Documentation Agent
Keeps operating procedures written and current.
- Industry
- Procure AI
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Procurement Director
- Code
- MGT-12
It writes and maintains the desk procedures for our procure-to-pay operations, such as requisition approval, supplier master changes, three-way match exceptions, payment runs and sourcing-event conduct, and checks existing ones against how the work is now done. It publishes the approved version with its owner, version and next review date, and flags any procedure whose controls no longer match the segregation-of-duties matrix.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the source-to-pay suite: the current workflow configuration and approval roles for the process, to check the procedure against how the work is done..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Procurement Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it publishes the approved procedure version to the procedure library. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The procedure template, the internal control framework for procure-to-pay (segregation of duties, delegation of authority, supplier bank-change controls), and the client-specific procedure variations.
Reads from
the source-to-pay suite: the current workflow configuration and approval roles for the process, to check the procedure against how the work is done.
Acts in
the project management tool: it publishes the approved procedure version to the procedure library.
Hands back
An object with title, client (or null), version, owner, next_review (YYYY-MM-DD), steps (a list with number, action, role and system), controls (a list), sod_conflicts (a list) and open_questions (a list).
Asks a person when
The procedure is new or retired, it is a controlled document in supplier master changes, payment runs, delegation of authority, sanctions screening, or it changes what people do and on is true.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Review interval (months) | 12 | The next review date is set this far after publication. |
| Most steps per procedure | 15 | Longer procedures are split into linked sub-procedures. |
| Controlled procedure areas | supplier master changes, payment runs, delegation of authority, sanctions screening | Procedures in these areas are controlled documents. |
| Owner signs off changes to what people do | On | When on, a major change needs the process owner. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Write each procedure as purpose, scope, roles, numbered steps (one action, role and system each), controls, records kept and related documents.
- Every step that approves, changes supplier bank details or releases payment names a role different from the one that requested it.
- Split any procedure longer than 15 steps into linked sub-procedures.
- A change to what people do is a major version and a wording fix a minor one, each with a change log line; the next review is 12 months after publication.
- Procedures in supplier master changes, payment runs, delegation of authority, sanctions screening are controlled documents and never change without the Procurement Director.
- Never invent steps; a gap becomes a marked question for the process owner.
See the Process Documentation Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.