Employees
Add company staff as employees, filter the list, and track their transactions — simple steps for admins.
What is this page?
Employees are your company staff records (shared across all branches). Use them when salary or staff-related payments and Daily Register lines should show under a person. Vouchers still post in the current branch.
Route: Parties → Employees (/parties/employees).
Why you use this page
- Store employee name, contact, ID, and job details once for the whole company.
- View transactions linked to the employee (from register — filtered by current branch).
- Pay salary through Payments with correct party from any allowed branch.
What you see on the screen
What you will see on the screen
- Employees — page title.
- Manage Columns — customize table.
- Filter — find by name or other fields.
- New Employee — red/primary add button when allowed.
- Row / eye — open employee details and transaction tabs.
Step-by-step: add an employee
Open Employees
Parties → Employees.
Click New Employee
Top right → New Employee.
Fill personal and job details
Name, mobile, address, designation, join date — as shown on your form.
Add documents (if required)
Upload ID proof or photo if your shop keeps them.
Save
Wait for success. Employee shows in the company-wide list (visible from every branch).
Step-by-step: record salary payment
Open Payments
Accounting → Payments → New Payment.
Choose employee as payee
Select employee party type and person.
Enter amount and mode
Cash/bank/UPI → complete payment (Payments guide).
Verify on employee details
Open employee → check transaction list matches payment date (for the branch you are in).
What happens after save?
- Employee appears in party pickers from any branch of the company.
- Posted payments/expenses show in employee detail for the current branch (same pattern as Daily Register fields).
Tips
| Tip | Why |
|---|---|
| One employee record per person | Staff who work at multiple branches share one master — do not recreate per branch |
| Separate employee from customer | Same person should not share one record type if your policy forbids it |
| Use Filter in large teams | Faster than scrolling |
| Restrict add to HR/admin | Fewer duplicate staff rows |
If something goes wrong
| Problem | What to do |
|---|---|
| No New Employee | Role permission |
| Transactions empty | No vouchers yet in this branch, or wrong branch selected |
| Cannot edit | Locked or permission — ask admin |
| Same person listed twice | Legacy duplicates from when employees were per-branch — keep one and soft-delete the other |