Admin Page

Edit a payslip, and a fix for the frozen Individual Payroll page

• Added Payslips can now be edited. Each row in Payslips has an Edit button that loads the slip back into the Individual Payroll form, with every field restored. Saving updates that same payslip in place rather than creating a second one for the period, so the list and the BIR reports never double count. A banner and an Update Payslip button make it clear a correction is in progress.
• Fixed The Individual Payroll page could freeze with a "page is not responding" prompt. The sidebar saving indicator retried an unsaved change in a loop whenever the queue could not drain (no active session, or the database paused), starving the browser and locking the whole page. It now retries only when a change actually saves, and leaves the rest to the periodic background retry.

No em dashes anywhere

• Fixed Two em dashes had slipped into the BIR 1604-C schedule headings; replaced with plain hyphens. A repo-wide scan confirms no em or en dashes remain in any page.

Removed the BIR Annual Income report

• Removed The earlier BIR Annual Income report, now superseded by the BIR 1604-C annual alphalist, which covers the same figures in the official schedule format. Its page, code and the Reports.annualBir helper were all removed, leaving no dead code behind.

BIR 1604-C annual alphalist

• Added A BIR 1604-C report under Reports: pick a year and it builds the annual alphalist, Schedule 1 for non-MWE employees and Schedule 2 for Minimum Wage Earners, from the year's payslips for employees included in BIR reporting.
• Added A full-column CSV matching the alphalist layout (33 columns for Schedule 1, 21 for Schedule 2), including the Jan-Nov versus December tax-withheld split. The on-screen view is a per-schedule summary; print and CSV are provided.

Columns the system does not hold (branch and region codes, nationality, employment-status code, previous-employer figures, PERA credit, substituted-filing flag, and the tax-due/year-end-adjustment reconciliation) are left blank to complete before filing, as the sample alphalist itself expects. Verify against each employee's BIR Form 2316 before submission.

BIR 1601-C monthly report

• Added A BIR 1601-C report under Reports: pick a month and year and it produces the per-employee payroll summary plus the numbered form lines (14 to 36), from the payslips issued that month, for employees included in BIR reporting. For keying into eFPS, with print and CSV.
• Added 13th Month & Other Benefits and De Minimis fields on Individual Payroll, recorded as non-taxable and itemised on the report.

Minimum Wage Earners (from the tax classification field) are treated as fully non-taxable, and their mandatory contributions are not double-counted the way a hand-built sheet can, so the taxable figure is the correct, higher one. 13th month over the annual cap and de minimis over its limits are year-end adjustments to handle on the return. Verify against BIR rules before filing.

Keep-alive now writes, not just reads

• Changed The scheduled keep-alive now performs a real database write each run (it upserts a one-row heartbeat table) instead of a read that changed nothing. A write is heavier and uncacheable, so it stands a better chance of registering as genuine activity.
• Added An optional signed-in ping: set a dedicated keep-alive user in the workflow secrets and the ping becomes authenticated activity as well as a write. Left unset, it still writes, anonymously.

Honest caveat: the project paused twice on the free tier even with a keep-alive running, so this is a best effort, not a guarantee. Supabase decides what counts as activity, and only a plan that does not pause (Pro) or a host without such a rule removes the risk entirely. The heartbeat table holds no payroll data, only a timestamp and a counter.

Employee ID number

• Added An Employee ID No. field on the add and edit employee form, for the company-assigned employee number. Optional, free text, shown near the top of the form.

Like the other later fields it carries its own database-readiness check, so a database without the column keeps saving everything else. Added by supabase/migration_add_employee_id.sql; until it runs the field shows on the form but notes it will not save yet.

Stronger keep-alive after a free-tier pause

• Fixed The project paused despite the keep-alive running. The old ping was a plain read: empty under RLS and cache-servable, so it could return "success" without ever waking the database. The ping is now an RPC to a keepalive() function, which is a POST that PostgREST cannot cache and runs as a real query on Postgres.
• Added The keepalive() function, in supabase/migration_add_keepalive_function.sql. It returns only the server time, so granting it to anon exposes nothing. The script falls back to the old read until the function exists, so nothing breaks before the migration is applied.

