Every mall bills turnover rent on tenant sales, and every mall has a version of the same problem: the sales number comes from the tenant. A monthly emailed figure is unauditable. Even an honest tenant's back office rounds, lags and forgets; a stressed one under-declares. The gap between actual and declared sales is invisible by definition — which is exactly why it needs a system rather than trust.
The capture stack, layered
- Daily declarations with teeth: daily, not monthly, declared in two taps from the tenant portal — with nil-sales enforcement, so a missing day is a chased exception rather than silent zero.
- Direct till feeds: where the tenant runs your POS — food courts, operated outlets — capture is perfect and dispute-proof by construction.
- POS connectors: for tenants on their own systems, API or file-based daily feeds from their till. The lease can make the feed an obligation.
- Aggregator channels: delivery orders are sales too, if the lease says so. Zomato and Swiggy volumes bypass the till narrative entirely unless they are wired into the same sales base.
- Anchor and cinema files: category-rate revenue share needs the multiplex and anchor sales files on the same rails, not in a separate spreadsheet.
Anomaly detection: footfall doesn't lie
With capture layered, the interesting work begins: comparing what tenants declare against what the building observed. A store whose zone footfall rose 20% while declared sales fell 30% is not proof of anything — but it is exactly the store to look at. Anomaly detection against footfall, seasonal history and category peers turns audit selection from ritual into targeting.
The audit has to end in a bill
A sales audit that produces a strongly worded letter changes nothing. The process that works is formal: audit rights exercised under the lease clause, findings documented, and — where under-declaration is established — rebilling computed under the same deterministic engine as the original invoice, so the corrected figure carries the same line-by-line defensibility. In CuroCentral the whole chain lives in one system: declarations, feeds, anomaly flags, audit workflow, rebill. The revenue you were owed stops depending on whether anyone remembered to chase it.