Moldova: Ministry of Finance

The Ministry of Finance tracks information in MTender.

You can explore this dataset through our business intelligence tool. (You can change the language using the icon at the top-right.)

According to Law No. 131 on public procurement, all public entities are required to use MTender for procurements above the following thresholds:

  • State owned enterprises
    • 2,300,000 MDL for goods and services
    • 90,000,000 MDL for works
    • 13,000,000 MDL for social and other services
  • Other public entities
    • 200,000 MDL for goods and services
    • 250,000 MDL for works
    • 400,000 MDL for social and other services
Available formats:
JSON
Excel
CSV
Access

Overview

Data date range:
Oct 2018 - Oct 2026
Update frequency:
Real time
Last retrieved:
Oct 21, 2026 (retrieved monthly)
Retrieved from:
https://mtender.gov.md/en/public/for-civil
License:
http://opendefinition.org/licenses/
Publication policy:
http://opendefinition.org/licenses/
Main language:
Moldovan
OCID prefix:
test-b3wdp1

Data available

A contracting process has several stages: tendering, awarding, contracting and implementation. You can learn about the contracting stages in this tutorial.

These counts are the number of JSON objects across all contracting processes. Parties, tenderers and suppliers are unique within a contracting process, but can be repeated across contracting processes. You can learn about data publication in this tutorial.

Parties

Count of parties:
191,448

Planning

Count of planning activities:
125,774

Tenders

Count of tenders:
125,774
Count of tenderers:
0
Count of tender items:
203,578

Awards

Count of awards:
115,289
Count of suppliers:
107,254
Count of award items:
90,778

Contracts

Count of contracts:
0
Count of contract items:
0
Count of transactions:
0

Documents

Count of documents:
836,619

Milestones

Count of milestones:
0

Amendments

Count of amendments:
3,661

Extensions are used, such as lots, bids, enquiries, and local extensions for address details and conversions.

Data quality

Accessibility issues

To download this dataset, we use the OCIDs listed on https://public.mtender.gov.md, which publishes contracting processes under multiple OCIDs, and data is downloaded from http://public.eprocurement.systems/ocds/tenders/{ocid}, which publishes contracting processes under one OCID but has no endpoint to list OCIDs.

The /tenders/ endpoint lists contracting processes by date of last update, but returns empty responses for offsets older than about a year. The /tenders/plan/ endpoint lists contracting processes since 2018, but omits many processes that the /tenders/ endpoint lists. As such, OCIDs are listed from the /tenders/plan/ endpoint and, for processes updated in the past year, from the /tenders/ endpoint. Processes that are omitted from the /tenders/plan/ endpoint and that were not updated in the past year could be missed.

Quality issues

The dataset has quality issues to take into account, notably:

  • Contracts for which the award referenced in .awardID does not exist.
  • Discrepancies between organization identifiers in the data and in the IDNO register
  • All contracts have status ‘pending’

The dataset has minor issues that should not interfere with most uses. They include:

  • Blank and empty fields, including:
    • bids/details/documents/description
    • tender/items/deliveryAddress/description
    • awards/description
    • tender/documents/description
    • bids/details/documents
  • Placeholder values, including:
    • bids/details/documents/description
    • bids/details/statusDetails
    • awards/statusDetails
    • tender/lots/statusDetails
  • Awards and contracts for incomplete tenders
  • Tender amendments with a date which is before the tenderPeriod/startDate
  • Address data is provided using the addressDetails extension rather than the address.locality, address.region and address.country fields.

Last reviewed: Nov 2020

Access data

This OCDS dataset is available for download in JSON, Excel or CSV format. You can download the data for contracting processes in a specific year or for all time.

JSON

Each contracting process is represented as one line of JSON text in the .jsonl file.

The .jsonl file is compressed using Gzip. Windows users need 7-Zip, WinRAR or WinZip to decompress the .gz file.

Excel

Each contracting process is represented as one row in the main sheet. Other sheets link to it via the main_ocid column. In general, each sheet is linked to its parent sheet via the [sheet_name]_id column.

Excel files can have at most 1,048,576 rows. If a year is missing, it had too many rows. Download the CSV files, instead.

CSV

Each contracting process is represented as one row in the main.csv file. Other files link to it via the main_ocid column. In general, each file is link to its parent file via the [file_name]_id column.

The .csv files are archived using tar and compressed using Gzip. Windows users need 7-Zip, WinRAR or WinZip to decompress the .tar.gz file.

Do you have any questions or feedback on this dataset or any other content on this page?
Contact Data Support Team