This improves the odds but is still a band-aid: the free tier can pause for reasons a ping cannot cover. For a system that pays real people the reliable fix is Supabase Pro, which does not auto-pause at all.

Compute Payroll split into two pages

• Changed Compute Payroll is now a sub-menu with Batch Payroll and Individual Payroll on their own pages, rather than stacked on one long screen. Same forms, same behaviour; the batch run and the per-employee computation each get the full width.

The Pay button on an employee and the "final pay" dashboard reminder open Individual Payroll; the "run payroll" reminder opens Batch Payroll.

BIR Annual Income Report

• Added A second report under Reports, which now has a sub-menu: the existing Consolidated Report, and a new BIR Annual Income Report. It gives each employee's total gross income for January 1 to December 31, one row per person.
• Added Its columns: employee name, TIN, position, gross taxable compensation, non-taxable compensation, total gross income, tax withheld, and the payroll period actually covered. Prints landscape and exports to CSV.

Only employees marked as included in BIR reporting are counted, so anyone taken off the filing is left out. Identity and position read off the live employee record, so a correction reaches the return, falling back to the payslip snapshot for a deleted employee. The figures are summed from the payslips issued, never recomputed, so the report equals what was actually paid.

Group the Individual Employee filter

• Changed The Individual Employee filter now lists "All employees", then the active employees on their own, then anyone separated or deleted who still has payslips. Active staff are quick to pick, an active employee with no payslips yet is selectable at last, and a former employee stays available for a historical report.

Fuller report filters

• Added A custom date range as a Cover option: pick From and To dates and the report counts every payslip whose end date falls between them, instead of being tied to a calendar year. It seeds to the latest year so it is never accidentally every payslip at once.
• Added Department and Employment Status filters, both reading the live employee record so a corrected department or a change of status is reflected.
• Added A BIR Reporting Status filter with three settings: all, included in BIR, or not in BIR.
• Changed Split the combined employees dropdown back into a BIR status filter and an Individual Employee filter, now that there are several distinct employee filters rather than two that read alike. Picking an individual still reports just that person and overrides the group filters.

The filters combine: choose a department, a status and a BIR setting together and only payslips matching all of them are counted, on screen and in the CSV, which both state the coverage on their face. All filtering runs off one shared pair of checks, so the totals never disagree with the payslips behind them.

Tax classification and bank details on employees

• Added Three fields on the add and edit employee form: Tax Classification as a dropdown, plus Bank Name and Bank Account Number. The dropdown covers wage classification (minimum wage earner or not) and the exemption codes (Z, S, ME, S1 to S4, ME1 to ME4).
• Added Their own database-readiness check, separate from the earlier ones, so a database missing these columns keeps saving everything else. The form's pending note now names only the fields actually waiting on a migration rather than a fixed list.

The account number is stored as text, not a number, so a leading zero survives. The columns are added by supabase/migration_add_tax_bank_fields.sql; until it runs the three fields show on the form but note that they will not save yet, and everything else saves as normal.

Date Separated on the edit form

• Added A Date Separated field when editing an employee. Setting a date moves them from Active to Separated Employees on save; clearing it returns them to the active list and drops the separation reason and notes, the same as Reinstate.

It writes the same separation date the Separate button always has, so the two agree and a record separated either way behaves identically. The field shows only when editing, never when adding, and it cannot predate the employment start date. This needs no database change: the separation date column has been there since the database move.

Department and position on employees

• Added Two optional fields on the add and edit employee form: department and position, both free text.
• Added Their own database-readiness check, separate from the earlier personal-fields one. A database that already has the personal columns keeps saving them even before the department and position columns are added, so a partly applied migration never stops the fields that already work.

The two columns are added by the same supabase/migration_add_personal_fields.sql, now covering them too. Until it runs, the form shows the fields but notes they will not save yet, and everything else saves as normal.

One employees filter on Reports, not two

• Changed Folded the coverage filter and the single-employee filter into one Employees dropdown: all employees, BIR-registered only, then each individual. The two had sat side by side both reading "All employees", which looked like a duplicate.

Picking a name reports that one person and shows them even if they are off the BIR filing, since choosing them is explicit. The only combination lost was "BIR-registered only" together with a single named employee, which never meant anything.

Report coverage: all employees or BIR-registered only

