manage-procurement

Find pending purchase orders safely by searching procurement records via the Ramp CLI, inspecting PO details, and approving the matched unified request UUID only after confirming intent. This workflow prevents mixing up identifiers during approval.

A unified request UUID is the required approval target identifier for procurement workflows. You must pivot from a purchase order number to the unified request UUID to execute approve or reject actions correctly.

JSON search filters procurement records by applying JSON-driven filters to query purchase orders and unified requests. This mechanism retrieves specific POs by vendor or number while respecting pagination cursors.

Yes, you can review pending approval steps before acting. The workflow pulls authoritative details for a unified request, presents key identifiers and statuses, verifies the approval step, and requires confirmation before executing.

Approving directly with a PO number risks mixing up related identifiers. The safe workflow requires inspecting the purchase order, pivoting to the unified request UUID, and confirming intent through a confirmation gate before action.

Yes, procurement approval workflows respect pagination cursors when searching pending queues and retrieving unified requests. This ensures complete record retrieval when reviewing large volumes of pending approvals.