Payroll as Universal Employment API Core
Jeremy Zhang, CEO of Finch, on building a universal API for employment systems
Owning payroll data is what lets a software company become the control plane for the rest of the employer stack. Payroll is where the legal employee record, pay rates, deductions, and company contributions already live, so benefits, retirement, underwriting, and workforce software all end up reading from it or writing back into it. That makes HR and payroll the best starting point for any universal employment API.
-
The practical workflow starts in payroll. A 401(k) provider like Human Interest needs employee census data, paystub level data, and the ability to add deductions and employer contributions on each payroll run. Without payroll access, the product falls back to CSV files, email, and manual ops teams.
-
Other employment tools are usually downstream systems, not the master record. Benefits, recruiting, and time tracking each hold part of the picture, but payroll is where data is reconciled and money actually moves. That is why Finch built organization, pay, and deductions before expanding into adjacent modules.
-
This also explains the macro tailwind. Employment software is unbundling into specialized apps, while payroll data is becoming easier to access through infrastructure layers. More point solutions means more demand for a shared API that can connect the same payroll system to retirement, insurance, lending, tax, and HR tools.
The next step is broader coverage around the payroll core, then deeper control of the rails themselves. As more employers mix Gusto or ADP with separate benefits, compensation, and finance tools, the winner is the platform that can both read the system of record and write back into deductions, contributions, reimbursements, and other payroll actions.