--- title: Base system procurement case type reference description: Procurement Case Management provides 13 base system case types that classify procurement work. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/source-to-pay-operations/sourcing-and-procurement-operations/base-system-procurement-case-types.html release: australia product: Sourcing and Procurement Operations classification: sourcing-and-procurement-operations topic_type: reference last_updated: "2026-04-13" reading_time_minutes: 5 keywords: [procurement case types, base system case types, procurement case management, PCM, sourcing and procurement operations, SPO, case type reference] breadcrumb: [Reference, Sourcing and Procurement Operations, Finance and Supply Chain] --- # Base system procurement case type reference Procurement Case Management provides 13 base system case types that classify procurement work. ## Purchase modification cases Purchase modification cases are initiated by a requestor or shopper from within ShoppingHub.
| Case type | Purpose | How it is created |
|---|---|---|
| **Edit a purchase** `edit_purchase` | Modify an existing purchase requisition or purchase order — for example, to change quantity, price, delivery date, or line items. | Requestor selects the edit action in ShoppingHub. The system creates a purchase modification record and the `create_procurement_case` subflow creates the case. |
| **Return a purchase** `return_purchase` | Return received goods to the supplier. | Requestor selects the return action in ShoppingHub. The system creates a purchase modification record and the `create_procurement_case` subflow creates the case. |
| **Replace a purchase** `replace_purchase` | Replace damaged, incorrect, or defective goods. | Requestor selects the replace action in ShoppingHub. The system creates a purchase modification record and the `create_procurement_case` subflow creates the case. |
| **Edit a receipt** `edit_receipt` | Correct a receiving record after goods have been received — for example, to adjust the quantity received. | Requestor selects the edit receipt action in ShoppingHub. The case is handled end-to-end by the Edit a Receipt playbook. |
| Case type | Purpose | How it is created |
|---|---|---|
| **GL Coding Review** `gl_coding_review` | Verify and correct the general ledger account coding on a purchase line before the order is placed. | Automatic — the Task Generation Decision Table creates the case when a purchase requisition is submitted and the GL coding review rule fires. |
| **Budget Review** `budget_review` | Confirm that sufficient budget exists for the purchase before the order is placed or sourced. | Automatic — the Task Generation Decision Table creates the case when a purchase requisition is submitted and the budget review rule fires. |
| **Contract Review** `contract_review` | Review applicable contracts before the purchase proceeds. | Automatic — the Task Generation Decision Table creates the case when a purchase requisition is submitted and the contract review rule fires. |
| **Send NDA for Signature** `send_nda` | Send a non-disclosure agreement to the supplier associated with the purchase for signature before the purchase proceeds. | Automatic — the Task Generation Decision Table creates the case when a purchase requisition is submitted and the NDA rule fires. |
| **Delivery Address Review** `delivery_address_review` | Verify and approve the delivery address on a purchase before the order proceeds. The case is created when the delivery address on the purchase requisition requires verification or company approval. | Automatic — created by the system when a purchase requisition is submitted and the delivery address on a line item requires review. Requires the Purchase Modification Content Pack \(`sn_spend_cp`\). |
| **Due Diligence** `due_diligence` | Conduct a supplier due diligence assessment before a purchase proceeds. | Manual — opened by a procurement specialist — or automatically via the Task Generation Decision Table during supplier qualification. The case is initially assigned to the user who creates it. |
| Case type | Purpose | How it is created |
|---|---|---|
| **Inquiry** `inquiry` | Request general support or ask a question of the procurement organization. | Employee submits the **Ask procurement** catalog item in the Service Catalog or Employee Center. |
| **Request a Corporate Card** `request_cc` | Request a corporate purchasing card for business expenses. The procurement or finance team processes the request and coordinates card issuance. | Employee initiates the request. The specific catalog item or portal entry point is configured during implementation. |
| **Request a copy of contract** `request_contract_copy` | Obtain a copy of an existing supplier contract for reference. | Employee submits the **Request a copy of contract** catalog item in the Service Catalog or Employee Center. The system links the case to the relevant contract record and populates the case description with the contract number. |