Skills Drill 11-1 Requisition Activity

Introduction

Skills Drill 11-1 Requisition Activity is a foundational educational exercise commonly found in accounting, supply chain management, and business administration curricula. It simulates the critical first step in the procurement cycle: the formal request for goods or services. This drill is designed to bridge the gap between theoretical knowledge of purchasing procedures and the practical application of generating, authorizing, and tracking a purchase requisition. By working through this activity, students learn to work through the documentation that triggers the expenditure of organizational funds, ensuring they understand the internal controls, data accuracy requirements, and workflow logic essential for effective resource management. Mastering this drill is not merely about filling out a form; it is about comprehending the lifeblood of operational readiness and financial accountability.

Detailed Explanation

The Context of Chapter 11: Purchasing and Inventory Controls

In most standard accounting and business textbooks, Chapter 11 typically focuses on Purchasing, Inventory, and Cash Disbursements. The "Skills Drill 11-1" label usually denotes the first practical application exercise in this chapter. Before a company can record a purchase order, receive inventory, or process a vendor invoice, a need must be identified and communicated internally. The Purchase Requisition is that internal document. It originates from a department (the "requestor") and flows to the Purchasing Department. This drill forces the student to act as the requestor, the approver, and sometimes the purchasing agent, providing a 360-degree view of the document's lifecycle.

Core Components of the Requisition Document

A standard requisition form—whether paper-based or digital within an ERP system like SAP, Oracle, or QuickBooks—contains specific data fields that the drill requires the student to populate correctly. These fields are not arbitrary; they serve distinct control purposes:

• Requisition Number: A unique, sequential identifier for tracking and audit trails.
• Date: Establishes the timeline for urgency and budget period allocation.
• Requestor Information: Department, employee ID, and delivery location (cost center).
• Vendor Suggestions: Often the requestor suggests preferred vendors based on past experience or specific technical requirements.
• Item Specifications: Detailed descriptions, part numbers, quantities, units of measure (UOM), and estimated unit prices.
• Account Coding: The General Ledger (GL) account number or project code to which the expense will be charged. This is critical for budgetary control.
• Authorization Signatures: Digital or physical approvals verifying budget availability and managerial consent.

The "Activity" Aspect: Simulation vs. Reality

The "Activity" component implies a simulated scenario. Students are typically given a narrative case study: "The Marketing Department needs 500 custom brochures for the Q3 trade show. The budget code is 6400. The preferred vendor is PrintCo." The student must translate this narrative into a structured document. This translation process—unstructured narrative to structured data—is the primary learning objective. It teaches the student that ambiguity in requisitions leads to procurement errors, wrong deliveries, and budget overruns.

Step-by-Step Concept Breakdown

Step 1: Need Identification and Specification

The drill begins before the form is even opened. The student must analyze the scenario to determine exactly what is needed. Vague descriptions like "office supplies" are insufficient. The drill demands specificity: "HP 962XL Black Ink Cartridges (Pack of 2), SKU: HEW12345." This step teaches the importance of standardized item masters and clear specifications to prevent the purchasing agent from guessing, which introduces risk Practical, not theoretical..

Step 2: Vendor Selection Justification

Many versions of Skills Drill 11-1 require the student to justify the vendor choice. Is it a sole source? Is it a preferred vendor contract? Are three quotes required per company policy? This step introduces procurement policy compliance. The student learns that the requisition is not just a wish list; it is a legal commitment trigger. Selecting a vendor without a valid contract number or ignoring the "three-bid rule" for purchases over a certain threshold (e.g., $5,000) is a control failure the drill highlights.

Step 3: Financial Coding and Budget Checking

This is often the most technically challenging part for students. They must locate the correct Chart of Accounts code. Charging "Marketing Brochures" to "Office Supplies Expense (6300)" instead of "Advertising Expense (6400)" distorts financial statements. The drill often includes a "Budget Availability Report" exhibit. The student must verify that the $2,500 expense does not exceed the remaining $3,000 balance in the Q3 Marketing budget. This enforces the concept of encumbrance accounting—reserving funds before the actual liability is created.

Step 4: Approval Workflow Routing

The activity usually requires mapping the approval path. A $200 requisition might need only a Supervisor approval. A $25,000 requisition might route: Supervisor → Department Head → CFO → Purchasing Director. The student must identify the correct authority levels based on the Delegation of Authority (DOA) matrix provided in the drill materials. This teaches organizational hierarchy and segregation of duties.

Step 5: Conversion to Purchase Order (The Handoff)

The final stage of the drill often simulates the Purchasing Department receiving the approved requisition. The student switches roles to become the Buyer. They must verify the requisition is complete, check for existing blanket purchase orders, and convert the requisition into a Purchase Order (PO) sent to the vendor. This demonstrates the "Source-to-Contract" transition and the critical segregation of duties: the person requesting the goods (Requestor) cannot be the person ordering the goods (Buyer) It's one of those things that adds up..

Real Examples

Scenario A: The Standard Stock Replenishment (Low Value, High Frequency)

Context: The Warehouse Manager notices safety stock levels for "12-inch Pipe Wrenches" have dipped below the reorder point. Drill Execution: The student fills out a requisition for 20 units. Because this is a standard catalog item with a standing Blanket Purchase Order (BPO) with "Industrial Supply Co.," the vendor field is pre-populated. The GL code is "Maintenance Supplies (1550)." The approval is automatic (system-approved) because it is against a pre-approved BPO. Lesson: Efficiency. Not every requisition requires manual negotiation. The drill shows how MRP (Material Requirements Planning) systems auto-generate these to reduce administrative burden Simple, but easy to overlook..

Scenario B: The Capital Expenditure (CapEx) Request (High Value, Complex)

Context: The IT Director requests a new Server Cluster costing $150,000. Drill Execution: This requisition triggers a completely different workflow. The student must attach:

1. A Capital Expenditure Request Form (justifying ROI/NPV).
2. Three competitive bids (RFP results).
3. IT Security Compliance Checklist.
4. Depreciation schedule estimates. The routing goes: IT Director → CIO → CFO → CEO → Board Committee (if >$100k). Lesson: Risk Management. High-value requisitions are business cases, not shopping lists. The drill teaches the gravity of financial commitment and the documentation required for audit defense.

Scenario C: The "Emergency" Requisition (Policy Exception)

Context: A critical production line motor burns out. Operations needs