Technical Integration
The Payroll Engine is based on the open standard OpenAPI Specification and can be used by any REST-enabled client.
NET clients can use the Payroll Engine at code level with the Client Services. Examples of the use of Client Services are the Payroll Console and the Web Application.
Die Payroll Konsole bieten verschiedene Kommandos für den Datenaustausch.
| Command | Description |
|---|---|
PayrollImport |
Import regulations, company and employee data (case data) with support from zip-archive |
PayrollImportExcel |
Import regulations, company and employee data (case data) in Excel documents |
PayrollExport |
Export regulations, company and employee data (case data) selectively |
Report |
Data reports in XML, Excel and PDF |
DataReport |
Data reports io JSON |
Webhooks enable bidirectional communication between the API client and the backend. When certain events occur, the backend calls an external endpoint. Triggers for webhooks are:
- Specific system events like a case change or a payrun execution
- Individual trigger in automation script
For specific events in the payroll process, such as a new employee case or the final payroll run, webhooks can be registered. Each webhook message is stored in the system. For special cases, it is possible to trigger a webhook from a rule script.
The tutorial Webhook Consumer shows how Payroll Engine messages are forwarded to another service.
Currently the backend supports the SQL Server with approx. 65 tables, 40 stored procedures and 8 functions.
To integrate other databases, the interface
IDbContextof the backend project must be implemented.
🤝 Thank you for supporting this project with a donation.
⚡ This is a pre-relase version of the initial development, please read the restrictions.
