Here's a specific, almost invisible failure mode: you run a PG on software that also does hotel bookings, you open the occupancy or revenue report, and it shows nothing. Not wrong numbers — zero. The report isn't broken. It's just not looking at the right table.

Quick answer (for the impatient)

• Generic hotel reports query hotel reservations — and a PG tenancy is never a reservation, so those reports are structurally blind to a PG property.
• PG-specific analytics tracks occupancy, revenue, turnover and electricity trends — built to actually read PG data.
• Revenue is broken into billed vs. collected vs. outstanding — not one lump number.

The zero-report problem

A hotel's occupancy report counts reservations. A PG doesn't create reservations — it creates tenancies, bills, and payments, on entirely different tables. Software that was built reservation-first and had PG bolted on later often keeps the old reports pointed at the old tables, which means a PG property technically exists in the system but is invisible to every report that was written before PG was.

It's not a bug in the sense of broken code — the report does exactly what it was written to do. It's just querying the wrong thing for a PG, which makes "why does my report show zero occupancy when I have thirty tenants" a genuinely confusing moment for an owner who has no reason to know the underlying data model.

What PG analytics actually shows

A PG-specific report reads from the tables a PG actually writes to: occupancy trend across months (not just a current snapshot), revenue trend split into what was billed, what was actually collected, and what's still outstanding, tenant turnover (check-ins and check-outs per month), an electricity usage trend, and an occupancy breakdown by sharing type — single, double, triple, dorm — so you can see which room configuration is actually filling up and which isn't.

Billed-versus-collected-versus-outstanding matters more than it sounds like it should: a PG with high occupancy can still be bleeding cash if collection lags billing, and a single combined "revenue" number hides that completely.

Where AXOIX is honest about its limits

• This is PG-specific, not a general BI replacement. It closes the specific gap where generic hotel reports miss PG activity entirely — it isn't a claim about cross-vertical analytics depth beyond that.

FAQ

Why does my hotel occupancy report show zero for my PG?
Because that report queries hotel reservations, and a PG tenancy isn't a reservation — it's a structurally different record the report was never built to read.

Does PG analytics separate billed from collected revenue?
Yes — billed, collected, and outstanding are shown separately, not combined into one number.

Can I see which room type (single/double/dorm) is filling up?
Yes — occupancy breaks down by sharing type.

The bottom line

A report that shows zero isn't reassuring — it's just wrong for what you're actually running. A PG needs numbers pulled from what a PG actually does: tenancies, bills, and payments, not reservations it never creates. That's the difference between a report that happens to exist and one that actually tells you how the property is doing.

See the full PG system overview, the honest limits of PG accounting, or pricing.

See real numbers for your PG, not a zero. Start free →