Introduction and purpose
Please note: LessorLøn is a Danish payroll system and operates only in Danish.
This article dives into the details of what the integration contains, how to set it up and what to look out for. It is a supplement to our setup guide.
Integration content
In the table below is an overview of the content of the LessorLøn integration.
| Title | Function in LessorLøn |
| Connection to LessorLøn | Authentication of integrationen |
|
New employee newemployee.xml |
Inserts data in "medarbejdere til godkendelse" in LessorLøn Note Emply supports by default:
If you do not use the above, please check with a web service specialist. |
|
Opdater medarbejder updateemployee.xml has same content as new employee |
Inserts data in "medarbejderændringer til godkendelse" in LessorLøn |
|
Termination of employee termination.xml |
Terminates employee |
|
Registration of absence Absence.xml |
Inserts information of absence for employee |
|
Departments department.xml |
Creates and changes the name of departments
|
|
LessorLøn codes inquiry.xml |
Query codes from LessorLøn and make them available for mapping with Emply |
*New departments are only created when a staff member is recruited and transferred within the department
Connect Emply with LessorLøn
For the integration to be set up, the following criteria must be met:
- The customer has ordered the integration from Emply and it is stated in the contract
- Emply has ordered access to the customer's LessorLøn solution
- LessorLøn web service and Inquiry have the same credentials.
This order is sent to and delivered by Emply integration team through help center or support.
Then Emply integration team tests and connects customer's Emply and LessorLøn solutions*.
* Cloud
For customers with cloud solution, Emply integration team knows the information to be filled in under Title(Titel), Client(Klient), Username(Brugernavn) as well as Password(Kodeord).
Title - Use client name or same as client name in LessorLøn
* Onprem
If the customer has OnPrem, the customer hosts and operates LessorLøn.
The customer must then provide
- URL to LessorLøn installation
- Emply servers are whitelisted our public IP addresses
- Provide and test username and password for web service and inquiry.
- Book and coordinate consulting help from Emply integration team.
Title - Use client name or same as client name in LessorLøn
URL - This is known by the client
Username (Brugernavn)
Password (Kodeord)
Mapping
After the integration has connected to the customer's LessorLøn, you can see the bindings that are fixed and those that need to be selected with e.g. a form field or absence type.
File extraction from LessorLøn
The customer must provide the files to Emply in a secure way, they can find it in their LessorLøn after Lessor support has formed them.
When loading the three files (Payroll.csv, hourly_salary_rates.csv and Masterdata.csv) into Excel it is important to pay attention to the following;
If data is simply imported into excel, then leading 0's will be removed from the employee code and cpr no. fields.
You must therefore do the following with the Master Data file:
- Open excel - Select files and New
- Select Data and then From Text/CSV
- Select file and Import
- Click on 'Transform data'('Transformer data')
- Select all data with ctrl-a - right click and select 'Edit type'('Rediger type') - select 'Text'('Tekst') - select 'replace current'('erstat aktuelle') - click 'close'('luk') and load.
- Select files and save the file.
You therefore need to do the following with the Payroll file:
- Open excel - Select files and New
- Select Data and then From Text/CSV
- Select file and Import
- Click on 'Transform data'('Transformer data')
- All columns should have changed type to 'Text', except 'Monthly Salary' and 'Working Hours (Weekly)' - right click and select 'Edit Type'('Rediger type') - select 'Text'('Tekst') - select 'replace current'('erstat aktuelle') - click 'close'('luk') and load.
- Select files and save the file.
You therefore need to do the following with the Hourly_salary_rates file:
- Open excel - Select files and New
- Select Data and then From Text/CSV
- Select file and Import
- Click on 'Transform data'('Transformer data')
- All columns should have changed type to 'Text', except 'Number of hours' and 'Hourly salary rate' - right click and select 'Edit type'('Rediger type') - select 'Text'('Tekst') - select 'replace current'('Erstat aktuelle') - click 'close'('luk') and load.
- Select files and save the file.
Fields of integration
The table below gives an overview of the fields that are part of the integration. It contains the name from LessorLøn and Emply, the binding and where in Emply the data comes from.
(F) = The binding cannot be changed
(V) = The binding has multiple choices (dynamic fields / fixed fields)
| Lessor term | Type | Emply data | Emply source / binding |
Masterdata-contact information |
Type |
Emply data |
Emply binding |
| Employee Code | Mandatory(F) | Emplyee number | Standard/form |
| From date | Mandatory(F) | Date of employment | Salary widget |
| Cpr.nr. | Mandatory(F) | CPR number | Standard |
| Initials | Optional(V) | Initials | Form |
| Address | Mandatory(F) | Address | Standard |
| Address 2 | Optional | can be set up | Form |
| Postal Code | Optional(F) | Postal Code | Standard |
| Country Code | Optional(F) | County Code | Standard |
| Phone number privat | Optional(F) | Phone number privat | Standard |
| Private mobile number | Optional(F) | Private mobile number | Standard |
| Work phone | Optional(F) | Work phone | Standard |
| Private email | Optional(F) | Private email | Standard |
| Work email | Optional(F) | Work email | Standard |
| Bank account number | Optional(V) | Can be selected if NemKonto is not set up | Form |
| Bank registration number | Optional(V) | Can be selected if NemKonto is not set up | Form |
Employment |
Type |
Emply data |
Emply binding |
|
Company Code (Code description) Retrieved automatically via Inquiry |
Mandatory(F) | Company Code | Form |
|
Organisation Code (Code description) Retrieved automatically via Inquiry |
Mandatory(V) | Organisation Code | Form |
| Date of employment | Mandatory(F) | Date of employment | Salary widget |
| Resignation date | Optional(F) | Resignation date | Salary widget |
| Resignation reason code | Optional(F) | Resignation reason | Salary widget (Set up on salary group) |
|
Settling Group Code (Code description) Retrieved automatically via Inquiry |
Mandatory(V) | Select from options | Form |
| Quota Numerator | Mandatory(F) | Working hours each week | Salary widget |
| Quota notice | Mandatory(V) | Working hours each week / FTE | Working hours on salary group |
| Salary | Mandatory(F) | Monthly / hourly | Salary widget |
| Alt. Pay Seniority-/ Experience Date |
Optional(V) | Can be selected | Salary widget |
| Anniversary Seniority Date | Optional(V) | Can be selected | Salary widget |
| Date of Pension Seniority | Optional(V) | Can be selected | Salary widget |
Agreement |
Type |
Emply data |
Emply binding |
| Seniority date | Mandatory(F) | Seniority date | Salary widget |
| Job description | Agreement job title | Salary widget | |
|
Job Profile Code (Code description) Retrieved automatically via Inquiry |
Optional(V) | Can be selected | Form |
|
Posting Group Code (Code description) Retrieved automatically via Inquiry |
Optional(V) | Can be selected | Form |
|
Dimension Codes (Code description) Retrieved automatically via Inquiry |
Optional(F) | Can be selected | Form |
Department |
Type |
Emply data |
Emply binding |
| Department Code | Mandatory(V) | Customized department code | Department |
| Department Description | Mandatory(F) | Department name | Department |
| Department start date | Mandatory(F) | Department created | Department |
| Production number | Mandatory(F) | P-number | Department-Location |
Absence |
Type |
Emply data |
Emply binding |
| Absence start date | Mandatory(F) | Absence start date | Absence registration |
| Absence end date | Mandatory(F) | Absence end date | Absence registration |
| Employee Code | Mandatory(F) | Employee Code | |
| Absence Codes | Optional(V) | Absence Types | Fraværs-registrering |
Form fields
All form fields to be used in the integration must be shared elements. It is set on the individual field of the form. Here select Advanced - see below.
Salary number / employee number (code)
A salary number is usually linked to the employee's employment and will follow the employee throughout the period of employment. The exception is when the employee changes from hourly to monthly or monthly to hourly.
(link to remuneration section or copy it here)
A salary number series:
Customer's Emply solution can be set up to map to Emply employee number and can make use of automatic employee number assignment when new employees are created.
Existing employees in LessorLøn keep their employee number and are imported into Emply.
Multiple number ranges:
If the customer needs multiple number series, it will not be possible to assign automatic payroll numbers from Emply. Employee payroll numbers will then need to come from a form field.
Initials
Emply can create initials in LessorLøn
Bank reg. and account number(rarely used)
Most often the customer uses Nemkonto to pay wages and these fields are created very rarely.
Address 2 (Address2)
If the customer needs more address lines, this can be set up and mapped with the integration
Form field with options
The following fields must be created as optional fields
Company code (companycode)
Separates the employees of companies in LessorLøn.
If the customer has several company codes, they are entered as options - see example above.
If the customer has only 1 company code - only one option is entered and this can also be set up to be pre-filled.
Organisation code (organisationcode)
Determines rights in LessorLøn.
If the customer has more than one organisationcode, they are entered as options.
If the customer has only 1 organisationcode - only one option is entered and this can also be set up to be pre-filled.
Settlement group code (settlinggroupcode)
Controls the payment of wages
Specifies the payroll types used by the customer e.g. 'Month in arrears'.
Pay group code (paygroupcode)
The paygroup code determines the type of employment e.g. civil servants or hourly workers etc. The job profile codes are automatically retrieved in the integration.
In the extract there will be a code, the customer should know the designation as these are the ones to be used for the form field.
Posting group code (postinggroupcode)
Most often used to allocate employee costs in LessorLøn.
Dimension code 1-8 (dimensioncode1-8)
Setting up fields in the integration
This part is further described in the setup guide
LessorLøn setup guide
Activity log
The activity log is found under integrations in the menu and can show if one or more transactions have gone through or failed.
Below is an example of a list of activity logs.
- The red ones indicate that there was an error.
- The green ones that it was a success and will be visible in LessorLøn on the employee or under employees for approval.
You can click on 'Read more' to get a further description of what it is about: