Procurement Requests & Intake

Procurement requests and intake is the capture and management of requests for purchases, services, and financial transactions, from submission through approval. It is the entry point for all procurement activity, and when it runs on email and spreadsheets, requests stall and policies get bypassed. SmartSuite collects every request through a form, routes approvals with automations, and shows the pipeline on a dashboard, so procurement and finance see demand before it becomes a purchase order.

Each request type has its own form, with required fields and conditional sections that appear only when they apply: a purchase request asks for the vendor and quote, a travel request for dates and destination, a reimbursement for receipts. Submissions become records in the request table, complete on arrival. Requesters stop being asked for missing details.

Approval routing is an automation that reads the request type, value, and department and assigns the approvers in order, for example manager, then procurement, then finance above a threshold. Approvers act from a notification or their My Work list, and reminders and escalations keep the chain moving. Every approval and its timestamp stay on the request.

Policy checks are built into the forms and the workflow: required documentation, preferred vendor lists, and value limits are fields and rules, and a request that fails a rule is routed for exception review rather than approved. Procurement updates the rules in one place when policy changes. Audit teams see the rule and the exception on the request itself.

Each request links to the budget line it draws on in Budget Planning & Management, and rollups on the budget total the approved and pending requests against it. A formula flags a request that would exceed the remaining budget, and the approval automation routes it to finance for a decision. Department leaders see remaining budget on the same record they approve from.

Yes. Departments, locations, and entities can share one intake with routing rules per unit, or run separate request tables in the same workspace with permissions that keep them apart. Reporting rolls up across all of them for procurement and finance leadership. A new department is a set of routing rules, not a new system.

Dashboards show request volume by type and department, approval cycle times, the current backlog, and where requests wait longest, with each widget drilling into the requests behind it. Procurement uses them to clear bottlenecks; finance uses the same page for spend planning. Requesters see the status of their own requests without emailing anyone.

Efficiency comes from a complete request on day one, an approval chain that runs itself, and a record that carries into the purchase order without re-entry. Cycle times fall, exceptions become visible, and spend is checked against budget before it is committed. Over time, the request history supports better vendor and budget decisions.