Skip to main content

Dynamics 365 Business Central (BC)

Integrate BitaBIZ time registration in Business Central via Power Automate. Step-by-step guide.

Written by Mathias Anneberg

BitaBIZ → Dynamics 365 Business Central (BC)

This article shows how you can integrate BitaBIZ time registrations directly with Microsoft Dynamics 365 Business Central.
The goal is to automate the transfer of employee hours, projects, and absences, so that registrations in BitaBIZ can be used directly in Business Central for accounting and reporting.

This guide is written for developers and administrators who want a practical step-by-step setup with API, Power Automate flow, and field mapping – complete with examples and images.

How to do it (step by step)

1) Enable and test the BitaBIZ API

  • Enable the API key in BitaBIZ (Setup admin → Company → Subscription plan).

  • Use the key as x-apikey in requests.

Example (BitaBIZ REST GET):

GET https://registrations.api.bitabiz.com/v2/registrations?from=2025-10-01&to=2025-10-01&reason=HH
Headers: x-apikey: <BITABIZ_API_KEY>

2) Prepare Business Central API access

  • Use BC Standard API v2.0.

  • Base URL:

    https://api.businesscentral.dynamics.com/v2.0/<environment>/api/v2.0/

  • Endpoint: timeRegistrationEntries. Supports GET/POST.

Example (BC POST):

POST https://api.businesscentral.dynamics.com/v2.0/<env>/api/v2.0/companies(<companyId>)/timeRegistrationEntries
Authorization: Bearer <AAD_OAUTH_TOKEN>
Content-Type: application/json

{
  "employeeId": "<BC-employee GUID>",
  "date": "2025-10-01",
  "quantity": 7.5,
  "unitOfMeasureId": "<GUID for HOUR>",
  "jobId": "<job GUID>",
  "jobTaskNumber": "100"
}

Power Automate HTTP POST to BC

3) Build a Power Automate flow

  1. Trigger: Recurrence (e.g. daily).

  2. Step 1 (HTTP): GET from BitaBIZ API.

  3. Step 2 (Parse JSON): Map fields (date, hours, employeeId, jobNo).

  4. Step 3 (For each): POST to Business Central timeRegistrationEntries.

Power Automate flow with steps in sequence

4) Key details you need to handle

  • Match employees: Map BitaBIZ employee ID to BC’s employeeId.

  • Units & dimensions: Make sure HOUR is defined in BC.

  • API limits: Use batching and retries.

Mini mapping sketch

BitaBIZ field

BC field (timeRegistrationEntries)

registrationDate

date

hours (decimal)

quantity

employeeGuid

employeeId

project/job identifiers

jobId / jobTaskNumber

reason (e.g. IS = Sick)

absence

👉 The BitaBIZ API guide provides an overview of all dimensions and reason codes.

👉Read this article for an overview of the 2 API calls /employees & /registrations.

Alternatives

  • Create journalLines (e.g. Resource/General Journal) via API if that fits your accounting flow better.

Did this answer your question?