Monthly Pack Assembly

The problem

Every site sends its numbers in whatever shape it keeps them, and someone spends the first week of the month making thirty different things look like one thing.

By the time the pack reaches the board it describes a month that ended a fortnight ago, and the questions it raises are already too late to act on.

How it works

We read each source on a schedule you setLedger exports, the spreadsheets each site actually sends, and the folder someone drops the late one into. Read-only throughout.
Each file is normalised to one layoutMapped against your chart of accounts, not an idealised one. The mapping is written down and yours to change.
Anything that does not reconcile is flagged, not guessedA variance outside your tolerance, a site that has not reported, a code that does not exist. Listed at the top of the pack rather than discovered on page four.
The pack is assembled as a documentThe same layout every month, in the order your board reads it.
A person reviews it before it goes anywhereIt is produced for review, not sent on your behalf.

What you get

The pack itself — assembled on the schedule you set, in a fixed layout
An exceptions page — what did not reconcile, and which site it came from
A source log — which file was read, when, and what it contained
The mapping document — how each site's codes translate to yours, in writing
Portal access — every run, every exception, and the monthly statement

What we need from you

Read-only access to the accounting system, or a scheduled export to a folder we can read
Sample files — three months of what each site actually sends, including the messy ones
A named person for sign-off — whoever currently owns the pack
Your tolerances — what counts as a variance worth flagging

What stays with your people

Reviewing the pack and deciding it is right
Accounting judgment on anything flagged
The commentary — we assemble the numbers, not the narrative
Sending it to the board

This system is read-only. It never writes to your ledger.

Timeline

Day 1–2: Audit and scope. We look at the real files and agree what the system will and will not do, in writing.
Day 3–10: Build. Connected read-only to your own data, with the rules agreed as we go.
Day 11–13: You watch it run. Against live data, still read-only, and you sign off what it produces.
Day 14: Live. Write scope opens only where you have agreed it.

Works with

It is built into the finance software you already run. No migration, and no vendor switch.

Price

Setup: —
Monthly: —per month, rolling

The monthly fee includes:

—

This system is part of the Finance & Reporting suite. One system is the suite's Essentials tier, two to four are its Growth tier, and all five together are Full Finance Operations.

Prices exclude VAT. The audit and scoping before any of this costs nothing.

Pairs well with

System Connectivity Built into the finance software you already run. Audit Preparation Evidence that files itself, all year.