Seven sites, seven formats
Every Monday head office waits for the weekly figures. One branch emails a tidy spreadsheet. Another uses last year's template with a column missing. A third sends a photo of a handwritten sheet. One forgets until someone phones. A franchisee sends figures including VAT when everyone else excludes it.
Someone at head office retypes, reformats and chases until the group report can be put together, usually a day or two after anyone wanted it.
Why a template alone does not fix it
Most groups have already tried sending a standard template. It drifts. Branches insert columns for their own notes, rename tabs, paste values in the wrong format, or keep using an old copy. The spreadsheet has no way to enforce anything once it leaves head office.
Different branches may also run different tills, booking systems or even accounts packages, especially after acquisitions or in a franchise model. Each produces its figures differently, and branch managers are not data people. They have a site to run.
Timing adds another layer. Some branches trade Monday to Sunday, others close their week on Saturday, and a franchisee may report on their own accounting calendar. Unless the period is fixed and enforced, the group total quietly mixes different weeks together.
What the stitching costs
- Head office time spent retyping and chasing
- Group figures arriving late in the week
- Inconsistencies such as gross versus net that nobody spots
- No easy way to compare branches fairly
- Branch managers annoyed by repeated calls for missing numbers
Late group figures mean problems at one site are spotted late. A branch that has a bad month is only visible once the whole stitched report exists.
There is a fairness issue too. When one branch reports gross and another net, or one counts a returned sale and another does not, league tables and bonuses built on those figures are quietly wrong. Branch managers usually know, and it sours the conversation with head office.
How we build one reporting route for every site
There are two routes, and most groups end up using both: direct feeds where a branch system allows it, and a controlled form where it does not.
- We list each branch, the system it runs and what it currently sends.
- For branches whose tills, booking or accounts systems have an API, such as Square, Lightspeed, Xero or QuickBooks, we pull the figures automatically. The branch does nothing.
- For the rest, we build a short web form with fixed fields, dropdowns and clear rules like net of VAT, so the branch manager can fill it in on a phone.
- Every submission is validated on arrival: required fields present, values in sensible ranges, totals consistent with each other. Problems go straight back to the branch with the reason.
- Missing submissions trigger automatic reminders to the branch and a note to head office.
- Accepted figures flow into one database, and the group report or dashboard builds itself from there.
| Branch situation | Route |
|---|---|
| System with an API | Automatic feed, no branch effort |
| System with scheduled exports only | Export dropped to a shared folder and read automatically |
| No system, or manual figures | Mobile-friendly web form with validation |
Monday without the chasing
Figures from connected branches arrive by themselves. The others submit through a form that will not accept an incomplete or inconsistent return. Head office opens the group report instead of building it, and can compare branches on the same basis.
Branch managers benefit too. They can see their own history and how they compare with the group average, which turns the weekly return from a chore for head office into something useful for running their site. Questions from head office become specific rather than a general chase for numbers.
When a new branch opens or is acquired, it is added to the same route rather than inventing its own spreadsheet.
Sounds familiar?
- Branches send figures by email, spreadsheet, photo or phone
- Head office retypes figures into a master sheet
- Someone chases late or missing returns every week
- Branches run different systems after growth or acquisition
- Comparing sites needs manual adjustments