Version 2.0.0 with 2024 data

README.md

@@ -22,11 +22,11 @@ The Russian Financial Statements Database (RFSD) is an open, harmonized collecti
 
 - 🏛️ Sourced from two official data providers: the [Rosstat](https://rosstat.gov.ru/opendata/7708234640-7708234640bdboo2018) and the [Federal Tax Service](https://bo.nalog.ru).
 
-- 📅 Covers 2011-2023, will be continuously updated.
+- 📅 Covers 2011-2024, will be continuously updated.
 
 - 🏗️ Restores as much data as possible through non-invasive data imputation, statement articulation, and harmonization.
 
-The RFSD is hosted on 🤗 [Hugging Face](https://huggingface.co/datasets/irlspbru/RFSD) and [Zenodo](https://doi.org/10.5281/zenodo.14622208) and is stored in a structured, column-oriented, compressed binary format Apache Parquet with yearly partitioning scheme, enabling end-users to query only variables of interest at scale.
+The RFSD is hosted on 🤗 [Hugging Face](https://huggingface.co/datasets/irlspbru/RFSD) and [Zenodo](https://doi.org/10.5281/zenodo.14622208) and is stored in a structured, column-oriented, compressed binary format Apache Parquet with yearly partitioning scheme, enabling end users to query only variables of interest at scale.
 
 The accompanying paper provides internal and external validation of the data: [https://doi.org/10.1038/s41597-025-05150-1](https://doi.org/10.1038/s41597-025-05150-1).
 
@@ -34,7 +34,7 @@ Here we present the instructions for importing the data in R or Python environme
 
 [![Zenodo](http://img.shields.io/badge/DOI-10.5281%20%2F%20zenodo.14622208-blue.svg)](https://doi.org/10.5281/zenodo.14622208) [![Paper-publication](https://img.shields.io/badge/Scientific-Data-darkred)](https://www.nature.com/articles/s41597-025-05150-1) [![arXiv](https://img.shields.io/badge/arXiv-2501.05841-b31b1b.svg)](https://arxiv.org/abs/2501.05841) [![License: CC BY-NC-SA 4.0](https://img.shields.io/badge/License-CC_BY—NC—SA_4.0-lightgrey.svg)](https://creativecommons.org/licenses/by-nc-sa/4.0/) ![R](https://img.shields.io/badge/R-4.0+-blue) ![Python](https://img.shields.io/badge/Python-3.10+-blue.svg) 
 
-## Importing The Data
+## Importing the Data
 
 You have two options to ingest the data: download the `.parquet` files manually from Hugging Face or Zenodo or rely on 🤗 [Hugging Face Datasets](https://huggingface.co/docs/datasets/en/index) library.
 
@@ -47,11 +47,11 @@ It is as easy as:
 from datasets import load_dataset
 import polars as pl
 
-# This line will download 6.6GB+ of all RFSD data and store it in a 🤗 cache folder
+# This line will download 6.6 GB+ of all RFSD data and store it in a 🤗 cache folder
 RFSD = load_dataset('irlspbru/RFSD')
 
-# Alternatively, this will download ~540MB with all financial statements for 2023
-# to a Polars DataFrame (requires about 8GB of RAM)
+# Alternatively, this will download ~540 MB with all financial statements for 2023
+# to a Polars DataFrame (requires about 8 GB of RAM)
 RFSD_2023 = pl.read_parquet('hf://datasets/irlspbru/RFSD/RFSD/year=2023/*.parquet')
 ```
 
@@ -63,7 +63,7 @@ renaming_df = pl.read_csv('https://raw.githubusercontent.com/irlcode/RFSD/main/a
 RFSD = RFSD.rename({item[0]: item[1] for item in zip(renaming_df['original'], renaming_df['descriptive'])})
 ```
 
-Please note that the data is not shuffled within year, meaning that streaming first __n__ rows will not yield a random sample. 
+Please note that the data is not shuffled within year, meaning that streaming the first __n__ rows will not yield a random sample. 
 
 ### R
 
@@ -116,7 +116,7 @@ To the best of our knowledge, the RFSD is the only open data set with up-to-date
 
 #### What is the data period?
 
-We provide financials for Russian firms in 2011-2023. We will add the data for 2024 by July, 2025 (see Version and Update Policy below).
+We provide financials for Russian firms in 2011-2024. We will add the data for 2025 by July, 2026 (see Version and Update Policy below).
 
 #### Why are there no data for firm X in year Y?
 
@@ -130,11 +130,11 @@ Although the RFSD strives to be an all-encompassing database of financial statem
 
 #### Why is the geolocation of firm X incorrect?
 
-We use Nominatim to geocode structured addresses of incorporation of legal entities from the EGRUL. There may be errors in the original addresses that prevent us from geocoding firms to a particular house. Gazprom, for instance, is geocoded up to a house level in 2014 and 2021-2023, but only at street level for 2015-2020 due to improper handling of the house number by Nominatim. In that case we have fallen back to street-level geocoding. Additionally, streets in different districts of one city may share identical names. We have ignored those problems in our geocoding and [invite](https://github.com/irlcode/rfsd/issues/1) your submissions. Finally, address of incorporation may not correspond with plant locations. For instance, Rosneft [has](https://websbor.rosstat.gov.ru/online/info) 62 field offices in addition to the central office in Moscow. We ignore the location of such offices in our geocoding, but subsidiaries set up as separate legal entities are still geocoded. 
+We use Nominatim to geocode structured addresses of incorporation of legal entities from the EGRUL. There may be errors in the original addresses that prevent us from geocoding firms to a particular house. Gazprom, for instance, is geocoded up to a house level in 2014 and 2021-2024, but only at street level for 2015-2020 due to improper handling of the house number by Nominatim. In that case we have fallen back to street-level geocoding. Additionally, streets in different districts of one city may share identical names. We have ignored those problems in our geocoding and [invite](https://github.com/irlcode/rfsd/issues/1) your submissions. Finally, address of incorporation may not correspond with plant locations. For instance, Rosneft [has](https://websbor.rosstat.gov.ru/online/info) 62 field offices in addition to the central office in Moscow. We ignore the location of such offices in our geocoding, but subsidiaries set up as separate legal entities are still geocoded. 
 
 #### Why is the data for firm X different from https://bo.nalog.ru/?
 
-Many firms submit correcting statements after the initial filing. While we have downloaded the data way past the April, 2024 deadline for 2023 filings, firms may have kept submitting the correcting statements. We will capture them in the future releases.
+Many firms submit correcting statements after the initial filing. While we have downloaded the data way past the April 1, 2025 deadline for 2024 filings, firms may have kept submitting the correcting statements. We will capture them in the future releases.
 
 #### Why is the data for firm X unrealistic?
 
@@ -150,14 +150,34 @@ The data is provided in Apache Parquet format. This is a structured, column-orie
 
 ## Version and Update Policy
 
-Version (SemVer): `1.0.1`.
+Version (SemVer): `2.0.0`.
 
-We intend to update the RFSD annualy as the data becomes available, in other words when most of the firms have their statements filed with the Federal Tax Service. The official deadline for filing of previous year statements is April, 1. However, every year a portion of firms either fails to meet the deadline or submits corrections afterwards. Filing continues up to the very end of the year but after the end of April this stream quickly thins out. Nevertheless, there is obviously a trade-off between minimization of data completeness and version availability. We find it a reasonable compromise to query new data in early June, since on average by the end of May 96.7% statements are already filed, including 86.4% of all the correcting filings. We plan to make a new version of RFSD available by July, 2025.
+We intend to update the RFSD annualy as the data becomes available, in other words when most of the firms have their statements filed with the Federal Tax Service. The official deadline for filing of previous year statements is April, 1. However, every year a portion of firms either fails to meet the deadline or submits corrections afterwards. Filing continues up to the very end of the year but after the end of April this stream quickly thins out. Nevertheless, there is obviously a trade-off between minimization of data completeness and version availability. We find it a reasonable compromise to query new data in early June, since on average by the end of May 96.7% statements are already filed, including 86.4% of all the correcting filings. We plan to update RFSD annualy in late July — early August.
 
 ## Changelog
 
 All notable changes to this project will be documented below. The format is based on [Keep a Changelog](http://keepachangelog.com/).
 
+## [2.0.0] - 2025-08-19
+
+### Added
+- Financial statements for 2024 have been added, totaling approximately 2.25 million observations.
+- More than 315,000 new statements (as well as 55,000 new non-statements by eligible firms) for 2011–2023 have also been included:
+    - More than 24,000 statements for 2023 were imputed using the 2024 filings.
+    - Approximately 3,400 statements were either added to GIR BO retrospectively or missing in v1.0.1 due to the absence of the corresponding organizations in the EGRUL. When we updated the EGRUL, we were able to reconstruct those filings.
+    - The remaining 286,000+ statements are the ones that we had previously imputed from firms' future statements but erroneously dropped due to a bug (see Fixed).
+
+### Fixed
+- Resolved a bug in the final filtering of the panel. We removed all non-eligible non-filers, as intended, but inadvertently excluded observations of non-eligible non-filers whose statements we were able to reconstruct from the following-year filings. Fixing this filter returned about 286,000 statements to the panel.
+
+### Changed
+- The `region_taxcode` now reflects a firm's region of incorporation. Earlier it was simply derived from the first two digits of the firm tax identifier (`inn`) and did not account for reincorporations. The format has been extended from 2 to 4 digits, allowing for differentiation between Arkhangelskaya oblast (`"2900"`) and Nenetskiy AO (`"2983"`), which the former includes.
+- We have revised the statements of all firms previously marked as `outlier` and set the flag to 0 where anomalous revenue has been corrected in the GIR BO database retrospectively.
+- The outlier detection procedure has been updated. Before, we manually reviewed top-20 firms in terms of revenue or total assets within each 2-digit industry (excluding financial firms). Now, we conduct the outlierness review of 2024 filings at OKVED section level, manually examining the top-30 firms by revenue within each OKVED section.
+- The `filed` flag for observed but all-zero statements (all fields, even Equity, are 0) statements is now set to 0 as it is clearly erroneous.
+- The `exemption_criteria` for eligible organizations is now set to `"none"` (previously `NA`).
+- Enhanced geocoding quality (see [this issue](http://github.com/irlcode/RFSD/issues/1)): improvements in address pre-processing procedure have enabled us to upgrade geocoding quality from the city level to the street level for firms accounting for ~8% of revenue from 2022 onwards:
+
 ## [1.0.1] - 2025-05-13
 
 ### Fixed
@@ -166,7 +186,7 @@ All notable changes to this project will be documented below. The format is base
 
 - Fixed a bug in adjustment of line 1300 (total capital and reserves) and 2500 (result of the period).
 
-The updated lines 2400 are quite different from the original values. The value of line 2400 changed in 6-11% of observations in 2011-2018 and in about 25% observations in 2019-2023, the summed difference in the original and new values ranges from 5% to 110% depending on year. Fix for signs inconsistency implies revising scripts for all calculations where negative-only, those ()-ed in statement forms, variables were used.
+The updated lines 2400 are quite different from the original values. The value of line 2400 changed in 6–11% of observations in 2011–2018 and in about 25% observations in 2019–2023, the summed difference in the original and new values ranges from 5% to 110% depending on year. Fix for signs inconsistency implies revising scripts for all calculations where negative-only, those ()-ed in statement forms, variables were used.
 
 ## Licence
 <a rel="license" href="https://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br />