• Added An Employees filter on Reports with two settings: all employees, or BIR-registered only. It drives the on-screen figures, the totals and the CSV export, and both the report and the CSV state on their face which coverage produced them.
• Changed The report now shows all employees by default. Since the BIR flag arrived it had been hiding anyone taken off the filing; that exclusion is now the "BIR-registered only" setting, chosen when preparing a filing, rather than something applied to every report.

The two settings never disagree with the payslips they sum: both read the include-in-BIR flag live off the employee record, so moving someone on or off the filing re-scopes the BIR-only view at once, while the all-employees view is unaffected. Anyone off the filing still carries the "Not in BIR reports" tag in the employee list, so it is clear who the BIR-only view would drop.

More employment statuses

• Added Regular, Probationary, Contractual, Casual and Others to the employment status choices, alongside the existing Full-time and Part-time.
• Changed The database no longer fixes the list of statuses. The check constraint that only allowed Full-time and Part-time is dropped in the pending migration, and the employee form's dropdown is now the source of truth, so a future status is an app change with no migration.

Until that migration runs the database still rejects the new statuses, so saving one is blocked with a message rather than being lost, and Full-time and Part-time keep working. The dashboard's active-employee note no longer calls everyone who is not part-time "full-time", since that is no longer the only other option.

Batch payroll for a whole group at once

• Added A batch run at the top of Compute Payroll: pick a scope, a period and the days worked, and it generates one payslip per active employee in a single step. Scope is either all active employees or BIR-registered only, which reuses the include-in-BIR flag.
• Added A live preview naming exactly who a run will cover before the button is pressed, and a confirm step stating the count and period.

Batch payslips go through the same compute and save path as a hand-made one, so they open, edit and delete identically. Anyone who already has a payslip for that exact period is skipped, so a run is safe to repeat and the report can never double count. Separated employees are left out on purpose: their pay is final pay, computed one at a time. Overtime, holiday pay and per-person deductions are not part of a batch; those still go through the single computation.

Choose who is on the BIR report

• Added A switch on the employee form, "Include in BIR reporting", on by default. Turn it off for someone who should not appear on the BIR payroll report or its alphalist CSV, and their payslips drop out of the report and its totals.
• Added A "Not in BIR reports" tag beside excluded employees in the list, so who is off the filing is visible without opening each record.

The report reads the flag live, not from the frozen payslip, so turning it off re-scopes past reports as well as future ones, and turning it back on restores them. An employee whose record has since been deleted stays on the filing by default, so no one is dropped by omission. The flag rides along on the same pending database update as the personal fields; until that is run the switch shows on the form but does not persist, and everyone stays included, which is the safe default.

Date of birth, mobile and email on employees

• Added Three optional fields to the add and edit employee form: date of birth, mobile number and email address. The birth date cannot be set in the future, guarded both in the picker and on save.
• Added A safeguard so the fields could ship without waiting on the database. On sign in the app checks whether the new columns exist; if they do not it leaves those three values off each save, so nothing breaks, and shows a note on the form saying so. The moment the columns are added they begin persisting, no redeploy needed.

The columns are added by supabase/migration_add_personal_fields.sql. It can be run at any time: the check means the app does not depend on the migration having run first, which removes the usual ordering trap where new code and a pending schema change have to land in lockstep.

Keep-alive so the database does not pause

• Added A scheduled GitHub Actions job that runs a real query against the database every three days, so a free-tier project does not pause after seven days of quiet. Well inside the window, so a skipped or delayed run still lands in time.
• Added The health check itself, in scripts/keepalive: it uses the publishable key, which Row Level Security already limits to reading nothing, so the job cannot see anybody's pay. Its one dependency is isolated there, so the app keeps its zero dependencies.
• Fixed The first run failed in CI, which is what CI is for: current supabase-js needs Node 22 for a WebSocket it initialises even for a plain query, and a newer local Node had hidden it. Pinned to Node 22.

This is a band-aid, not a fix. A database that can pause is a poor system of record for real payroll, and if it stops right before a cutoff that is people not paid on time. It buys time to decide on a plan that does not pause; it does not remove the risk. It also stops if the repo goes 60 days without a commit, when GitHub disables scheduled workflows.

Cleared out what the database move left behind

