Employee Salary Advances and Loans: Running Them Without Chaos
Salary advances are standard practice across South Asia and badly supported by most HR software. How to structure the policy, the approvals and the automatic recovery.
Salary advances are normal here. An employee has an unexpected expense, asks for part of next month's pay early or for a small loan against salary, and it is recovered over the following months. Almost every company in Bangladesh does this. Almost no imported HR software supports it properly. So it ends up in a side spreadsheet, and that is where it goes wrong. The three failure modes Over-recovery. Deductions continue after the balance is cleared, because stopping was somebody's job to remember. This is the worst one — you have taken money you were not owed, from someone who was already short. Under-recovery. An installment is skipped during a busy month and never caught up. The balance ages and eventually gets written off informally. No record. The person who approved it left, and there is no documentation of the amount, the terms or the approval. Write the policy down Six decisions, made once, remove most of the ambiguity: Eligibility — minimum service period, and whether probationary staff qualify. Maximum amount, expressed as a multiple of monthly basic rather than a fixed figure that goes stale. Maximum recovery period, and therefore the minimum installment. Whether interest applies. Most companies here run these interest-free as a benefit; either way, state it. Approval authority by amount — a manager up to one threshold, finance above it. What happens on resignation. Almost always: the outstanding balance is settled from the final payment. This must be in the written agreement, not assumed. The most damaging advance is not the one that was too large. It is the one that kept being deducted after it was repaid. What the process should look like Four steps, each leaving a record: The employee requests, with amount and reason, from their own portal. The approver sees the request together with existing outstanding balances — approving a second advance without seeing the first is a common and avoidable mistake. On approval the system generates the installment schedule automatically from amount and period. Each payroll run applies the installment and reduces the balance, and stops on its own when the balance reaches zero. That last point is the whole reason to automate this. The stop condition is what humans forget. Reporting finance will ask for Total outstanding advances across the company, as a single current figure. Ageing — how long each balance has been outstanding. Recovery expected in the coming month, for cash-flow planning. Balances attached to anyone currently serving notice, which is where write-off risk concentrates. Where expense claims fit Expense reimbursements are the mirror image — money owed to the employee rather than by them — and they belong in the same flow for the same reason: an approved claim should reach the next payslip without anyone retyping it. Handled separately, reimbursements are chronically late, which does more damage to goodwill than the amounts involved would suggest. In Project Help Hr&Payroll both run through the payroll engine directly. Advances deduct in installments until cleared, approved expenses are added to the next run, and employees can see every balance themselves. Stop tracking advances in a side spreadsheet.
Home · Features · Pricing · Blog · Contact