Real-time comp budget tracking for Finance

Comp value is one of the largest discretionary spends on a casino floor. Yet Finance usually sees it last — reconstructed weeks later from systems that were never built to agree.

Every free room, every rebate, every meal and match-play offer is real money leaving the property. Across a busy weekend it adds up fast. But the people accountable for that spend rarely get to watch it happen. By the time the numbers arrive, the decisions are long made and the month is closed.

The problem is not that Finance lacks reports. It is where the numbers come from. This guide sets out a simpler premise: when the authorization ledger is the source of truth, the budget view is the record, not an estimate.

The Finance problem: spend you can only see afterwards

Comp is a discretionary lever, and a large one. It is also spread across the property — issued at cages, hosts' desks, restaurants, the players club, and increasingly by automated systems. Each of those touchpoints records its own version of events, and Finance is left to stitch them together after the fact.

That reconstruction is slow, and it is fragile. Figures are pulled from disparate systems that count things slightly differently, reconciled by hand, and delivered at month-end — long after any of it could have informed a decision. The result is a view that is always backward-looking: accurate, eventually, about spend nobody can now change. When the number is a surprise, it is a surprise about the past.

A live view, by the dimensions that matter

AEGIS gives Finance a live view of every dollar of comp value leaving the property — by venue, by approver, by patron tier, and by comp type — tracked against budget as it happens rather than at month-end.

Those dimensions are the ones Finance actually steers by. Which venue is running hot. Which approver is closest to a limit. How reinvestment breaks down across patron tiers. Where a particular comp type is trending against plan. Because each authorization already carries this context, the breakdown is a property of the record, not a report someone assembles later.

Why the numbers are trustworthy

A live dashboard is only as good as the data under it. What makes this one dependable is that the figures are not gathered from around the floor — they come from the same sealed, immutable decision ledger that governs authority in the first place.

Every authorization AEGIS makes is written to a ledger that is hash-chained and anchored into immudb, which the platform itself cannot alter. Each decision carries the matrix version it was judged against, so the record shows not only what was approved but under which rules. Finance reads the budget view straight off that ledger. There is no second set of books to reconcile, because the authority record and the spend record are the same record. The budget view is the ledger.

Model before you commit

Because the delegation-of-authority matrix is versioned data, not code, Finance is not limited to watching. A proposed change to the matrix — a raised limit here, a new approver there — can be modelled against months of real historical comp volume before it is published.

That turns a policy change from a leap into a measurement. Instead of publishing a new limit and discovering the budget impact a quarter later, Finance can replay the proposed matrix against what actually happened and see the effect first. The question moves from "what will this cost us?" to "here is what it would have cost us."

From police to partner

Give Finance a trustworthy live view and its role changes. The month-end chase — pulling figures, reconciling systems, explaining variances after the fact — is what a live ledger removes. What is left is the work that matters: steering reinvestment.

With comp spend visible as it happens and modelable before it changes, Finance stops policing the numbers and starts directing them. Where to lean in, where to pull back, which tiers and venues are returning on the spend — these become decisions made in the moment, on figures nobody disputes, rather than post-mortems on a month already spent.

Where this sits

AEGIS is the comp authority engine. It complements the casino management system rather than replacing it: your existing systems still calculate worth and issue value, while AEGIS governs who may authorize it, seals every decision, and provides the live budget view off that record. It answers each authority check in under roughly 5ms and is gaming-literate — it understands theoretical win, patron tiers, and comp types natively.

The budget picture and the audit trail are the same artefact. If that pairing matters to you, two companion guides go deeper: the defensible audit trail behind comp approvals, and building a comp approval matrix.

Frequently asked questions

Where do the comp budget figures come from?

From the same immutable decision ledger that governs authority. Every authorization is hash-chained and anchored into immudb, which the platform itself cannot alter, and each decision carries its matrix version. Finance reads the budget view directly off that ledger, so the numbers are the record rather than a reconstruction.

How current is the comp spend view?

Live. Every decision is broadcast the moment it happens on an Apache Kafka event backbone, so analytics and reporting feeds consume comp value as it leaves the property rather than waiting for a month-end reconciliation.

Can Finance model a change to the authority matrix before publishing it?

Yes. Because the delegation-of-authority matrix is versioned data rather than code, a proposed change can be modelled against months of real historical comp volume before it is published — so Finance can see the budget impact of a limit or approver change before it takes effect.

Does AEGIS replace our accounting or casino management system?

No. AEGIS is the comp authority engine. It governs and records who may authorize comp value and provides the live budget view; your casino management and accounting systems still issue value and keep the books. AEGIS complements them.