• Fixed The dashboard still warned "no backup has ever been taken, all data lives in this one browser". True once, false the day the database arrived, and it fired every session. It now flags the real risk instead: changes that have not reached the database yet.
• Removed The browser-side login's hashing helper, an unused sync status method, and the whole backup-timestamp mechanism that only existed to feed the old alert. Each confirmed unreferenced before removal.

Kept, each proven still load-bearing rather than assumed: the name-splitting for older backups, the single-deduction fallbacks for payslips issued before that change, and the rescue that lifts a machine's last browser-held copy into the database on first sign in.

Corrections reach payslips and reports

• Fixed Editing an employee updated the employee list and nothing else, so correcting a typo left the error on every payslip and in the BIR figures. Names and government numbers now come from the live record.
• Changed Money stays frozen, deliberately. A payslip records what was actually paid, so a later rise never rewrites one already handed over. Employment status is frozen the same way.

Nothing is kept on the computer any more

• Changed The working set is held in memory and filled from the database when you sign in. Employee names, salaries, TINs and SSS numbers are no longer written to the machine's disk, so there is no second copy to drift out of step and nothing left for whoever sits down next.
• Changed Signing out clears the working set, and refuses to discard changes that have not reached the database without asking first.
• Changed The sign in token moved to session storage. It survives a refresh but not closing the browser, and keeping it on disk bought nothing once the data came from the database.
• Added A sync indicator in the sidebar, and a warning when closing the page with work that has not been saved.
• Added A one time rescue for machines still holding the old browser copy. It uploads on first sign in and deletes the local copy only after reading it back from the database and confirming it arrived.

Only read() and write() in storage.js changed, so reads stayed synchronous and the payroll engine, payslips, reports and dashboard needed no changes. The cost is that the app now needs an internet connection: a cutoff cannot be run offline.

The payroll moved to a database

• Added A Supabase Postgres database holding employees and payslips, so every device that signs in sees the same payroll instead of each browser keeping its own separate copy.
• Added Real sign in through Supabase Auth. Accounts live in the dashboard and no password is stored anywhere in this codebase.
• Added Row Level Security on both tables. Requests without a signed in session read nothing, which is what makes it safe to ship the database key in the browser. Verified against the live project: reads returned empty and writes were rejected.
• Removed The old sign in, which compared a password hash inside the browser and could be stepped around from the developer tools in seconds.
• Changed The client is hand written rather than the official library. It needs two endpoints, and a payroll system with no dependencies has nothing to keep patched and no supply chain to poison.

Security review

• Fixed The server listened on every interface, so the payroll system answered on the shop wifi to anyone who knew this machine's address. Confirmed reachable at a LAN address during the review. It now binds to 127.0.0.1 and answers this computer only.
• Fixed The .git directory was downloadable, which is enough to rebuild every file and every past version of the project. The server now refuses any dot-prefixed path.
• Added A Content Security Policy that forbids inline script and anything not served from this folder, plus nosniff, frame-ancestors none, no-referrer, a permissions policy, and cross-origin isolation headers.
• Changed The admin page's inline script moved to js/admin-page.js, so the policy can forbid inline script honestly rather than allowing it and pretending.

Deliberately not added: Strict-Transport-Security. On plain http localhost it would tell the browser to force https on every localhost port permanently, breaking this and every other local site on the machine. Output escaping was tested by storing script payloads in every user field: none executed, in the app or in a downloaded payslip. None of this changes the fact that the payroll data is unencrypted and readable by anyone at this keyboard.

Cleanup

• Changed The favicon was stored at 256 by 256 and weighed 69 KB, for something a browser draws at 16 to 32 px. Regenerated at 128 px, 72% smaller, with no visible difference.
• Removed The apple-touch-icon links. Nothing pins a local desktop payroll system to a phone home screen.
• Removed An unused .sep-reason rule from the stylesheet, and a withhint class on the employee form that had no styles behind it.

An audit of all 162 stylesheet classes, every function, and every object method found nothing else dead. The backward compatibility code was checked against real old-format records and kept: it is what lets employees saved before the name split, and payslips saved before multiple deductions, still open correctly.

Bigger logo on the sign-in

