The First Deadline Nobody Warns You About

You are forty-eight hours into the role. The acquisition has closed. The press release went out. The operating partner has sent a congratulatory message and a list of reporting expectations.

And somewhere in a credit agreement you are still reading, there is a covenant reporting deadline. It is in 45 days. It requires auditable numbers from a business you have not yet fully seen, running on systems you do not yet control, with a finance team you have not yet met.

This is the first deadline nobody warned you about. Not because it is obscure. Because by the time most incoming CFOs find out about it, the clock is already running.

The difference between the CFOs who get this right and the ones who are still reconciling spreadsheets at 11pm the night before is almost always a decision made in week one about whether the data foundation work starts now or later.

What you inherit on day one

Most PE-backed companies at the point of acquisition are not running clean, consolidated financial data. They have grown through a combination of organic expansion and bolt-on acquisitions. Each entity runs its own ERP. The chart of accounts differs by country, sometimes by business unit. Intercompany transactions are tracked inconsistently, or not at all. The finance team has been producing numbers, but the process involves manual reconciliation that lives in shared drives, personal spreadsheets, and the institutional memory of one or two people who have been there long enough to know where everything is.

An incoming CFO at a mid-market PE-backed business typically inherits: two to four source systems that do not talk to each other, a chart of accounts with entity-level variations that made sense locally but create chaos at consolidation, a close process that takes two to three weeks and depends heavily on people who may not still be there in six months, and a set of management accounts that the previous CFO could explain but that have no clean audit trail underneath them.

The details vary. The pattern does not. One entity uses a different depreciation assumption that nobody flagged in due diligence. An intercompany loan between the Czech and Slovak entities has been coded as external revenue in one system and cost in another for the past three years. The German subsidiary reports under HGB and the consolidation team applies IFRS adjustments manually at close, in a spreadsheet that only one person understands. None of this is visible until you start pulling the data.

None of it is unusual. All of it becomes urgent the moment a covenant deadline appears on the calendar.

The covenant clock

Most PE-backed companies carry debt with financial covenants: leverage ratios, interest coverage, minimum liquidity thresholds. Lenders require regular reporting against these, typically monthly or quarterly, with tight deadlines and no tolerance for late or qualified submissions.

The first reporting deadline typically falls 45 to 60 days after close. For a CFO still mapping the data landscape, that window is shorter than it looks. Week one is orientation. Week two is system access and team assessment. By week three, if you do not have a clear picture of where the consolidated numbers are going to come from, you are already behind.

Missing the deadline is not just an administrative failure. It triggers a formal breach process with the lender, requires written explanation, and often involves a waiver request that hands the lender negotiating leverage they did not have before. Even if the numbers were fine, the late submission creates a question mark about the competence of the finance function that can follow the company for years.

Submitting numbers you cannot fully stand behind is worse. A covenant calculation that turns out to be wrong, even by a small margin, introduces doubt about every number that came before it and every number that comes after. Lenders are not unsophisticated. They know when a CFO is presenting numbers with confidence versus numbers with caveats. The relationship between a PE-backed company and its lender runs on data credibility, and the first covenant submission is where that credibility is either established or put in question.

Both outcomes are avoidable. But only if the data foundation work starts in week one, not week four.

Why the first board review compounds the pressure

The covenant deadline is not the only clock running. The first PE board review typically happens within 60 to 90 days of close. The operating partner will want to see the investment thesis validated against current trading data: actual revenue versus the model, margin performance by entity, working capital position, cash conversion, and an honest view of where the business sits against the acquisition plan.

This is a different kind of pressure to the covenant deadline. The lender relationship is transactional: you submit the numbers, they check the covenants, the relationship continues. The operating partner relationship is something else. It is a working partnership that will run for three to five years, through strategic pivots, operational challenges, and eventually an exit process. The first board review is the moment that relationship either starts on a strong footing or does not.

A CFO who arrives at that review with a consolidated view they can trace to source, who can answer a question about regional margin by drilling into the underlying data in the room, who can explain a variance without having to say 'let me come back to you on that': that CFO has established something that is very difficult to build later if you miss the window. Credibility is easier to establish on day 60 than to recover on day 180.

