Jurisdiction packs: comp rules that adapt to each regulator

A large operator rarely lives under one rulebook. Each property answers to its own regulator, with its own comp and reporting requirements — and one global ruleset serves none of them well.

The problem: one enterprise, many regulators

An integrated-resort group spans jurisdictions. Each has its own settlement: comp rules differ, currency-transaction reporting differs, responsible-gaming obligations differ. A property in one place must file when a transaction crosses a local reporting line; a property elsewhere follows a different line entirely, and layers on local exclusion and duty-of-care rules of its own.

A single global ruleset cannot honour all of that at once. Set it to the strictest jurisdiction and every other property over-complies — friction where none is required, staff working around controls that do not apply to them. Set it looser and the strict properties under-comply — the more serious failure, and the one a regulator finds. The instinctive fix is a different system per venue, and that is worse: many deployments, many rulebooks to keep current, no shared view of a patron who plays across them.

Jurisdiction packs: the local rules, applied in place

A jurisdiction pack is a per-jurisdiction rule pack that applies the local requirements at a property. The pack carries the rules in force where that property sits — its comp rules, its reporting thresholds, its local responsible-gaming checks — and the property runs under it.

Take reporting thresholds. A Singapore property runs under a pack whose Title-31-style currency-transaction-report threshold drives when a transaction crosses a reporting line; a property in another jurisdiction runs under a pack with its own line. Neither property is asked to know the other's rules. Each behaves correctly for the regulator it actually answers to, because the requirements that govern it are the ones applied to it. The thresholds here are illustrative — the point is that the pack, not the operator's memory, holds them.

One platform, many rulebooks

Jurisdiction packs do not stand alone. AEGIS resolves each comp against the delegation-of-authority (DOA) matrix — the map of who may authorise which comp type, up to which limit, and what happens on exceed — and against the property's jurisdiction pack. Authority and locality apply together: the matrix decides whether the requester holds the limit; the pack applies the local rules that also bear on the decision. Exclusion and responsible-gaming checks run before any incentive reaches a patron, under the pack in force.

All of it runs on one multitenant, cross-property platform. There is no separate install per venue and no separate rulebook to drift out of sync. A patron's worth and tier are tenant-wide, so a player who moves between properties is understood as one person, while each decision is still judged under the local pack. Adding a property — or standing up a new jurisdiction — is a configuration change, not another deployment to run and reconcile.

Reporting reflects the jurisdiction

Because every decision is sealed to an immutable audit trail that carries the rules in force — the matrix version and the jurisdiction pack applied — the record knows which regulator's requirements governed it. Reports built from that ledger reflect the local rules that actually applied, property by property. When a regulator uses the self-serve portal to query the immutable ledger, the decisions returned are the ones judged under that jurisdiction's pack, and a single button proves the record is unaltered. There is no reconciliation step to translate a global record into local terms after the fact; the local terms were sealed in at the moment of decision.

What this changes

The operator stops choosing between over- and under-compliance, and stops running a system per venue. Written policy — the group's, and each regulator's — becomes a rule pack applied automatically, at machine speed. AEGIS answers an authority check in under roughly five milliseconds, is MCP-native, and runs containerised active-active, so applying the right rulebook in each place costs nothing in latency or availability. For the reporting side of this discipline, see regulatory reporting for casino comps; for the authority side, building a comp approval matrix.