• Changed The logo is 63% wider, from 184 to 300, and its white card now spans the brand column rather than sitting as a small box in the corner. On a phone it stays a compact chip beside the title.
• Fixed The local server sent no cache headers, so browsers kept showing an old copy of a page after it had been edited. It now sends Cache-Control: no-store. Everything is read from local disk, so there was nothing to gain by caching.

Sign-in no longer displays the username

• Fixed The username field used the real username as its placeholder, so the sign-in screen handed it to anyone who looked at it. Removed.
• Removed The password placeholders on both gates as well. Every field has a visible label, so the placeholders said nothing the label did not.

Sign-in screen scaled up

• Changed The sign-in panel is larger, from 860 to 1020 wide, with a bigger logo, heading, fields and button. It was sitting small in a lot of empty background.
• Removed The footnote line under the blurb, and the rule above it, on both gates.

Sign-in screen redesigned

• Changed The sign-in is now a brand panel beside the form rather than a plain card: the logo, the RC colours drawn from the mark, and a yellow rule down the join. On a phone the brand panel becomes a compact header and the form takes the rest of the screen.
• Changed The admin gate uses the same design, so the two doors match.
• Changed Show password is now an eye button inside the field rather than a checkbox below it. It announces "Show password" instead of "on", and its label names the action rather than the state.
• Added Icons in the username and password fields, and a taller target on the button.
• Fixed A revealed password stayed revealed after signing out, so it was still readable at the next sign-in. Signing out and locking both reset it.

Sign-in on the payroll system

• Added The payroll system asks for a username and password. It stays signed in for the browser session, and Sign out in the sidebar footer ends it.
• Added js/auth.js, shared by the sign-in and the admin gate, so the credential handling lives in one place.
• Changed The app is built only after signing in, so nothing renders behind the sign-in screen. Signing out and back in does not rebind the handlers.
• Changed The admin page is a second door: signing in does not unlock it, and it keeps its own password.

This is not security. There is no server, so the check runs on the same machine as the person being checked and can be skipped from the developer tools. The payroll data is not encrypted either: names, salaries, TINs and SSS numbers sit in the browser storage as plain text and can be read without ever reaching the sign-in screen. It stops someone sitting down at the shop computer and seeing everybody's pay. That is all it is.

Search and filters on Payslips

• Added Employee, Month and Payroll Period filters on the Payslips page, alongside the search box. Choosing a month narrows the period list to that month's cutoffs.
• Added A Clear filters button, and a count that reads "6 of 18" while filtered so a short list is never mistaken for the whole history.
• Changed The search now matches the name parts, TIN and SSS number rather than the full name only, so "juan dela" finds "Dela Cruz, Juan P.".
• Changed Months are labelled with their year, so no separate year filter is needed.

A filter whose payslips are all deleted falls back to showing everything, rather than leaving an empty list with no explanation.

Password on the admin page

• Added The admin page asks for a password before showing anything. It stays unlocked for the rest of the browser session, and a Lock button in the sidebar footer re-locks it without closing the browser.
• Added The password is held as a SHA-256 hash rather than plain text, so the literal string is not sitting in the source for anyone who opens the file out of curiosity.
• Changed The payroll system itself is not locked. Only this admin page is, since payroll is the daily work.

This is a lock on an internal door, not security. Everything runs in the browser with no server, so anyone determined can bypass the check from the developer tools or read these files directly. It keeps a colleague from wandering in on a shared machine, nothing more. Do not treat the admin page as private.

Payroll period within a single month

• Added Choosing Single month now also offers a Payroll Period, listing only that month's cutoffs and defaulting to all of them. Narrowing to one cutoff this way is easier than scanning the year-wide list of every period.
• Changed A month's cutoffs are listed earliest first, since inside one month they read as a sequence.

Changing the month drops a cutoff selected under the previous one, which would otherwise have reported zero without saying why.

Export all months at once

• Added An "All months" cover option on Reports. One row per month for the whole year, printed or exported to CSV in a single step instead of twelve. Months with no payroll stay as zero rows, greyed, because a gap in the year is worth seeing.
• Changed "Month" is now labelled "Single month" to separate it from the new option, and the first column reads Month rather than Employee in that view.
• Fixed The Quarter, Month and Payroll Period filters were all showing at once whatever the cover was set to. The hidden attribute was being set correctly, but label { display: block } in the stylesheet beat the browser's own rule for hiding it, since author styles win over the browser's regardless of specificity.
• Removed The version numbering note from the top of this page.

