Source-to-Contract Procurement Act Prerequisites

Peter Campbell Updated by Peter Campbell

Now that we know what the act is, here is what is needed to have the features enabled in your site.

Inside Source-to-Contract

Process Templates needs to be enabled and active in your site. 

The site also needs to have been provisioned with the Procurement Act features toggled on. This should be applied during the provisioning stage of your project, with your implementation project team however, can be done at a later date if required.

Once the Procurement Act features have been toggled on, the Procurement Act Dashboard (PA23) module will be visible in the Navigation Panel:

Externally to Source-to-Contract

You will need an eSender account. This involves registering as a buyer with the Cabinet office. Once this is complete, Cabinet will issue you with an API key that needs to be passed onto OneAdvanced.

It’s this API key that enables us to set up your site to publish notices to the CDP on behalf of your organisation.

Once This Has Been Done

Once you have provided OneAdvanced with these details and have the features enabled in your site, you will have to configure the site to ensure your notice requirements are accurate. More information on how to do this can be found in the Configuration section of the Navigating Procurement Act Features Within Source-to-Contract article.

Was this article useful?

Source- to-Contract and the Procurement Act

Navigating Procurement Act Features Within Source-to-Contract

Contact