Skip to content

Data Conversion Checks

The IMF provides an online tool to help countries convert data into the SDMX format required for their NSDP.

The source files are analyzed for conversion and a detailed report is provided on the following checks that were performed on the source file. 


To review these checks in detail, please click on the highlighted issue, which will show a breakdown of test results.



As highlighted below, some categories require additional action prior to conversion. For help on permitted excel format and additional tips see article on Common Excel Format Questions

Categories that do NOT prevent conversion: Users are encouraged to fix issues identified in this category.

  • Semantically Compliant: Ensures the underlying dataset specification is correct. This is the only category which is specific to the data format.
For example, this highlights when dates in the worksheet columns are not in ascending order.

  • Time Period Format: Ensures all reported time periods formats conform to the reported Frequency.
For example, FREQ=A will expect time periods in format YYYY. The following table shows the expected date format for each frequency of data.

  • Missing Observations: Ensures that the series reports an observation value for the time period that lies within the time range that the series is reporting data for.
For example, if the first Observation value for a series is reported for 2001 and the last is reported for 2004, then this test that observations were reported for 2001, 2002, 2003, and 2004

  • Valid Representation: Ensures the reported values for Dimensions, Attributes, and Observation values exists within the DSD.
For example, if the Excel file reports using an INDICATOR not contained in this DSD then it will fail this test.


Categories that PREVENT conversion: Users are required to fix issues identified in this category. 
  • Duplicate Observations: Ensures the data file does not contain any duplications which contradict each other.
For example, if there are two observations with different values for the same period.

  • Mandatory Attributes: Ensures all Attributes, as defined in the DSD, are reported if they are marked as Mandatory.
For example, datasets using the EcoFin DSD are required to define the scale [UNIT_MULT] in the Excel file.

  • Time Period Format: Ensures that dataset with multiple frequencies, FREQ should always be the highest reported frequency.
  • Valid Calculations: If any additional rules exist to perform mathematical calculations to ensure compliance, then these tests are run, and any failures are reported against this category.
  • Valid Constraint: A Dimension or Attribute in the dataset may report a value which is valid in the DSD but has been restricted for the reporting entity in the Reporting Constraints. These are additional checks which are performed when a Dataflow and/or Provision Agreement are selected.
For example, FR (France), the data provider, will not be allowed to report data for the UK (United Kingdom). Both FR and UK are valid countries in the Codelist but are limited based on their reporting constraints. 

Feedback and Knowledge Base