Forty-five days after close, a controller at a $280 million industrial services company joins a kickoff call with the PE sponsor’s valuation advisor. She came prepared to hand over a clean trial balance. Instead, the advisor opens with requests for five-year financial statement projections with revenue segmented by customer relationship, a breakdown of technology assets by remaining economic life, and her view on historical customer attrition rates. The sponsor’s deal team is not on the call. Nobody briefed her on what a purchase price allocation (PPA) would actually demand of her time or her credibility. She is now the primary operational voice in a process that will determine how $150 million in purchase consideration gets allocated across the opening balance sheet. And that will flow directly into EBITDA addbacks, amortization schedules, and impairment risk for years.

This scene repeats across middle-market PE transactions. Most controllers at newly acquired companies are encountering purchase price allocation accounting for the first time, and the expectation gap is consequential.

Those controllers may assume the PPA is a compliance exercise managed by the valuation firm. The reality under Accounting Standards Codification Topic 805, Business Combinations (ASC 805), is different. While the critical role the valuation firm plays must not be understated, the controller must actively participate in identifying intangible assets, developing or validating the projections that drive their values, and constructing an opening balance sheet that withstands audit scrutiny. The distance between what controllers may think is expected of them and what the process actually requires can create timeline delays and balance sheets that do not hold up.

What ASC 805 Expects From the Controller

ASC 805 places the burden of fair value measurement on the acquirer: the entity, not the third-party advisor it hires. The valuation firm ultimately is an input provider to the opening balance sheet. It leverages its unique expertise to advise on scope, construct models, select and apply appropriate valuation methods, and ultimately produce a report. But the assumptions embedded in that report like the projections, attrition rates, royalty rate selections, and the useful life estimates must ultimately be ones that management can explain and defend. When the external auditor’s valuation specialist challenges an assumption in the purchase price allocation valuation, the question lands on the controller’s desk. While a credible valuation firm will most likely assist management in the preparation of responses to these questions, the controller must ultimately be prepared to stand behind such audit responses.

