Most post-close integration checklists have a line for sales, a line for ops, a line for IT, and finance gets folded into “accounting cleanup,” even though it determines whether anyone trusts the numbers for the next 3 to 5 years.
That gap shows up fast. A finance integration checklist after acquisition determines whether the operating partner’s first board meeting is built on real numbers or best guesses.
Why finance integration gets treated as an afterthought
Sales and ops integration plans get built early because the stakes are visible: lose a customer relationship or a key operator, and everyone notices immediately. Finance integration problems are quieter. A misaligned chart of accounts or an unreconciled system doesn’t blow up in week one. It surfaces 2 or 3 months later, usually right when someone needs a clean number fast.
By then, the fix costs more than it would have on day one, because now there’s a backlog of transactions booked under the old structure that all need to be reclassified or reconciled retroactively. What would have been a decision in week one becomes a cleanup project in month three, and cleanup projects are always more expensive than the thing they’re cleaning up after.
There’s also a subtle reason finance gets deprioritized: it doesn’t have an obvious owner in most deal teams. Sales integration has a sales leader. Ops integration has an operator. Finance integration often falls to whoever happens to be closest to the books at the time, which usually means it gets handled reactively instead of planned deliberately. Reactive plans tend to address symptoms as they appear rather than the structural gaps causing them.
What a real finance integration checklist should cover
A finance integration checklist after acquisition needs to go well beyond “close the books on time.” At minimum, it should cover:
- Banking and treasury: opening new accounts, setting up treasury services, and mapping out how cash moves between entities during the transition.
- Payroll and HR systems: reviewing the acquired company’s existing payroll configuration and identifying what needs to be reconfigured, especially where compensation classification differs.
- Chart of accounts: assessing the current-state COA against what the combined entity actually needs, including dimension and segment design for reporting.
- Accounting remediation: a detailed walkthrough of existing processes to catch revenue recognition issues, cash-to-accrual gaps, or other corrections before they compound.
- FP&A and reporting: identifying data sources, standing up an initial KPI dashboard, and building toward a real forecast model rather than a static budget.
- Opening balance sheet and closing statement: coordinating with valuation providers early, since accounting work has its own lead time and can’t be rushed at the end.
Skipping any one of these creates a gap that someone eventually has to explain to a board, a lender, or an LP.
These categories aren’t independent of each other. A payroll system reconfiguration affects the chart of accounts. A chart of accounts redesign affects what the FP&A team can actually report on. Treating each line item as a standalone task, rather than a set of interdependent decisions, is one of the more common ways integration checklists fall apart in practice.
A phased approach works better than a single deadline
Trying to complete finance integration all at once, by some arbitrary date, tends to produce rushed, undocumented work. A phased approach holds up better, and it maps reasonably well to how most acquisitions actually unfold operationally.
In the first stretch after close, the priority is assessment and stabilization: getting banking and payroll functional, reviewing the existing chart of accounts, and identifying what data actually exists versus what still needs to be built. It’s unglamorous, foundational work, but skipping it means every later phase inherits the same gaps. This is also the window to reach out to valuation providers if an opening balance sheet needs to be prepared, since that work often has a longer lead time than teams expect.
The next phase is where the real infrastructure gets built: the chart of accounts gets redesigned around the combined entity, an intercompany elimination framework goes in if there’s more than one entity involved, and the forecast model starts to take shape. This is usually the busiest phase, and it’s where having a dedicated owner for finance integration pays off most, since it involves more judgment calls than the stabilization phase did.
The final phase is where reporting actually goes live: a first board package delivered, lender reporting running if applicable, and a documented month-end close process so the whole thing doesn’t depend on one person’s institutional knowledge. A good test for whether this phase is complete: could someone new to the finance team run the close process from the documentation alone, without pulling the person who built it into every step?
Common pitfalls
A few mistakes show up again and again in finance integrations:
- Treating the checklist as a one-time task instead of a phased plan with real ownership at each stage
- Waiting until month-end close breaks before addressing chart of accounts misalignment
- Starting ASC 805 valuation conversations too late, since these providers often need significant lead time
- Assuming the acquired company’s existing processes are “good enough” without a real walkthrough
- Building reporting for the business as it exists today instead of the combined entity it’s becoming
Most of these pitfalls share a common root: treating finance integration as something that happens passively, alongside the “real” integration work in sales and ops, instead of as its own work stream with its own timeline and its own owner.
How to assign ownership without overloading one person
One practical decision that’s easy to get wrong: who actually owns this checklist? In a lot of newly acquired companies, the answer defaults to whoever’s already doing the books, often a controller who’s also handling day-to-day close activity and doesn’t have the bandwidth to run a structured integration project on top of it.
A better approach splits the work. Someone owns the overall plan and phase-by-phase milestones, while the categories themselves (banking, payroll, chart of accounts, and so on) get assigned to whoever has the most relevant expertise, whether that’s an internal hire, a fractional resource, or an outside specialist for something like ASC 805 valuation work. The goal is to make sure every task has a name attached to it and a date it’s due.
A realistic scenario
Consider a services business acquired as a platform’s second add-on. On paper, the acquisition made sense: complementary customer base, similar margin profile, an obvious cross-sell story. In practice, the acquired company’s chart of accounts had grown organically over a decade, with dozens of ad hoc expense categories that didn’t map to anything in the platform’s existing structure.
Without a structured integration checklist, that mismatch might not surface until the first consolidated month-end close, when the finance team discovers that what looked like a straightforward roll-up actually requires manually reclassifying hundreds of transactions by hand, every single month, until someone rebuilds the chart of accounts properly.
With a checklist in place from day one, that chart of accounts review happens in the first 30 days, as an assessment, not a fire drill, and the redesign happens deliberately in the following phase, before it’s had a chance to create months of manual workaround. The difference is whether that work happens on a schedule the team controls or one forced by a broken month-end close.
Building your own checklist
The specifics of any finance integration checklist after acquisition will vary by deal. A services business integrates differently than a manufacturer, and a platform with several add-ons already in place has different needs than a first acquisition. But the categories above hold constant across most deals, and mapping owners and target dates against each one, phase by phase, is what turns a checklist from a wish list into something that actually gets executed.
The firms that treat this as seriously as they treat sales and ops integration tend to hit their first board meeting with numbers they can stand behind. The ones that don’t usually find out the gap exists at the worst possible time: mid-diligence on the next deal, when the numbers need to hold up under scrutiny and don’t.
The bottom line
A finance integration checklist after acquisition is the difference between a finance function ready to support the next deal and one still catching up on the last one. Building it early, phasing it deliberately, and assigning real ownership at each stage is what makes the difference between reporting that holds up and reporting that quietly falls apart the moment someone asks a hard question.
None of this requires a massive team or an enterprise budget to get right. It requires treating finance integration as a real workstream from day one, with the same visibility and accountability given to sales and ops integration. It’s the function everyone else’s numbers ultimately depend on.
FAQ
Do we need this if we already have a controller or an in-house finance team?
A controller running day-to-day close usually doesn’t have the bandwidth to also run a structured integration project on top of it. The checklist gives that team, or a fractional resource brought in alongside them, a plan with owners and dates instead of a list of things to get to eventually.
How long does a full finance integration usually take?
Most run 90 to 120 days from close to a documented, repeatable month-end close, though assessment and stabilization should start in the first 30 days regardless of company size. Deals with multiple entities or an opening balance sheet tend to run longer, mostly because of the valuation provider’s lead time, not the accounting work itself.
Does this apply outside PE-backed deals?
The categories hold for any acquisition, but the urgency changes. A PE-backed company answers to a board and often a banker, so a broken chart of accounts surfaces fast, usually in the first board package. A privately held acquirer without that reporting cadence can stretch the timeline, though the same backlog of unreconciled transactions still builds underneath it.
What happens if we just handle issues as they come up instead of following a checklist?
Skipped issues resurface later, and bigger. Fixing a misaligned chart of accounts in week one is a design decision. Fixing it in month four is a cleanup project with a backlog of transactions that need to be reclassified by hand. Reactive integration costs more, it just costs more later instead of now.
