OpenFEMA Dataset: HMA Subapplications Financial Transactions - v1
| Key | Value |
|---|---|
| Entity Name | HmaSubapplicationsFinancialTransactions |
| API Endpoint | https://www.fema.gov/api/open/v1/HmaSubapplicationsFinancialTransactions |
| Update Frequency | R/P1M |
| Program URL | https://www.fema.gov/grants/mitigation |
| Category | Hazard Mitigation |
| Keywords | mitigation |
Description
This dataset contains the financial transactions for Hazard Mitigation Assistance (HMA) subgrants from the FEMA Grants Outcomes (FEMA GO) system (FEMA’s new grants management system). FEMA GO started accepting Flood Mitigation Assistance (FMA) and Building Resilient Infrastructure and Communities (BRIC) subapplications in Fiscal Year 2020. FEMA GO is projected to support the Hazard Mitigation Grant Program (HMGP) in Calendar Year 2023. For details on HMA subgrants not captured in FEMA GO, visit https://www.fema.gov/openfema-data-page/hazard-mitigation-assistance-projects-v3.
This dataset contains information on the HMA subgrants that have recieved financial transactions in FEMA GO. Sensitive information, such as Personally Identifiable Information (PII), has been removed to protect privacy. The information in this dataset has been deemed appropriate for publication to empower public knowledge of mitigation activities and the nature of HMA grant programs. For more information on the HMA grant programs, visit: https://www.fema.gov/grants/mitigation. For more information on FEMA GO, visit: https://www.fema.gov/grants/guidance-tools/fema-go.
This dataset comes from the source system mentioned above and is subject to a small percentage of human error. In some cases, data was not provided by the subapplicant, applicant, and/or entered into FEMA GO. The financial information in this dataset is not derived from FEMA's official financial systems. Due to differences in reporting periods, status of obligations, and how business rules are applied, this financial information may differ slightly from official publication on public websites such as https://www.usaspending.gov. This dataset is not intended to be used for any official federal financial reporting.
FEMA's terms and conditions and citation requirements for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page: https://www.fema.gov/about/openfema/terms-conditions.
For answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq.
If you have media inquiries about this dataset, please email the FEMA News Desk at FEMA-News-Desk@fema.dhs.gov or call (202) 646-3272. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.
Full Data
| Format | Address | Record Count | Approximate File Size |
|---|---|---|---|
| csv | Link to csv | 3115 | tiny (< 10MB) |
| json | Link to json | 3115 | tiny (< 10MB) |
| jsona | Link to jsona | 3115 | tiny (< 10MB) |
| jsonl | Link to jsonl | 3115 | tiny (< 10MB) |
| parquet | Link to parquet | 3115 | tiny (< 10MB) |
Data Fields
| Name | Title | Type | Description | Is Searchable |
|---|---|---|---|---|
| subapplicationIdentifier | Subapplication Identifier |
text
|
Single-value that uniquely identifies the subgrant. The Subapplication Identifier is made up of the [FEMA Organization Code][FEMA Region Letter Code]-[Fiscal Year Opportunity]-[Program Code]-[Application Number]-[Subapplication Number]. This is a system generated field in FEMA GO. | yes |
| transactionType | Transaction Type |
text
|
The type of financial transaction (i.e., Award, Amendment, Deobligation, Payment). | yes |
| transactionDate | Transaction Date |
date
|
Date the financial transaction was processed by FEMA. While this value may contain time information (00:00:00.000), these are system generated and do not reflect the actual time associated with the subapplication/subgrant. | yes |
| commitmentIdentifier | Commitment Identifier |
text
|
Single-value that identifies the commitment identifier associated with the financial transaction. A commitment is the reservation of funds for a specific purpose and the certifying of funds availability. Commitment identifier is made up of the [Location Code][Sequentially Assigned Number][Procurement Method][Fiscal Year][Optional Characters]. | yes |
| accsLine | ACCS Line |
text
|
Single-value that identifies the line of account used for the financial transaction. The Accounting Classification Code Structure (ACCS) is used to identify the expenditures for appropriated funded. The ACCS is made up of the [Budget Fiscal Year]-[Fund Code]-[Program Code]-[Organization Code]-[Project Code]-[Object Code]-[Fund Type]. For more information on the ACCS components, visit https://emilms.fema.gov/is_0337/groups/51.html. | yes |
| fundCode | Fund Code |
text
|
Single-value that identifies the source of appropriation funding for the subgrant. The possible codes include 5 (National Flood Insurance Fund, National Flood Insurance Act of 1968), IN (National Flood Insurance Fund, Infrastructure Investment and Jobs Act), 6M (Disaster Relief Fund, Disaster Recovery Reform Act of 2018), and 6N (Disaster Relief Fund, Infrastructure Investment and Jobs Act) | yes |
| amount | Amount |
decimal
|
Amount in dollars associated with the financial transaction. | yes |
| id | ID |
uuid
|
Unique ID assigned to the record | yes |
See Also
Access the metadata API calls for additional information: