← Back to Stories

Story · Case study

Eleven days to three — and the close pack builds itself

Nine ledgers, three currencies and a group controller who had run the same eleven days every month for four years.

The company

Company
Bramwell Retail
Industry
Retail
Company size
1,001–5,000 people

The starting point

Bramwell Retail closes four trading entities across three currencies. Nine ledgers have to be reconciled before anyone can say what the group earned, and until last year that reconciliation was a fortnight of a six-person team's life: export, match, chase, re-export, and a pack assembled by hand on the eleventh working day.

Nobody in that team is an engineer, and nobody wanted to become one. Two attempts to fix it had been scoped as data projects, and both had been de-prioritised behind a store systems programme — which is the ordinary fate of finance's own tooling in a retail group.

What changed

What they actually described

The starting artefact was a paragraph. It said what the close is: which ledgers, in what order, what counts as matched, what has to be explained rather than matched, and what the audit committee expects to read at the end of it. It named no technology at all.

What came back was an application — a real one, with a screen, a set of named operations and its own place to keep what it produced. The team's first afternoon with it was spent doing what they would have done with a new analyst: correcting it. The intercompany rule was too generous, the FX cut-off was a day out, and the variance threshold that mattered to the committee was not the one it had assumed. Each correction was another paragraph, and the application was rebuilt from the corrected description rather than patched — which is why the version they run today has no accumulated special cases in it.

The results

The middle two figures are the ones the controller quotes internally. Nine ledgers is the scope, and twelve open items is the honest number: the application does not pretend to resolve a disputed accrual, it surfaces it with the workings attached and stops.

Example

Working days to close

3 days

down from eleven

Ledgers reconciled each run

9

Manual matches left

12

the ones that genuinely need judgement

Hours returned to the team monthly

190 hrs

“I did not want a data project. I wanted the thing I do every month to still be the thing I do every month, and to take an afternoon instead of a fortnight.”

— Priya Nandakumar, Group financial controller, Bramwell Retail (an example business)

The apps

What it cost to run and what to expect

What it cost to run

Bramwell is on a fixed monthly platform fee with a credit allowance sized for a normal month, and the close is comfortably inside it. The two months that ran hot were the year-end and the month somebody re-ran the whole prior year to answer an auditor's question — both visible in the usage view before they became an invoice, because the organisation's spend cap is set and the cap is what the platform enforces.

What they would tell you to expect

Two things, both said without much enthusiasm. The first is that the description is the work: a paragraph that is vague about what "matched" means produces an application that is confidently wrong about it, and the fix is a better paragraph rather than a support ticket. The second is that the first fortnight is still a fortnight — of correcting, not of building — and that the difference is who spends it and whether it happens again next month.

Connected to this story

Tell me when it's ready

We keep your email only to tell you once, when the app is ready, and delete it then.

What happens next

Thank you. We will write once, when it's ready.