Skip to content
Adjacent — we have the machinery

Payroll that reaches the ledger by itself.

Most payroll stops at a number on a payslip. The work nobody sees is everything after it: the advance recovered over three months, the leave encashment, the loan instalment, and the journal entry that has to balance at month end.

We built a full HR and payroll module and it is sold today as a paid add-on — employees, departments and designations, daily attendance with regularisation, leave entitlements, salary structures and components, increments, advances, loans and repayments, and disbursement that posts to the general ledger. It is homegrown, not a wrapper around anyone else’s HR product. What it is not is a standalone HR platform: it runs inside our ERP, so buying it as a separate system would be a build, not a licence.

Sound familiar?

A week in this business.

If three or more of these are true, the problem is usually not the tools. It is that none of them talk to each other.

  • Attendance is a register, and payroll day starts by typing it up
  • Salary is calculated in a spreadsheet only one person fully understands
  • Advances and loans are tracked on a separate sheet and sometimes missed
  • The payroll total and the accounts never quite agree without manual adjustment
  • Nobody can answer what an employee actually costs, all-in
  • Leave balances are disputed because two records disagree

What we’d build

The parts that matter here.

Employee records with job, bank, documents and full lifecycle to exit
Departments, designations, work locations, employment types and statuses
Daily attendance with clock in/out, and regularisation with a reason and an approver
Leave types, policy entitlements and per-employee balances, including encashment
Salary structures and components, with per-designation templates
Payroll periods with an explicit state, so a month can be closed and disbursed
Advances and loans with scheduled recovery against future payroll
Increments, reserve ledger, and salary trails per employee
Disbursement batches that post to the general ledger rather than ending at a payslip

Which route

Configure something proven, or build it?

Most vendors answer this the way that suits them. Here is how it usually goes in this sector — and we will tell you plainly which side you are on.

Open-source ERP

Usually faster and cheaper

Often the sensible answer if you want HR standalone. Odoo brings recruitment, appraisals and self-service that our module deliberately does not have, and we implement and operate it.

How we do this

Custom build

When the standard parts run out

Right when payroll has to be correct against your own accounts — our module was built accounting-first, which is the part that usually breaks. Also right when local rules do not fit a package.

How we do this

Questions

Does it calculate income tax and statutory deductions?
No. There is no built-in tax engine or statutory social-insurance calculation — components are defined and applied, but the rules are yours to specify. For Pakistan or Gulf payroll that is scoped work, and we would rather say so than let you discover it in month two.
Can staff see their own payslips?
There is a self-service surface, but it is narrow compared with a dedicated HR platform. If employee self-service is the main thing you are buying, say so early — it changes the Odoo-versus-custom answer.
Is biometric attendance supported?
Not as a built integration. Attendance records carry a source field, so a device feed is a connector we would build rather than something that works on day one.

Other sectors

Tell us what isn’t working.

Thirty minutes, no deck. We’ll tell you what we would do — and say so plainly if software isn’t the answer.

Book a call

Talk to us

Book a call