Consolidating Multi-Entity Spend at Quarter-End with a Dust Agent
Groups with 3+ entities spend hours consolidating their Spendesk data every quarter-end. A Dust agent, shared across the whole Finance team, does it in a single question — in the web chat or in Slack.
The problem
Every quarter-end, the same routine plays out: export data from the France entity, then Germany, then the UK. Open three separate Excel files, align the columns, convert currencies at today's rate, and attempt to produce a coherent consolidated view. This typically takes between two and four hours — and half that time is spent just verifying that the totals add up correctly.
The problem isn't the complexity of the data: it's that the data lives across separate Spendesk instances, and aggregation is entirely manual. Any last-minute change — an invoice approved at the wire, a payment pushed back — means partially starting over.
The result: a Q2 consolidation ready on July 8th, based on data frozen as of July 5th. For a CFO who needs to present numbers to the board, that's a permanent risk of discrepancy between reality and reporting.
What a Dust agent connected to the Spendesk MCP changes
Once the Spendesk MCP is connected by the workspace admin, a Dust agent connects directly to all entities configured within the organisation. A single question is enough to get a consolidated view, broken down by cost center or analytical field (expense categories are not a grouping dimension), with each entity's total in its own currency and a conversion at the rate you provide — and since the agent is published for the whole Finance team, everyone asks the same agent the same question instead of rebuilding their own spreadsheet.
@Dust give me the Q2 2026 spend consolidation for our 3 entities — France, Germany, and the UK — with a breakdown by category.
Here is the Q2 2026 spend consolidation (April–June) across your 3 entities:
| Category | France (EUR) | Germany (EUR) | UK (GBP→EUR) | Consolidated Total |
|---|---|---|---|---|
| SaaS / Software | 184,200 € | 96,400 € | 71,300 € | 351,900 € |
| Contractors & Consulting | 112,500 € | 43,800 € | 38,600 € | 194,900 € |
| Cloud Infrastructure | 67,800 € | 51,200 € | 29,100 € | 148,100 € |
| Marketing & Events | 48,300 € | 18,900 € | 14,400 € | 81,600 € |
| General Expenses | 32,100 € | 22,600 € | 17,800 € | 72,500 € |
| Q2 Total | 444,900 € | 232,900 € | 171,200 € | 849,000 € |
GBP/EUR conversion: rate used — 1 GBP = 1.175 EUR (Spendesk does not supply exchange rates: confirm it or give me your closing rate)
Entity breakdown:
Would you like the same table for Q1 to track quarter-on-quarter progression?
Going further: 2 additional use cases
Identifying which entity is most over budget
At quarter-end, knowing which entity has drifted furthest from its budget is critical for calibrating Q3 forecasts. The Spendesk MCP does not read budgets: give the agent your budget figures in the question and it pinpoints relative overruns against actual spend, directly in the finance leadership Slack channel.
@Dust which entity has the biggest budget overrun this quarter? Our Q2 budgets: France 420,000 €, Germany 210,000 €, UK 165,000 €.
Budget vs Actual Analysis — Q2 2026
| Entity | Q2 Budget | Q2 Actual | Absolute Variance | % Variance |
|---|---|---|---|---|
| France | 420,000 € | 444,900 € | +24,900 € | +5.9% |
| Germany | 210,000 € | 232,900 € | +22,900 € | +10.9% |
| UK | 165,000 € | 171,200 € | +6,200 € | +3.8% |
Would you like a supplier-level breakdown of the Germany overrun?
Negotiating group contracts for shared suppliers
Paying Salesforce or AWS separately across each entity means leaving money on the table. The agent can identify in seconds which suppliers appear across all three entities — an analysis that stays available to anyone in Finance who mentions @Dust, without having to rebuild it from scratch.
@Dust are there suppliers shared across all 3 entities where we could renegotiate a group contract?
I found 6 suppliers present across all 3 entities over the past 12 months:
| Supplier | France | Germany | UK | Group Total | Negotiation Potential |
|---|---|---|---|---|---|
| Salesforce | 68,400 € | 31,200 € | 24,800 € | 124,400 € | ⭐⭐⭐ High |
| AWS | 42,100 € | 28,600 € | 18,300 € | 89,000 € | ⭐⭐⭐ High |
| Notion Enterprise | 8,400 € | 4,200 € | 3,600 € | 16,200 € | ⭐⭐ Medium |
| Figma | 6,800 € | 3,100 € | 2,900 € | 12,800 € | ⭐⭐ Medium |
| Docusign | 4,200 € | 2,800 € | 1,900 € | 8,900 € | ⭐ Low |
| Zoom | 3,600 € | 2,100 € | 1,800 € | 7,500 € | ⭐ Low |
Would you like the month-by-month spend for each of these suppliers to help plan the negotiations?
Key takeaways
- The multi-entity consolidation that used to take 2–4 hours now happens in a single question to a Dust agent.
- Each entity's total comes back in its own currency: the agent converts at the rate you give it (Spendesk supplies no exchange rates).
- The agent surfaces not just totals, but relative overruns across entities, against the budgets you give it (the MCP does not read budgets).
- Suppliers present across all entities are instantly identifiable for group negotiation.
- An agent published for the whole Finance team means no one rebuilds the same analysis on their own.
- For more on setting up multi-entity access in the MCP, see the guide on Dust MCP tools.
Related skills