The HOA software jurisdiction problem

Every major HOA and property-management platform was built for the same customer: a US rental property manager. The vocabulary gives it away — tenants, leases, rent rolls. Then it gets sold to a condo community in Baja California, where nobody is a tenant, nobody signs a lease, and the money is cuotas, not rent.

The translation layer is where the money leaks.

What actually differs

The money has different names and different rules. Cuotas (assessments), mora (late fees), estado de cuenta (account statements) — these aren't translations of "rent." They're a different financial relationship: owners paying into a common regime, with delinquency procedures and assembly approvals that vary by state and country. Software that models them as "rent with a different label" gets the workflow wrong: who can be charged, how late fees accrue, what a statement must show.

The governance is different. Assemblies (asambleas), quorums, voting procedures, administrator powers — these follow local condo law, not US property-management practice. A voting module built for "board elections, Robert's Rules" misfires on a Mexican régimen de condominio assembly.

The notices are different. What must be communicated, to whom, how far in advance, and with what proof of delivery — these are legal requirements, not UX choices. Generic communication tools don't know them.

The spreadsheet era

So most Latin American HOAs run on the same stack: a spreadsheet for dues, a WhatsApp group for everything else, and one long-suffering treasurer who holds it all in their head. It works until it doesn't — until the treasurer moves, or the delinquency list passes what anyone can track, or two neighbors disagree about what was paid and there's no record to check.

The cost isn't the software. It's the absence of records: uncollected dues nobody chased, maintenance nobody scheduled, disputes with no paper trail.

What jurisdiction-aware looks like

Not a translation — a pack. A jurisdiction pack encodes one place's practice:

• The dues cycle: how assessments are set, billed, and aged
• Late-fee rules as they're actually applied locally
• Statement formats owners recognize (estado de cuenta, not "rent ledger")
• Assembly and voting procedures per local law
• Notice requirements with delivery proof

Baja California first, because that's where the work started — then the pattern repeats per state and country. Each pack is research, not localization: someone has to read the local practice and encode it.

The honest trade-offs

Jurisdiction depth is the wedge and the cost. A generic platform covers fifty markets shallowly; a jurisdiction-aware one covers five deeply. For a community in one of those five, the choice is obvious. For a community elsewhere, the generic platform — or the spreadsheet — is still the honest answer.

And software doesn't collect dues. The best system in the world still needs a treasurer willing to send the second notice. What the software buys is leverage for that person: records instead of memory, workflow instead of WhatsApp archaeology, statements that print clean instead of screenshots of spreadsheets.

The question to ask any HOA vendor

Not "do you support Spanish?" — ask "show me an estado de cuenta for a Mexican condo regime, and show me how mora accrues." The answer tells you whether you're looking at a jurisdiction or a translation.