🕒 From what point are the files sent to the RPC?

  • The files that will be sent automatically are those created in the Publications Manager from the date the integration is activated (17/11/2025) and that reach the refinement phase. Those created before this date will not be sent automatically and will need to be entered by the contracting authority in the Public Contracts Registry.

  • The moment of transfer will be the publication in the Contractor Profile of the phase defined by the submission in each case (detail of the phases that are sent to the RPC).

📄 Phases and documents that are transferred to the RPC


1. Award phase , in the following cases:

  • 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 aggregate contracts of dynamic systems.

2. Formalization phase , in cases that have not been sent for adjudication.
3. Execution phase:

  • Objective modifications

  • Extensions

  • Extinctions

  • Deserted lots

4. Documents attached to publications sent to the RPC:

  • They must be in PDF format.

  • They must have a maximum size of 10 MB.

🚫 Posts that will not be initially sent to the RPC

  1. Framework agreements (not required to be reported to the PRC)

  2. Dynamic purchasing systems (not required to be reported to the RPC)

  3. Partnership for innovation  Multiple awardees (the current version of the RPC does not allow this)

  4. Pre-commercial public purchases (not required to be reported to the PRC)

  5. Term extensions  Settlements of minor contracts of less than 5,000 euros (they are settled automatically in the RPC).

  6. Cancelled lots that are not deserted (do not need to be reported to the RPC)

  7. Execution phase:

  • Direct executions.

  • Subjective modifications.

  • Other enforcement actions.

🔄 Changes implied by integration

1. The obligation to report the additional fields incorporated into the Publications Manager in the Contractor Profile is enabled with the aim of enabling integration in the version of 05/22/2024. You can consult the details in the publication: The Public Procurement Services Platform incorporates new fields to prepare for integration with the Public Contracts Registry.

2. Need to adapt file managers that publish automatically through the service integration mode, to report these fields in a mandatory manner. In the event that they do not do so automatically, users will need to incorporate this data manually in order to reach the publication. It is necessary to take into account the latest version of the specific messaging integration document of the PSCP.

3. New consoles at PSCP:

  • Tracking submissions to the RPC: Through this console, Publication Manager users will monitor submissions. Additionally, the tool sends email notifications to validators related to the publication, in the event that an error occurs in the submission.

  • Settlement of aggregate minor contracts

4. Incorrect/technical error contract messages or warnings in the RPC submission console:

If any contract has not been correctly sent to the RPC or has been left in warnings (has reached the RPC but has not been sent due to lack of some data) in the sending console, the tool will send an email informing the validators of the publication in the PSCP of the reason. In this case, details can be reviewed from the response visible in the RPC sending tracking console to identify what adjustment needs to be made to the publication or the RPC.

In the event that data needs to be modified or added to the PSCP publications, an amendment to the publication must be made so that the identified data is sent correctly to the RPC.

A common case that causes the publication to have to be amended in PSCP is the following example:

  • In the case of contracts with lots , it is also necessary to take into account that the number of lots reported in the contract data must correspond to the lots of the contract itself and not that of the reference framework agreement , in order to avoid common errors such as the one below. If this occurs, it will be necessary to amend the lot numbers of the contract publication in the PSCP so that the amendment is correctly transferred to the RPC:


There are cases where, for now, the action must be taken directly on the RPC screens, such as:

In this case, the RPC would report the message "Documents are missing to complete the contract" and it would be necessary to enter the RPC to report the document and complete the submission.

  • Another common error casuistry may be that the contract to be sent is based on a framework agreement that does not exist in the RPC . In this case, the error below would be received and it would be necessary to request the creation of the framework agreement in the RPC so that automatic sending can be done.


  • Finally, there is a currently common casuistry that can occur and that requires specific action by the body so that the data is well informed in the RPC. This is the amendment of the contract development phases (award or formalization according to procedure), which were already sent to the RPC and are in Advisory Board status . Given the current functioning of the RPC, these cases cannot be modified automatically, taking into account that the data and it is necessary to request the Advisory Board of Public Contracts, the modification of the data sent, through the usual procedure described in " Request the RPC service " "[ Request form for correction of data in the RPC |

🔄 Aspects to take into account by organizations that have developed integration with RPC from their procurement file managers

Initially, the new integration services with the RPC, from the PSCP, and the existing RPC web services, for third-party contracting managers, will coexist. 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 integrators will have to take into account to interpret correctly in order to retain the registration number in the RPC of the contracts that have already been sent, and to give these messages as valid from your system.

Contract response:

  • “There is a contract with the same file number, the existing registration number is (…)”.

  • “A contract submitted to the JCCA cannot be modified.”

  • “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.”