Projects
Projects group procurement activity under a named initiative—so you can tie purchase orders to a project, watch spend against an allocated budget, and report by project.
Overview
Use projects when spending should be attributed to:
- Capital builds or internal initiatives
- Client or program codes
- Any structure where budget and reporting must roll up by project
Each project acts as a container for linked POs and related spend visibility.
Creating projects
Step 1: Open Projects
- Navigate to Projects from the main menu (or procurement section)
- Click New project / Create
Step 2: Enter project details
| Field | Notes |
|---|---|
| Name | Clear, recognizable project title |
| Code | Often auto-generated by the system for uniqueness |
| Department | Owning department (if applicable) |
| Budget allocation | Planned amount or budget link for tracking |
Step 3: Save
Save the project. You can return later to adjust metadata if your role allows.
Naming consistency
Agree on a naming pattern (client + phase, fiscal year, etc.) so reports and searches stay easy for everyone.
Linking POs to projects
When creating or editing a purchase order:
- Locate the Project field (or equivalent)
- Select the target project from the list
- Save the PO
Linked POs roll into project spend and project-focused reports.
Project-based budget tracking
With a budget allocation on the project (or linked budget):
- Committed and spent amounts typically aggregate from linked POs (and related documents, per configuration)
- Thresholds and alerts may mirror department budget behavior
Use the project detail or budget views to see remaining capacity.
Project spending reports
Run or schedule reports that group or filter by project:
- Total spend and commitments by project
- Comparison across projects for a period
- Drill-down to POs tied to a project
Pair with Reports & Analytics for standard report entry points.