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. Salaries are not calculated here. A Malaysian payroll module is being built and is not yet an installable applet; until it is, the shape this module supports is the one a business in that position already runs — payroll in whatever system computes it, and the monthly result brought into BigLedger as a general journal.
This section is for whoever keeps employee records, runs claims or posts the payroll journal.
Start here.
- Setting the module up? Read Configuration first: what must exist before the first employee record, in the order that avoids re-work.
- Doing this month’s job? Posting the month’s payroll journal and Handing salary-paid claims to payroll are the two monthly jobs, step by step. For adding or closing a person, Use cases walks each shape with whose job it is and how they know it went right.
- A name or a number already looks wrong? Wages in the trial balance do not match the payroll and An approved salary-paid claim never reached the payslip take the two commonest; for the rest, start from the symptom table in What happens behind the people screens.
Applets in this module
Membership is an editorial judgement — the product has no module↔applet relationship in its data. Under it, 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. |
What reaches the ledger
Employee records and claims post nothing. Payroll Admin’s Post GL does not reach the general ledger either, so bringing payroll into the accounts is a manual journal a person posts in the month the work was done — the detail, and how you know it worked.
What this module does not do today
No leave record, no attendance capture, no approval engine outside Claims, and no salary, payslip or statutory calculation you can use today — and for each, who does the job instead: what this module does not do today.
One month at GadgetSphere, followed through
New hires, a claim approved too late for the list, the payroll journal and a leaver: one month followed through.
When it goes wrong
The symptom table covers Claims not finding a person, salespeople missing from a picker, leavers still approving, import surprises, Bank Report gaps, unpaid salary claims and a payroll journal that does not tally.