Built for the plant
Seven plant-floor problems, and what we do about each
Every card names a real pain point and the shipped feature that answers it.
Three readers, three export files, one person merging them the night before cutoff
Feature: Biometric punch log processing takes the raw logs and resolves them into the DTR cutoff per employee, against each worker's assigned work schedule. Time-clock locations add web or mobile face-recognition punches with geolocation for sites without a reader. Reader logs are loaded per cutoff, not synced live from the device.
Production on daily rates, supervisors and office on monthly, all in one cutoff
Feature: Pay classes and ranks are master data, and payroll processing computes each employee from their own class: days worked from the DTR for daily-paid, salary for monthly-paid, overtime from approved requests, with SSS, PhilHealth, Pag-IBIG, and withholding tax at the rates currently in effect. 13th month is computed inside the cutoff.
Regular holidays, special days, and the local fiesta nobody told payroll about
Feature: A holidays calendar maintained in master data, applied by DTR and payroll processing to the days actually worked. Premium handling is configured to your policy during implementation and verified in the parallel run.
Line maintenance, power interruptions, and forced leave that has to be recorded correctly
Feature: A shutdown workflow with its own approval chain, filed and approved before the cutoff so the days are treated the way your policy says, not the way the punch log implies.
Company loans, cooperative loans, canteen, uniforms — each on its own repayment schedule
Feature: Loans are recorded per employee with entries and balances, and deduction schedules control which cutoff each statutory and company deduction hits. Retro adjustments handle corrections. Workers see their own loan balances in the app instead of asking the cashier.
Tools, PPE, radios, and lockers issued to workers who may resign next month
Feature: A company assets tab on every 201 file records what was issued to whom. At separation, final pay computation is run from the same record, with BIR 2316 generated on the official form as a PDF.
An incident on the floor, an NTE due tomorrow, and an inspection visit next week
Feature: Employee relations: an offense log, NTE and decision templates, a case module with deliberation, evidence uploads, confidentiality controls, and suspension or termination including the authorized-cause 30-day notice track. Behind all of it, an audit log of every create, update, delete, approve, reject, and login with before/after values — the record you hand over when asked.
Everything else a plant's HR office runs
Included: leave balances with the annual refresh and leave conversion report, per-cutoff payslips on company letterhead, payroll summary with Excel export, recruitment for the next hiring batch, 201 file document uploads, HR form templates, trash and restore for every record, and a dedicated instance with your own database.
How a cutoff runs
From the gate to the payslip
- Load the punch logs. Reader exports from every gate go in; the system resolves them into each worker's DTR against their schedule.
- Clear the exceptions. Failure-to-swipe, late slips, overtime, official business, shutdown, and leave requests already approved in their chains are applied. What is left is the short list worth a supervisor's attention.
- Process payroll. Daily and monthly rates, holidays, overtime, loans and deduction schedules, statutory contributions, withholding tax, retro adjustments, and 13th month where due.
- Review and release. Payroll summary on screen and in Excel for finance; payslips published per cutoff to the portal and the app.
Switching without the fear
What the parallel run looks like for you
One full month, every gate, every pay class
We migrate your 201 files, pay classes, schedules, loan balances, and leave balances, then run one complete month (two cutoffs) in AppDeep Payroll alongside your current system, from the same raw reader logs. For a plant that means the comparison covers daily-paid and monthly-paid workers, overtime, a holiday if one falls in the period, loan and canteen deductions, and any separation with final pay. Your finance team gets the line-by-line comparison and signs off only when it matches to the peso. On our first migration, a 580-employee company, 580 of 581 employees matched on the first run; the one exception was a data-entry error in the old system.
If your cutoff has a rule we have not seen, the parallel run is where it surfaces. We configure it, re-run, and compare again before anyone goes live.