Employee Loans and Salary Deductions Done Right

Almost every Philippine employer ends up in the lending business, whether it planned to or not. Someone asks for an advance before enrolment season, a supervisor vouches for an emergency loan after a typhoon, and SSS and Pag-IBIG loan repayments have to be withheld and remitted no matter what. The money is usually the easy part. What breaks is the record — the deduction missed on one cutoff, the balance nobody can state with confidence, and the year-end reconciliation that takes three days longer than it should.

Why employee loans get messy before they get expensive

Most company loan programmes start informally. Terms are agreed in a conversation, confirmed in an email, and passed to payroll as an instruction to deduct a certain amount every cutoff. Six months later the approver has moved to another department, the email thread is buried, and the only surviving artefact is a column in a spreadsheet.

Spreadsheet tracking fails in a specific way: it stores a balance instead of a schedule. A balance is a number a human has to maintain. If a cutoff is skipped because the employee was on unpaid leave, or because the deduction would have wiped out the net pay, nothing in the file records that the plan has shifted — the balance simply stops matching what payroll actually withheld.

The cost shows up as small, repeated leakage. An overdeducted employee raises a complaint. A resignation is processed and the final pay released before anyone checks for an outstanding loan. And the receivables-from-employees line in the books becomes a figure that cannot be substantiated employee by employee, which is exactly the sort of account an auditor will ask about.

Define loan products before you approve anything

ERPat's Lending module is built around loan products rather than one-off arrangements. A product is defined once — its purpose, its term, how often it is repaid, and who is eligible — and every application is then made against that definition. The work of deciding terms happens before anyone asks, not in the middle of a difficult conversation.

That is a governance decision as much as a systems one. When a salary advance, a calamity loan and a longer-term multi-purpose loan are three named products with three sets of terms, two employees in comparable situations get comparable answers. The supervisor's relationship with the requester stops being a variable in the outcome, which matters more than it sounds when a request is declined.

Defined products also make exposure legible. Instead of one blended figure for money owed by staff, you can see what is outstanding under each product and judge whether a programme is sized for the company's cash position rather than for its goodwill.

Put applications through a pipeline you can audit

Lending carries an underwriting pipeline for applications, so a request is a record from the moment it is filed. It enters as an application, moves through review, and reaches payroll only once it has been approved — with a decision, a date, and a decision-maker attached to it.

Two practical things follow. Declines become defensible, because the file shows what was requested and on what basis it was refused; an undocumented "no" is the one employees remember and dispute. And affordability gets checked at the right moment, before approval, when the applicant's existing statutory and company deductions are already in view. Approving a repayment the employee cannot sustain is not a kindness — it just relocates the problem to the next cutoff.

The pipeline is also what protects the process from turnover. When the approver leaves, the reasoning does not leave with them.

The amortisation schedule is the source of truth

Repayment tracking in Lending works from an amortisation schedule generated when the loan is approved. Every period that will carry a deduction is laid out in advance, with its amount and its date, and the outstanding balance is derived from what has actually been posted against that schedule rather than kept as a number someone edits.

The difference becomes obvious the first time a period is missed. With a schedule, a skipped cutoff produces a visible gap and a clear decision — extend the term, or catch up over the following periods. With a maintained balance, a skipped cutoff produces nothing at all until the totals fail to reconcile months later.

It also lets you answer the only two questions employees ever actually ask: how much do I still owe, and when does this end. Being able to answer both in under a minute, from the record rather than from memory, removes most of the friction a loan programme generates.

Deduction accuracy is a payroll problem, not a lending one

A loan is only as accurate as the payroll run that collects it. ERPat's Compensation module handles earnings, deductions, allowances and payslips as DOLE-compliant payroll fed straight from attendance, so the period's scheduled repayment becomes a deduction line in the same run that computes basic pay, overtime and statutory contributions. Nobody retypes an amount from one system into another, which is where most deduction errors are actually born.

It helps to keep two categories firmly apart on that payslip. Company loans are your receivable. Government loan repayments are money you collect and pass on — Pag-IBIG, for instance, has required employers to remit premium contributions and employee loan repayments through an accredited electronic payment and collection facility under HDMF Circular No. 355, with employers of at least ten employees required to comply by 31 July 2016. Treating a pass-through amount as company income, or netting the two against each other, creates a reconciliation problem that outlives the loan itself.

Plan for the cutoffs where the deduction cannot run

Every loan programme eventually meets a period where the arithmetic does not work: unpaid leave, a short cutoff, a final pay run. Decide the rule in advance and write it into the product — skip and extend the term, or take a partial amount — so the payroll officer is applying policy rather than improvising under deadline.

Affordability deserves the same forethought. An employee earning at or near the statutory minimum has very little room in a deduction stack; in NCR, Wage Order No. NCR-25 set the non-agriculture daily minimum wage at P645.00 effective 17 July 2024, and a repayment term that ignores what is left after mandatory contributions will simply default. Separation is the other predictable case: state in the agreement how an outstanding balance is settled from final pay, before anyone resigns.

Year-end is worth a line too. Thirteenth month pay is due not later than December 24 under Presidential Decree No. 851, and if your policy allows a lump-sum catch-up against it, that belongs in the signed agreement rather than in a December decision.

Doing this right is mostly about keeping one record

Employee lending does not need to be complicated to be sound. It needs a defined product, an approval you can point to, a schedule the balance is derived from, and a payroll run that reads that schedule instead of a note. Get those four in one place and the questions that used to take an afternoon — what does this person still owe, why was this deducted, does the receivables account tie out — become things you can answer while the person is still standing at your desk.