Ziarat operations software for pilgrimage operators
A season of revenue arrives in days, across two visa regimes. Travix Ziarat builds the package, holds the roster, tracks Iraq and Iran visas separately, and posts the sale to your accounts — one line per component, each with its own vendor and margin.
Accounting ends at the invoice. Operations start there.
Travix Ziarat is the operations layer for Najaf, Karbala, Kadhimiya and Samarra — and for the Mashhad or Qom leg you bolt onto them. It builds the package an agent actually quotes from, holds the pilgrims who are really travelling, and follows each one through each country’s visa process. It posts nothing to your general ledger itself: it raises the invoice Travix Finance posts, so one set of numbers stays true.
The money
Travix Finance
Invoices and receipts
Customer and vendor ledgers
Double-entry GL, P&L
Refunds, commission, tax
The movement
Travix Ziarat
Packages and per-component pricing
Iraq, Iran and Syria visa tracking
Pilgrim rosters and passports
Per-component vendors and margin
What Travix Ziarat does
Four capabilities, all shipping today.
Packages that price themselves
A package is a list of components — nights, meals, transfers, staff, visa fees — each with a rate, a quantity and a vendor. Quote for twelve pilgrims and Travix expands the whole thing line by line. The price is the sum of its parts, so nothing is apportioned and no rounding drift is possible.
Per-pilgrim build-up of rate x quantity, expanded at quote time
Sell rate and cost rate on the same line, so margin is visible before you sell
A currency per package, with the exchange rate captured on the sale
Change a rate in your masters and every future quote uses it
Re-quote at a different pax count without rebuilding the package
Two visa regimes, tracked separately
One row per pilgrim per country, not one visa field per pilgrim. Iraq and Iran progress independently, a Damascus leg is a third row rather than a migration, and no pilgrim is ever "half approved".
Iraq, Iran and Syria tracked as separate rows on the same pilgrim
Visa company, number, applied, issue and expiry dates per country
Pending, approved, rejected, expired, cancelled — or not required, for exempt nationalities
Rows derived from the package’s own destinations, so nobody chases a visa the trip does not need
Documents attached to the visa row they belong to
A named roster on every booking
The invoice says twelve pilgrims. The roster says which twelve. Each is a real pilgrim record keyed on passport, shared with the rest of Travix, and carrying every trip they have taken with you.
Pilgrims attached to the invoice, not retyped onto it
Passport-keyed records reused across trips and across products
Passports and documents held against the pilgrim, not the booking
A status per pilgrim per trip
One pilgrim cannot be added to the same booking twice
It posts to your accounts
Selling a package raises a travel invoice in Travix Finance. Every component line carries its own vendor payable, its own revenue account and its own cost account — so Ziarat margin is separable in the P&L instead of being one lump labelled "packages".
One invoice line per component, each with its own vendor
Revenue and cost accounts set per component type in your masters
Resolved at sell time, so a masters change reaches every future sale
Customer, vendor and general ledgers all posted by the finance module
Refunds, receipts and aging work exactly as they do for any other invoice
