The integration between the Contractor Profile and the Public Register of Contracts, planned for the second half of 2025
Share
Over the past few months, through different press releases, we have been providing information about the project ofenabling the integration functionality of the Public Procurement Services Platform (hereinafter PSCP), which hosts the contracting profiles of the contracting bodies of Catalonia and is the tool through which they must advertise all phases of the tenders and other information related to the contracting process, and the Public Registry of Contracts (hereinafter RPC), necessary to send theinformation regarding awarded contracts.
The goal of this integration, is that with a single action by the contracting authority, the files and the data are published in the two eContracting tools.
The expectation is that this tool will be available to all contracting authorities. before the end of the second half of 2025, specifically:
15/9/2025: the integration of supramunicipal local entities will be activated: County Councils and Provincial Councils.
By the end of October 2025 (pending specific date) will be activated the integration of other local entities and entities in the university field.
When will the published data from the Contractor Profile be transferred to the Public Register of Contracts?:
For files created in the Contractor Profile, from the activation date of the integration of the contracting body in question, will be sent to the RPC from posting, in the Contractor Profile, of the phase in which his/her improvement.
What phases and documents will be transferred to the Public Registry of Contracts?:
1.- Phase of formalization of procedures that have gone through the rest of the previous phases.
2.- Award phase in the types of contracts or publications below.
Contract based on framework agreement
Specific contracts for dynamic purchasing systems
Minor contracts
Abbreviated simplified open
Contracts with emergency processing
Publications of minor/based and specific dynamic systems aggregate contracts.
3.- Formalization phase, in cases that have not been sent for adjudication.
4.- Execution phase:
Objective modifications
Exaggerate
Extinctions
The documents sent to RPC, if necessary, must meet the following characteristics:
PDF Format
Maximum size 10 MB
What publications will not be sent to the Public Register of Contracts?
Initially this integration will have, as an exception, some assumptions that will not be transferred to the RPC (given that, coinciding with the renewal of the same, it is planned to gradually reduce them):
Framework agreements
Dynamic acquisition systems.
Purchase by items/multiple bidders
Direct executions
Subjective modifications
Other enforcement actions
Lots vacant before the award.
Aggregated publications with multiple awardees (regardless of the type of aggregate)
2.- File managers who automatically report data to the Publications Manager of the PSCP (due to the integration usage mode), they must have adapted to inform these necessary fields so that the phases can be published. It is necessary to take into account the latest version of the specific messaging integration document PSCP.
3.- In the Publications Manager PSCP Two consoles will be enabled that will allow:
-Tracking the status of shipments from the PSCP towards the RPC. The console allows you to view the status of contracts sent based on filters. Additionally, the PSCP sends information emails in the event that any error occurs during the sending.
-The settlement of aggregate minor contracts.
Aspects to take into account by entities that have developed integration with the Public Registry of Contracts from their procurement file managers.
Initially, the new integration services will coexist with the RPC, from the PSCP, and the web services of the RPC already existing, for third-party contracting managers. However, these directly integrated applications will receive a -1 error for those contracts that attempt to pass and have already been sent by the PSCP previously
This error -1 may contain one of the messages below, which integrators must take into account to interpret correctly in order to keep the registration number in the RPC of the contracts that are already sent, and give these messages as vàlids from your system.
Contract Answer:
"There is a contract with the same file number, the existing registration number is (…)"
"A contract cannot be modified through the JCCA."
"A contract validated by the JCCA cannot be modified."
Settlement Response:
"The data of a settlement sent to the JCCA cannot be updated."
"The data of a settlement validated by the JCCA cannot be updated."
