Introduction
10/01/2004 — 04/04/2024Released DailyLast Updated 04/05/2024
The U.S. Government Revenue Collections dataset provides a daily overview of federal revenue collections such as individual and corporate income tax deposits, customs duties, fees for government service, fines, and loan repayments. These collections can be made through either electronic or non-electronic transactions by mail, internet, bank, or over-the-counter channels.
Preview
Data Table:
N/A
Date Range:
Dataset Properties
Data Table Name | Field Name | Display Name | Description | Data Type | Is Required |
---|---|---|---|---|---|
U.S. Government Revenue Collections | record_date | Record Date | The date that data was published. | DATE | 1 |
U.S. Government Revenue Collections | electronic_category_desc | Electronic Category Description | There are four electronic categories, which are mutually exclusive. The four categories are: 1. Fully Electronic - All - The government (Agency and Fiscal Service) processes these transactions electronically (Example: EFTPS transactions). 2. Fully Electronic - FS - Fiscal Service programs process these transactions electronically, but an agency processes some aspect of these transactions non-electronically (Example: OTC net electronic check transactions). 3. Electronic Settlement - Fiscal Service programs settle these transactions electronically, but also process some aspect of these transactions non-electronically (Example: Lockboxes and ECP). 4. Non-Electronic - The government processes these transactions non-electronically (Example: OTC net cash deposits). | STRING | 1 |
U.S. Government Revenue Collections | channel_type_desc | Channel Type Description | Channel Program is the collections program reporting the data to Collections Information Repository (CIR). In most cases, the collection program name is synonymous with the concatenation of the Reporting Program and the Source Processing Program within CIR. However, Fiscal Service has provided derivation rules to enable specific breakdowns. The report lists the Channel Programs alphabetically within each collections channel. The four types are: 1. Over-the-Counter (OTC) - The OTC channel exists for collection information presented by the public or an agency to an agent or depositary in person or via an electronic terminal. 2. Mail - The mail channel exists for collection information presented by the public to an agent or depositary by mail. 3. Internet - The internet channel exists for collection information presented by the public or an agency to an agent or depositary over the Internet. It includes online banking transactions initiated by the public through private third party applications and received by an agent or depositary through a defined interface. 4. Bank - The bank channel exists for collection transactions presented by a member of the public to an agent or depositary through closed banking networks. It includes Automated Clearing House credit and Fedwire collection transactions. | STRING | 1 |
U.S. Government Revenue Collections | tax_category_desc | Tax Category Description | There are five tax categories, which are not mutually exclusive. The Tax Category Total contains the sum of the Non-Tax and Internal Revenue Service (IRS) Tax amounts. The five categories are: 1. Non-Tax - Sum of IRS-Non-Tax and Non-Tax (other than IRS Non-Tax). 2. IRS Non-Tax - Collections for ALCs (Agency Location Codes) that begin with 2009 but do not include any of the IRS Service Centers. 3. IRS Tax - Collections for the IRS Service Center ALCs. 4. Non-Tax (other than IRS Non-Tax) - Collections that do not begin with ALC 2009. 5. IRS Tax & IRS Non-Tax - Sum of IRS Non-Tax and IRS Tax. | STRING | 1 |
U.S. Government Revenue Collections | net_collections_amt | Net Collections Amount | Dollar amount of transaction. | CURRENCY | 1 |
Showing 1 - 5
rows
of
rows
Table Name | Description | Row Description | Row Count |
---|
Name | Definition |
---|
Notes & Known Limitations
The Department of the Treasury has a goal of transitioning all revenue collection activities to an electronic format.
API Quick Guide
Check out our more detailed API Documentation.
API Documentation
Endpoint
BASE URL:
https://api.fiscaldata.treasury.gov/services/api/fiscal_service/
ENDPOINT:
FULL URL:
https://api.fiscaldata.treasury.gov/services/api/fiscal_service/
Fields
Refer to Dataset Properties above for a data dictionary with field names and descriptions, as well as notes and known limitations. known limitations.
Field Name | Display Name | Data Type |
---|
Showing 1 - 5 rows of 15 rows
Data Types
All data is returned as a string, including nulls. Refer to the chart above for the intended data type of each field.
Parameters
Refer to Dataset Properties above for a data dictionary with field names and descriptions as well as notes and known limitations
Fields
toggle contents
- Parameter:
fields=
- Definition: The fields parameter allows you to select which field(s) should be included in the response.
- Accepts: The
fields=
parameter accepts a comma-separated list of field names (no parentheses). - Required: No, specifying fields is not required to make an API request.
- Default: If desired fields are not specified, all fields will be returned.
- Notes: When a field named passed to the
fields=
parameter is not available for the endpoint accessed, an error will occur. Note that omitting fields can result in automatically aggregated and summed data results. For more information, view the full documentation on Aggregation and Sums.
EXAMPLE
?fields=
Filters
toggle contents
Sorting
toggle contents
Format
toggle contents
Pagination
toggle contents
Methods
Our APIs accept the GET method, one of the most common HTTP methods.
Example Request & Response
In this example, we are...
- Specifying the endpoint
- Requesting the JSON response format
- Sorting the data by
in descending order
- Setting pagination parameters
EXAMPLE REQUEST
https://api.fiscaldata.treasury.gov/services/api/fiscal_service/undefined?sort=-undefined&format=json&page[number]=1&page[size]=1
EXPECTED RESPONSE
Loading...
For More API Information
Visit our full API documentation to find out more about:
- Aggregation and sums
- Pivoting
- Response codes
- Meta object
- ...and more!
API Documentation