Citywide Payroll Data (Fiscal Year)

k397-673eCity Government17 columns

Data is collected because of public interest in how the City’s budget is being spent on salary and overtime pay for all municipal employees. Data is input into the City's Personnel Management System (“PMS”) by the respective user Agencies. Each record represents the following statistics for every city employee: Agency, Last Name, First Name, Middle Initial, Agency Start Date, Work Location Borough, Job Title Description, Leave Status as of the close of the FY (June 30th), Base Salary, Pay Basis, Regular Hours Paid, Regular Gross Paid, Overtime Hours worked, Total Overtime Paid, and Total Other Compensation (i.e. lump sum and/or retro payments). This data can be used to analyze how the City's financial resources are allocated and how much of the City's budget is being devoted to overtime. The reader of this data should be aware that increments of salary increases received over the course of any one fiscal year will not be reflected. All that is captured, is the employee's final base and gross salary at the end of the fiscal year. In very limited cases, a check replacement and subsequent refund may reflect both the original check as well as the re-issued check in employee pay totals. NOTE 1: To further improve the visibility into the number of employee OT hours worked, beginning with the FY 2023 report, an updated methodology will be used which will eliminate redundant reporting of OT hours in some specific instances. In the previous calculation, hours associated with both overtime pay as well as an accompanying overtime “companion code” pay were included in the employee total even though they represented pay for the same period of time. With the updated methodology, the dollars shown on the Open Data site will continue to be inclusive of both types of overtime, but the OT hours will now reflect a singular block of time, which will result in a more representative total of employee OT hours worked. The updated methodology will primarily impact the OT hours associated with City employees in uniformed civil service titles. The updated methodology will be applied to the Open Data posting for Fiscal Year 2023 and cannot be applied to prior postings and, as a result, the reader of this data should not compare OT hours prior to the 2023 report against OT hours published starting Fiscal Year 2023. The reader of this data may continue to compare OT dollars across all published Fiscal Years on Open Data. NOTE 2: As a part of FISA-OPA’s routine process for reviewing and releasing Citywide Payroll Data, data for some agencies (specifically NYC Police Department (NYPD) and the District Attorneys’ Offices (Manhattan, Kings, Queens, Richmond, Bronx, and Special Narcotics)) have been redacted since they are exempt from disclosure pursuant to the Freedom of Information Law, POL § 87(2)(f), on the ground that disclosure of the information could endanger the life and safety of the public servants listed thereon. They are further exempt from disclosure pursuant to POL § 87(2)(e)(iii), on the ground that any release of the information would identify confidential sources or disclose confidential information relating to a criminal investigation, and POL § 87(2)(e)(iv), on the ground that disclosure would reveal non-routine criminal investigative techniques or procedures. Some of these redactions will appear as XXX in the name columns.

View on NYC Open Data

Quality

A90.7 / 100

From a 500-row sample across 17 columns.

completeness98/ 25% weight

consistency74/ 20% weight

accuracy94/ 20% weight

timeliness84/ 15% weight

usability100/ 20% weight

· Has geographic keys — joinable to other NYC datasets

Related datasets

Sample rows

fiscal_year	payroll_number	agency_name	last_name	first_name	mid_init	agency_start_date	work_location_borough	title_description	leave_status_as_of_june_30	base_salary	pay_basis
2025	67	ADMIN FOR CHILDREN'S SVCS	PASCALL	DERRICK	F	2011-02-22T00:00:00.000	MANHATTAN	CHILD PROTECTIVE SPECIALIST SUPERVISOR	ACTIVE	106346.00	per Annum

Columns

17 queryable · 17 profiled

The machine field names SoQL needs, with the publisher's own description of each.

Field	Type	Description	Null	Values
`fiscal_year`	categorical	Fiscal Year	0%	`202220192020`of 12
`payroll_number`	integer	Payroll Number	26%	`74274756`
`agency_name`	text	The Payroll agency that the employee works for	0%	`DEPT OF ED PEDAGOGICALDEPT OF ED PER SESSION T…POLICE DEPARTMENT`
`last_name`	text	Last name of employee	0%	`RODRIGUEZWILLIAMSSMITH`

Query this from your own app

GET /api/datasets/k397-673e
GET /api/datasets/k397-673e/quality
GET /api/datasets/k397-673e/related
GET /api/columns?dataset=k397-673e