What’s inside: company memory · savings measurement
The question this file answersWhy does close week still end with my controller pasting extracts at ten at night and writing commentary in the morning?
Fits: finance teams whose reporting and close packs are assembled by hand from several systems.
Typical, from the finance playbook's reporting section: monthly and quarterly cycles, a crunch each time, no count published for the close. ERP and sub-ledger extracts are pasted into one template, variances hunted by eye, commentary written last. It hurts in the crunch, when numbers move after the report is built.
On the first working morning after the ledgers close, the controller opens a filled report with the variances marked and a draft line under each, and spends the day on the adjustments and the explanations rather than the pasting. When a late journal lands, the figures refresh and the commentary is re-read, not rewritten from scratch.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
the same reporting build as regulatory reporting — no published figure for the month-end close
Before: close week is extracts, pastes and commentary at 22:00. After: the figures are pulled, the template filled and a draft line written under each variance; judgement stays with the controller. No percentage — the reporting figures live on the parent file.
EY Global RegTech Survey (2023) and Gartner (2023) measure regulatory-report preparation; the management close is a neighbouring desk, so their ranges stay on the regulatory file and this one carries no percentage. Not a claim about how long your close takes.
Your ERP and consolidation tools stay — Dynamics, SAP, Oracle or whichever you close in — and the template stays yours. This is the same reporting build as our regulatory-reporting file, pointed at the close:
Sign-off, adjustments and the sentence to the board are not automated.
Judgement on the numbers. Adjustments. The sentence to the board. Letters to auditors.
Not a claim about how long your close takes.
If the chart of accounts and the template mappings drift each month, the fill breaks and someone re-maps first — that mapping discipline is the real dependency. Drafted commentary is a starting sentence about a number, never an explanation of the business; if it is published unread, that is a control failure the build cannot prevent.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Finance.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.