Sorry, not yet translated. I’m working on it. Summary The Technical White Book, Livre Blanc Technique in french, is a payroll configuration analysis tool designed for HR Access, by Sopra HR. It automates time-consuming phases of collecting configuration elements, as well as certain analysis phases: Upstream analysis Downstream analysis Understanding a pay calculation result Pay rules systems comparison It is the tool I build to help me, in my professional life as a HR Access consultant.

In 2019, a former colleague, Xavier, reached out to me. He remembered that on the Ifremer project, I had personal tools. One tool extracted payroll categories, and another was capable of reconstructing the hierarchy of a category. Having since joined a client teams, he needed a similar tool to get ready to migrate towards HR4You: together, we built what would become the LBT, the Technical White Book. For Xavier, the LBT allowed him to approach the project preparation phase, to identify what he wanted to see discontinued, harmonized, or continued.

The downstream analysis simply consists of searching for the code of one item in the calculation formula of other items. Nothing more, nothing less. Just like the upstream analysis, the process is iterative: Displaying impacts on payslip, accounting, or DSN When launching the analysis, it is possible to activate options, independent from each other, to mark: items with a position on the payslip items with an accounting allocation items with DSN reporting Here, 3 new columns have been created:

The “upstream analysis” function lists the items used in the calculation formula of an item and searches for their definition. This iterative approach allows you to “visualize” a payroll rule. The data used comes from the export of LBT-SQL. Each payroll item is presented here following the HR Access coding: And a bit more The tool allows processing a batch of items: simply list them, separating them with spaces: This produces a tab for each processed payroll item:

In a nutshell HR Access regulations are exported as the LBT is not a connected tool. They are exported into Excel spreadsheets. The exported data represents the current regulations and is the result of processing performed on the server, including: Reconstructing the mathematical formulas applied by the items Searching for triggers Pros & Cons It takes only a few minutes to process the regulations in their entirety. Currently, the programs are written in Oracle PL/SQL, but with a tool like ChatGPT, it is possible to translate the PL/SQL code into any other database language.

Pay System exports are contained in Excel spreadsheets. In an export, a rule has been adopted: one row, one payroll item. After loading the regulatory files, it is possible to compare the items from 2 different regulatory exports, which may have been generated in different environments and/or at different points in time. This feature can assist you in managing the received deliveries, communicating changes/corrections to the business… Here, with 5000 items and comparing 10 columns, the comparison took 1'10’’ (the PC was up to the task).

The purpose of this feature is to achieve the following result: Indeed, the HR Access payroll inspector displays the valued items. While it explains the final result, it does not show the possible alternatives, the ones that are expected… The attentive reader will object that the screenshot does not show any non-valued elements: they are right; due to the lack of access to an HR Access environment at the time of writing this article, it will have to wait…