Reference: Salary Accounting Process Definition

The salary accounting process is created per customer as its own XPDL process definition – the module deliberately ships no production definition. The behavior of the accounting form is controlled almost entirely through extended attributes of the process definition. This page is the reference for consultants creating or adapting such processes.

Basic structure

Typical participants: the requester, the provider's consultant and manager, optionally the client's HR admin, plus System for automatic steps. Typical flow: data entry → generate difference list → consultant processing → manager approval (→ optionally HR admin review) → write-back/exports → payslip distribution, with correction loops.

The link to the form is established by the process attribute CustomController=ps_editSalaryAccounting. On first save of an accounting, the form sets the following process variables: SalaryAccounting_UID, from_date, to_date, client_name, clientUID, group_shortname, groupUID.

Extended attributes at process level

`CustomController`	Binds the process to the form `ps_editSalaryAccounting` (mandatory).
`OnDeleteProcessInstanceListener`	Set to `PsDeleteSalaryAccountingProcessListener`: deleting the process instance then also deletes the accounting (the reverse always applies).
`ChangeListActionURL`	Target URL of the "open change list" button in the form.
`ListDetailTemplate`	Velocity template for the detail column in workflow lists.
`HelpMessage`	Help text displayed in the form.

Extended attributes at activity level

Tab enablement

Per activity, six attributes with the values editable or readonly control which tabs of the form can be edited in the respective process step:

`StateSalaryPositionsTab`	Salary positions (fixed/variable)
`StateAbsenceEntryTab`	Absences
`StateRawFilesTab`	Raw files
`StateEmployeeFilesTab`	Employee files (incl. PDF split)
`StateCorporateFilesTab`	Corporate files
`StateGeneratedFilesTab`	Generated files

Additional functions and approvals

`WageTypeCsvExport` / `AbsenceEntryCsvExport`	Shows the CSV export buttons for components or absences in this activity (holders of the update-admin role always see them).
`UploadSalaryPositions`	Allows uploading positions (CSV) in this activity.
`DisplayLinkToChangeList`	Shows the link to the change list.
`ActionApprove`	Defines the activity's approval flag, e.g. `approved_LLConsultant`, `approved_LLManager`, `approved_HRAdmin` – the variable is set on approval and drives the transitions.
`ActionEdit` / `ActionView`	Edit and view action of the activity in the workflow lists.
`AutoApprove`	The activity is approved automatically (for pass-through steps).
`ConnectorLinkPart1` / `ConnectorLinkPart2`	Overrides, for the difference-list step, the master-data connector links of the payroll system (see interfaces).
`ConnectorLinkPart1SourceConstraint` / `...Part2SourceConstraint`	Additional source constraint (filter) for the two master-data exports.

System steps (workflow applications)

The following supplied applications can be included as tool activities (details on the salary accounting page):

PsGenerateDifferenceListApplication – generate and attach the master-data difference list
PsCopySalaryComponentChangesToHrPersonSalary – write salary changes back to HR-Expert (parameters: accounting UID, optionally "create salaries with amount 0")
PsProcessTimeAccountBasedSalaryPositions – execute the TA-account corrections/transfers from variable wage types
PsCopySalaryDocumentsToRepository – distribute payslips into the personnel file (parameters: accounting UID, section ID)
PsStartConnectorLinkChangeListAndAttachToSalaryAccounting / ...AndAttachToProcess – run any connector route and attach the result

Working method and tips

Use the reference definitions in the module (SalaryAccounting.xpdl) as the starting point for new customer processes; they show the typical structure including correction loops.
Every activity where people work should set the six tab attributes explicitly – unset tabs otherwise do not behave deterministically across process versions.
Never omit OnDeleteProcessInstanceListener, otherwise orphaned accountings remain when process instances are deleted.
Process definitions are imported and versioned via process administration; running instances stay on their version.

Kommentare (0)