The Requisitions Report is a comprehensive historical dataset used to track the lifecycle of a request from its initial creation through to its final approval and conversion into a Purchase Order. This report is essential for auditing procurement activity and measuring the efficiency of your internal approval workflows.
Purpose of the Report
This report is the primary tool for Procurement Administrators and Department Managers to:
- Audit Request History: Review the justification and approval path for all completed requests.
- Measure Workflow Efficiency: Analyze the Cycle Time to see how long it takes for a request to become an order.
- Compliance Tracking: Review justifications provided for non-catalog or high-value purchases.
- Spend Forecasting: Look at approved requisitions to anticipate upcoming invoice volumes.
- Sample report: Unimarket Requisitions Report Example
How to Analyze Performance
- Cycle Time Analysis: Sort by Cycle Time (Hours) to find outliers. Requests with high cycle times but a low No of Approvals may indicate that a specific individual is causing delays.
- Justification Audit: Periodically review the Justification column, to ensure users are providing sufficient detail for audit purposes; especially for non-standard or expensive items.
- Workflow Complexity: Compare the No of Approvals against the Cycle Time. If certain departments have a high number of approvals that lead to significant delays, it may be time to streamline their approval rules.
- Retrofit Identification: Check the Created From Invoice column to identify how many requisitions are being generated, after a supplier has already billed you.
Note: This report provides a "header-level" view of the requisition. For more granular details on the specific items within these requests, refer to the Requisition Items in Progress report.
Report Scope and Logic
- Inclusions: All requisitions created within the specified date range.
- Exclusions: This report automatically excludes requisitions that are Incomplete or Abandoned. Ensuring that your data only reflects requests that were actually submitted for approval.
- Key Metric (Cycle Time): The report calculates Cycle Time (Hours) as the duration from when a requisition is initially created to the time, it is fully approved.
Report Columns and Definitions
Requisition Identity & Status
| Column Name | Description |
| Requisition Number | The unique identifier for the request. |
| Requisition Date | The date the requisition was first created. |
| Requisition Type | The nature of the request (e.g., Standard, Blanket). |
| Requisition State | The current status (e.g., Approved, Declined, Order Created). |
| Order Number | The resulting Purchase Order number (if already generated). |
| Order Submission | Details regarding how the order was sent to the supplier. |
Users and Organization
| Column Name | Description |
| Requester | The user who owns the requisition. |
| Buyer | The user who finalized/submitted the requisition. |
| OBO | The "On Behalf Of" user, if applicable. |
| Org Unit | The department or group associated with the spend. |
Financials & Accounting
| Column Name | Description |
| Subtotal / Tax / Total | The financial breakdown of the requisition value. |
| Blanket Amount Sent | The value sent to the supplier for a blanket order. |
| Blanket Amount Hidden | The internal value of a blanket order not shared with the vendor. |
Justification & Approvals
| Column Name | Description |
| Justification Type / Justification | The reason provided by the user for the purchase. |
| Approved Date | The date the final approver cleared the request. |
| Cycle Time (Hours) | The total time from creation to full approval. |
| No of Approvals | The total number of approval steps the request passed through. |