HR & Payroll Module

BigLedger keeps a record of every employee — who they are, which branch and company they belong to, how they log in, which bank account they are paid into, and who they report to — and it runs employee expense claims through to the point where a line is either paid by finance or handed to payroll. Where Payroll Admin is installed on the tenant, you can also configure Malaysian statutory payroll, run monthly pay runs, generate bank files and statutory TXT, and Post GL.

Payroll Admin. The installable applet is documented at Payroll Admin. First-time setup and the monthly cycle: Configure and run monthly payroll. Payroll Admin has no row in the applet registry (checked 2026-09-18), so it does not appear in the Applet Store. Ask your BigLedger contact to enable it on your tenant.

Applets in this module

Membership is an editorial judgement — the product has no module↔applet relationship in its data — and it is written down in planning/specs/module-applet-membership.md. Under that spec HR & Payroll is primarily a supporting module for the registered people-administration applets below. Payroll Admin is documented separately under Human Resources when it is available on your tenant.

Applet	Owned by	What it does for HR
Employee Maintenance	Core	The employee master. One record per employee: identity, employment status and dates, default company / branch / department, the link to their login, bank details (Payment Config), tax rows, spending limits, up to three levels of Report To, employee categories, org charts, and a CSV import.
Entity Maintenance	Core	The type-agnostic view of the same entity table. An employee is an entity with the `EMPLOYEE` flag; this applet is where the Employee Category tree is also maintained, and where you turn an existing customer or supplier into an employee as well.
Claim Applet	Claims	Where an employee submits an expense claim and a supervisor approves it. Claim items marked Salary Payment are approved for payroll rather than paid by finance.
Claim Cycle Applet	Claims	The finance side of claims. Its Payroll Payment Report and salary-payment CSV export are the list of approved amounts to hand to whoever runs payroll.
Payroll Admin	HR & Payroll	When installed: company statutory setup, pay calendars/periods, salary structures, GL mapping, employee roster, pay runs, bank files, Post GL, and statutory TXT reports.

The employee record is an entity

There is one entity table in BigLedger. Customers, suppliers, employees and merchants are rows in it with four flags, and the same person can carry more than one. Employee Maintenance shows the employment fields only while EMPLOYEE is among the record’s types; Entity Maintenance shows every record regardless of type. Two consequences follow:

An employee who is also a customer is one record, not two. The CSV import matches on employee code first and, failing that, on ID number, tax number, e-mail and phone against all entities — so a row without an employee code can update an existing customer and flag it as an employee rather than create a new person.
Employee codes are generated from the EMPLOYEE_ID running number and the tenant’s employee prefix when you leave the field blank. Set the prefix before the first import if you want codes with the prefix you chose.

What reaches the ledger

Employee Maintenance and Entity Maintenance write master data and post no journal. The two claims applets post no journal, move no stock and create no payment voucher — a claim is not a generic financial document and has no entry in the platform’s journal-posting handler for the claim itself. Money for a Salary Payment claim line leaves the business through payroll.

When Payroll Admin is installed and you run Post GL on a finalized pay run, the payroll backend posts the payroll journal using the company’s default GL Mapping. Until that step succeeds, treat payslips and bank files as operational outputs, not as proof that the general ledger has been updated.

What this module does not do today

Worth stating plainly:

No leave record. Employee Maintenance has an Approved Leave tab, and it saves nothing — its add handler is empty and its save call is commented out. Do not use it to record leave.
No attendance capture. No registered applet writes a clock-in or clock-out event.
No approval engine of its own outside Claims. Claims has one, always on, built on bl_aat_claim_approval_setting.
Payroll Admin is documented when installed — see Payroll Admin. This wiki still does not publish EPF, SOCSO, EIS or PCB rate tables; rates are tenant configuration.