Tender detail

Development and maintenance work for the tax accounting and allocation service (RmIT)

Summary

The tender concerns development and maintenance work for the information systems of the Estonian Tax and Customs Board’s accounting, claims and debt management services. A framework agreement will be concluded according to the contracting authority’s needs. The bidder must take into account previous experience, a quality management system, compliance requirements and exclusion grounds confirmations. Environmental requirements, joint tender rules and trade secret rules also apply, and a sample task and a signed confidentiality form may be required.

Reference number
307294-0000
Buyer
Riigi Tugiteenuste Keskus
Country
Estonia (EST)
Procedure
Open procedure
CPV
72262000 Software development services
Deadline
2026-06-15
Status
Open
Contract subject
Services
Estimated value
10 000 000 EUR
Source
RHR

Participation requirements

Tender requirements are available in the official tender documents.

Compliance requirements

The bidder must confirm that neither the bidder nor its management, administrative or supervisory body members, procurators or other persons authorised to represent it have been finally convicted in the last 5 years for participation in a criminal organisation, corruption, fraud, terrorist offences, money laundering, child labour or human trafficking, or for any other exclusion grounds listed in the ESPD. If any such ground applies, the bidder may in certain cases provide evidence of self-cleaning measures to restore reliability. The machine-readable notice listed the exclusion grounds, but the full list should be checked in the tender documents if needed.

Qualification criteria and exclusion grounds

The bidder must have completed at least 2 contracts in the last 36 months, each with a value of at least EUR 100,000 excluding VAT. Together, those two contracts must cover at least systems analysis and information system development and testing. Both contracts must have been delivered to and accepted by the client; if the work is handed over in stages, ongoing contracts may also be counted if the required volume has already been accepted. Framework agreements may not be used as reference contracts, but contracts concluded under a framework agreement may be used to prove qualification. The bidder must provide the contract details, including value, partner name, contact details, description of the work, contract period and, where applicable, the public procurement reference number. If the bidder relies on the capacities of other entities, an ESPD for those entities must also be submitted. The bidder must have a quality management system applied in software development that meets at least ISO 9001:2015 or an equivalent document. Equivalence may be demonstrated by a statement from an independent audit firm or an accredited certification body. The tender must comply with the procurement documents and, where necessary, equivalence must be explained and supporting evidence attached. Conditional tenders are not allowed. If architectural drawings, source code or a blurred copy of the database are needed to prepare the tender, they can be requested from the contracting authority together with a signed confidentiality undertaking. A sample task must be submitted with the tender, but the exact content of the sample task was not fully visible in the machine-readable notice; it must be checked in the tender documents.