Vergleichsreport

Data exchange between Webdesk and the payroll provider's accounting system (BMD NTCS, DATEV, ...) runs through five typical export interfaces, configured as connector links on the payroll system (ps_editSystem). This page describes the interfaces, their data fields and the configuration rules.

Overview: the five interfaces

All five are implemented as linked connectors: a PS source connector delivers the data, a target connector (usually separator file/CSV) writes the export file in the accounting system's format. Field mapping and target format are therefore maintained entirely in connector administration – making the PS interfaces adaptable per customer and target system without changing the module.

Person master data (1 + 2)

The master-data exports supply the accounting system with the person data (name, address, entry date, social security number, bank details, labor contract, pay group, cost center, ...). The basis is a dedicated staging table filled from HR-Expert via a connector; comparison with the last state yields the difference list (changed persons only).

• The workflow step prefers the links configured on the payroll system; if none are configured, the default names PSExportMAStammdaten-Part1 and PSExportMAStammdaten-Part2 apply.
• Both can be overridden per process activity (extended attributes ConnectorLinkPart1, ConnectorLinkPart2, ConnectorLinkPart1SourceConstraint, ConnectorLinkPart2SourceConstraint, see the process definition reference).
• If the client's PS configuration is missing (company number, payroll system), the step aborts with "Client not correctly configured for Payroll-Services ...".
• For BMD, internal codes (country, marital status, labor contract, pay group, ethnicity) are translated into BMD codes via shipped mapping tables; changes to these mappings require a restart.

Components and absences (3 + 4 + 5)

The three transaction-data exports deliver the positions of the current accounting. The PS source connectors provide, per position, fields including:

• clientPayrollId – the client's company number (key in the accounting system)
• employeeId – the employee number
• periodStartDate / periodEndDate – the accounting period
• value or noOfHours, for absences fromDate / toDate
• wageTypeName, wageTypeCode, wageTypeSalaryCode, wageTypeAbsenceCode, wageTypeExportCode (already resolved per the precedence rule: system export code before general export code)
• variableUsageType – amount / hourly rate / quantity

Specifics:

• The components connector is configurable: export zero values (yes/no) and export types (fixed only, variable only, or all components). For fixed components with a valid-from before the period start, additional monthly rows are generated.
• The absence connector has no configuration of its own; it exports the recorded absence intervals of the period.
• If the connector is client-bound, the client restriction is added automatically.
• Number format and encoding of the CSV files are controlled by the PS options csvFileLocale (default de) and csvFileEncoding (default iso-8859-1).

Configuration rules and storage

• Link resolution order: first the client's payroll system, then the fallback names in the PS options (fixedWageTypesExportConnectorLink, variableWageTypesExportConnectorLink, absenceEntriesExportConnectorLink). If neither resolves, the error "No connectorLink could be found ..." appears.
• Storage of export files: CSV exports are stored in the accounting's export history; the master-data file from part 2 in the raw files tab. Downloads are subject to the accounting's document authorization.
• Visibility of the export buttons: configurable per workflow activity; holders of the update-admin role always see them.

BMD code mappings in detail

For BMD exports, the module translates internal Webdesk codes into BMD codes via five shipped mapping tables (CSV, semicolon-separated). The tables are loaded into memory at startup – changes require a restart.

For the hierarchical mappings (pay group), the parent columns reference the labor contract – a pay group therefore always applies in the context of its collective agreement. Missing mappings show up in the export as empty or untranslated codes; in that case, extend the respective table.

Import direction

The way back from the accounting system into Webdesk is currently twofold:

• Documents: the accounting results (collective payslip PDFs, evaluations) are uploaded in the accounting's file tabs and brought into the digital personnel file via split and distribution.
• Data: person and wage-type imports from BMD run through dedicated connector routes (BMD person import interface); a generic bulk document import into the personnel file is being developed as an extension.

Related pages: Salary Accounting Process, Wage Types, Process Definition Reference, Digital Personnel File.