Why Global Tax is the Hardest PMS Problem

Talk to any PMS engineering team about their hardest sub-system, and they'll say the same thing: tax. It looks like a percentage. It is not a percentage.

Five problems disguised as one

• India GST: slab-based, with state-level CGST/SGST splits and reverse-charge edge cases
• EU VAT: TOMS for tour operators, OSS for cross-border, reduced rates per country per service
• US sales tax: county-level, with occupancy taxes layered on top, no central registry
• UK: HMRC-compliant invoicing with mandatory line-item VAT breakdown
• Italy and Mexico: real-time e-invoicing to a government endpoint, with cryptographic signing

Why a rule engine, not a flag

Most PMSes treat tax as a flag on a rate plan. That works in one country. It breaks the moment you operate across borders or sell packages with mixed components — a room is taxed one way, breakfast another, a spa treatment a third.

“Tax is not a rate. It's a function of jurisdiction, service, guest type, and date.

StaySynq's tax engine evaluates each folio line against a rule graph: jurisdiction, service category, guest residency, booking date, applicable exemptions. The result is an invoice that holds up to local audit and a paper trail your finance team will thank you for.