--- title: Create a requisition on Coupa through Procurement application description: Create software requisitions directly on Coupa through the ServiceNow Procurement application to purchase software. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-asset-management/procurement/create-req-coupa.html release: australia product: Procurement classification: procurement topic_type: task last_updated: "2026-03-12" reading_time_minutes: 5 breadcrumb: [Integrating with Coupa, Integrating with external procurement applications, Procurement, Common applications, Asset Management] --- # Create a requisition on Coupa through Procurement application Create software requisitions directly on Coupa through the ServiceNow Procurement application to purchase software. ## Before you begin To create a requisition on Coupa through ServiceNow Procurement application, you must perform the following tasks. - Create and publish a Coupa integration profile. For more information see, [Create a Coupa integration profile](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/procurement/create-coupa-int-profile.md). - Ensure that the Purchase Order you create has at least one Purchase Order Line, and all Purchase Order Lines must be for software products. - Synchronize reference data types on both ServiceNow Procurement and Coupa applications. For more information, see [Reference data synchronization](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/procurement/ref-data-coupa.md). If all these conditions are met, you can create a requisition in Coupa. If the conditions aren’t met, requisitions aren't created on Coupa, and the legacy procurement flow continues on the Procurement application. Role required: sam\_admin and procurement\_integrator **Note:** The procurement\_integrator role is added to the sam\_admin role. The procurement\_integrator role enables the SAM admin to view the connections and aliases. ## About this task You can create a requisition on Coupa through the following ways: - When a user requests software through Service Catalog. For more information, see [Request a catalog item from Service Portal](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/request-cat-item-portal.md). - If a procurement\_user or sam\_admin directly creates a Purchase Order on the Procurement application. For more information, see [Create a Purchase Order](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/procurement/t_CreateAPurchaseOrder.md). - When a sam\_user creates a Purchase Order directly from the Remediation Options form. For more information, see [View software model results](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/t_ViewSWModelResults.md). Requisitions are of the following types: - **Catalog request**: A requisition created for an item that is already present in the external purchasing application. - **Non catalog request**: A requisition created for an item that isn't present in the product catalog of the organization. For more information about creating a Purchase Order, see [Create a purchase order](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/procurement/t_CreateAPurchaseOrder.md). ## Procedure 1. Navigate to **All** > **Procurement** > **Orders** > **Purchase Orders**. 2. Select **New**. 3. On the form, fill in the fields.
| Field | Description |
|---|---|
| Number | The unique number identifying the purchase order. |
| Due by | The date by which the purchase order **Total cost** must be paid. |
| Vendor | The supplier to which the purchase order was issued. |
| Ship to | The stockroom to which the items on the purchase order should be shipped.**Note:** This field is required but doesn't affect creating requisitions for software on Coupa. |
| PO date | The date on which the purchase order was created. |
| Status | The status of the purchase order: **Canceled**, **Ordered**, **Received**, **Requested**, or **Suspended**. |
| Assigned to | The user to whom the purchase order is assigned. |
| Bill to | The location responsible for paying the purchase order **Total cost**. |
| Short description | A brief description of the purchase order. |
| General section | |
| Shipping | The delivery method to be used when shipping the items on the purchase order. |
| Terms | The purchase order payment terms: **Credit**, **Net 30 days**, or **Net 90 days**. |
| Ship rate | The amount that must be paid for the delivery method specified in the **Shipping** field. |
| Total cost | The sum of all item costs on the purchase order and the shipping costs. |
| Description | A full description of the purchase order contents. |
| Details section | |
| Initial request | The record number of the request that requires the items on the purchase order. |
| Requested by | The user requesting the items on the purchase order.**Note:** The email ID or email address of the user requesting the items on the purchase order must be the same on both Coupa and ServiceNow Procurement application. |
| Requested | The date the user in the **Requested by** field requested the items on the purchase order. |
| Ordered | The date and time of clicking the **Order** button on the Purchase Order form. |
| Expected delivery | The date the items associated with the purchase order are expected to arrive in the stockroom identified in the **Ship to** field. This field can’t be edited when the purchase order has a **Status** of **Received** or **Canceled**. \(For more information about this field, see[Purchase order expected delivery date](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/procurement/r_SetExpectDelDateOnPurchOrder.md).\) |
| Received | The date and time at which the purchase order status changed to **Received**. |
| Contract | The record number of the contract with the vendor from which the items on the purchase order are ordered. |
| Department | The department responsible for paying for the purchase order. |
| Budget number | The budget number related with the purchase order. |
| Vendor account | The vendor account related with the purchase order. |