To enable integration between the Third-party Human Resources/Payroll software and Dynamics 365. The integration allows for employee and worker data as well as payroll transactions to be shared between these software solutions. The Axnosis ISV solution utilises the following two modules:


Assumed setups to be completed and data to be configured:

Worker data may be imported to D365 via an Excel spreadsheet as exported from the 3rd party software. The data includes custom worker fields which is part of the Axnosis HRM ISV module.
The import file allows for workers to be create or detail of existing workers to be updated including:
|
Import column |
Description |
|
PersonnelNumber |
Employee number |
|
LastName |
Employee surname |
|
FirstName |
Employee first name |
|
PersonalTitle |
Employee title |
|
IdentificationNumber |
Identification number of employee |
|
IsDisabled |
Yes or No answer indicating if the employee is disabled or not |
|
EthnicOrigin |
Ethnic origin of employee |
|
Gender |
Employee gender |
|
EmploymentFromDate |
Employment start date |
|
EmploymentToDate |
Employment end date if any |
|
WorkerStatus |
Status of worker e.g. Employed or Terminated |
|
PrimaryContactEmail |
Email address of employee if any |
|
AddressState |
Province/State of worker office address |
|
AddressCity |
City of worker office address |
|
OfficeLocation |
Location of employee office address |
The import file should preferrably only contain a single sheet else the user will have to select the appropriate sheet during the import process.








Verify that the workers have been successfully imported (or whether the data has been updated/adjusted accordingly) by accessing the relevant HR workers in D365 and confirming the data as per the import file.
This process allows for payroll data to be imported via an Excel spreadsheet exported from the 3rd party software. Once successfully imported in D365, data may be validated and a payroll journal may then be generated and posted.
The import file may include the following data:
|
Import column |
Description |
|
AccountCode |
Account identifier |
|
AccountGroup |
Optional account group if required |
|
BatchID |
Optional batch identification |
|
CostCentre |
Cost centre dimension value |
|
DebitCredit |
Either Debit or Credit |
|
ElementDescription |
Description of the payroll journal line item |
|
ElementType |
Identifies the type of line item:
|
|
MonthProcessed |
Month value i.e. 1 |
|
PayGroup |
Optional payment group if required |
|
PeriodEndDate |
Payment period end date |
|
Amount |
Amount value |
|
Reference |
Optional additional reference number if required |
A line item for the same account and same period may only be repeated for different element descriptions OR if the same element description, then it may only be repeated where one item is a debit and the other a credit.
The import file should preferrably only contain a single sheet else the user will have to select the appropriate sheet during the import process.







This step will create any additional categories (if applicable) in D365 ensuring synchronization between the two software systems.
This step will validate the imported (raw) data from for accuracy to match data residing in D365.




If the validation of staging data or journal creation fails due to incorrect data, the staging data needs to be deleted before importing updated data by following the previous steps.

This functionality can only be executed before the system created payroll journal has been posted.



