Every screen walked by hand. Every document opened and read.

Recruitment, onboarding and separations, seen by an employee with no rights

What we found

The refusal message appeared, and above it sat a live New button and a Refresh button. On recruitment there was also a working link to the applicant list. The server refused every one of those actions correctly, so nothing could be done with them, but the screen was advertising doors that were not there.

Fixed

Those controls now render only when the screen is not a refusal.

This was a regression. The same class of defect had been found and fixed once already, and it came back on three more screens. It is in this register rather than quietly dropped from it because a sweep that only ever finds new problems is not being run often enough.

Payroll, seen by an employee with no rights

What we found

A link to the Salary Register was kept beside the payroll refusal for every account, including ordinary employees, for whom it led to a second refusal. It belonged there for the HR accounts that can actually reach that report, and nowhere else.

Fixed

The link is gated to the same roles the navigation uses. The server remains the authority either way.

Personal Data Sheet, on screen

What we found

An employee record with no height or weight recorded displayed both as 0, while the printed CS Form 212 left both blank. The same record told two different stories about the same person depending on where you read it.

Fixed

An unset measurement and a zero now collapse to the same dash the printed form shows.

Executive dashboard

What we found

The browser console logged a markup error on every single load of the dashboard. Nothing was visibly broken, and all eight of the automated checks on that screen passed. But an evaluator from your ICT office opening developer tools on our flagship screen would have seen a red error sitting there.

Fixed

The offending wrapper was corrected, and a check now fails if that screen logs an error again.

Certificate prints

What we found

For any employee with no designation recorded, three of the four document prints produced “This is to certify that Gavino, , has been employed”. The fields themselves were guarded against being empty. The punctuation around them was not.

Fixed

The phrase is now assembled once, and its commas are printed only when there is something between them.

Found because a person opened the files and read them. Three of the four prints had never been read by a human before that pass. The Service Record was the one that was already right, and its correct handling became the model for the other three.

Personal Data Sheet print, CS Form 212

What we found

Words broke in the middle across a line on a signed CSC form. “Administrati / ve Officer V”. “BS Public Administrati / on”. “DEGREE/COURS / E”. A form that reaches CSC looking like that is a form that comes back.

Fixed

The four child-record tables on the form size their columns to their content instead of splitting into eight equal ones.

There is no automated test behind this fix. Catching a mid-word break automatically means rendering the PDF and reading the pixels, which our checks deliberately do not do. It was verified the only way it can be: by re-rendering the form and reading all four pages.

Every published tax figure, across two BIR filings and a payslip

What we found

The withholding was half. A monthly payslip was taxed against the table for a half-month period, while every other line on it — basic pay, PERA, all three premiums — was a full month. The annual return filed ₱696,075.78 where ₱1,392,197.10 was due, 49.998% short, and one employee's slip withheld ₱10,387.45 against the table's ₱20,775.05. Ten of the fifty-two sat in the zero bracket and were unaffected either way.

Fixed

The pack selects the monthly table, because the revenue regulation prints one table per payroll period and says to use the one you actually pay. Every affected slip was re-cut and both filings regenerated from them.

This is the finding that justifies the whole practice. This site's own build recomputes the reconciliation between the two filings on every deploy, and it passed throughout — because the two files agreed with each other exactly, and were both wrong. Two derived files checked against each other can only ever prove they came from the same source, never that the source was right.

The annual filings, for every employee

What we found

PERA was taxed. It is a non-taxable allowance, but the step that splits a year's pay into taxable and non-taxable had no non-taxable set at all, so PERA fell through to the taxable side. The certificate's taxable figure then disagreed with the base its own withholding had been computed on.

Fixed

PERA is classified non-taxable and prints in its own box on the certificate, where a government reader looks for it.

The payslip PDF

What we found

It was the stock, generic payroll layout: three pages, with Cost to Company, Income from Other Sources, Standard Tax Exemption Amount and Future Income Tax all printing ₱0.00, half of page two blank, no PERA line, and no split between what the employee pays and what the agency remits.

Fixed

A government payslip format, one page, now the default for every path that prints a slip.

This is the document an HR officer judges fastest, because it either speaks government or it does not. Until it was fixed the payslip was the one exhibit kept off this site.

BIR Form 2316, item 3

What we found

The employee's own TIN box printed blank. A certificate handed to a bank or to a new employer with that box empty gets handed back.

Fixed

The certificate reads the TIN from the employee's Personal Data Sheet, and the subject of the published certificate now has one. A check fails if he ever does not.

The first fix went to the code that prints the box, and it was already live when this was reported. The cause was the record, not the printer: the subject had no sheet to read a TIN from — a state a real agency never reaches, because the sheet is required at appointment. Fixing the wrong layer first is why this one carries its history.

CS Form 212, Section V

What we found

A work-experience row printed its FROM date as 07-01-2008 and its TO date as 2013-06-30 — two different formats side by side in one row, on a form a CSC reviewer reads column against column.

Fixed

Both columns are reformatted as the form is printed.

The first fix shipped and changed nothing at all. The cause written down at the time was wrong: the TO column is not a date field, because it has to be able to hold a blank or the word PRESENT for a post someone still holds. Writing a cause into a findings file does not make it the cause — the re-render is what checks.

CS Form 212, Section V

What we found

The monthly salary column broke between the peso sign and the figure, printing ₱ on one line and 28,000.00 on the next.

Fixed

That column no longer wraps between the two.

The Service Record print

What we found

The office printed as “Collection Division - BRA”, carrying a suffix the software appends to a department name rather than the office's actual name, and the date of original appointment printed in raw numeric form beside nothing else in that format.

Fixed

The suffix is stripped and the date is formatted. The document now carries one caveat stamp rather than two.

The finding as reported was that Present Position and Office both printed blank. That did not reproduce: the captures showing it predated a data refresh. What was actually wrong was smaller, and real, and would have gone unfound if the headline had been taken at face value.

Notifications and the approvals queue

What we found

An approval by Rogelio Reyes carried an avatar circle stamped H. Other rows showed a question mark.

Fixed

The initial comes from the name in the message rather than from the account that sent it.

The H was the first letter of the sending account's address, not of anyone's name. The question marks were employees with no account at all.