Total budgeted expenses for fiscal year ended June 30, XX Total actual expenses for fiscal year ended June 30, XX Additional Dataset Considerations Dataset Technical The dataset is an Excel export from Metro’s financial accounting and Description reporting system (E1). Dataset Assumptions The data is accurate. The data is static; once it is loaded on the data portal, it will not change. However, the file will be replaced annually adding in each additional fiscal year. The data agrees to Metro’s audited financial statements. Why was the Dataset The dataset supports management within Metro in tracking and managing expenses related to their departments, and it supports Created? external reporting needs. How was the Dataset The dataset was created by exporting fiscal year end totals from Created? Metro’s financial accounting and reporting system (E1). What similar or related data None. While it’s possible that other departments could publish some should the user be aware of? level of financial activity, it is expected that it would be at a more detail level, from other sources, and not have a direct cross reference with this dataset. How reliable is the Data? The dataset is highly reliable. It agrees to Metro’s audited financial statements. How well have the data The dataset will be agreed to Metro’s financial accounting and points been checked? reporting system (E1) and Metro’s audited financial statements prior to being published. Are there Legal Restrictions None. The data is public record. It is already available to on the Access or Use of the departments, and it is provided to external parties as requested. Data?
Total budgeted expenses for fiscal year ended June 30, XX Total actual expenses for fiscal year ended June 30, XX Additional Dataset Considerations Dataset Technical Description The dataset is an Excel export from Metro’s financial accounting and reporting system (E1). Dataset Assumptions The data is accurate. The data is static; once it is loaded on the data portal, it will not change. However, the file will be replaced annually adding in each additional fiscal year. The data agrees to Metro’s audited financial statements. Why was the Dataset Created? The dataset supports management within Metro in tracking and managing expenses related to their departments, and it supports external reporting needs. How was the Dataset Created? The dataset was created by exporting fiscal year end totals from Metro’s financial accounting and reporting system (E1). What similar or related data should the user be aware of? None. While it’s possible that other departments could publish some level of financial activity, it is expected that it would be at a more detail level, from other sources, and not have a direct cross reference with this dataset. How reliable is the Data? The dataset is highly reliable. It agrees to Metro’s audited financial statements. How well have the data points been checked? The dataset will be agreed to Metro’s financial accounting and reporting system (E1) and Metro’s audited financial statements prior to being published. Are there Legal Restrictions on the Access or Use of the Data? None. The data is public record. It is already available to departments, and it is provided to external parties as requested.
Metro-Budget-To-Actual-Expenses-Metadata.docx