Remote logoMicrosoft Dynamics 365 logo

HR to ERP

Remote to Dynamics 365 integration: Remote employments as employees in Business Central, per company

With an integration between Remote and Microsoft Dynamics 365 Business Central, every EOR employee and own employee from Remote becomes an employee in the Business Central company that bears the costs, with job title, work email and the department as default dimension. The end date from the offboarding in Remote reaches Business Central, and is updated as long as Remote still changes it.

What the integration does

Organisations that have employees in other countries through Remote and use Dynamics 365 Business Central for finance add those employees to Business Central by hand. The entity that gets the invoice for an employee then differs from the company they are in, and a cancelled offboarding is not reversed.

  1. KoppelHet loads all employments once and then follows Remote's webhooks.
  2. Per employment KoppelHet determines the Business Central company from the billed entity.
  3. The employee is created or updated, with the department as default dimension.
  4. A submitted offboarding fills the end date; a deleted offboarding removes it again.
  5. On the end date KoppelHet sets the employee to terminated.
Remote → KoppelHet → Microsoft Dynamics 365SOURCERemoteTARGETMicrosoft Dynamics 365KoppelHetmapping · logging · monitoringRemote → KoppelHet → Microsoft Dynamics 365SOURCERemoteTARGETMicrosoft Dynamics 365KoppelHetmapping · logging · monitoring
Out: Employee per Business Central company · Job title and work email · Default dimension for the department · Employment date, end date and status

What to watch for with Remote and Microsoft Dynamics 365

  • Remote names per employment the entity that engaged someone and the entity that receives the invoice. In Business Central every company has its own employee list and its own API path. KoppelHet puts the employee in the company of the billed entity, because that is where the costs of that employee are posted.
  • Remote warns that the end date can still change during offboarding, even after it has been finalised. Business Central keeps the end date separate from the status. KoppelHet updates the end date on every change, but only sets the status to terminated once Remote reports that the date has been reached.
  • If an offboarding is deleted in Remote, Remote sends its own event for it. KoppelHet then removes the end date in Business Central again, so an employee who stays after all does not appear as a leaver in reports.
  • Business Central's employee resource has no department field, and dimension values are read-only in the API. Remote gives the department as a name with an ID. KoppelHet translates the name into an existing dimension value and sets it as default dimension; if the value is missing, finance gets an alert.
  • Remote reports a new work email with its own event, separate from other changes. Business Central uses the employee's email address for documents, among other things. On that event KoppelHet only updates the email address, so an address change does not wait for the weekly comparison.
  • Besides employees Remote also has contractors, who are often in Business Central as vendors rather than as employees. KoppelHet only sends EOR employees, own employees and global payroll employees, so a contractor does not become both vendor and employee.

How we build and run it

  • The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
  • Every sync and every error is visible in the functional log; on an error your administrator is notified.
  • A change that cannot go through is not half-applied but queued for another attempt.
  • KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
  • After go-live we manage the integration and adjust it when your process changes.
  • The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.

Implementation, architecture and compliance

Implementation and price

This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.

A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Does this also work with Dynamics 365 Finance?

This page assumes Business Central. For Dynamics 365 Finance we choose the right interface at the start.

Do Remote invoices go to Business Central?

Not in this integration. Invoices or payroll costs per entity can be added later as an extension.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Remote through GET /v1/employments for the initial load and webhooks through POST /v1/webhook-callbacks for employment.updated, employment.details.updated, employment.work_email.updated, offboarding.submitted, offboarding.deleted and contract.termination_date_reached. Fields type (employee, contractor, direct_employee, global_payroll_employee), bill_to_legal_entity_id, engaged_by_legal_entity_id, department and department_id, job_title, work_email, provisional_start_date and termination_date (only with an active offboarding).
  • Business Central through API v2.0 per company - employees (number, givenName, surname, jobTitle, email, employmentDate, terminationDate, status Active, Inactive or Terminated) and defaultDimensions with parentType Employee; dimensionValues GET only.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in RemoteField in Microsoft Dynamics 365Notes
employment idnumberOr finance's employee number, per customer
NaamgivenName, surname
work_emailemail
bill_to_legal_entity_idBedrijf (companies)Lookup table
job_titlejobTitle
departmentdefaultDimensions (Employee)Existing dimension value
provisional_start_dateemploymentDate
termination_dateterminationDate en status Terminated

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.