What is actually
in the box.

The employee record everything else points at: personal details, department, designation, grade, employment type, joining and separation dates, photo, blood group and emergency contact.

Each employee also maintains their own profile without being able to edit the fields that decide their pay or their approvals — self-service where it is safe, locked where it is not.

Organisation structure is data rather than a diagram: departments, designations, org units and grades are lists you edit, and every approval route reads from them.

Two clocks, one record. Biometric devices are read directly from their own database — nobody exports a file — and phone punches with face matching and geofencing land in the same timeline.

Shifts carry their own start, end and grace period, so late, early leave and overtime are judged against the employee's actual working day rather than one company-wide number. Field staff can be granted an explicit remote-punch permission, one person at a time, and remote punches are marked as such rather than hidden.

A live daily report groups the whole company by location and punctuality band, and knows the difference between somebody who has not punched out yet and somebody whose punch is genuinely missing.

Leave is a rulebook rather than a register. Entitlement, accrual, carry-forward, encashment ceilings and continuous-service qualification are settings, and the balance is derived from approved applications — never typed, never deducted by hand, so it cannot drift.

The balance separates what has been used from what is awaiting approval, which removes the commonest support question in any leave system: why a balance of five refuses a five-day request the employee has already spent.

Employees apply from a calendar showing their own shift's off-days and the company holidays. The system blocks double-booking, refuses ranges that are entirely non-working days, and computes the deduction with one rule that the form, the balance and the printed form all read.

Payroll reads the attendance and leave that already exist rather than asking anyone how many days somebody worked. Pay scales, components and policies are configured, and a pay run produces payslips employees can see themselves.

Rates are effective-dated throughout. Changing this month's allowance rate creates a new rate from a new date — it does not rewrite last year, which is what makes a payslip from eight months ago still worth trusting.

Advances, loans and expense claims are handled as their own documents with their own approvals, so what reaches a payslip has already been agreed by somebody.

A full subsidised-meal operation, because for a company feeding a few hundred people a day it is a real cost centre rather than a perk to be handled in a spreadsheet.

Ordering, vendor delivery, serving points, menus, rates and per-employee subsidy percentages are all configured. Deliveries are matched against orders, and what an employee contributes flows to their payslip automatically.

The reporting is where it earns its place: no-shows, waste, variance against order, vendor performance and a settlement report for paying the caterer.

A real double-entry ledger, not a summary of one. Chart of accounts, account groups, cost centres, projects, currencies, financial years and periods.

Every posting enters the ledger through a single controlled route. That is the design decision the whole module rests on: because nothing can write to the ledger by another path, the sub-ledgers and the general ledger cannot quietly disagree, and the separation between who prepares and who approves is enforced rather than requested.

Receivables and payables carry their own documents — invoices, receipts, bills, payments — with ageing, ledgers and exposure reporting on top.

Items, item groups, units, warehouses and suppliers, then the documents that move things: requisition, purchase order, goods receipt, issue, transfer and adjustment.

Stock movements are written to one signed ledger, and which account a movement hits is resolved in a defined order — the item first, then its warehouse, then its group, then policy — so nothing lands in a suspense account because a setting was missing.

There is a reconciliation report whose only purpose is to prove the stock value in the warehouse against the stock value in the accounts. If those two ever disagree, you find out from a report rather than from an auditor.

One approval engine serves every document type — leave, late arrivals, expense claims, purchase orders, requisitions, vouchers and meal orders all travel the same machinery.

The chain itself is data: an approval matrix of levels and approvers you edit on a screen. Adding a level, naming a stand-in for the holiday season or changing which manager signs is an afternoon's admin work, not a development request and a release.

Levels run in order, levels that do not apply are skipped and the skip is recorded, nobody approves their own request, and Return and Cancel both require a written reason. Approvers work from a directory of cards showing who is asking and what for — most requests never need to be opened.

The parts that are not a module but make the modules usable.

A role centre home page whose tiles are generated from the menus you were actually granted; global search across twenty-two record types with prefixes and a voice option; dashboards and charts; a document registry that knows where every file in the system lives; an ID-card studio that prints real badges with self-verifying QR codes; internal chat with voice notes; a shared task board; and a customisation studio.

Underneath: role-based access enforced at every address rather than by hiding menus, one live session per user, an audit log, and automatic document numbering with rules you set.