Seat by seat, rupee by rupee — a hostel that runs itself.
Pakistani hostels sell seats, not rooms; deduct mess for the days a student went home; and take money in cash, JazzCash, Easypaisa and bank transfer with a screenshot on WhatsApp. Mizenzo Hostel was built around exactly that, not adapted from a hotel system.
Built around the disputes, not around the brochure.
Every feature here exists because it is what actually goes wrong in a hostel office.
Seats, not rooms
A three-seater room 201 becomes 201-A, 201-B and 201-C automatically — three residents on three rents with three joining dates. Add rooms 401 to 406 in one action; re-running skips the numbers that already exist instead of failing.
Mess that matches reality
Fixed monthly or per day consumed. A student who went home for ten days has those days deducted automatically and shown as an itemised line — which removes the single most common monthly argument in a hostel.
Invoices and receipts that print
An A4 invoice on your letterhead with the bill-to, the guardian, itemised charges, the previous unpaid balance, the total payable, payments already received and how to pay. A half-sheet receipt for every payment. Save as PDF and send it to the guardian on WhatsApp.
Payments verified, not assumed
Cash, JazzCash, Easypaisa, bank transfer or cheque with a reference number. A digital transfer can be held as pending — a WhatsApp screenshot does not reduce anybody's balance until a senior user reviews it and confirms.
Accounting that is actually correct
Security deposits are a liability until forfeited, never income. Arrears are never double-counted — an invoice bills only its own period. An unallocated payment is an advance until it is applied. Payments settle the oldest invoice first.
Two levels of profit and loss
Per hostel: room rent, mess, AC and admission income against building rent, salaries, raashan, meat, vegetables, LESCO, Sui Gas, generator diesel and repairs. On a cash basis or a billed basis — and comparing the two shows exactly how far collections lag billing.
Leads inbox, with or without a public page
Walk-ins, phone calls and WhatsApp enquiries typed in by staff land in the same inbox as requests from your public hostel page, where a student verifies their mobile with an OTP. A public request never reserves a seat, so ten casual enquiries can never zero out real availability.
Guided setup
Hostel, then room types and the price list, then rooms, then the mess plan, then your first resident — in the order it has to happen, with a progress tracker. Day to day you can do all of it from the seats and residents screens instead.
Proration, AC months, and a checkout that settles properly.
Most of a hostel manager's month is spent on the awkward cases. These are handled by the system rather than by an argument at the counter.
- Proration on the joining date, the checkout date and a mid-month room change.
- The AC surcharge applies April to September only, automatically.
- Checkout settles the deposit properly: held, minus forfeited, minus damages, minus arrears. Whatever the deposit covers is applied as a credit, so checkout never leaves a phantom receivable sitting in the P&L.
- Guardian details are mandatory, because the guardian is the real contract party.
- Amounts are grouped the South-Asian way — Rs 12,34,567 — and dates are read in Asia/Karachi, so a report for "1 July" does not quietly drop the first five hours of the day.
Verifying a payment is never a blind click.
Confirming a held payment is effectively irreversible, so the screen shows everything before anything is committed.
- Why it was held — the note the staff member left.
- Who it is for — the student, their seat, room, guardian and current dues.
- What was claimed — amount, method, transaction number, who entered it and the attached screenshot.
- Exactly which invoices it will settle — oldest due date first, each marked cleared or partial, with the balance that results.
- A missing transaction number on a digital transfer is flagged in red. From there it is Verify, or Reject with a reason.
What you get on day one.
One hostel or a chain of them, on the same login.
1Rooms & seats
- Room types — seats per room, rent per seat, deposit, admission fee, AC charge
- Add rooms in a range; seats generated automatically
- Live seat map with occupancy
- Move a resident to another seat
2Residents
- Admission with mandatory guardian details
- Ledger per resident
- Notice period and checkout
- Full settlement on checkout
3Billing
- Monthly invoice generation
- Mess plan — fixed or per day consumed, with mess-off deduction
- Late fees and rent-due days
- Discounts, recorded as a reduction in income
4Payments
- Cash, JazzCash, Easypaisa, bank transfer, cheque
- Hold digital transfers for senior verification
- Oldest-invoice-first settlement
- Printed receipt for every payment
5Money & reporting
- Hostel P&L on a cash or billed basis
- Organisation P&L across a chain
- Expenses with an approval step
- Defaulters list and dashboard
6Leads & public page
- Leads inbox for walk-ins, calls and WhatsApp
- Optional public hostel page
- Mobile verified by OTP
- Offer a specific seat; the hold expires by itself
The technical detail
| Architecture | Node.js + Express + Prisma on PostgreSQL, with a Next.js web application |
| Platform | Web — works on a laptop, a desktop or a phone browser |
| Currency | PKR only, with lakh / crore grouping |
| Payments | Recorded manually — cash, JazzCash, Easypaisa, IBFT, cheque. No gateway needed |
| Roles | Owner, manager, warden, accountant — and your own, with per-action permissions |
| Branches | Multiple hostels on one account, with consolidated reporting |
| Printing | A4 invoices and half-sheet receipts, both print-ready and PDF-ready |
| Timezone | Asia/Karachi, applied consistently in every report |
There is deliberately no online payment gateway. Pakistani hostels move money by hand, and a system that pretends otherwise simply gets ignored.
Mizenzo Hostel — common questions
Yes. Each hostel is a branch with its own rooms, staff and P&L, and there is an organisation-level P&L across all of them. Staff can be limited to one branch.
You record the days a student was away. On the next invoice those days come off automatically, shown as their own line with the count and the rate, so the student and the guardian can both see exactly how the figure was reached.
Your staff enter it as an Easypaisa or bank payment with the transaction number and attach the screenshot, and it sits as pending. A senior user opens a review screen showing the student, the claim, and precisely which invoices the money would settle — then verifies or rejects it with a reason. Until then, nobody's balance has changed.
No, it is optional. With it off, everything still works — walk-ins and phone enquiries are typed in by staff and land in the same leads inbox. With it on, students find the hostel, verify their mobile with an OTP and send a request, which never blocks a real seat.
Hostel ka hisaab ab register par nahin.
Tell us how many beds and how many branches you run, and we will show you the real system with hostel data — seats, mess, invoices and the P&L — on your own screen.