While this promise sounds good, pure no-code/low-code solutions often reach their limits when it comes to designing complex solutions. Things get exciting when a programming interface is also available.
With the Payroll Engine, regulations (for a country, an industry, a pension fund, company-specific additions, etc.) can be developed completely autonomously using JSON configuration and a scripting programming interface.
The test-driven approach ensures a documented demarcation between stakeholders and provides assurance that the solution meets customer requirements. The test data also serves as a basis for future enhancements.
In the Payroll Engine development process, the various implementation approaches are distributed among the respective qualified developers.
| User | Task | Technical skills | Outcome | |
|---|---|---|---|---|
| No-code | Regulation Owner | Capture requirements and test regulations | JSON | Case-Test, Payrun-Test, Report-Test |
| Low-code | Regulation Builder | Design and develop regulations | JSON, C# Beginner | Regulation |
| Code | Regulation Developer | Develop features | JSON, C# Intermediate | Case-Action, Regulation, Report |
Since Regulation Builder requires minimal C# knowledge (method calls), a tech-savvy Regulation Owner can develop the application themselves. The use of Regulation Developer becomes necessary when the functionality is not available in the payroll engine's regulation ecosystem.
The combination of no-code/low-code and custom programming enables Payroll Providers to meet even the most complex customer requirements. All at an unprecedented development speed.
The excitement this customization creates with customers quickly motivates payroll professionals to learn JSON configuration and basic coding skills. Payroll knowledge and experience remains a mandatory requirement for the Regulation Builder.
Learn more about payroll automation.
Top comments (0)