Dashboard

• Added A Dashboard as the first sidebar item and the page the system opens on. Headcount, payslips issued, gross and net for the year, the latest payroll run, recent payslips, and net pay by month.
• Added Alerts for the things that are easy to miss: employees left out of the latest cutoff, final pay approaching or past the DOLE 30 day deadline, records about to be purged from Recently Deleted, work saved since the last backup, and statutory rates left on a previous year. Each links to the page that fixes it.
• Added Backup now records when it last ran, so the dashboard can say how many payslips are unprotected.
• Fixed The header title was hard coded in the markup and only updated on a click, so the first page loaded showed the wrong name. It now takes its title from whichever item is active at boot.

Consolidated payroll reports

• Added A Reports page giving per employee totals for basic pay, overtime, holiday pay, other taxable and non-taxable compensation, gross, SSS, PhilHealth, Pag-IBIG, withholding tax, other deductions and net pay, with a grand total across employees.
• Added Filters for calendar year, quarter, month, a single payroll period, and employee. Only the control the current scope needs is shown, so the filters cannot contradict each other.
• Added A year-end summary for BIR when one employee is selected: gross, less non-taxable, less mandatory contributions, giving taxable compensation and the tax withheld. The payslips behind the totals are listed so any figure can be traced back.
• Added CSV download for spreadsheet work and alphalist preparation, and printing in landscape.
• Fixed Printing was hard coded to the Payslips page, so any other page would have printed blank. It now prints whichever page is open.
• Fixed The report table ignored its own font sizing. The base rule table.list is an element plus a class, which outranks a bare .rp-table, so the print size never applied and the report would have been cut off at the page edge.

Reports read the stored payslips and never recompute, so a report always equals the payslips actually issued, even if a rate or a statutory table changed afterwards.

Multiple other deductions

• Added Other Deductions takes as many lines as you need, with "+ Add deduction" and a remove button on each, matching how Overtime and Holiday Pay already work.
• Changed The payslip itemises each deduction with its own description and amount, rather than one combined figure. A period with none still shows "Other Deductions" at ₱0.00.
• Changed The live breakdown shows the total with each deduction listed beneath it.
• Changed The form rows were aligned onto a fixed grid, so the description, amount and tag columns line up across Overtime, Holiday Pay, Other Earnings and Other Deductions. On a phone the description takes its own line rather than being squeezed to a few characters.

Payslips saved before this change store a single deduction and no line list. They still render, keeping their original description and amount.

Employee name captured as separate fields

• Changed Add an Employee now takes Last Name, First Name and M.I. instead of one free text field. Last and first are required, the initial is optional and is uppercased as you type.
• Added A live preview under the fields showing how the name will read on lists and payslips.
• Added A one time migration that fills in the parts for employees saved before the split, including when restoring an older backup. Best effort: it splits on the comma, so a multi word surname like "Dela Cruz" survives. Check anything it gets wrong on the employee form.
• Changed Search now matches the parts as well as the composed name, so "juan dela" finds "Dela Cruz, Juan P.".

The composed name is still written to the record on save, so lists, the payroll dropdown and every existing payslip render exactly as before.

Payslips page: list beside the preview

• Changed The saved payslips table and the payslip preview now sit side by side instead of stacked. The list stays put while a long payslip scrolls next to it, and stacks again on narrow screens.
• Added The selected row is highlighted, and a placeholder invites you to pick one when nothing is open.
• Changed Payroll Period is its own column, and the list is wider to hold it. Gross and deductions are no longer repeated in the list, since the preview beside it shows the full breakdown for the selected row.
• Added A compact period format for the table, "Jul 1 to 15, 2026", with the full date kept on the payslip itself and as a tooltip.
• Fixed The payslip's earnings and deductions tables shrank to the width of their own text when stacked, instead of filling the page. The base rule's align-items: flex-start governs the horizontal axis once the direction flips. This also affected downloaded payslips on a phone.
• Fixed The list table overflowed its column, leaving the View and Delete buttons rendered outside the visible area and unclickable where they appeared.

Recently Deleted

