Employees Realtime-enabled

Create or update the employees an expense report is filed for and a reimbursement is paid to, with their name, address, contact details and employee posting group.

Resolve an employee by number, id or integrationId. Sending integrationId lets SmartConnect keep the key your expense or payroll system already uses. An expense report then arrives carrying that key, not a Business Central number your source system never sees.

Set employeePostingGroup before you send expenses for someone. It decides which payables account an employee-balanced expense posts to, and an expense without it stops in error rather than reaching the ledger.

Personal HR data is not exposed

The published columns cover identity, address, contact and posting group. Social security number, birth date, gender, union code and union membership number are deliberately left off the contract, and no other personal HR field is exposed. An integration that never carries that data cannot leak it.

email is the employee's company email address. The private email address on the employee card is not published.

Resolving an employee on a document

Two endpoints resolve an employee by the key you set here:

• Expenses: send employeeIntegrationId to set the report's balancing account to that employee, instead of sending balancingAccountType and balancingAccountNumber.
• Employee Payments: send employeeIntegrationId in place of employeeNumber to name the person the reimbursement pays.

Employees are also a valid parentType on Document Attachments and Notes, so receipts and paperwork can hang off the person rather than only off the staged document.

Seeding ids for employees that already exist

Employees usually exist in Business Central before the integration does. The Integration Id migration tool copies an existing field into integrationId in bulk, so you do not have to PATCH each employee by hand. See Integration Id migration.