ProcurementExpress purchase request management — the approver's workflow. Purchase requests are POs waiting for the current user's approval action (their approver queue). This is DIFFERENT from "purchase orders" which are approved/paid/delivered POs. CLI commands: pex po pending-requests|pending-count, then pex po show|approve|reject|override|cancel. Triggers on: pending requests, requests, how many requests, what needs my approval, approve request, reject request, my approval queue, approver queue, pending count.
pex po list --status=pending instead (see pex:purchase-orders skill).pex po list --status=approved (see pex:purchase-orders skill).Authenticate and set active company first (pex:setup skill).
# How many requests need my attention?
pex po pending-count
# List POs pending my approval (paginated)
pex po pending-requests # alias: pex po pending
pex po pending-requests --page=2
# View full PO details including approval tokens
pex po show 12345
Key fields in the response:
approver_requests[] — each has accept_token and reject_tokencan_cancel, can_override, can_edit — action permission flagsstatus, total_gross_amount, supplier_name, notes# Approve (requires accept_token from approver_requests)
pex po approve 12345 --token=<accept_token>
# Reject (requires reject_token from approver_requests)
pex po reject 12345 --token=<reject_token>
# Override and approve (finance role, no token needed)
pex po override 12345
# Cancel
pex po cancel 12345
1. pex po pending-count # check if anything needs attention
2. pex po pending-requests # list all pending requests
3. pex po show <id> # review details, get tokens
4. pex po approve <id> --token=... # or reject/override/cancel
# Add a comment before or after taking action
pex comment add-purchase-order 12345 --comment="Approved - within budget"