## TL;DR

Blanket POs authorize spend up to a ceiling over a period, and invoices draw down against it. Match each invoice to the blanket PO, track cumulative spend against the ceiling, and validate that the invoice falls within the effective dates and category scope. Alert as spend approaches the ceiling so renewals happen before invoices start failing.

## Steps

1. Identify the blanket PO and its ceiling, dates, and scope.
   Expected: The authorization envelope.
2. Match the invoice category and date against the envelope.
   Expected: Scope validation.
3. Add the invoice to cumulative spend.
   Expected: A running drawdown.
4. Check ceiling headroom.
   Expected: Early warning on exhaustion.
5. Route over-ceiling invoices for PO increase or new PO.
   Expected: Explicit re-authorization.

## When to use

- Blanket or standing orders
- Recurring service invoices
- Consumables purchasing

## When not to use

- Discrete one-time POs
- Capital purchases
- Non-PO spend

## Compatibility

ERP-agnostic; supported by NetSuite, SAP, Oracle blanket PO types.

## Variant phrasings

### blanket PO matching

### standing order invoice

### drawdown against blanket PO

## Root cause

Blanket POs trade line-level precision for flexibility. The control moves from line matching to envelope enforcement: ceiling, dates, and scope.

## Edge cases

- Releases against blanket POs restore line-level control where needed
- Price changes within the blanket period need the escalation path
- Auto-renewal of blankets needs procurement sign-off

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_c2zSGzY-8u0EB7-9ZVFuLw