Skip to main content

Case Study

Multi-Location Finance Reporting Dashboard

Consolidated finance reporting across several branches into one live dashboard, in place of month-end spreadsheet stitching.

Alex

Alex

CEO

May 27, 2026
Industry Case Study
Focus Custom Development
Year 2026
Published May 27, 2026

At a glance

The problem
Each branch kept its own accounts, and group finance stitched monthly exports together in Excel, so the board saw stale numbers.
Systems touched
Each branch's accounting software, read through its API into a central data store.
What we built
A reporting layer that pulls every branch's transactions nightly, maps them to a group chart of accounts with rules finance can edit, and serves a live dashboard with drill-down.
What changed
The numbers are already consolidated when the month closes, and the finance director answers questions by drilling down instead of rebuilding spreadsheets.

Anonymised and illustrative. Client details are hidden and in some cases combined into a composite, and there are no outcome figures.

The Problem

A multi-site services group operating several branches across the South of England had no consolidated view of its own finances. Each branch ran its own copy of the same accounting software with its own chart of accounts, its own customised categories, and its own way of recording the same transaction. Group finance lived in Excel: every month, the finance director pulled exports from every branch’s accounting instance, mapped each branch’s categories to a group-level structure, and stitched them together into a board pack.

The process took up the opening stretch of every month. By the time the board saw the previous month’s numbers, they were already stale, and any branch-level question (say, why utilities were up in one branch) triggered another round of digging because the consolidated spreadsheet did not retain the underlying transactions.

Two problems compounded. Branches sometimes recoded categories without telling group finance, which broke the mapping silently and produced numbers that looked plausible but were wrong. And when a new branch was acquired, integrating it into the consolidation took weeks because the spreadsheet had to be restructured to absorb another column set.

The Approach

We built a reporting layer that sits above the accounting software rather than replacing it. Each branch carries on using the system it already uses; we pull transaction-level data from each instance nightly via the accounting platform’s API and write it to a central data store, normalised into a group-level chart of accounts.

The normalisation was the hardest part of the build. Every branch had drifted slightly from the original chart of accounts, and mapping had to handle real-world messiness: accounts that had been renamed, sub-accounts that existed in some branches but not others, and a small number of transactions miscoded so consistently they had become de facto categories. We worked through the mapping with group finance branch by branch, and the rules live in the platform as editable configuration rather than buried in spreadsheet formulas.

The System We Built

A central reporting platform pulling nightly from each branch’s accounting instance via API, normalising into a group-level chart of accounts, and serving a live dashboard. The dashboard shows group P&L, branch comparisons, and category drill-downs with the ability to click through to the underlying transactions, something the spreadsheet consolidation never permitted. Mapping rules are editable by group finance without developer involvement. New branches are onboarded by adding API credentials and applying the mapping rules through the admin interface. The underlying data layer follows the same architecture described in our reporting dashboard system.

The Outcome

Month-end consolidation is no longer a stitching job, because the numbers are already consolidated when the month closes, and what remains is review. More usefully, the finance director can answer ad-hoc questions by drilling into the dashboard rather than rebuilding part of the spreadsheet. Branch managers see their own performance against group averages in near-real time, so a conversation can move from “explain last month” to “manage this month”.

What We Learned

Replacing the branch-level accounting software was off the table. Branches knew it, used it, and the disruption would not have been justified. Building a layer above the existing systems rather than under them meant we could deliver consolidated visibility without touching what was working at branch level. The approach connects directly to two related case studies: the spreadsheet to internal platform migration covers a similar move away from spreadsheet-based operations, and finance back-office modernisation covers how we have restructured finance operations more broadly without forcing a system replacement.

Want Consolidated Visibility Without Replacing What Works?

If your group runs multiple instances of the same accounting or operational system and month-end is a spreadsheet ordeal, get in touch to discuss what a reporting layer could look like for you. The case studies overview has more examples of how we have approached similar consolidation problems for multi-site operations.

Written by

Alex

CEO

I’m a software developer and CEO of Digital Royalty, helping growing teams scale their SaaS platforms without losing quality, visibility, or control. I focus on building structured, maintainable systems with clear processes, reporting, and accountability. With over a decade of experience across agency and in-house roles, I specialise in delivering long-term, scalable solutions that support complex, evolving products.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.