Almost nobody pays for an Umrah package in one transfer. The reality of this business is a deposit at signup, monthly installments, and a final balance due weeks before departure — collected in a mix of bank transfers, card payments and cash handed over after Friday prayers.
That payment pattern is a feature, not a problem: it's how families afford the trip, and it's why communities book with a trusted local agency instead of a faceless website. The problem is tracking it.
Where agencies lose track
The typical system is a "paid?" column in Excel, plus memory:
- A cash payment taken at the mosque gets written on a paper slip that never reaches the spreadsheet.
- A bank transfer arrives with a reference like "UMRA - AHMED" — which of the three Ahmeds?
- The husband pays for four family members in one transfer; the spreadsheet has four rows and one confused amount.
- Two people update two copies of the file, and the totals disagree forever after.
The result: three weeks before departure — right when the airline and hotels demand their balances — nobody can say precisely who still owes what. So the owner spends two evenings reconstructing payments from bank statements and memory, and usually eats a shortfall somewhere.
The ledger structure that works
Payment tracking for group travel needs exactly four levels, connected:
- The pilgrim — every payment attaches to a person (amount, date, method, currency).
- The plan — what this pilgrim owes in total (their package tier) and in what stages.
- The balance — owed minus received, always current, per pilgrim.
- The group roll-up — total collected vs total outstanding vs what you owe suppliers, per departure.
If your system can't answer "show me everyone in the Ramadan group with an unpaid balance" in one view, it isn't a system — it's an archive.
Design the installment schedule around your deadlines
Set installment dates so money arrives before you must pay it out: deposit ≥ your flight deposits; mid installments ≥ hotel prepayments; final balance comfortably before the airline's name deadline (which is also your last realistic chance to replace a cancellation — see pricing buffers).
Chasing balances without awkwardness
In a community business, payment reminders feel socially risky — you're texting people you'll pray next to. What works:
- Remind against the agreed schedule, not ad hoc. "As agreed, the second installment of €400 is due this Friday" reads as organization, not distrust.
- Remind everyone the same way. A standard reminder to all pilgrims with open balances removes the personal edge entirely.
- Give a receipt for every payment, instantly — especially cash. Receipts protect both sides and quietly signal that this agency keeps proper books.
Know your real position, not your revenue
Collected money isn't profit. The number that matters per group is: collected − supplier costs − what's still owed to you. Agencies that only watch the incoming total routinely discover after the trip that a "full" group lost money through uncollected balances and forgotten expenses.
How Ziyara handles it
In Ziyara, every payment is recorded against a pilgrim and their group — amount, date, method and currency — and the pilgrim's balance updates automatically. Basic payment tracking is on every plan, including the trial.
The Professional plan adds the full finance layer: installment plans per pilgrim (each stage tracked, due dates visible), invoices as branded PDFs, generated receipts and contracts, outstanding-balance views that show exactly who to remind before departure — and a Financial Dashboard with live profit and loss per group, exportable as a PDF report.
Payments connect to the same profiles as registration and rooming, so "who still owes?" and "who's approved to fly?" are finally the same list. Try it with a real group's numbers on the free trial.