- Electronic contracting
The integration between the Contractor Profile and the Public Register of Contracts, planned for the second half of 2025
The next September 15 The integration between the Contractor Profile and the Public Register of Contracts of supramunicipal local entities, that is, county councils and provincial councils, will be activated, as we have already discussed. previous publications.
THEgoal 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 functionality will be available to all contracting authorities. before the end of the second half of 2025.
Below you will find general information regarding how the integration works:
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 the 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 the 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 cases 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)
- Settlements of minors under 5.000 euros.
What changes does integration imply?
1.- At the moment it is activated, on the dates specified above, the PSCP fields, added to the version of 22/05/2024 and detailed in this publication, will become mandatory: The Public Procurement Services Platform incorporates new fields to prepare for integration with the Public Contract Register
2.- File managers who automatically report data to the PSCP Publications Manager (for the integration use mode), must have adapted to report these necessary fields so that the phases can be published. It is necessary to take into account the latest version of the PSCP-specific messaging integration document.
3.- Two consoles will be enabled in the PSCP Publications Manager that will allow:
-Monitoring the status of shipments from the PSCP to the RPC. The console allows you to view the status of contracts sent based on filters. In addition, the PSCP sends information emails in the event that an error occurs in the shipment.
-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 existing RPC web service, for third-party procurement managers. However, these directly integrated applications will receive a -1 error for those contracts that attempt to pass and have already been previously sent by the PSCP.
This error -1 may contain one of the messages below, which the integrators must take into account to interpret correctly in order to be able to keep the registration number in the RPC of the contracts that have already been sent, and give these messages as valid 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."