Loading
A run draws from contracted terms and approved time. Every line traces back to the timesheet and the approval behind it. Adjustments, loans, advances and reimbursements sit on the person's record rather than in a spreadsheet appended to the run.
Payslips are generated from the run, and compensation revisions are dated so a mid-month change is applied correctly rather than approximated.
Because the inputs arrive from three places: contracted salary from HR, variable hours from a timesheet, and adjustments from an email thread. Somebody assembles them into a file, and that file is the only place they have ever existed together.
When a figure is questioned three months later, the file is the audit trail. Often it is the only one.
Nothing is retyped, so the class of error that comes from retyping disappears. More importantly, the same approved hours become project cost in Loop, so the cost of a week's work and the payroll for that week cannot disagree.
A questioned figure resolves in one click to the timesheet, the approval and the person who gave it.
It does not file with tax authorities on your behalf, and it does not replace a payroll bureau where you use one. It produces the run and the audit trail; submission depends on your jurisdiction and is not something this page claims.
Statutory deduction rules are configured rather than shipped. What is current in one country this year will not be next.
Import contracts, terms and opening balances, then run a full cycle in parallel with your existing process before switching. Compare line by line, not totals — totals agree while individual lines are wrong more often than anyone expects.
Agree who signs off a run, and make that the only route to publishing payslips.
Books posts salary, statutory dues and employer costs to the ledger from the approved run. Loop uses the same hours for project cost and margin. That is the whole point of running payroll on the shared record: the cost of people appears in the project margin as it is incurred rather than at the end of the month.
A run draws from contracted terms and approved time. Every line traces back to the timesheet and the approval behind it. Adjustments, loans, advances and reimbursements sit on the person's record rather than in a spreadsheet appended to the run.
Nothing is retyped, so the class of error that comes from retyping disappears. More importantly, the same approved hours become project cost in Loop, so the cost of a week's work and the payroll for that week cannot disagree.
It does not file with tax authorities on your behalf, and it does not replace a payroll bureau where you use one. It produces the run and the audit trail; submission depends on your jurisdiction and is not something this page claims.
Import contracts, terms and opening balances, then run a full cycle in parallel with your existing process before switching. Compare line by line, not totals — totals agree while individual lines are wrong more often than anyone expects.
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.