Posted Employee Payments Realtime-enabled

Read-only posted employee payments, a webhook source for reimbursement status: subscribe to be pushed the moment a reimbursement posts to the employee ledger. The applications child reports which employee balances the payment settled and each one's resulting balance.

The reimbursement round trip

An expense posts what the company owes an employee, which raises that employee's ledger balance. An employeePayments document pays the balance back down. This feed is the third step, and it tells SmartConnect that the money actually reached the employee.

Two measures fall straight out of it. Compare postingDate here with the posting date of the expense it settled to get days-to-reimburse. Sum remainingAmount over the open rows for an employee to get the balance still owed to them.

The settlement-truth feed

Reimbursement status lives here. When a reimbursement posts, in full or in part, SmartConnect is pushed one notification on postedEmployeePayments. Use $expand=applications (or GET postedEmployeePayments({id})/postedDocApplications) to see, per settled balance, the appliedAmount, the balance's resulting appliedRemainingAmount, and appliedOpen. A $30 reimbursement against a $100 expense balance reports "still $70 owed", and the next $70 reports "paid in full".

Late application, where a reimbursement posts unapplied and is applied later through Apply Entries, re-fires this payment rather than the expense side.

Subscribing

Register a subscription against the entity set; Business Central notifies your endpoint when a row changes. The notification carries the record id. GET it to read the current values.

POST /subscriptions
{
  "resource": "/postedEmployeePayments",
  "notificationUrl": "https://your-endpoint",
  "clientState": "<secret>"
}

Status

status is the human-readable settlement state (Open, Partially Settled, or Settled) computed from the ledger entry, so you write status back without interpreting raw open/remaining-amount semantics. remainingAmount and settledAmount carry the figures behind it.

Retention

The projection is a short-lived event feed, not a store. The background job purges a row once its posting date falls outside the retention window, 7 days by default. The options are 7, 14 and 28 on the setup page, or via the integrationSetup API. The backfill only seeds documents within that window, and a purge sends subscribers a delete notification. Consume and reconcile within the window.