GullyHR configures how your input pack is assembled: which sources feed it, when the cut-off falls, how reimbursements, incentives and deductions are submitted and approved, how a salary revision applies from its effective date, and what format the finished pack is exported in for the person or firm that runs payroll. You supply your current input format and salary components, confirm the cut-off timing and the approval levels for claims and deductions, and keep the payroll function itself, whether that is an in-house accountant, a consultant or a payroll provider. This is a configuration and rollout engagement covering the input side of payroll only. Statutory calculation, filings and disbursement stay where they are today.
One pack replaces the files and messages payroll currently chases.
Everything payroll needs for the cycle is consolidated into a single input pack, so the monthly conversation moves from chasing four people for four files to reviewing one document against a cut-off.
Attendance and leave arrive already closed for the cycle.
Present days, absences, approved leave and regularisations for the payroll period come straight from the attendance and leave records, closed off at the cut-off rather than re-keyed from a register.
Salary components sit on the employee record, not in a separate sheet.
Each employee's salary structure and components are held against their record, so the pack is built from the current approved figures instead of a master sheet that somebody last updated at their own discretion.
Reimbursement claims are approved before they reach the pack.
Claims are submitted with their details, routed for approval at the level you set, and only approved amounts enter the input pack, which ends the email trail and the argument about what was actually sanctioned.
Incentives are recorded against the cycle they belong to.
Incentive amounts are entered and approved against a specific payroll cycle, so a variable payout stops being a verbal agreement remembered at the wrong time or paid twice by mistake.
Deductions carry a reason and an approval.
Advances, recoveries and other deductions are recorded against the employee for the cycle they apply to, with the approval step your policy requires, so a deduction can always be explained to the person it affected.
A salary revision applies from its effective date without a manual correction.
An approved revision takes effect on the employee record from the date you set, so the pack reflects the revised figure from that cycle onward instead of needing an arrears adjustment somebody has to remember.
The finished pack leaves in the format your payroll actually accepts.
The export is configured to the layout your in-house payroll, accountant or provider needs, rather than a generic file somebody reformats by hand every month before it can be used.
A full and final is assembled the same way as a normal month.
An exiting employee's attendance, leave balance, notice period, dues and recoveries are consolidated into a full and final input pack from the same records, instead of being rebuilt from scratch under time pressure.