PROJECT STORY

IdenfitConnector: data transfer between HR and ERP

An application we developed to configure personnel, leave and expense transfers through a management panel. Fields and record types are mapped in the panel, alongside transfer plans and record-level results.

Contact us

How does the workflow take shape?

Illustrations adapted from the application workflow, using sample data.

Sample personnel transfer plan showing ERP as the source, HR as the destination and the selected direction.
Source, destination and record type are defined in the same transfer plan.
Field mapping example showing source fields, a transformation rule and their destination fields.
Each field has a destination mapping and, where needed, a transformation rule.
Sample record follow-up showing preview, transfer results and records to review.
After preview, transfer results can be followed for each record.
On this page7 sections

Connections and transfer plans in one panel

We developed the web management panel together with the background transfer service. Companies, source and destination connections, and transfer plans are defined in the panel. Each module has its own transfer direction and run interval.

WORKFLOW

Setting up a transfer plan

Connections and mappings are prepared in the panel before a transfer is started.

  1. Connections
  2. Module and direction
  3. Mappings
  4. Preview
  5. Run and monitor

Matching fields and organisation records

Source and destination fields are selected in the panel, with required fields protected. Mappings can include transformations such as trimming spaces, keeping only the digits in a phone number or supplying a default for an empty field. Initial employee matching can use keys such as a staff number or email address. Organisation records, including branches, departments and job titles, can be matched by code or name.

Choosing a direction for personnel and leave

The source application can be selected for personnel and leave transfers. The active plan for a company and module runs in one direction. Leave types have their own mappings; revisions and cancellations are tracked through records linked between the two systems.

Recording expenses in ERP

Expense transfers run from the HR application to ERP. Status filters and category, account and VAT mappings are defined in the plan. Depending on the selected flow, the application can create a debit note or a purchase invoice.

Preview before writing, record history afterwards

A plan can preview its actions before writing to the destination system. Plans can run at set intervals or be started manually. The operation history shows results and issues for each record. Leave and expense records also have retry tracking.

Installation and updates

The application was prepared for installation as a Windows service, with the management panel accessed through a browser. The update flow covers stopping the service, backing up local data, replacing application files and checking service health.

Questions and answers

How could this approach be adapted to Logo?

The same panel and mapping approach could be adapted to Logo fields and services. A Logo connection would be a separate development scope, requiring its own personnel, leave and expense mappings, cancellation handling and retry rules to be implemented and verified.

HR and personnel systems integration

We can review which systems need to exchange your personnel, leave or expense records and which mappings are required.

Explore integration services

Discuss the records shared by HR and ERP

Tell us which records need to move and in which direction. We can review the source fields and mappings around that flow.

info@vibebilisim.com +90 (850) 242 84 23

ERP product and version, HR application, and personnel, leave or expense records. At least 10 characters.

We use your details to respond to your request. Privacy notice