Chachi HRISA Chachi platform module
Philippine HR · Timekeeping · Payroll
Every Philippine HRIS computes SSS, PhilHealth, Pag-IBIG and withholding tax. That is the entry fee. Chachi HRIS is built for the two places the generic ones hand the work back to you — a faculty load sheet and a field shift with no office to clock into — and carries both into a payroll run and a government form with no manual step in between.
One account across every Chachi product. Signing in is handled by the Chachi platform — there is no separate password here, and nothing on this page asks you for one.
Chachi HRIS is in pre-release. It is not yet listed or priced on the Chachi catalogue, and it is not sold self-service. The reason is a gate we set ourselves and have not cleared: two consecutive payroll cycles matched to ₱0.00 per employee against the client's own computation, run in parallel with whatever they use today. That takes two real cutoffs of calendar time and cannot be shortened by working faster.
Until it clears, we take pilot clients and we run beside your existing payroll rather than instead of it. If that is interesting, it is a conversation and not a checkout.
Teaching faculty paid per unit or per contact hour against a semestral load, plus non-teaching staff on fixed office shifts. DTR is processed by hand and faculty pay is rebuilt in a spreadsheet every semester — so the school pays for payroll software and still runs payroll in Excel.
Site-deployed crews and safety officers who never enter a building, plus an administrative core. No trustworthy attendance record for people with no office, and statutory forms assembled by hand each month.
Same statutory core, different attendance evidence, and the same failure in the products they shopped. The load sheet and the geofenced shift are the wedge — not the brochure.
Personal, employment and government identifiers, dependants, and an append-only employment history — a change is dated and kept, never overwritten. Separation retains the record; it does not delete a person who worked for you.
Monthly, daily and hourly rates on effective-dated assignments a database constraint refuses to overlap. A rate change mid-period produces two spans and two figures, never one blended rate that reconciles to nothing.
A geofenced clock-in from the employee's own bound handset, with an offline queue for a site with no signal. A doubtful punch is recorded and flagged, never dropped — and "the phone did not know where it was" is kept distinct from "300 m away", because those lead an approver somewhere different.
Punches paired in Asia/Manila against the schedule, a midnight-crossing shift filed on the day it started, exceptions listed with the evidence behind them, and corrections that are new attributed records rather than edits.
Service Incentive Leave seeded and undeletable. Balances held on submission. Approval chains that resolve to a person — or to HR with the reason. Overtime payable only up to what an approver actually authorised, with the remainder recorded and unpaid.
Every peso on a payslip names the row that produced it. A posted run is immutable and records the exact statutory table versions it used, so it recomputes identically six months later. Corrections are adjustment runs, not edits.
An AES-256 encrypted PDF opened with a passphrase the employee sets themselves — and that we cannot recover, because there is no function in the product that could. A lost passphrase means re-issue. Every open, download and refusal is audited.
Payslips, leave balances, filing a request, seeing the balance before filing, own DTR, own documents. Installable, works through a dead spot, and every route is scoped to the employee's own record by construction.
Receipted claims, mileage on your own rates, per diem, cash advances and their liquidation. A reimbursement returns the employee's own money, so it reaches net pay and touches no contribution basis, no taxable income and no 13th-month base.
Every rate, bracket, floor and ceiling is a versioned, effective-dated row with the circular it came from recorded beside it. A period reads the table in force on its own dates, so a table loaded this afternoon cannot change what last month paid — and where no version is in force, the run refuses rather than quietly using the newest one.
SSS R-3 and R-5, PhilHealth RF-1, the Pag-IBIG remittance list, BIR 1601-C, 1604-C, Alphalist and 2316 — generated from posted runs only, reconciled to the payroll register, and identical byte for byte when regenerated. Where we have not verified a current agency layout, the output says so instead of presenting a guess as a filing. The module generates; you file.
Row-level security on organisation and branch, enforced by the database rather than by a query somebody remembered to write, under an application role that cannot bypass it. Payroll figures, 201 files and government identifiers are treated as sensitive personal information under RA 10173 throughout.
Face-matched clock-in exists and is off until a tenant switches it on — which the database will not allow without a Privacy Impact Assessment, a versioned privacy notice, a working non-biometric alternative, retention windows and an accuracy measurement on your own staff. An employee who declines enrols in nothing and loses nothing.
One button, one redirect. If you have no account yet, that same page creates one — you are not sent somewhere else and you do not fill in a second form. Google or Facebook, then your business details, once, for every Chachi product you ever use.
Your organisation, your first branch, who owns the account, the plan and the trial all live with Chachi Central — along with billing, invoices and settlement. This product never sees a card and never holds a price.
Your Chachi dashboard lists the products you hold. Opening Chachi HRIS from it brings you straight into the setup wizard.
It never blocks you, and it resumes where you stopped — on a different device, after a browser restart, weeks later. Pay groups, employer registrations, your staff, rates, schedules. Nothing here is finished until the database itself agrees it is, which is why the product tells your portal it is ready rather than letting anybody tick a box.
Because the fastest way to lose a payroll client is to be discovered rather than to have said so first.