The scope is broader than many first-timers expect. Under ASC 805-20-25, the acquirer must recognize all identifiable intangible assets meeting either the contractual-legal or separability criterion (or pursue the private company alternative under ASC No. 2014-18, Business Combinations (Topic 805) (ASU 2014-18). In a typical middle-market industrial or business services deal, that might mean customer relationships, trade names, developed technology, non-competes, and/or backlog, among others. The controller’s role is not to value these assets but to supply and validate the inputs each one requires: customer revenue concentration and contract terms for relationship valuations, brand-level revenue breakdowns and royalty rate support for trade names, technical documentation, and remaining life estimates for technology.

Many of these valuations sit at Level 3 in the ASC 820 fair value hierarchy, which relies on unobservable inputs: in practice, principally management’s projections and assumptions, calibrated to market participant perspectives. The controller’s internal data carries outsized weight in determining asset values. A controller who treats the PPA as a data handoff lets the valuation firm fill gaps with generic benchmarks that may not reflect the specific business, and that disconnect is exactly what auditors probe.

PPA Accounting Runs on Projections, and Many Controllers Aren’t Prepared for That

If the controller’s data drives the valuation, the projections are the engine. And the projection problem is where controllers can lose control of the PPA process. It starts with a misunderstanding about what “projections” means in this context.

The forecasts used in a purchase price allocation valuation are not necessarily simply the operating budget. A PPA often requires the overall target company forecast to be disaggregated in order to drill down to asset-level expectations: revenue attributable to existing customer relationships, modeled with an attrition curve that decays over time; revenue attributable to the trade name; or revenue bifurcated among underlying technology of other IP. Further, the forecast needs to reflect the perspective of a hypothetical market participant (excluding any forecast attributes solely specific to the acquirer). Many controllers have never needed to model for such granular detail, or from a market participant perspective, because nothing in their role prior to the PPA required it.

Two failure modes follow, both common. In the first, the valuation firm builds projections with minimal controller input, using the company’s budget as a starting point and producing models the controller sees for the first time in draft form. The numbers may be reasonable, but the controller cannot explain their derivation when the auditor’s specialist asks.

In the second, the controller submits the company-wide budget unmodified and the valuation firm reverse-engineers asset-level assumptions from it. A flat five percent growth rate becomes a customer-level assumption implying zero attrition and uniform expansion, neither of which reflects how the business actually retains and grows accounts.

PCAOB inspection reports have flagged insufficient auditor scrutiny of management projections in business combination accounting.¹ The pattern is instructive: auditors accept projections because the valuation firm incorporated them, and the valuation firm accepted them because management provided them. The circularity creates risk for everyone, but the controller bears the most direct exposure, as management’s name is on the representation letter.

Projections are often among the largest drivers of intangible asset values in middle-market PPAs. A controller who declines to engage with projection development is not saving time. They are ceding control over numbers that will determine amortization expense, credit agreement addbacks, and the baseline for future goodwill impairment testing.

Building the Opening Balance Sheet: Judgment at the Center of Competing Interests

Once the projections produce asset values, those values must be assembled into an opening balance sheet. Controllers run the risk of approaching the opening balance sheet as a mechanical output: the valuation firm provides numbers, the controller books entries. In practice, it involves a series of judgment calls affecting multiple stakeholders, and the controller sits at the center without formal authority over any of them.

The PE sponsor cares about the split between goodwill and amortizable intangibles because it directly affects credit agreement mechanics. A higher allocation to identified intangibles often increases amortization expense and reduces reported net income, but many credit agreements add purchase accounting amortization back to adjusted EBITDA, muting the income statement impact. The tax picture pulls the other direction: amortizable intangibles generate a shield under IRC §197 over fifteen years, meaning a higher intangible allocation can increase after-tax cash flow even as it compresses pre-tax earnings. The controller needs to understand both dimensions, because preferences may not align with the most defensible accounting outcome or the optimal tax result.

The auditor’s valuation specialist occupies different ground and is focused on whether the allocation is supportable under ASC 805 and ASC 820, whether valuation methods are appropriate, and whether the inputs withstand scrutiny. If the specialist concludes that an intangible has been undervalued or goodwill overstated relative to identifiable assets, the controller faces a late-stage adjustment that cascades through the financial statements.

ASC 805 provides a measurement period of up to one year to finalize the allocation. Provisional allocations let the controller issue timely financial statements while complex valuation issues resolve, and measurement period adjustments provide flexibility to refine amounts as better information emerges. But the measurement period is not a grace period. Auditors track provisional items closely, and sponsors can expect convergence toward a final allocation within the first two reporting cycles. Controllers who lean on provisional estimates without a clear resolution timeline lose credibility.

Why Purchase Price Allocation Delays Cascade Into Audit and Reporting Failures

The PPA often sits on the critical path of post-acquisition reporting, and its dependency chain can be unforgiving. The valuation cannot get to reliable conclusions until the controller provides projections and supporting data: customer lists, contract details, technology documentation, fixed asset inventories. The valuation must be substantially complete before the auditor’s specialist can review it. That review must clear before the financial statements can be issued. In middle-market PE deals, the typical window from year-end to audited financials is 90 to 120 days. When the acquisition closes in Q3 or Q4, the PPA and the year-end audit run simultaneously, and the PPA is frequently the pacing item.

Some first-time controllers face the risk of underestimating the time required to compile the valuation firm’s data request. Customer revenue detail by account, going back three to five years, may not exist in the format the valuation model requires. Contract summaries may need to be assembled manually. Technology documentation is rarely organized for a separability analysis. What looks like a two-week exercise on paper takes four to six weeks when the controller is simultaneously managing month-end close, integration workstreams, and sponsor reporting.

Downstream effects compound quickly. A valuation report delivered two weeks late pushes the specialist’s review into the final days before the reporting deadline. Compressed timelines produce more questions, not fewer, and specialists working under time pressure ask broader, more conservative questions, generating additional work for the controller.

In the worst case, the controller issues financial statements with a provisional allocation requiring measurement period adjustments in subsequent quarters, each requiring adjustment to the provisional amounts on the opening balance sheet and recognition of catch-up effects, along with additional audit procedures. The cost is not just compliance. Delays run the risk of eroding the controller’s credibility with the sponsor at the moment they are establishing their reputation under new ownership.

Mastering the Purchase Price Allocation as a Controller

The controller is the person whose name appears on the representation letter, who fields questions when assumptions don’t reconcile, and who explains to the operating partner why the audit is delayed because the valuation isn’t final. The pragmatic move is to treat PPA literacy as a core competency. The best controllers learn this once and build a repeatable framework.

It’s equally important to recognize that the process rises or falls on the quality of the valuation partner you choose. A credible, qualified valuation firm drives the timeline, pressure-tests assumptions, anticipates auditor scrutiny, and translates operating reality into defensible fair value conclusions. That leverage matters in every deal.

The controllers who perform well will take three steps before or immediately after close. First, request a PPA kickoff meeting with the valuation firm within the first two weeks, including a detailed data request list and a milestone timeline mapped against audit fieldwork. Second, build asset-specific projection frameworks before the valuation firm asks: at minimum, a customer revenue bridge with attrition assumptions and a trade name (or other IP) revenue isolation. Third, establish direct communication with the auditor’s valuation specialist early, rather than waiting for review comments to surface disagreements months later.

The PPA is the first financial test of the new ownership structure, and the controller’s command of it establishes credibility with the sponsor, and with every auditor, lender, and board member who will rely on that balance sheet for years.

1. “Audit Committee Dialogue,” Public Company Accounting Oversight Board, webpage, May 2015.