A leisure group's head office rarely has a live picture of what its centres are spending. One gym is ordering pool chemicals and cleaning supplies, the site across the county is replacing treadmills and restocking the café, and each duty manager is buying locally to keep their building running. Every month finance asks all of them the same question, what did you spend, and every month the answers come back late, each in a different shape, and never quite adding up.
Someone then stitches those returns into a consolidated report that is already out of date by the time anyone reads it. The instinct is developing a better dashboard on top, but the fix sits much earlier than that. This article covers why the monthly report is always behind, why a reporting layer cannot fix it, and where a single view of spend actually comes from.
Why the monthly report is always behind
The report is late and patchy because it is assembled after the fact from whatever each site chose to send in. One centre exports from its own leisure-management system, another sends a spreadsheet, a third replies to an email with a rough figure. Head office is not seeing spend at that point, it is collecting each site's version of what it spent and then trying to reconcile those versions into something comparable. That work cannot be fast because it only starts once the month has closed and every site has returned its numbers. And it cannot really be trusted because each return was put together to a slightly different standard.
You can't consolidate what wasn't captured the same way
A better reporting layer assumes the data already exists in a form you can roll up. But across most multi-site groups it doesn't, because each site recorded its spend differently in the first place. You can buy the most capable business-intelligence tool on the market and it will still only be as consistent as the returns feeding it, which means it will produce a tidier version of the same unreliable picture.
The single view has to be created where the spend happens. That means capturing every site’s spend in the same structure at the moment it occurs, with the same cards, limits and approval rules applied at every site. Once you have this, the comparable view exists by default instead of being rebuilt by hand each month.
Where Moss fits
This is what Moss is built for. Each site's staff get their own cards, with the site set as the cost centre and a limit on each card, and project cards with an end date cover one-off work such as a refurbishment. Merchant-category restrictions can narrow a card to, say, fuel or office supplies where the Advanced Controlling module is enabled. Expense Management applies one approval logic and one accounting export across every location, so head office sees spend across all its centres as it happens rather than chasing site managers for their figures. The reconciliation that used to take the first week of every month shrinks, because the site, cost centre and category were on each transaction when it was made, and consolidation becomes a filter rather than a rebuild.
What Moss gives you is a single view of spend across every site in a company, built to the same standard. Where sites sit in separate legal entities, as they often do in leisure groups with a trading company alongside a trust or a charity, Moss supports a multi-entity setup in which each entity runs as its own Moss account.
Each entity’s cards and spend stay in that entity, so transactions land in the right company’s books. Anyone invited to more than one entity with the same email address can switch between them from one login, on desktop or mobile, and admins decide who works in which entity. A head-office finance lead can move between every company in the group, while a site manager only sees the entity they belong to. Spend is reviewed entity by entity, but because each one follows the same structure, comparing them means switching between them rather than reconciling different formats.
What changes
Month-end stops starting with a round of emails. Every site's spend is already in one place, coded the same way, so the question finance asks is no longer what did you spend but whether anything on the list looks wrong. The duty manager who used to assemble a spreadsheet on the last day of the month has nothing to send, because the transactions they made were the return.
Head office should be able to open one screen and see every site, on the same terms, without sending a single email to a manager.
