Human resources
Staff records, payroll, attendance, leave, recruitment, contracts, clearance, and appraisal — in one HR file.
Sign in
Hushmand ERP is the operations system for people, purchasing, projects, finance, and the office — one dataset, no mining module on this page.
See the modulesEvery module below is in production in this codebase. Mining is omitted here on purpose.
Staff records, payroll, attendance, leave, recruitment, contracts, clearance, and appraisal — in one HR file.
Purchase requests, RFQ, purchase orders, GRN, payment requests, advances, fuel, and taxi — one approval chain.
Projects, daily activity, timesheets, and task boards so work is planned and recorded in the same system.
Stock in and out, catalogue items, and non-stock items tracked against the same organisation data.
Visitors, incoming and outgoing correspondence, and staff in/out at the gate.
Visas, permits, vehicle permits, weapons records, and membership cards.
Fixed assets, vehicles, furniture, equipment, maktoob, and marketing records.
Finance ledger and operational reports on the same dataset as procurement and payroll.
Service-business contracts stored and printed with the rest of operations — not a side spreadsheet.
Users, roles, permissions, system notifications, and backups that gate every other module.
Domain reports across HR, procurement, stock, reception, and finance — one login, same numbers.
The staff home after login: leave, movement, tasks, and the shortcuts people actually use each day.
These are capabilities the product already has — not a roadmap.
HR, procurement, projects, finance, and the rest share the same people, vendors, and permissions. No second password for a second tool.
Multi-step process verification is in the product — not forwarded email. Each step is a named person and a recorded decision.
After login, staff land on their own portal: leave, movement, tasks. The heavy admin screens stay with the people who run them.
Forms that use the Persian calendar convert correctly before they hit MySQL. The working UI has a Dari locale staff can actually read.
Attachments and process alerts are common infrastructure. A purchase request and a staff file do not invent their own upload path.
Request, quotation, order, goods received, then payment request — the chain is in one system, with the same URN-style identifiers.
Pay runs from the same staff records as leave and attendance, including device attendance where it is in use.
Gates and permissions decide who sees HR, who signs a PO, and who opens a report. Administration is not a decorative settings page.