Payroll & finance
The same boundary, a different ledger.
Identical scope to the Xero connection: payroll inputs assembled here, calculation and filing staying where they belong.
What connects
A connection carrying the period's employment changes out, and summary employment cost back in.
What crosses the boundary
- Sent: starters, leavers, rate and salary changes, unpaid leave, approved expenses.
- Received: employment cost by period.
- Received: pay run dates for cut-off alignment.
- Never sent: absence reasons, performance records or manager notes.
What this lets you do
- Generate the change list for each pay run automatically.
- Keep an audit trail from a paid figure back to the approval behind it.
- Feed real cost into planning rather than a budgeted assumption.
- Spot people employed but not on the pay run, and the reverse.
Setting it up
- 1Authorise the connection and select the company file.
- 2Map employees between the two systems.
- 3Choose the level of cost detail you want back.
- 4Validate one period before switching off the manual process.
Permissions
Payroll and employment cost scopes only. No access is requested to invoicing, banking, customers or the wider ledger.
What you can ask once this is connected
- “Show me this period's payroll changes.”
- “Who started or left since the last run?”
- “What is our employment cost trend this year?”
Where it stops
Not a payroll engine and not an accounting integration in the general sense. It moves employment inputs and reads back cost; everything else stays in your finance system.
Payroll & finance
Others in this category.
Run your team with clarity.
From the moment someone joins to the day their responsibilities are handed over, Orglume keeps your people, their work and your organization connected.
Set up from a spreadsheet · Nothing about the AI is metered · [email protected]