Direct-P2P Admins: Linking a Direct-P2P Cost Category to a Requirement

Modified on Wed, 5 Feb at 2:22 PM

Cost Categories must be linked to a Requirement in order to link approved suppliers and set Buyers access to use it for purchases. Please see here for more information on Cost Categories.


Access to a Cost Category on the Catalogue is limited to the organization(s), department(s), or team(s) designated as Buyers in the Requirement, and purchases can only be made from Suppliers who are marked as "Live" for the relevant Category or Lot within that Requirement.


You must first add a Category on your Requirement in order to link a Cost Category to. You can add multiple Categories if you have multiple different goods/services suppliers can be approved for within one Requirement.

  • Click '+Create New'
  • Tick the relevant Cost Category(s) you wish to associate with the Category
    • If you need to add a new Cost Category, you can click the '+Add Cost Category (Direct P2P)' button next to the search bar to quickly add a new one from within the same screen (without having to navigate out of your Requirement)
  • Click 'Save'

When you qualify a supplier for a Category, this will approve them for use for all the Cost Categories you've linked to that Category.


_____________________________________________________________________________________________________________________________________


⚠ Important


When adding a category, you will need to select your GL code. GL codes cannot be created via a Requirementthis must be performed by your system administrator within the Direct-P2P module. Administrators can see here for more information.


_____________________________________________________________________________________________________________________________________



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article