
A case: supporting a stretched finance team through the IPO transition
THE SHORT VERSION
A private company prepares to list. Its finance team runs several business units, each with its own P&L, and closes the month in about three weeks. That timetable will not survive public reporting.
The Controller is carrying most of the load personally, and the team has no spare capacity to redesign anything.
The work: assess the function, add experienced finance capacity around the Controller, redesign the month-end close, consolidate the P&Ls into one repeatable reporting process, strengthen finance systems, and keep daily operations running until the permanent team can take over.
Post-IPO finance support is usually needed before the listing date, not after it. By the time the first public results are due, the close, the reporting structure and the team have to be ready. This case follows a common version of the transition: a growing private company, several P&Ls, a Controller doing too much, and a close that is too slow for a listed company. It sets out how the finance function was assessed, where extra capacity went, how the close and reporting were rebuilt, and how knowledge was handed to the permanent team. The case is representative, not a named company, and it is the type of situation NEO Expertise supports finance teams through.
On this page
- The situation
- Step 1: Assess the finance function
- Step 2: Add capacity around the Controller
- Step 3: Redesign the month-end close
- Step 4: Consolidate the P&Ls into one reporting process
- Step 5: Systems, continuity and handover
- Where IPO finance transitions go wrong
- IPO Finance Transition Checklist
- Frequently asked questions
The Situation
The company has grown by adding business units, each run with its own P&L, its own account structure and its own habits at month end. Group results are assembled by the Controller in a spreadsheet, from files sent by each unit, around working day 18.
The listing process has started. A prospectus under the EU Prospectus Regulation (EU) 2017/1129 requires historical financial information, and once listed, periodic reports follow a fixed public calendar. The board expects finance to be ready for both. The Controller knows the numbers better than anyone, which is exactly why every question lands on the Controller’s desk.
The risk is not a single error. It is a finance function that depends on one person, on a timetable that has just become public.
Step 1: Assess the Finance Function
The assessment looked at both the finance and accounting organisations: roles, workload, skills and the calendar. It identified three kinds of gap:
- Capacity gaps. The team could close the month or support the IPO work, not both.
- Expertise gaps. No one had prepared listed-company reporting or supported a public-company audit.
- Single points of failure. The Controller, and one senior accountant who alone understood the revenue accruals.
The revenue accruals showed why the third gap mattered most. Two business units invoiced customers in arrears, so each month’s revenue had to be estimated from delivery records before invoices were raised. The senior accountant built those estimates from a personal spreadsheet with no written method. When the estimates were tested against the invoices that followed, the method turned out to be sound, but nobody else could have reproduced it. Documenting that one calculation, and training a second person on it, removed a risk that would otherwise have sat under every set of published results.
The output was a list of the specific areas needing additional expertise, the roles to be covered temporarily, and the roles to be created permanently.
Step 2: Add Capacity Around the Controller
Experienced finance professionals joined the team on an interim basis, working alongside the permanent staff rather than as a separate project team. Their first job was to take recurring work off the Controller: reconciliations, accrual calculations, intercompany matching and the first draft of the reporting pack.
That freed the Controller to lead the redesign and to deal with the auditors and the listing advisers. Day-to-day finance operations (payments, payroll, billing, collections) continued without interruption, because the interim support covered execution, not just advice.
Step 3: Redesign the Month-End Close
The close was reviewed step by step to find the delays and the gaps. The biggest delays were waiting for business-unit files, rework after late adjustments, and intercompany differences discovered only at consolidation.
The redesign introduced a written close calendar with one owner per task and a deadline per working day. Illustrative close calendar from this case:
| Working day | Task | Owner |
|---|---|---|
| WD -2 | Accrual estimates agreed with business units | Unit accountants |
| WD 1 | Sub-ledgers closed, bank reconciled | Accounting team |
| WD 2 | Intercompany balances matched and agreed | Group accountant |
| WD 3 | Unit trial balances locked | Unit accountants |
| WD 5 | Consolidation run, first review | Controller |
| WD 8 | Reporting pack final | Controller, CFO sign-off |
The close moved from working day 18 to working day 8 over four months. The step that made the largest difference was moving intercompany matching to working day 2. Before, differences surfaced at consolidation on day 15 and took three days to resolve. The method is set out in reconciling intercompany balances.
Step 4: Consolidate the P&Ls Into One Reporting Process
Each business unit reported on its own account structure. The fix was a single group reporting chart with every unit’s accounts mapped to it, one reporting template, and one set of definitions for revenue, gross margin and operating costs.
The mapping exposed differences that had been invisible in the spreadsheet. Illustrative: one unit booked delivery costs in cost of sales and another in operating expenses, which moved reported gross margin by 2.3 percentage points between units that were in fact performing similarly. Aligning the definition changed how the board read the business.
Once mapped, reporting became repeatable: the same pack, built the same way each month, with every figure traceable to a unit trial balance. The approach mirrors preparing subsidiaries for group reporting, applied to business units rather than acquired companies.
Step 5: Systems, Continuity and Handover
The finance systems review defined the technology requirements behind the new process: a consolidation tool to replace the spreadsheet, standard sub-ledger reports, and automated intercompany matching. A named person in finance was given ownership of finance systems, so that technology decisions stopped being made by default in IT.
Throughout, the transition was managed so that business as usual continued: every interim role had a named permanent counterpart, and procedures were written as the work was done, not afterwards. Knowledge transfer ended with the permanent team running two consecutive closes without interim support before the support stepped back.
The permanent structure was decided from evidence gathered during the interim period, not guessed in advance. The workload logged by the interim team showed which tasks recur every month and how many hours they take. In this case, that supported two new permanent roles, a group reporting accountant and a technical accounting lead, and showed that a third role originally planned was not needed once the close had been redesigned.
The same sequence of assessment, capacity, close and reporting applies after a large acquisition, set out in the first 100 days finance integration roadmap.
Where IPO Finance Transitions Go Wrong
- Interim support as a separate team. Advisers working in a parallel project leave nothing behind when they go. Support has to sit inside the team and do the work with them.
- A faster close without earlier cut-offs. Shortening the timetable while estimates are still agreed after month end just moves the rework to a later day.
- Consolidation before definitions. Mapping units to one chart without agreeing what goes in each line produces one pack with the same inconsistencies inside it.
- Stepping back too early. One good close with support is not proof. Two unassisted closes are the minimum test.
This approach assumes the business units share one legal and tax structure. Where each unit is also a separate legal entity with its own statutory audit, the redesign has to cover statutory closes too, and the timeline roughly doubles.
The IPO Finance Transition Checklist
Use this as a working checklist. Each item is a check to complete, not a topic to consider.
Assessment
- ☐ Map capacity gaps, expertise gaps and single points of failure
- ☐ Document every calculation that exists only in one person’s spreadsheet
- ☐ Decide which roles are temporary and which must be permanent
Month-end close
- ☐ Write a close calendar with one owner and a deadline per working day
- ☐ Agree accrual estimates before month end, not after
- ☐ Move intercompany matching to the start of the close
- ☐ Lock business unit trial balances before consolidation
Reporting
- ☐ Map every unit to one group reporting chart of accounts
- ☐ Agree one definition for revenue, gross margin and operating costs
- ☐ Make every figure in the pack traceable to a unit trial balance
Systems and handover
- ☐ Name a finance owner for finance systems
- ☐ Replace spreadsheet consolidation with a tool once the process is stable
- ☐ Write procedures as the work is done
- ☐ Run two consecutive closes without interim support before it steps back
Frequently Asked Questions
What does post-IPO finance support involve?
It typically combines interim finance professionals working inside the team, a redesigned month-end close, consolidated reporting across business units, clearer finance systems ownership, and structured knowledge transfer, so the permanent team can meet public reporting deadlines without depending on one person.
How fast should a listed company close its books?
There is no single legal deadline for the monthly close, but public reporting calendars and audit timetables push most listed groups towards a close within 5 to 10 working days. The right target depends on the number of entities and the reporting calendar the company has committed to.
When should interim finance support step back?
When the permanent team has run at least two consecutive closes without support, procedures are written and used, and each interim task has a named permanent owner. Stepping back after a single supported close usually means the old dependency on one or two people returns.
NEXT STEP
NEO Expertise supports finance teams through transitions like this one, adding experienced capacity for reconciliations, the close and reporting while your Controller leads the redesign. You can discuss your finance project with our team.

Brahim Rami | Member of institute of chartered accountants in Morocco
He is a CPA and tax advisor, founder of NeoExpertise.net, a Legal and Tax firm helping foreign companies with business setup, due diligence, payroll, and tax compliance in Morocco and Africa.




