Exports

nx_employeemanagement registers one public client export and three public server exports. The server exports let your other scripts post a row to a company's ledger, check a rank permission, and run a business's payroll. Hiring, firing, invoicing and day-to-day payroll go through the tablet UI.

Server

Company transactions

A wholesale app, a shop, a fuel station or any other script can add a row to a company's transaction list. The row shows in the tablet's Society Funds ledger and in nx_computer's Employees app under Company funds.

-- Wholesale app: the company pays for an order from its own account.
-- The money moves and the row is written together.
local ok, res = exports.nx_employeemanagement:AddCompanyTransaction('mechanic', {
    amount    = 1250,
    label     = ('Wholesale order #%s'):format(orderId),
    type      = 'purchase',
    reference = ('wholesale-%s'):format(orderId), -- safe to retry
    actor     = source,                           -- the employee who placed it
}, true)

if not ok then
    -- res is the error code, e.g. 'insufficient_funds'
    return TriggerClientEvent('ox_lib:notify', source, {
        type = 'error', description = 'The company cannot afford this order.'
    })
end
print(('order logged as row %d, company balance now %s'):format(res.id, res.balance))

If your script already moved the money itself, leave move out and only the row is written:

exports.nx_employeemanagement:AddCompanyTransaction('burgershot', {
    amount = 86.50,
    label  = 'Delivery fee: Vespucci supply run',
    type   = 'fee',
})

What each mode does

The row is written first and the money moves second. If the move fails, the row is deleted again, so a failed debit never leaves a ledger line.

With nx_realbanking as the backend, the label is passed as the bank transaction's reason and { source = 'employees', resource, category, reference } as its metadata. nx_realbanking keeps a transaction row only for accounts it owns itself. A society account stored in esx_addonaccount or qb-management shows the same balance in the bank, and this ledger is where the rows live.

Rows posted this way do not count toward Config.Payroll.Limits.WithdrawPerDayNonOwner. That cap is for bosses taking cash out, and a supplier order is not a cash withdrawal.

Error codes

Every posted row also fires the server event nx_employeemanagement:server:societyChanged with { job, id, direction, amount, category, resource, moved }. Rows are also written to the audit log and to the Discord webhook when one is configured.

Rank permissions

-- Only let grades with the society grant pay supplier invoices
local job = player.job
if not exports.nx_employeemanagement:HasRankPermission(job.name, job.grade, 'society') then
    return false, 'not_authorized'
end

Payroll runs

-- Admin command: pay out the mechanics now.
-- restricted = true, so only players with the command.paymechanics ACE can run it.
RegisterCommand('paymechanics', function()
    local ok, res = exports.nx_employeemanagement:RunPayroll('mechanic')
    if not ok then
        return print('payroll not run: ' .. res) -- e.g. 'no_employees'
    end
    print(('paid %d, queued %d, total %s (%s)'):format(res.paid, res.queued, res.total, res.status))
end, true)

On success summary holds:

Employees who could not be paid keep their owed hours, so the next run or payday pays them.

Client

-- Open the tablet from any client script
exports.nx_employeemanagement:useJobTablet()

The same entry point is used by:

• The jobtablet inventory item (via client.export in ox_inventory, or via CreateUseableItem on QBCore).
• The /employeelist command and its Config.UIKey keybind.
• The server-side nx_employeemanagement:openTablet event that the inventory bridge fires when the item is used on QB-style inventories.

LB Tablet mode

While Config.LBTablet.Enabled is true, the app inside LB Tablet is the only way to open the UI, and this export returns without doing anything. LB Tablet exposes no export for opening a specific app from Lua, so there is no equivalent call to forward to. Existing callers get a no-op rather than an error, so nothing breaks when you switch modes.