Purchase Orders - admin/portfolio queue¶
| Stage | Building |
|---|---|
| Status | Partial |
| Design status | In progress |
| Estimate | 2w (M) |
| Confidence | Medium |
| Linear | PIN-254 ↗ PIN-137 ↗ |
| Linear status | Todo · +1 backlog |
| Cycle | C16 |
| Design | Design ↗ |
| Linear epic | Financial Management & Reporting |
| Module | Billing ↗ |
Priority: Medium · Route: /admin/purchase-orders
Scope¶
Cross-project admin queue for purchase order approvals: PM/estimator PO requests land in a company-wide review queue where Finance/Admin accept, reject, or request more info, with budget-vs-cost-code validation and tiered approval thresholds — distinct from the project-scoped PO tab. (Source: PIN-254, PIN-137.)
Acceptance criteria¶
- Admin queue page at
/admin/purchase-orderslisting pending PO requests across all projects - Budget validation warns (does not block) when a PO amount plus prior POs against the same cost code exceeds the budgeted scope amount
- Actions per request: Accept (manual Foundation issue today; API auto-issue later) / Reject with reason / Request more info (notifies the requesting PM)
- Tiered, admin-configurable approval thresholds (e.g. auto-approve under $5k, single approver $5k–$50k, two approvers above $50k)
- Permission-gated: only Finance/Admin roles see the queue; PMs see the status of their own requests
- Full audit log on every state transition
- Auto-numbered POs (
PO-{YY}-####) carry the same record through Issued / Received / Closed
Conor's comments¶
This ties into Project Detail - Purchase Orders
Notes¶
Two-level: project PO tab built; standalone admin center Under Construction
Open question for Conor¶
-