From Line Manager to HR: An eHajira Guide to Leave and Overtime Approvals
November 03, 2026
From Line Manager to HR: An eHajira Guide to Leave and Overtime Approvals
A line manager approves an employee’s leave because the team can cover the shift. At month-end, HR finds that the request was recorded under the wrong leave category. Meanwhile, another manager authorizes two hours of overtime to finish an urgent order, but the attendance record shows a longer shift. Both managers made reasonable operational decisions. The problem is that neither decision, on its own, gives payroll enough information to close the record correctly.
A clear approval workflow separates three responsibilities: the line manager reviews operational need and staffing, HR checks policy and exceptions, and payroll processes the verified outcome. eHajira can support this workflow through its documented leave requests, multi-level leave approvals, attendance reporting, and plan-dependent overtime and payroll features. This guide explains how to divide approval authority, handle absent managers, reconcile overtime against actual work, and prepare reliable payroll inputs for businesses in Bangladesh.
What Multi-Level Approval Means in eHajira
Multi-level approval means that a request passes through more than one authorized reviewer before it is finalized. Each reviewer should answer a different question. For leave, the line manager might confirm whether colleagues can cover the work, while HR checks the requested category, available entitlement, and applicable policy. For overtime, a supervisor might confirm why extra work is needed, while HR reviews the employee’s schedule and any exceptions before payroll receives the result.
Trimatrik’s published eHajira documentation describes an Approvals area that supports leave requests passing through multiple authorities. It also describes Leave Types, Leave Requests, and Leave Balances. Selected manufacturing plans list shift management, attendance reports, overtime calculation rules, and payroll processing. Those are distinct capabilities. An overtime calculation rule can flag or calculate hours under configured settings; it does not establish that a particular manager has authorized those hours. The public materials reviewed do not establish that overtime uses the same approval routing as leave or that automatic temporary delegation is included in every plan. Verify those controls in your workspace before designing a process around them.
How a Leave Request Moves from the Employee to HR
A leave request starts with the employee identifying the dates and the appropriate leave type. Set up categories in eHajira to reflect the organization’s approved policy and applicable requirements. Ask employees to use a consistent submission channel so the line manager and HR work from the same request. If someone reports an urgent absence by phone first, define who will record it afterward and how the employee can confirm the details.
The line manager reviews the effect on operations. Suppose a Chattogram distribution branch receives a two-day leave request from the person normally responsible for dispatch reconciliation. The manager can check the duty schedule, identify a trained colleague to cover, and document any handover required. That decision establishes that coverage is workable. It does not settle which leave balance should be used or whether both dates count as working days for that employee.
HR then checks the employee’s record and the selected leave category. A request spanning three calendar days may include a scheduled rest day, so the dates and the chargeable leave days may differ under the rules applicable to the case. If the employee chose the wrong category, resolve it through the approved correction process and tell the employee what changed. Once finalized, confirm that the request status, balance, and attendance treatment agree. A practical test is to compare one approved leave request with the relevant roster and attendance report before relying on the workflow at scale.
Not every employer needs a manual HR review on every routine request. Some organizations may assign final authority for standard requests to a manager and reserve HR review for cases such as unclear eligibility, disputed balances, or changes after a payroll cutoff. Whether that design is available in eHajira depends on your configuration. The principle is to give each approval stage a defined purpose, so additional reviewers catch distinct problems instead of repeating the same check.
Why Overtime Authorization and Overtime Verification Are Separate
Overtime pre-approval records an operational decision before extra work takes place. A supervisor may authorize a warehouse employee to stay until 8:00 p.m. because a shipment must leave that evening. The authorization records the intended duration and business reason. The employee may finish early, continue longer because the loading bay is delayed, or remain on site after work for another reason. The plan and the actual record answer different questions.
Consider a Gazipur manufacturing team with an approved two-hour overtime assignment. The attendance device records a checkout two hours and forty minutes after the scheduled shift ends. The supervisor should confirm what work took place and whether any break, handover, or device issue explains the difference. HR should check the applicable working-time rules and investigate the additional forty minutes before the payroll record is finalized. A checkout time is useful evidence, but it does not settle every question about the nature or duration of the work.
The reverse can happen as well. An employee authorized for two hours may finish after ninety minutes. If the organization simply copies the approved amount into payroll without reviewing actual work and applicable rules, it can create an inaccurate record. Keep the originally authorized duration, the evidence of time worked, and the verified payroll treatment distinguishable. Where overtime pre-approval is managed outside eHajira, give the authorization a reference so reviewers can match it with attendance and payroll records later.
Set Approval Authority by Role, Branch, and Request Type
An approval route works only when the people receiving requests have both authority and enough information to act. A branch manager may know whether a store can operate with one fewer employee on a busy day. Head office HR may be better placed to resolve a disputed leave balance or apply a common policy across branches. Payroll needs the verified number of hours or days and the correct treatment for the pay period.
Start with the reporting relationships already in use. If a technician works in Sylhet but reports to a service manager in Dhaka, decide whether local coverage should be confirmed before the reporting manager reviews the request. If an employee transfers mid-month, determine who owns pending requests tied to the old assignment and who reviews new requests. Tie the route to the responsibility being exercised rather than assuming that a person’s location always identifies the right approver.
Use additional approval levels where the decision warrants them. For example, a branch supervisor might confirm overtime need and head office might review exceptional spending. That budget decision remains separate from the review of time already worked and any pay owed. Keeping the responsibilities separate helps an employer control future commitments without making payroll depend on an unresolved budget discussion.
Before rollout, run a sample leave request from submission through final status using the actual employee, manager, and HR permissions in a test or demonstration environment. If the organization needs a different route for overtime, test that workflow separately. Verify who can see each request, who can act, and what happens when the first reviewer returns a request for clarification.
Delegate Approval Authority When a Manager Is Away
Temporary delegation keeps requests moving when an approver is on leave, travelling, or otherwise unavailable. Define who can act, which employees or branches they cover, what kinds of requests they can review, and when the delegation expires. An assistant branch manager might cover routine leave requests for one branch during a one-week absence, while overtime exceptions continue to go to HR. Avoid giving broader authority merely because it is easier to describe.
Pending requests deserve special attention. A request submitted before a delegation starts may still be assigned to the original manager. Decide whether the backup reviewer can handle existing requests or only new submissions. When the original manager returns, check which requests the backup completed and who owns any that remain open. This is also useful if a manager changes roles permanently and an old approval queue has not yet been reassigned.
Confirm whether your eHajira setup supports the reassignment or temporary permissions you intend to use. If the feature is unavailable, use a documented alternate approval route and have an authorized administrator record the outcome through the organization’s approved process. The record should show who actually made the decision. Having a substitute sign in with the absent manager’s credentials would make that difficult to establish.
Apply Bangladesh Labour Requirements Before Configuring Payroll
Bangladesh employers should review the rules applicable to their establishment and workforce before configuring leave and overtime calculations. Section 108 of the Bangladesh Labour Act addresses overtime allowance for covered workers who work beyond the hours specified under the Act. It also includes a separate provision for piece-rate workers. Section 117 addresses annual leave with wages and reflects changes made by the Bangladesh Labour (Amendment) Act, 2026. The correct application depends on the worker and establishment, so a single rate or leave rule should not be copied across every employee group without checking coverage.
This distinction matters when an approval record is incomplete. If work has already taken place without pre-approval, investigate the circumstances and determine any applicable payment obligation. Treat the missing authorization as a process exception. It should not, by itself, determine whether time worked is payable. Similarly, a staffing concern raised by a manager does not settle an employee’s entitlement to a particular category of leave. HR should apply the relevant requirements and approved policy to the case.
For a Bangladesh retailer operating several outlets, the immediate concern may be shift coverage during a seasonal sales period. For a manufacturer with rotating shifts, it may be matching overtime to the correct shift when work crosses midnight. A service company may instead need to verify emergency work away from its main office. These are different operating examples, and each calls for different evidence. In each case, test the relevant eHajira attendance and overtime settings against known examples before relying on the resulting payroll figures.
Reconcile Approved Requests Before Closing Payroll
A payroll cutoff gives HR time to resolve missing or contradictory records before payment is processed. For leave, compare approved dates and categories with the employee’s roster and attendance. This can catch a day marked absent even though leave was approved, a cancellation that was not reflected in the balance, or a request charged to the wrong category. For overtime, compare the scheduled shift, authorization where required, attendance or other work evidence, and verified payable hours.
Define what happens when a request is still open at cutoff. An unresolved attendance entry, an outstanding manager decision, and a confirmed payroll adjustment are different situations. Give each case an owner and a resolution deadline. If a closed pay period needs correcting, retain a record of the original figure, the corrected figure, why it changed, and who approved the correction. This makes it easier to answer an employee’s question about a payslip and to identify recurring problems in the workflow.
To measure whether the rollout is helping, compare similar pay cycles. Track how long requests remain with each reviewer, how many reach cutoff unresolved, and how often attendance or payroll must be corrected afterward. If a second approval stage causes delays without resolving distinct issues, revisit its purpose. If exceptions repeatedly arise from one branch or shift, check its roster and authorization practices before changing rules for the whole organization.
Frequently Asked Questions
1. What is a multi-level leave approval workflow?
It is a process in which an employee’s request is reviewed by more than one authorized person. The reviewers may have different responsibilities, such as confirming shift coverage, checking eligibility, and resolving exceptions.
2. Does eHajira support multi-level leave approvals?
Trimatrik’s public product documentation describes multi-level approval for leave requests. Confirm how many stages your workspace supports, which roles can approve, and whether the available routing matches your policy.
3. What should the line manager check before approving leave?
The line manager should assess work coverage, existing absences, and any handover needed. If the leave type or balance is unclear, the manager should refer that question to the person authorized to apply the policy.
4. What does HR check after the line manager reviews a request?
HR can verify the category, eligibility, leave balance, dates, and exceptions relevant to the request. It can also check that the approved outcome is reflected in attendance and any payroll inputs.
5. Is overtime pre-approval the same as overtime payment approval?
No. Pre-approval records permission and the expected duration. Payroll review determines the treatment of verified time worked under the applicable rules. Planned hours and payable hours may differ.
6. Does eHajira support overtime calculation?
Selected eHajira plans describe configurable overtime calculation rules. Verify the calculation settings and resulting reports in your proposed plan, especially for rotating shifts, overnight work, and breaks.
7. Can the same approval route be used for leave and overtime?
An organization may assign some of the same reviewers, but the evidence they need differs. Do not assume that eHajira’s documented multi-level leave routing also applies to overtime. Test each workflow separately.
8. What happens when a manager is absent?
Use an authorized backup with a clear scope and end date. Confirm what happens to requests already waiting for the original manager and whether the substitute can act on them through the verified workflow.
9. Can temporary approval authority be limited to one branch?
The company’s delegation can define that scope. Verify that your software permissions can enforce the intended branch restriction. If they cannot, use the approved alternate route and document the actual decision maker.
10. Should managers approve their own requests?
Route their requests to another authorized reviewer, such as the next-level manager or designated HR authority. Define this route in advance so it also works when a manager is acting as someone else’s delegate.
11. How should urgent leave be recorded?
Let the employee notify the appropriate contact promptly through the organization’s agreed channel. Record the formal request or authorized entry afterward so the dates, category, decision, and attendance treatment can be reconciled.
12. What if a request includes a rest day?
Compare the requested dates with the employee’s roster and apply the relevant rules for that leave type. Do not assume that the number of calendar days and the number of chargeable leave days are always the same.
13. How should HR handle a leave cancellation?
Record the cancellation through the authorized process. Check whether the employee worked on the affected dates, whether the balance needs adjustment, and whether any attendance or payroll record already uses the original approval.
14. What if an employee works more overtime than planned?
Ask the supervisor to confirm the additional work and review the time evidence. Apply the relevant working-time and pay rules, then record why the verified outcome differs from the original authorization.
15. Can a biometric checkout prove how much overtime was worked?
A checkout helps establish when the employee left or recorded a punch. Compare it with the schedule and other work evidence to determine whether the elapsed time reflects work, a break, or another circumstance.
16. How should an overnight shift be handled?
Verify how the schedule and attendance records link the start and end of the shift across dates. Use a representative example to check that the hours are attributed correctly before applying the setting to payroll.
17. Does Bangladesh law address overtime allowance?
Yes. Section 108 of the Bangladesh Labour Act addresses overtime allowance for covered workers and includes a separate provision concerning piece-rate workers. Review the applicable legal text and worker classification before setting a calculation rule.
18. What should HR do if a request is still pending at payroll cutoff?
Identify the missing decision or evidence, assign a reviewer, and record the next action. Handle any confirmed pay obligation separately from the delay in obtaining internal authorization.
19. How can HR test a multi-branch workflow before launch?
Run a routine leave request, a request during a manager’s absence, and an overtime case where actual work differs from the plan. Verify permissions, final status, and how the outcome appears in the records payroll will use.
20. What records should be retained for an approval decision?
Keep enough information to explain who requested the change, who acted, what evidence was checked, and how the final outcome was treated. Restrict sensitive details to people who need them to carry out their responsibilities.
Begin with one branch or team and run the process through a complete pay cycle. Give the line manager responsibility for operational facts, HR responsibility for policy and exceptions, and payroll a verified record it can process. Use eHajira’s documented features where they fit, and test the handover between stages before expanding the workflow. Employees should be able to see where a request stands, and reviewers should be able to explain how the final decision was reached.
EAS Security
EAS Gate
Security Tag
EAS Accessories
Gadgets
Convex Mirror
Road Barrier
Burglar Alarm
Calling System