> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/playbooks/procurement.md).

# Procurement

These playbooks cover the core procurement workflows that Riff teams automate or build into Apps. Written for buyers, procurement leads, and sourcing managers — not developers.

| Playbook                                                                               | What it does                                           | Best fit    |
| -------------------------------------------------------------------------------------- | ------------------------------------------------------ | ----------- |
| [Chase supplier confirmations](/playbooks/procurement/chase-supplier-confirmations.md) | Follow up on unconfirmed purchase orders automatically | Agent       |
| [Run an RFQ](/playbooks/procurement/run-an-rfq.md)                                     | Send and track requests for quotation across suppliers | Agent + App |
| [Match purchase orders to invoices](/playbooks/procurement/match-purchase-orders.md)   | Reconcile GR/IR and flag discrepancies before payment  | Agent       |
| [Handle delivery exceptions](/playbooks/procurement/handle-delivery-exceptions.md)     | Surface and action inbound delivery discrepancies      | Agent + App |

## ERP compatibility

These playbooks are written for teams running **Infor LN / M3**, **SAP S/4HANA**, **Oracle ERP Cloud**, or **Microsoft Dynamics 365**. Where steps differ between systems, the playbook calls it out.

## Agent or App?

* **Agent** — runs on a schedule, acts on your ERP directly, escalates only when it needs a human call. Best for routine, high-volume tasks (chasing confirmations, matching POs).
* **App** — a screen your team opens to see status, take action, and approve decisions. Best for exception handling and approval workflows where a human needs to be in the loop.

Many procurement workflows use both: an Agent flags exceptions, an App lets the team action them.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.riff.ai/playbooks/procurement.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.