## TL;DR

Some spend cannot have POs (utilities, rent, subscriptions), so banning no-PO invoices just drives workarounds. Allow them by category with coding requirements, approval thresholds, and budget checks; everything else needs a PO. Monitor the no-PO rate: a rising share means the PO process is failing, not that the policy is working.

## Steps

1. Define allowed no-PO categories (rent, utilities, subscriptions).
   Expected: An explicit allowlist.
2. Require GL coding and cost center on every no-PO invoice.
   Expected: Accountability without a PO.
3. Apply approval thresholds, tighter than PO spend.
   Expected: Compensating control.
4. Check against budgets before approval.
   Expected: Spend control.
5. Track the no-PO rate and investigate rises.
   Expected: Policy health metric.

## When to use

- Non-PO spend policy design
- Recurring overhead invoices
- PO process bypass analysis

## When not to use

- PO-based purchasing
- Capital expenditure
- Fraud investigation

## Compatibility

ERP-agnostic.

## Variant phrasings

### non-PO invoice policy

### no PO invoice approval

### allowlist no-PO spend

## Root cause

POs do not fit all spend, and forbidding the invoices does not stop the spend; it stops the visibility. Controlled no-PO processing keeps the spend visible and approved.

## Edge cases

- Employees splitting purchases to avoid PO thresholds is a policy violation, not a no-PO case
- New categories need periodic allowlist review
- Tax treatment still needs review on no-PO invoices

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_YKtur1ifSouoFULOCdyQdA