Autonomous Procurement Policy
The Autonomous Procurement Policy is an internal policy that sets the rules for agents that buy on a company’s behalf. It sits under the delegation of authority policy and pulls together the controls from the guides: approval of deployments, vendor rules, enforced limits, human approval and review. Bracketed terms are placeholders.
1. Purpose
This Policy sets the conditions under which [Company] allows automated systems, including AI agents, to buy goods and services for it. It applies the Delegation of Authority Policy to those systems.
2. Scope
This Policy applies to any automated system that can communicate or negotiate with vendors about purchases, place orders, accept terms, start or change subscriptions, or commit [Company] to spend (a “Procurement Agent”). It does not apply to systems that only recommend purchases for a person to place. Those purchases are governed by [Company]’s ordinary purchasing policy and the Delegation of Authority Policy, applied to the person who places them.
3. Authority levels
Each Procurement Agent’s mandate assigns it one of these levels:
(0) Recommend. Suggests purchases, and a person places them. This level is outside this Policy and is listed so the scale is complete.
(1) Communicate. Requests quotes and information, but makes no commitments.
(2) Negotiate. Discusses terms but may not agree to them. This is an internal restriction: its system must block it from sending an acceptance, and vendors must be told in writing that its statements are not commitments.
(3) Agree subject to confirmation. Reaches terms that bind only after a named approver confirms them.
(4) Execute within limits. Places orders that bind [Company] within its mandate’s limits.
Dollar limits are set separately in the mandate. A Procurement Agent may be given only the tools and credentials its level needs.
4. Approval of deployment
A Procurement Agent may be deployed only under a written mandate approved by a person with authority under the Delegation of Authority Policy for the purchases it will make. Its limits may not exceed that person’s own. Each mandate also names the Procurement Agent’s business owner (the individual accountable for its activity) and a backup. Deployments with an aggregate limit above $[amount] per month, or that permit payments, signatures or acceptance of nonstandard terms, also require approval by [the approving person’s manager / the CFO]. Each mandate is recorded in the Agent Registry before credentials are issued. If an approver leaves, changes roles or has their delegated authority reduced, [Company] pauses the Procurement Agent until the required approvals are recorded again.
5. What agents may buy
Procurement Agents may buy only the categories listed in their mandate. They may not:
(a) enter commitments longer than [12] months or with minimum spend;
(b) buy capital equipment above $[amount];
(c) buy services that involve personal data without a data processing agreement in place; or
(d) take any action that requires board, committee, or stockholder approval.
6. Vendors
Procurement Agents may buy only from vendors on [Company]’s approved vendor list, maintained by [Procurement], that have signed a master agreement with designated agent, no-override and cancellation terms.
7. Limits and controls
(a) Enforcement. The orchestrator or ordering tool must check each order against the mandate before the Procurement Agent sends it or accepts terms. Where the check uses a credential, the system processing the request must verify the applicable permissions. Per-order, period and per-vendor amount limits must always be enforced this way. Where another limit cannot be, a reviewer under section 8 must verify compliance before the agent acts, or the mandate must be narrowed to exclude the action. Limits stated only in a Procurement Agent’s instructions do not satisfy this Policy, and neither does a cap on a payment instrument alone, because an order can bind [Company] before any charge is made and orders on account or invoice involve no charge at all.
(b) How limits apply. Each mandate must distinguish the limits stated to vendors from checks enforced only inside [Company]. Limits must apply per order, per period and per vendor, so that splitting an order does not avoid them. Orders far above a Procurement Agent’s normal pattern require confirmation by a named approver.
(c) Aggregate limits. Period and aggregate limits must be checked against a single record of all of [Company]’s agent commitments, pending and completed, across vendors and agents, so that orders placed at the same time cannot together exceed a limit.
(d) Payment instruments. Payment instruments must be single-purpose and capped at the mandate’s limits, as a backstop.
(e) Separation of duties. A Procurement Agent may not pay invoices, add vendors, change vendor bank details or payment instructions, or approve its own orders.
8. Human approval
For actions otherwise permitted by the mandate, orders above $[amount], the first order with a vendor, the first order under an applicable Agent Transaction Addendum, new subscriptions, plan changes and any nonstandard terms require approval by a named approver whose own authority under the Delegation of Authority Policy covers the order. Approval must be an affirmative decision after seeing the order’s material terms, by an approver authenticated with multi-factor sign-in. Approval by default or by another automated system is not approval, and neither is notice after the order is placed. If the approval step is unavailable, the Procurement Agent must wait. A refusal ends the request. A change to the vendor, amount or other material terms requires a new approval. Each approval step authorizes only the action described for it, such as sending a message, accepting terms or placing the order, and the record of each approval states the approver, what the approver saw and the limit the approver acted under.
9. Credentials, subagents and ending authority
Each Procurement Agent has its own identity and credentials. Procurement Agents may not use employee logins or shared keys. A Procurement Agent may hand work to another automated system only if its mandate permits it. Each such system has its own credentials, limited to its part of the task, and may not use the Procurement Agent’s credentials. Its commitments count toward the Procurement Agent’s limits and may not together exceed them, and its credentials end automatically when the Procurement Agent’s end. Credentials expire no later than the mandate’s end date and are revoked when the mandate ends or changes. When a mandate ends or its limits are narrowed, [Procurement] notifies each affected vendor promptly through the channels its agreement requires, within [one] business day or any shorter applicable deadline. Record when the vendor received notice and when the change takes effect under its agreement.
10. Terms and negotiation
Procurement Agents may negotiate only the terms listed in their mandate. They may not accept click-through or other interface terms that differ from the master agreement. The agent must stop before accepting any other term. Procurement may take up the proposed change separately.
11. Monitoring and review
(a) Notice addresses. Notice addresses given to vendors must be monitored shared inboxes, not an individual’s mailbox.
(b) Triage. The business owner, or a named backup when the owner is unavailable, reviews each alert of an action outside a mandate, and each confirmation or notice from a vendor, within [one] business day of receipt and early enough to meet each applicable dispute or rejection deadline. For orders where shipment cuts off rejection, route an alert immediately when the order is placed so the owner or backup can act before shipment.
(c) Disputes. Before the deadline in paragraph (b), orders outside the mandate are disputed in writing and, where the vendor’s agreement gives that right, rejected or cancelled under it. [Company] does not use goods or services obtained under a disputed order while the dispute is open.
(d) Periodic review. The business owner reviews each Procurement Agent’s overall activity at least [weekly], and spending is reconciled monthly.
12. Incidents
Suspected unauthorized, erroneous or manipulated actions are handled under the Agent Incident Playbook. Staff must report them to [Procurement and Legal] at once.
13. Records
Mandates, approvals and the transaction records in agent logs (the mandate version, credential identifiers, counterparty, terms and result of each action) are retained for [six] years after the transaction, or longer if subject to a legal hold. Keep raw inputs only as long as needed under [Company]’s retention schedule. Across all records, redact, anonymize or remove personal details when the need ends, and preserve evidence subject to a legal hold. Never record credential secrets.
14. Ownership and exceptions
[The CFO] is responsible for maintaining this Policy. Legal questions about it go to [General Counsel]. Exceptions require written approval by [the CFO and General Counsel] and are recorded in the Agent Registry. This Policy is reviewed at least annually and when laws or controls change.
Related: Corporate Authority for Agents · Building Limits into Agent Systems · Agent Incident Playbook