The Invoice That Shouldn't Be There
The move in short
Agent — An agent that runs each weekday, pulls the prior day's approved invoices from the accounts-payable system across all four properties, compares each line item against the rolling 90-day average for that supplier and cost-centre combination, flags any charge that deviates beyond a set threshold, and automatically sends a structured challenge message — showing the anomaly, the historical baseline, and a request for a brief justification — directly to the budget owner responsible for that cost centre, with a summary of all open challenges delivered to the head of finance each morning.
The Company
Kallisto Hospitality Group runs four independent hotels in and around Athens — two boutique properties in the city, one on the coast near Sounio, and a small resort on Aegina. About 160 people in total. Each property has its own character and its own way of doing things, which is mostly a strength. They're not a chain. They buy their olive oil from a specific farm in the Peloponnese and their linen from a supplier two streets from the Monastiraki property. That matters to them.
The Pain
Sofia, the head of finance, sees consolidated spend across all four properties — but she sees it after everything's already been approved and paid. By the time an anomalous charge shows up in her reporting, it's done. The invoice went to a property manager, the property manager approved it, the money's gone.
Last quarter she found a cleaning supplies invoice from the Sounio property that was almost double the usual charge. She traced it back six weeks. The property manager remembered approving it but assumed there'd been a price increase. Nobody had questioned it at the time because there was nobody whose job it was to question it at the time. Sofia spent most of a Friday afternoon untangling it.
That happens regularly. Not always at that scale, but regularly.
The Move
You'd build an agent that runs every weekday morning. It pulls the previous day's approved invoices from the AP system across all four properties, then checks each line item against a rolling 90-day average for that supplier and cost-centre combination. If a charge is more than, say, 20% above that baseline, the agent sends a structured message straight to whoever owns that cost centre — showing the charge, what the historical average looks like, and asking for a short explanation. Sofia gets a summary of every open challenge first thing each morning.
The tools to do this exist right now. Make or n8n can handle the workflow. You'd connect it to whatever AP system Kallisto already uses, set the threshold, map cost centres to budget owners, and it runs. No developer needed to maintain it once it's set up.
Most challenges probably resolve quickly — a seasonal price change, a one-off delivery, something the property manager can explain in two lines. But now that question is being asked every time, automatically, before it disappears into a monthly report.
The blind spot
The reason this doesn't get built is that Sofia's job is to report on what happened, not to chase individual invoices across four properties. Chasing feels like it's someone else's problem. And if you ask the property managers, they'd say they're already approving carefully. Both things can be true and the gap still exists.
The pattern
The same kind of agent fits a few other situations:
- A recruitment firm where individual consultants approve contractor timesheets, and no one at the centre notices when hours start creeping up on a placement
- A facilities management company where site managers order supplies locally and head office only sees the total cost per site, not per supplier
- A multi-location retail group where store managers handle their own consumables budget and overs only surface at month-end review