"Payroll is up 4% on budget" is not an answer — it's the start of a week of questions. SwiftBalance matches employees period to period, so the movement decomposes into the people behind it: who joined, who left, who moved cost centres, who got a raise.

One payroll model feeds every view: cost, headcount and FTE by cost centre, rolled up through the functions, with the month against last year and the year to date. Load next month's payroll file and every column moves on.

A standard variance tells you which cost centre moved. The payroll bridge matches each employee across the two periods and puts the whole movement on what happened: new hires, leavers, cost-centre moves and pay changes.
The payroll model you build for the monthly report answers the next questions too.
Drop the payroll register or HR export — one row per employee per period is all the bridge needs.
Confirm the dimensions (cost centre, grade, location) and pick the employee as the matching key.
Open the bridge between any two periods. Every pound of movement lands on a hire, a leaver, a move or a pay change.
A payroll or HR extract with an employee identifier, a period, a cost amount, and the attributes you want to cut by. If an employee appears in both periods it's a stayer; the bridge classifies everything else from the data.
Yes. New hires, leavers, cost-centre moves and pay changes add up to the total movement, every time: anything no rule claims lands in its own line. If the payroll ties to the ledger, so does the bridge.
Access is controlled at dimension-member level — a manager can be limited to their own cost centres, and drill-through respects the same rules. Plus roles, 2FA and an organization audit log.
Yes. Load the payroll by pay date and the model keeps days, so weekly-paid and monthly-paid people add up correctly in the same monthly report.
Start free with a payroll extract, or book a 30-minute demo.