Skip to main content
Xledger Integration

All you need to know about the Xledger integration

Daniel Tollefsen avatar
Written by Daniel Tollefsen
Updated over a week ago

Overview

With this integration you will connect Alexis HR to your Xledger account via API and can then do the following:

  • Scheduled or manual sync of employee data such as personal information, employment data, compensation data and more from Alexis HR to Xledger

  • Sync time off data such as sickness, parental leave and vacations to Xledger for the period that you choose. You have full control over what absences are exported for what employees and for what period

Available in: Norway

Xledger requirements

You need to have access to the following valid credentials.

  • Access token: this can be found in here: https://xledger.net/f/api-tokens

    • Click on Generate new token

    • Provide a Token description, for example, "Alexis HR" or "Simployer"

    • Select «Read» and «Write» for Accounts payable, Accounts receivable, Common and General Ledger

    • Click Generate token

    • Once the token has been generated, you can use it when setting up the Xledger integration in Alexis HR

Adding the integration

The integration is activated from SettingsIntegrationsAdd Integration (in the "Integrate with payroll system" section).

  • In the API Integrations section, select Xledger

  • Click Next to start the configuration wizard

  • Enter all the details needed for the connection

Settings

You can choose how the integration sync for employees is executed. The options available are as follows:

  • Manual sync

    • The data is manually synced to Xledger by the user

    • This can be valuable if you have the scheduled sync turned off and want to control when data is synced to Xledger. Either during the implementation phase or during times when an update is not wanted due to process and payroll timing

    • Manual syncs can be performed even when a scheduled sync is configured. This may be necessary if there have been a significant number of changes in Alexis HR after a scheduled sync has been executed

  • Scheduled sync

    • The sync runs on a schedule that you can define

    • Options include the day(s) of the week and the time of day for the sync to be executed

Note: when a scheduled sync is enabled, it is queued and executed shortly after 06:00 CET the following day.

Scope

  • Scopes allow more granular filters that determine which employees are included in the employee sync

  • This is especially useful if you require a specific set of employees to be excluded from the export to 24Seven Office

  • Scopes follow the same scope behavior as seen in other Alexis HR featuresHR.


Employee data

Employee data is synchronized from Alexis HR to Xledger. This means that if data is updated in Xledger on "data fields" and then the sync from Alexis HR is done the data in Xledger will be overwritten.

When the sync is executed it will compare the data in Alexis for the "data fields" to see if there is a difference between the values for those fields in Xledger. If there is no change, the user will not be updated. If there is a change present, the data will be updated.

Some fields are currently hardcoded or have a default value, see the table below for more information.

Data fields

Alexis field

Xledger field

Mapping conditions

Work

Employee.employeeNumber

Employee.code

Required

Employee.workEmail

Contact.email

Financial

Employee.bankAccount.number

Supplier.account

Personal

Person.firstName

Employee.firstName
Contact.firstName

Person.lastName

Employee.lastName
Contact.lastName

Person.firstName
Person.lastName

Contact.name
Employee.description

Fields from Alexis are concatenated and then separated by a space

Person.NationalIdList[0].NationalId

Contact.socialSec

If the SSN is removed in Alexis, it will be removed in Xledger as well

Person.Birthdate

Contact.birthday

Employee.nationality

Contact.country

Person.PhoneNumber

Contact.phone

Person.email

Contact.email

Person.Address.street1

Contact.streetAddress

Person.Address.city

Contact.place

Person.Address.postalCode

Employee.zipcode

Employment

Employee.hireDate

Employment.dateFrom

Employment.type

Employment.rate

Absence data

Absence data is synchronized from Alexis HR to Xledger. This means that if data is updated in Xledger on "data fields" and then the sync from Alexis HR is done the data in Xledger will be overwritten.

When the sync is executed, it will compare the data in Alexis for the "data fields" to see if there is a difference between the values for those fields in Xledger. If there is no change, the user will not be updated. If there is a change present, the data will be updated.

Some fields are currently hardcoded, see below for more information.

Alexis field

Xledger field

Mapping conditions

Data

leavePercent

Defaulted to 100

AbsenceStartDate

timeFrom

AbsenceEndDate

timeTo

AbsenceEndDate

toDate

AbsenceStartDate

fromDate

Comment

Defaulted to "temporary comment"

Codes

childcare

“CS”

vacation

“V”

sick_leave

“SWN”

{custom leavecode}

{custom leavecode}

A custom leave code must be set to the exact value defined in Xledger

Did this answer your question?