Payroll Allocation
Split each paycheck across the properties worked.
The Excel workbook that splits each employee’s payroll cost across the properties they worked is gone. Import ADP hours, allocate on a grid with a live balance indicator, layer in overtime, PTO, and one-time amounts, then finalize to lock an immutable, versioned archive that feeds reporting, a consolidated invoice broken out by GL account, and manager notifications.
AI partner: Sally
Helps allocate and explain payroll
How it works
Four steps from hours to a booked, invoiced period.
Import ADP hours
Upload the pay-period export from ADP. Hours are matched to employees by their records, so the period starts populated instead of blank.
No re-keying a payroll register into a workbook — the period opens with everyone's hours already in place.
Allocate on the grid
Split each employee's cost across the properties they worked on an employee × property grid. A live balance indicator flags any row that doesn't add up, and OT, PTO, and one-time amounts layer on top.
The markup matrix — pay role × entity type, effective-dated — applies the right rate automatically, even for historical periods.
Finalize & archive
When the period balances, finalize it. That locks an immutable, versioned archive of the allocation — the numbers behind a booked period never shift underneath you.
Reopen only creates a new version; the original stays intact for audit, and managers are notified their team's period closed.
Report & invoice
Finalized periods feed per-property and per-group reporting, analytics against budget, and a consolidated payroll invoice broken out by GL account — ready for accounting.
One invoice, split the way the ledger needs it, with the reporting behind every line.
See it in action
What you’ll see inside the tool.
The allocation grid
Split each employee across the properties they worked — the balance indicator turns green only when every row adds up.
Allocate · Jun 1–15, 2026
Bi-weekly · 22 employees
R. Alvarez
Maintenance
T. Nguyen
Leasing
K. Brooks
Maintenance
M. Diaz
PM
Ask Sally
The payroll co-pilot explains why a period won’t balance — scoped to the data your role can already see.
Sally
Payroll Allocation co-pilot
Consolidated invoice
One payroll invoice, broken out by GL account across the finalized period.
Why you’ll use it
The allocation workbook is fragile, and nobody trusts last quarter’s copy.
Payroll cost gets split across properties in a spreadsheet with hand-entered percentages, markup rates buried in formulas, and no record of what a booked period actually looked like. Payroll Allocation makes the split a grid, the markup a matrix, and the finalized period an archive you can defend.
The period has to balance before it books
The live balance indicator catches an employee split to 90% or 110% before you finalize — no more discovering an off-by-a-property error after the invoice went out. A payroll admin can override a documented exception for the rare period that can't tie.
Markup rates are effective-dated
The markup matrix — pay role × entity type — is effective-dated, so re-running a prior period applies the rate that was in force then, not today's.
A transparent salary and wage history for every employee
Each employee carries a complete, effective-dated record of their pay. Rates are never overwritten — every raise or change is a new dated entry — so the salary and wage history is fully transparent and traceable.
Finalizing locks an immutable archive
A booked period is versioned and frozen. Reopening creates a new version instead of overwriting, so the numbers behind a closed period never move.
One invoice, split the way the ledger needs it
The consolidated payroll invoice breaks out by GL account, with per-property and per-group reporting and budget analytics behind every figure.
Comp data is protected at the database
Compensation is guarded by deny-all RLS and SECURITY DEFINER RPCs — the route and the policy both gate who can see a rate, not just the UI.
Sally
Payroll Allocation co-pilot
Your payroll co-pilot
Ask Sally why the numbers look the way they do.
Sally lives in the bottom-right corner of every payroll screen. Ask her in plain English — “why won’t this period balance?”, “how are we tracking vs budget this year?”, “what’s driving overtime?” — and she reads the period on screen to answer.
Who uses it
Built for the people who run — and read — payroll.
Accountants
The people who run the pay-period cycle end to end — from the ADP import through the booked, invoiced period.
- Import ADP hours and match them to employees
- Allocate each employee across the properties worked
- Layer overtime, PTO, and one-time amounts
- Finalize to lock the immutable, versioned archive
- Run reporting and the consolidated GL invoice
Operating Leads, Principals & Property Leads
The people who need to see payroll cost for their scope without touching the allocation — everything they read is scoped to what they’re allowed to see.
- Operating Leads: read-only Team, Report, and Employees for their group(s)
- Get notified the moment their team's period is finalized
- Principals: read-only Analytics and Report across all groups
- Property Leads: read-only Analytics and Report for assigned properties
- Ask Sally, scoped to exactly what their role can see
Check a period from anywhere.
Reviewing an allocation, pulling up a finalized report, or asking Sally how the quarter is tracking against budget all work on any phone browser — so a manager can see their team’s payroll without waiting to get back to a desk.
More in the toolbox