Loading
Because payroll is a separate system and a single journal. One line hits the ledger, and what a team actually costs becomes a question needing a second export to answer.
Payroll posting takes the result of a pay run in Nest and writes it to the ledger: gross pay, employer costs, deductions, and the liabilities each one creates.
The run posts by employee to the cost centre on their record, splitting where somebody is allocated across teams. Employer taxes and pension contributions post alongside as liabilities.
A developer is split sixty-forty across two projects. Their cost posts in that ratio, so project margin carries the real cost of the people on it rather than an allocation invented at close.
Books does not run payroll. Nest calculates it and holds the contracts, leave and deductions; Books records what it costs and what is now owed.
It creates the payroll liabilities, the bank payment on pay date, and the cost lines by cost centre and project that the P&L and project margin read.
Yes, where confidentiality requires it, with the detail kept in Nest.
Yes, until paid, so the balance sheet shows what is owed.
Yes, pro-rated in Nest and posted with the run it falls in.
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.