Master Data Linked to Registrations
Master data in BitaBIZ forms the foundation that ensures employees’ registrations (work hours, absence, mileage, etc.) are automatically linked to the correct organizational and financial dimensions.
Through master data, registrations are linked to, for example: cost center, account number, cost price, activity, department, P-number, staff group, country, and company.
Master data comes from 2 sources (2 API calls):
The employee’s master data card (department/P-number, country, company, cost price, etc.)
Employee API:
RESTcurl -H "x-apikey: $API_KEY" \
https://api.bitabiz.com/v2/employees/CSV
https://api.bitabiz.com/pbi/INSERT_API_KEY_HERE/employees
The registration type itself (cost center/activity, project/account number, pay rate, etc.)
Registration API:
RESTcurl -H "x-apikey: $API_KEY" \
"https://api.bitabiz.com/v2/registrationsCSV
https://api.bitabiz.com/pbi/INSERT_API_KEY_HERE/registrations
Master Data Dimensions (Employee API)
Master Data Dimension | How is it set? | What is it used for? |
Department | Selected on the employee’s master data card. | Shows organizational affiliation. |
P-number (ID) | Field on the department. | Can be used for cost center or production unit number (P-number in DK). |
Policy (staff group) | The most central dimension in BitaBIZ. Selected when the employee is assigned to a policy. | Determines earning, time registration method, and absence rules. It is also a group in the company (agreement, country, company). |
Country | Added as a tag on the employee’s master data card. | Used for allocation and reporting in global organizations. |
Company | Added as a tag on the employee’s master data card. | Used for allocation and reporting to legal entities. |
Salary/cost price/hourly rate | Added on the employee’s master data card. | Used to calculate cost/invoice price. |
Payroll number | Added on the employee’s master data card. | Used as a unique ID for payroll systems. |
Employee number. | Added on the employee’s master data card. | Used as a unique ID for external systems. |
Added on the employee’s master data card. | Used as a unique ID for external systems. | |
GUID | API dimension | Used to link BitaBIZ API calls |
Registration Dimensions (Registration API)
Dimension | Time registration (work hours) | Absence |
Project / account number | ✔︎ – Created on project | ✘ |
Cost center / activity | ✔︎ – created on job code | ✘ |
Payroll system | ✔︎ – rates created on job code | ✔︎ – absence codes created on policy and/or payroll system form |
Reason | TT | HH, HF, IC, L, etc. |
Guid | API dimension | Used to link BitaBIZ API calls |
Master data from the 2 API calls (/employees & /registrations) are linked via GUID.
External systems integrate with the BitaBIZ API via employee number, e-mail, or payroll number:
