Skip to main content

Payroll

This page helps you prepare, process, review, and approve payroll with confidence.

Before you start​

  • Confirm the payroll group, cut-off, and payroll date.
  • Make sure employee records are complete and active.
  • Make sure attendance, leave, overtime, undertime, and official business requests are reviewed.
  • Confirm allowances, compensations, deductions, loans, bonuses, and commissions have the correct effectivity dates. Effective-dated rows are paid automatically in the period they cover.
  • Review the statutory rates with your payroll lead. Statutory tables are effective-dated so historical runs stay reproducible; the engine refuses to process a payroll whose date is outside every effective row.
  • Check each employee's payment type (monthly or daily) and benefit switches (rest day, holiday, overtime, night differential, de minimis).

Country and statutory configuration​

Payroll uses the country selected during installation. Open Settings → Country & statutory to review the country, currency, locale, and timezone. The country cannot change after the first processed payroll, because historical runs must keep the rules they were computed with.

  • A Philippine installation uses the built-in SSS, PhilHealth, Pag-IBIG, GSIS, and BIR withholding schedules. Review them under Statutory (PH).
  • Other countries use Statutory components and Statutory bracket rows. Each component declares whether it is a contribution, tax, levy, or fund; whether the employee, employer, or both pay it; and whether it is a percentage, bracket table, or fixed amount.
  • A component marked Reduces taxable income is applied before the tax component.
  • Deductions that are not statutory are maintained under Payroll Management → Deductions and can be fixed or a percentage of a chosen base.
  • Loans are maintained under Payroll Management → Loans and attached to an employee with an amortization. A government installation seeds the GSIS policy, emergency, and real-estate loan programs; they are salary deductions, not statutory contributions, and are remitted through the loans working paper.
  • Every run also writes itemised deduction lines used by the payslip and the remittance report.

Ask your payroll lead to confirm the effective dates and source of every rate. Effective-dated rows keep historical payrolls reproducible.

Payroll groups​

A payroll group defines how often employees are paid and which rules apply. Open Payroll Management → Payroll Group to review or create one.

Typical settings include:

  • frequency (for example, semi-monthly or monthly)
  • days per year and hours per day (261 for Monday–Friday, 313 for Monday–Saturday)
  • SSS, PhilHealth, Pag-IBIG, and tax schedules
  • whether the group is the default group

Employees must be assigned to the correct payroll group.

Compensation catalogue​

Compensations, allowances, bonuses, and commissions come from one catalogue shared by every company, so you do not need to create your own compensation types. Open Payroll Management → Compensations to review the catalogue. System rows are read-only.

If your company needs a different amount or non-taxable ceiling, open the row and choose Override. This creates a company-specific copy; only the amount and the non-taxable ceiling can be changed, and the override is used for your company wherever the original would be. Delete the override to fall back to the shared values. Assign the compensation to an employee from Employee Compensation or Employees → Assign compensations.

Each non-taxable row records its maximum amount per annum: the annualised BIR de minimis ceilings under RR 29-2025 (rice, uniform and clothing, medical cash allowance, laundry, actual medical assistance, achievement awards, gifts, and CBA/productivity incentives) and the ₱90,000 13th month and other benefits exclusion on the bonus rows. The ceiling payroll applies to a de minimis allowance is the statutory one from the de minimis table. It is tracked against what the employee has already used in the same month, semester or year, so a payment inside the ceiling is not taxed just because earlier payrolls used part of it; only the amount above the remaining ceiling is taxable.

An allowance assigned as special with a release date is paid only in the payroll period that contains that date. A recurring allowance follows its payment schedule (first pay, last pay or every pay).

A payroll processed before a ceiling change keeps the figures stored with it. Reopen and re-process the payroll to recalculate it with the current ceilings.

How pay is calculated​

  • Monthly-paid employees receive a fixed period basic (the monthly rate divided by the number of pays). Working fewer or more days in a cut-off does not change it; absences reduce it by the daily rate and premium days add only the premium portion (rest day +30%, regular holiday +100%, and so on).
  • Daily-paid employees are paid for attended days, with the full premium for rest days and holidays, 100% for an unworked regular holiday when they worked or were on paid leave the day before, and 125% overtime plus the 10% night differential.
  • Allowances, compensations, bonuses, commissions, loans, and other deductions configured for the period are included in gross and net pay.
  • Minimum wage earners are exempt from tax on the statutory minimum wage and on the holiday, overtime and night-shift pay attributable to it.

Payroll types​

TypePurpose
RegularThe normal cut-off payroll.
13th month1/12 of the basic salary earned in the year, with the ₱90,000 exclusion aggregated with other benefits.
Final payFinal period pay, pro-rated 13th month, leave conversion and separation pay for separated employees.
Annual adjustmentYear-end true-up of withholding tax against the annualised taxable income.

Create the non-regular runs from the console:

php artisan payroll:special {group} thirteenth_month --date=2025-12-24 --process
php artisan payroll:special {group} final_pay --separation-reason=retrenchment --years-of-service=5 --process
php artisan payroll:annualise {group} --year=2025 --process

Add --employee=ID (repeatable) to restrict a run.

Create or open a payroll run​

  1. Open Payroll Management → Payroll.
  2. Create a payroll for the period, or open an existing one.
  3. Check the payroll group, payroll date, cut-off, and date range.

The payroll run page shows a step indicator and the payroll status.

The payroll flow​

1. Preview​

Select Preview. The payroll engine calculates the run without saving the final results.

Use the preview to check:

  • employee count and totals
  • gross pay, deductions, and net pay
  • statutory contributions and withholding tax
  • employees with zero or unusual pay
  • missing attendance or incomplete records

Preview is a dry run. It is safe to repeat.

2. Process​

Select Process payroll and confirm.

Processing recalculates the run and writes the payroll details. The status moves to running. The page refreshes automatically while processing.

  • Smaller payrolls are processed immediately.
  • Larger payrolls are queued and may take longer. Keep the queue worker running.
  • If processing fails, the page shows the reason. Fix the data and process again.

3. Review​

When processing finishes, the status becomes processed. Review the payroll details carefully:

  • employee pay and deductions
  • overtime, leave, undertime, and official business effects
  • loans and other recurring deductions
  • statutory contributions and tax
  • employer contributions
  • totals and headcount

4. Approve and lock​

When the run is correct, select Approve & lock and confirm.

Approved payrolls are locked. This protects the numbers used for payslips and reports. If you need to change an approved payroll, a company owner must enter a reason and select Reopen. The reason is stored in the payroll audit trail, the journal entry is reversed, and the payroll moves back to processed so it can be reviewed and approved again.

Re-processing never destroys the prior run: the previous details are copied to the payroll revisions before the new figures are written.

4a. Review, then approve​

After processing, open the payroll run and complete the Review and segregation of duties panel:

  1. Read the register and the control totals.
  2. Enter an optional review note and select Mark reviewed.
  3. Approve with a different user where possible.

If the run has not been reviewed, or you are approving a run you processed yourself, approval requires an approval override reason. The reason and the reviewer/approver are recorded in the payroll audit trail.

4b. Paying without attendance​

If employees have no timesheet for the period and the company pays the basic salary without attendance, the run shows an attendance warning. Enter an attendance override reason before processing. The reason is stored on the payroll and in the audit trail.

4c. Statutory verification and data quality​

Before a 2026 run, verify that the statutory tables cover the payroll date:

php artisan payroll:statutory:verify 2026-11-30 --company={id}

Provisional rows are reported but do not block; add --strict to fail until every row is confirmed. Use the data-quality report to find invalid MWE flags, missing government IDs and missing office/employee region or industry:

php artisan payroll:data-quality --company={id}

5. Payslips​

After processing or approval, open an employee's payslip from the payroll register. Payslips can be printed from the browser or downloaded as a PDF, depending on your permissions.

See Reports and payslips.

6. Export the register and remittances​

php artisan payroll:register {payroll} --path=register.csv
php artisan payroll:remittance {payroll} --path=remittance.csv
php artisan payroll:bir-2316 {group} --year=2025 --path=bir-2316.csv

The register reconciles to the journal entry posted when the payroll was approved.

Payroll statuses​

StatusMeaning
OpenThe payroll exists but has not been processed.
DraftAn early state used by some records. Preview and process when ready.
RunningThe payroll engine is processing. Wait for it to finish.
ProcessedDetails are calculated and ready for review.
ApprovedThe payroll is reviewed and locked.
ClosedThe payroll is final and no further changes are expected.

Before you approve​

  • The payroll group and period are correct.
  • Every expected employee appears.
  • No unexpected employee appears.
  • Attendance and requests are up to date.
  • Overtime and leave are correct.
  • Allowances, compensations, bonuses, commissions, loans, and recurring deductions are correct.
  • Statutory contributions and tax look right.
  • Net pay totals match your review.
  • You have taken a database backup or snapshot if your team requires one.

Sector-specific payroll work​

The installer fixes the sector for the whole installation. Payroll, catalogues and reports follow it.

Government​

  • Contributions are GSIS (9% employee / 12% employer, effective-dated), not SSS.
  • The compensation catalogue includes PERA, RATA, mid-year bonus, year-end bonus, cash gift, SRI and CNA. PBB and the loyalty cash gift stay inactive until the current guidelines are verified.
  • Salary grade and step are part of the employee record. Use the step-increment command after the required years of service:
php artisan payroll:step-increments --company=1 # report only
php artisan payroll:step-increments --company=1 --apply # write the increments
php artisan payroll:loyalty-awards --company=1 --apply # loyalty cash gift
php artisan payroll:terminal-leave --company=1 --apply # separated employees

All three commands are dry runs without --apply and write to hr_audit_events.

Private​

  • Contributions are SSS, PhilHealth and Pag-IBIG.
  • 13th month pay (PD 851) and service incentive leave (Labor Code Art. 95) are in the compensation/leave catalogues.
  • payroll:remittance --format=sector writes the private remittance set.

Document check​

php artisan payroll:documents --company=1
php artisan payroll:documents --company=1 --format=csv

The checklist comes from the sector profile. Identifier codes are checked against the employee master data; other documents are reported as Manual until uploads are stored.

Common questions​

Why is the process button disabled? The payroll may already be approved or closed. Reopen it first if changes are needed.

Why is an employee missing? Check the employee's payroll group, employment status, date hired, and attendance for the period.

Why are the amounts different from last time? Check attendance, overtime, leave, loans, salary changes, and statutory rates. Use Preview to compare before approving.

Who can reopen an approved payroll? Only the company owner can reopen an approved payroll, and a reason is required. The reason and the engine version are recorded in the audit trail.

Why does processing stop with "statutory table does not cover the payroll date"? The payroll date is outside every effective row of a statutory table. Import the current schedule (php artisan payroll:statutory:import) or correct the payroll date. The engine will not silently use a stale table.

Can I process the same payroll twice? Preview as often as you like. Processing recalculates the run. Approved payrolls are locked, so reopen first if you need to process again.

See also​