# Procurement To Pay

> Optimize the procure-to-pay cycle — requisition, purchase order, receipt, invoice, and payment — for control, speed, and cash outcomes. Use when fixing AP bottlenecks, maverick spend, or three-way match processes.

- Skill: `itsual/procurement-to-pay` (Agent Skill)
- Install (CLI): `npx skillmds@latest add itsual/procurement-to-pay`
- Raw SKILL.md: https://api.skillmd.com/api/skills/itsual/procurement-to-pay/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Finance & Business
- Author: itsual (https://skillmd.com/u/itsual)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/itsual/procurement-to-pay

---


# Procure-to-Pay

## Overview

Procure-to-pay (P2P) is the end-to-end path from needing something to paying for it. Strong P2P reduces leakage, fraud, and friction.

## When to Use

- AP process improvement
- Implementing PO requirements
- Vendor master and payment controls
- Cycle time reduction for legitimate spend

## Core Practices

- Define when POs are required vs exception paths
- Enforce three-way match where appropriate
- Clean vendor master data and bank detail controls
- Route invoices efficiently; minimize email attachments chaos
- Capture early-pay discounts when ROI-positive

## Principles

- Maverick spend is a process design failure
- Controls at vendor setup prevent payment fraud
- Speed and control can coexist with good system design
- AP is a working capital and relationship function

## Verification

- [ ] PO and match rules match risk levels
- [ ] Vendor change controls are strong
- [ ] Invoice cycle time is measured