The CFOs who get this right do not scramble to produce the first board report the week before it is due. They have a live, consolidated, board-ready picture before the review, covenant reporting submitted on time, and a finance team that owns the system rather than tolerating it.

The 8-week window that changes everything

The data foundation work that makes both deadlines manageable is not a six-month ERP migration. It does not require replacing any source system. It requires connecting the systems that already exist, applying a governed mapping layer, and building a single consolidated view that the CFO owns and the auditor can trace.

In practice, this runs across four phases:

1. Weeks 1 to 2: Data inventory
   Map every source system, understand the chart of accounts structure in each entity, identify where intercompany transactions are coded and whether the coding is consistent.

2. Weeks 3 to 4: Consolidation baseline
   Connect the source systems, apply the harmonisation rules, produce the first consolidated view. This is the output you need before the covenant deadline.

3. Weeks 5 to 8: Board-ready reporting
   Clean the data model, validate the numbers against the prior period, build the board pack structure. This is the output you need before the first PE board review.

4. Weeks 9 to 12: Handover to the team
   Document the system, train the finance function, reduce dependency on the CFO as the single point of knowledge.

The deal type changes the complexity, not the timeline

Not every post-acquisition data challenge looks the same. The deal structure determines where the hard work sits:

The question worth asking before close

The best time to start the data foundation conversation is during due diligence, not after the covenant clock starts.

The questions that matter: how many source systems does the target run, what does their chart of accounts structure look like, how long does their current close take and who does it, and what is the mechanism for producing consolidated numbers across entities?

If the answer to that last question is 'our controller builds it in Excel every month,' you have a covenant clock problem waiting to happen. The playbook for that problem exists. The time to pick it up is before day one.

Frequently asked questions

1. What is a covenant reporting deadline in a PE-backed company? A covenant reporting deadline is a contractual requirement in a company's debt agreement to provide auditable financial data to lenders at regular intervals, typically monthly or quarterly. The data must demonstrate compliance with agreed financial thresholds: leverage ratios, interest coverage, minimum liquidity. The first deadline usually falls 45 to 60 days after acquisition close. Missing it or submitting unverifiable numbers triggers a formal breach process that gives the lender negotiating leverage and creates a credibility problem that is difficult to recover from.

2. How long does a PE-backed CFO typically have before the first board review? The first PE board review typically happens within 60 to 90 days of close. For an incoming CFO, that means the covenant reporting deadline (days 45 to 60) and the board review (days 60 to 90) overlap significantly. A CFO who has not built a clean consolidated data picture by week four is likely to be presenting unverified numbers at both. The two deadlines are not separate problems: solving the data foundation in weeks one through four addresses both simultaneously.

3. What financial data does an incoming PE CFO typically inherit? At a mid-market PE-backed company, the typical inheritance includes two to four source ERP systems that do not connect to each other, a chart of accounts with entity-level variations, a close process that takes two to three weeks and depends on a small number of people who may leave post-acquisition, and management accounts with no clean audit trail underneath them. Intercompany transactions are often inconsistently coded. Subsidiaries in different countries frequently apply different accounting standards with manual adjustments made at close by one person in a spreadsheet.

4. What is the difference between a buyout, carve-out, and growth equity from a data perspective? A buyout presents moderate to high data complexity: multiple ERPs, entity-level CoA variations, manual consolidation. The primary risk is key-person dependency. A carve-out is the hardest scenario: the acquired business has no standalone financial history, data was embedded in the parent company's systems, and true standalone financials often do not exist at close. Add two to three weeks to the Phase 1 timeline and flag this to the operating partner before close. Growth equity is typically lower complexity with one ERP and younger data infrastructure, but board speed expectations are higher and the absence of consolidated reporting becomes visible quickly.

5. Can a governed data foundation really be built in 8 weeks without replacing existing systems? Yes, and the critical qualifier is that it does not require replacing any source system. The 8-week framework connects whatever systems already exist, applies a governed mapping layer across all entities, and produces a single consolidated view that the CFO owns and the auditor can trace. Weeks one and two are data inventory. Weeks three and four produce the first consolidated view in time for the covenant deadline. Weeks five through eight produce the board-ready reporting layer. The ERP replacement conversation, if it happens at all, comes after the data foundation is in place, not instead of it.