• Added A Recently Deleted page under Employees. Deleted employees go there instead of being destroyed, and can be restored or deleted permanently.
• Added A 20 day retention window. Anything older is removed automatically, checked when the app loads and when the page is opened.
• Added A countdown per record, which turns red in the last three days, and a column naming the list each record would restore to.
• Changed Delete is now recoverable rather than permanent, so it is available on the Employee List as well. The confirmation still points you to Separate when the employee has actually left.
• Changed Restoring returns an employee to the list they came from, active or separated, because deletion and separation are tracked independently.
• Fixed A record with an unreadable deletion date showed "In NaN days". It now reads "Unknown" and is never auto-purged on a guess. Reachable by restoring a hand-edited backup.

Admin page uses the sidebar dashboard

• Changed The admin page now uses the same left sidebar shell as the payroll app, replacing the top tab bar. Workflow, Changelog and Documentation are sidebar items, with Back to Payroll in the footer.
• Changed The header title is now "Admin Page".
• Removed The subtitle line under the title, and the admin specific header and tab CSS that is no longer used.
• Added js/shell.js, holding the drawer behaviour now shared by both pages instead of being duplicated.

Favicon

• Added The RC heart mark as the favicon on the payroll app and this admin page, and inlined on downloaded payslips so they carry it standalone.
• Changed The source icon is 185 by 200, which browsers would squash into a square and distort. It is padded to a square 256 by 256 images/favicon.png instead, generated from images/RC ICON.jpg.
• Fixed The local server had no MIME type for .png and served the favicon as application/octet-stream. Added png, jpeg, svg and ico.

Admin section

• Added An admin page at /admin covering workflow, changelog and documentation.
• Added Admin link in the sidebar footer.
• Changed The local server now resolves a directory to its index.html, so /admin works as a clean URL.

Typography rule: no em dashes

• Changed Removed every em dash from all pages, dropdowns, placeholders, tooltips, dialogs and the payslip.
• Changed Removed en dashes too, since they were only used in date and number ranges. Payroll periods now read "July 1, 2026 to July 15, 2026".
• Changed Missing values now read "not set" instead of a bare dash.

Display text only. The pay computation was verified unchanged.

Employees sub-menu and separation tracking

• Added Sub-menu under Employees: Add an Employee, Employee List, Separated Employees, with live counts.
• Added Separation as a real concept: date, reason and notes, recorded through a dialog.
• Added Reinstate, for a rehire or to undo a separation entered by mistake.
• Changed Separate replaces Delete on the active employee list. Delete now lives only on the Separated page behind a warning, because deleting destroys a record that BIR and DOLE expect you to retain.
• Changed Separated employees stay selectable in Compute Payroll under "Separated (final pay only)", since final pay is normally processed after the separation date.
• Fixed Editing a separated employee silently reinstated them. The save handler rebuilt the record from scratch and wiped the separation fields it does not own.
• Fixed The mobile drawer backdrop never rendered. Its media query set position but never restored display, so it measured zero by zero and a real tap outside the drawer hit nothing.

Sidebar dashboard

• Changed The top tab bar became a left sidebar with icons, and the content area gained a header that names the open page.
• Changed Backup and Restore moved to the sidebar footer.
• Added Off-canvas drawer with a hamburger toggle on narrow screens.
• Fixed Icon-only buttons at narrow widths had no accessible name and disappeared from the accessibility tree entirely. All sidebar buttons now carry aria-label and title.

Header cleanup

• Removed The subtitle line under the title, and the CSS rule that styled it.

Initial system

• Added Employee records: name, TIN, SSS, PhilHealth, Pag-IBIG, daily rate, monthly equivalent, start date and employment status.
• Added Computation engine covering basic pay, overtime, holiday premiums, taxable and non-taxable earnings, the three contributions, withholding tax and other deductions.
• Added Statutory tables for 2026: SSS, PhilHealth, Pag-IBIG and the TRAIN withholding tax brackets, each with its source cited.
• Added Printable and downloadable payslip with signature and date received lines.
• Added Backup and Restore as JSON.
• Fixed Downloaded payslips would have arrived completely unstyled when the app is opened by double-clicking index.html. The download scraped the live stylesheet, which the browser blocks reading under file://, and the error was being swallowed silently.