Loading
Because payroll calculations, statutory deductions and cost reporting all depend on the split, not the total. A single figure forces the split to be recreated every month.
The breakdown of what somebody is paid: basic, allowances, variable components and employer contributions, defined per person or per grade.
Components are defined once and computed each run. Revisions are dated, so a change mid-period is applied pro-rata rather than approximated.
Somebody's salary changes on the 14th. The run applies the old structure to the first thirteen days and the new one after, without anybody calculating it.
It does not benchmark or recommend pay. Structures are what you decide, recorded so they compute consistently.
Payroll runs compute from it. Books posts each component to its own account. Loop uses cost rates derived from it for project margin.
Yes, and they usually must — statutory components vary.
Yes, as templates applied to people and overridable individually.
A field-level permission, separate from seeing the person's record.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.