Skip to main content
POST
Create Employee Payroll Run
This endpoint creates an Employee Payroll Run in the connected HRIS via Bindbee’s unified Employee Payroll Runs model.

Provider-specific behavior

Different HRIS systems can have slightly different requirements and behaviors when creating payroll runs. Use the accordions below to see details for each provider.

When the underlying HRIS is Workday, an earning can be created using a payload like:

Similarly, a deduction can be created using a payload like:

Important note

  • For Workday, you can add either earnings or deductions at a time - you cannot add both simultaneously.
  • You can only add 1 earning or deduction at a time, no more than that.
  • payroll_run field must be set to null for Workday integration.
The possible types for earnings are:
  • Workday_Earning_Code
  • WID
The possible types for deductions are:
  • Workday_Deduction_Code
  • WID

When the underlying HRIS is ADP , an employee_payroll_run can be created using a payload like:

When the underlying HRIS is UKG Ready , an employee_payroll_run can be created using a payload like:

When the underlying HRIS is SAP SuccessFactors, an employee_payroll_run can be created using a payload like:

Where to find these fields:

  • payroll_provider_id: Use the ID provided by the customer if it’s available. If not, any valid string can be used.
  • payroll_person_id: This value can be found in the employee’s raw_data.
  • payroll_employment_id: Source this either from the employee’s raw_data or from Binbee’s employment model (remote_id).
  • Deductions: When adding deductions, ensure the deduction codes are included in the name field.

Important notes

  • All top-level fields are mandatory.
  • earnings, deductions, and taxes can be sent together.
  • All fields inside each array are compulsory.

Authorizations

Authorization
string
header
default:<BINDBEE_API_KEY>
required

Your Bindbee API key, sent as Authorization: Bearer <BINDBEE_API_KEY>. Required on every request.

X-Connector-Token
string
header
default:<CONNECTOR_TOKEN>
required

The connector token for one customer's connection. This is not your Bindbee API key. Required on requests that read or write a single customer's data.

Headers

x-idempotency-key
string | null

Key to guarantee idempotent write execution.

Body

application/json

The body is of type Body · object | null.

Response

Successful Response