Custom Endpoints

Prepare DATEV Payroll

Changed on

What DATEV requires to prepare payroll is very specific and currently, as DATEV is not providing "read", this is not part of the unified model.

<Note> This endpoint requires the permission **Manage payroll** to be enabled in [your scope config](/scopes). </Note>

Example Request Body

{
  "employee_id": "EvLV61zdahkN4ftPJbmPCkdv",
  "payroll_run": {
    "date": "2022-05-01"
  },
  "fixed_payments": [
    {
      "amount": 560,
      "lohnart": 100
    }
  ],
  "hourly_payments": [
    {
      "hours": 14,
      "lohnart": 200
    },
    {
      "hours": 16,
      "lohnart": 232
    }
  ],
  "custom_lodas": [
    {
      "amount": 8,
      "lohnart": 300,
      "bearbeitungsschluessel": 4
    }
  ]
}
put/custom/datev/employees/{employee_id}/prepare-payroll

Request

Path parameters

employee_idstring required

ID of the employee that should be updated. You can use their Kombo id or their ID in the remote system by prefixing it with remote: (e.g., remote:12312)

Headers

X-Integration-Idstring required

ID of the integration you want to interact with.

Request body

Response

PUT /custom/datev/employees/:employee_id/prepare-payroll Positive response

status'success' required
dataobject required

Changes

    • breaking

      added the new required request property

    • breaking

      added the new required request property

    • breaking

      added the new required request property

    • breaking

      the request's body type changed from no type to object

    • warning

      removed subschema #1 from the request body allOf list

    • info

      added the new optional request property

    • info

      removed the non-success response with the status

    • info

      removed the non-success response with the status

    • info

      removed the non-success response with the status

    • info

      removed the non-success response with the status

    • info

      removed the non-success response with the status

    • info

      the response property const value success was added for the status

    • info

      removed the success enum value from the response property for the response status

    • info

      added the required property to the response with the status