Native requisitions

Native requisitions

When the organization has the native requisitions module enabled, every purchase created from Create Request is first registered as an internal requisition (code REQ-00042) before becoming a purchase (PR). For the buyer, the Create Request experience stays the same as always: if there's no approval workflow blocking it, the requisition is instantly converted into the usual purchase, with no extra steps.

Approval workflow (optional)

An organization admin can configure an approval workflow for requisitions from Approvals, under the "Purchase requisitions" process. If the process is active and the requisition requires approval, it's left pending: whoever has the assigned step gets a notification ("Requisition approval pending") and must approve or reject it from their approvals inbox before the requisition turns into a purchase.

The requisitions tray

Native requisitions left pending approval (or created by a user without permission to launch purchases) show up in the tray together with requisitions coming from the ERP. They're marked with the "Internal" tag and can be filtered by origin from the list's origin filter. Once approved (or if they didn't require approval), they're ready to be launched as a purchase from the tray.

Notifications to the requester

Whoever created the requisition gets a notification with the outcome:

• If approved: "Requisition approved" — "Your requisition {code} was approved and moved to purchasing."
• If rejected: "Requisition rejected" — "Your requisition {code} was rejected." (with the reason, if the person who rejected it left one).

There's no separate notification announcing the final purchase (PR) number: the approval notice is what indicates the requisition "moved to purchasing."