People
Employee master, departments, designations, roles and a self-service profile every employee maintains themselves. One record, referenced by everything else.
On-premise
Your server. Your database. No per-user cloud bill.
The ERP your company
can actually change.
ZakERP runs people, money and stock in one system — attendance, leave, payroll, general ledger, inventory, approvals and reports. The difference is what happens when you need something new: a screen or a report takes an afternoon, not a change request and a quarter.
Runs on your own Tomcat + SQL Server
Works on a slow connection
Your data never leaves the building
Punch recorded · 08:52
Leave approved by GM
Today at a glanceLive
Present
168
On time 141
On leave
11
Approved
Pending
6
Your approval
Attendance · last 7 days
Casual leave · 2 daysAwaiting GM
Purchase order PO-00418Approved
Advance request · Tk 12,000Awaiting MD
88
Business screens shipped
and ready to use
and ready to use
77
Saved searches and
live reports built in
live reports built in
29
Charts, KPI tiles and
dashboards out of the box
dashboards out of the box
0
Per-user licence fees
charged by the month
charged by the month
The real cost
The spreadsheets are not free.
The spreadsheets are not free.
They are just unbilled.
Most companies do not lose money on software. They lose it on the hours spent rebuilding the same numbers every month, and on the decisions taken from figures that were already three days old.
Before
- Attendance downloaded from the device, pasted into Excel, corrected by hand.
- Leave balance argued about, because three people keep three different registers.
- Payroll rebuilt from scratch every month — and one wrong formula reaches every payslip.
- Approvals travel on paper and WhatsApp; nobody can prove who approved what.
- The MD asks a simple question and waits two days for an answer.
- One person understands the master file. When they leave, the knowledge leaves.
After
- Punches arrive from the device and the phone into one attendance record, automatically.
- Leave balance is calculated from the rules, not typed. There is one number, and it is right.
- Payroll reads attendance, leave, allowances and deductions — and shows its working.
- Every approval is a signed step with a name, a time and a comment behind it.
- The MD opens a dashboard and sees today, not last week.
- The rules live in the system, in plain readable text, where anyone can review them.
One system
Everything the company runs on,
Everything the company runs on,
in a single database
Not eight tools that email each other. One login, one employee record, one ledger — so a punch, a leave day, a payslip and a journal entry are the same story told once.
Attendance
Biometric device and mobile punch in one timeline — with face match, geofencing and an optional remote-punch permission for field staff. Late, early-leave and overtime are judged against the employee's own shift.
Leave
Entitlement, accrual, carry-forward and encashment as rules rather than habits. Employees apply from the calendar, approvers sign in order, and the balance updates itself.
Payroll & allowances
Salary, daily allowance, meal contribution and deductions calculated from the attendance that already exists — with the working shown line by line, not hidden in a formula.
Finance
Chart of accounts, journals, receivables, payables, ageing, cash book and trial balance. Every posting enters through one controlled door, so the ledger and the sub-ledgers can never quietly disagree.
Supply chain
Items, warehouses, suppliers, purchase orders, receipts and issues on one signed stock ledger — with a reconciliation view that proves stock value against the accounts.
Approvals
Multi-level approval chains defined as data, not code. Supervisor, GM, MD — change the route in a table, and every future document follows the new one.
Reports & dashboards
Saved searches with filters, date ranges, sorting, export and scheduled email; charts and KPI tiles; and print-ready PDF forms for the documents that still need a signature.
Chat, To-Do & documents
Internal messaging with voice notes, a shared task board, an ID-card studio and a document registry that knows where every file in the system actually lives.
Why ZakERP is different
A new report,
A new report,
before lunch.
In most ERPs, "add a column" is a project. In ZakERP a screen, a report, a chart or an approval flow is a short, readable text file. Save it, refresh the browser, and it is live — no compiling, no restart, nobody logged out.
- Readable by people, not just programmers. A manager can look at the file and see exactly which columns and rules the report uses.
- Nine kinds of definition: screens, searches, charts, dashboards, approval flows, calendars, dialogs, home pages and ID cards.
- Point-and-click too. The built-in Customisation Studio writes these files for you, and exports your changes as a bundle you can move between servers.
- You are never held hostage. The customisation lives in your installation, in plain text, under your control.
// A complete report. This is the whole file. search lateArrivals table zAttendance select "zactive = '1'" order xdate desc rows 31 search paginate export columns xstaff, xdate, xintime, xouttime, xstatus headers "Staff","Date","In","Out","Status" daterange xdate caption "Period" default month end daterange filter xstatus caption "Status" pick "Late,Late & Early Leave" end filter end search
Save the file · refresh the browser · the report is in the menu, with a period bar, a status filter, sortable columns, paging and export.
Install on your server
Tomcat and SQL Server on a machine you own. One afternoon, including the attendance device bridge.
Load your people and rules
Employees, departments, shifts, leave types, approval chains, chart of accounts. Imported, not retyped.
Go live one module at a time
Attendance and leave first, because that is where the daily pain is. Payroll and finance follow once people trust the numbers.
Change it yourself, forever
New report, extra field, different approval route — from the Customisation Studio, without waiting for anybody.
Getting started
Live in weeks,
Live in weeks,
not financial years
A large cloud ERP wants you to change how your company works. ZakERP starts from how your company already works, and puts it into a system your own people can keep adjusting.
Because it installs onto ordinary hardware you already own, there is no procurement cycle, no data-residency argument and no monthly bill that grows with headcount.
Talk through your rollout
Honest comparison
Where ZakERP wins —
Where ZakERP wins —
and where it does not
You should choose the right tool, not the loudest one. Here is the straight version.
| Spreadsheets | Global cloud ERP | ZakERP | |
|---|---|---|---|
| Where your data lives | Scattered files | Someone else's data centre | Your own server |
| Cost as headcount grows | Hidden, in hours | Rises every month | Flat |
| Time to add a report | Hours, every month | A change request | An afternoon |
| Works on a weak internet line | Yes | Poorly | Yes — it is on your LAN |
| Audit trail of approvals | None | Strong | Strong |
| Local attendance devices, allowances, meal rules | Manual | Needs custom work | Built in |
| Multi-country consolidation, 20 legal entities | No | Its strength | Not our territory |
| Vendor ecosystem of thousands of add-ons | No | Yes | No — we build what you need |
If you are a multinational consolidating twenty legal entities, buy the global suite. If you are one company that wants its own rules followed exactly, that is what ZakERP is for.
Already using ZakERP?
The manual is open
The manual is open
to everyone
Every task an employee does — punching in, applying for leave, checking a balance, running a report, approving a request — written as a short, illustrated walkthrough. No login, no PDF download, printable one chapter at a time.
Straight answers
The questions people
The questions people
actually ask
Do we need our own IT team to run it?
No. It runs as an ordinary web application on one Windows server. Day-to-day, somebody who can restart a service and take a database backup is enough — and the backup can be scheduled. Everything else is done from inside the browser.
What happens to our existing attendance device?
It keeps working. ZakERP reads the device's own database directly, so the punches you already collect flow in without anyone exporting a file. Mobile punches from phones land in the same timeline.
Can we move our old data in?
Yes, and it is normal to. Employees, leave history, suppliers and opening balances are imported from your existing files. Import routines are part of the system, not a one-time favour.
What if we need something the system does not do?
That is the point of the customisation layer. Most requests — a new report, an extra field, a different approval route, another dashboard — are configuration, done in hours, by your own staff after training. Genuinely new modules are quoted as work.
Is our data safe on our own server?
Access is controlled by role, every screen and report is permission-gated, sessions are single-login, and administrative actions are written to an audit log. The database is yours to back up, encrypt and keep inside the building.
How is it licensed?
A licence key installed on your server, not a per-user subscription that grows every time you hire. Support and enhancements are agreed separately, so you always know what next year costs.
No slide deck
See it running on
See it running on
your own numbers
Thirty minutes, screen shared, using a sample of your real attendance or payroll data. If it does not fit your company, we will say so.
Prefer to look around first? The full user manual is public — read it before you talk to anybody.