ASC 805 Purchase Price Allocation Case Study: SaaS Acquisition With Customer Relationships & Developed Technology

Completing a SaaS acquisition is only the beginning of the financial reporting process.

After the transaction closes, the acquirer may need to determine the acquisition-date fair value of the assets acquired and liabilities assumed under ASC 805, Business Combinations.

For technology acquisitions, this process can become particularly complex.

Much of the value being acquired may not appear as tangible assets on the target company’s historical balance sheet. Instead, value may reside in:

• existing customer relationships;
• developed software and technology;
• trade names;
• contractual relationships;
• backlog;
• other identifiable intangible assets; and
• goodwill.

The difficult part is not simply identifying these assets.

The valuation team must determine which assets should be recognized separately, which valuation methodologies are appropriate, what assumptions can be supported, and how the resulting values reconcile with the economics of the transaction.

This representative case study illustrates how an ASC 805 purchase price allocation could be approached for a hypothetical U.S. SaaS acquisition.

Important: This is an illustrative representative case study. The company, transaction amounts and valuation results below are hypothetical and are intended to demonstrate the analytical process. They do not represent a specific Synpact client engagement.

Engagement Snapshot

Industry: B2B SaaS / Enterprise Software
Transaction: 100% acquisition
Buyer: U.S.-based strategic acquirer
Target: Privately held SaaS company
Purchase Consideration: $120 million
Reporting Framework: U.S. GAAP
Primary Requirement: Purchase Price Allocation under ASC 805
Key Intangible Assets: Customer relationships, developed technology and trade name
Primary Complexity: Recurring subscription revenue, customer attrition, technology valuation and reconciliation of identifiable assets to goodwill

The acquirer needed an acquisition-date PPA that could support financial reporting and subsequent auditor review.

For companies facing similar requirements, Synpact’s Business Combination & Purchase Price Allocation Services support the identification and valuation of acquired tangible and intangible assets under applicable financial reporting frameworks.

The Transaction

Assume a strategic software company acquires a B2B SaaS provider for total consideration of:

$120 million

The target generates recurring subscription revenue from approximately 900 enterprise and mid-market customers.

At the acquisition date, the target has:

• approximately $30 million of annual recurring revenue;
• high gross margins;
• proprietary developed software;
• an established customer base;
• a recognizable niche brand;
• positive operating cash flow; and
• meaningful expected growth.

The buyer expects the acquisition to strengthen its product offering, expand its customer base and create cross-selling opportunities.

But those strategic expectations do not eliminate the need to separately identify and value acquired assets for financial reporting.

The headline purchase price must be analyzed.

Why the Purchase Price Cannot Simply Be Recorded as Goodwill

Before the acquisition, many internally developed intangible assets may not have been separately recorded at fair value on the target’s balance sheet.

After a business combination, however, acquisition accounting requires an analysis of identifiable assets acquired and liabilities assumed.

For a SaaS company, potentially significant intangible assets can include:

• developed technology;
• customer relationships;
• customer contracts;
• trade names and trademarks;
• backlog;
• non-compete agreements; and
• other contractual or separable intangible assets.

Whatever residual remains after the relevant identifiable net assets are recognized generally contributes to goodwill.

Therefore, a $120 million acquisition does not mean:

Purchase Price = $120M Goodwill

Instead, the analytical framework is closer to:

Purchase Consideration
– Fair Value of Identifiable Net Assets
= Residual Goodwill

That makes the valuation of identifiable intangible assets one of the most important parts of the PPA.

Step 1: Understand the Purchase Consideration

The first step is determining what consideration was transferred in the transaction.

Consideration can potentially include:

• cash paid at closing;
• equity issued;
• deferred payments;
• contingent consideration;
• earnouts; and
• other components depending on transaction terms.

For simplicity, assume the illustrative transaction has acquisition-date consideration of:

$120 million

In a real engagement, the valuation and accounting teams would review the underlying transaction documents rather than relying only on the headline deal value.

Relevant documents may include:

• purchase agreement;
• closing statement;
• merger agreement;
• earnout provisions;
• rollover equity documentation;
• debt payoff schedules; and
• other transaction-related agreements.

The objective is to establish the appropriate acquisition-date consideration before allocating it.

Step 2: Review the Closing Balance Sheet

The next step is understanding the assets and liabilities acquired.

Assume the preliminary analysis identifies net tangible assets with an illustrative fair value of:

Item	Illustrative Fair Value
Cash	$6.0M
Accounts Receivable	$5.0M
Other Current Assets	$2.0M
Property & Equipment	$1.5M
Other Assets	$0.5M
Accounts Payable & Accrued Liabilities	($4.0M)
Other Assumed Liabilities	($3.0M)
Illustrative Net Tangible Assets	$8.0M

These amounts are simplified for illustration.

In an actual PPA, book value and fair value may differ, and individual assets and liabilities may require separate analysis.

Step 3: Identify the Acquired Intangible Assets

For this hypothetical SaaS transaction, the valuation team evaluates the sources of economic value associated with the acquired business.

After reviewing the transaction documents, management interviews, customer data, technology information and business model, assume three material identifiable intangible asset categories are selected for valuation:

1. Customer Relationships

The target has an established base of recurring subscription customers expected to continue generating revenue after the acquisition.

2. Developed Technology

The company’s existing software platform supports its products and revenue generation.

3. Trade Name

The target operates under an established name with recognition within its niche market.

Other potential intangible assets would still need to be considered based on the transaction facts.

The objective is not to force every possible intangible into the PPA.

The objective is to identify the assets supported by the economics, contractual rights and applicable accounting requirements of the specific acquisition.

Synpact’s broader Valuation Services include financial-reporting valuations involving customer relationships, technology, intellectual property and other intangible assets.

Step 4: Value the Customer Relationships

For many SaaS acquisitions, customer relationships can represent one of the most significant acquired intangible assets.

Why?

Because the buyer is not starting with zero customers on Day 1.

It acquires an installed customer base capable of generating future subscription revenue.

But the valuation cannot simply take current customer revenue and apply a revenue multiple.

The analysis needs to isolate the economic benefits attributable specifically to existing customers at the acquisition date.

Using the Multi-Period Excess Earnings Method

One method commonly considered for customer-related intangible assets is the Multi-Period Excess Earnings Method, or MPEEM.

Conceptually, MPEEM estimates the present value of future economic benefits attributable to the subject intangible asset after recognizing the economic returns required by other assets that contribute to those cash flows.

For this case study, assume the acquired existing customer base generates:

$25 million of acquisition-date annualized revenue

The analysis then considers how much of that revenue is expected to remain over time.

Customer Attrition: One of the Most Important Assumptions

Existing customers do not remain forever.

Some customers may:

• cancel;
• fail to renew;
• reduce spending;
• switch providers;
• merge with other companies; or
• otherwise stop generating revenue.

Therefore, customer retention or attrition can have a major impact on the customer-relationship value.

Assume historical cohort analysis indicates approximately:

90% annual revenue retention from the existing customer population

A simplified illustration might look like:

Year	Illustrative Existing-Customer Revenue
Year 1	$25.0M
Year 2	$22.5M
Year 3	$20.3M
Year 4	$18.2M
Year 5	$16.4M

The actual analysis could be considerably more detailed.

For example, SaaS businesses may have different retention characteristics by:

• enterprise vs. SMB customers;
• geography;
• product;
• contract type;
• customer tenure;
• annual vs. monthly contracts;
• customer cohort; or
• revenue size.

That is why good customer data can materially improve a PPA.

Existing Customers vs. Future Customers

A particularly important analytical distinction is separating value attributable to customers that already exist at the acquisition date from value associated with customers acquired in the future.

Suppose management forecasts total company revenue increasing substantially over the next five years.

Not all of that growth belongs to the acquired customer-relationship asset.

Some future revenue may come from new customers acquired after the transaction.

That future customer acquisition may instead relate to other assets, future marketing efforts, workforce activities or goodwill.

A customer-relationship valuation therefore should not simply take the company’s entire future revenue forecast and label it “customer relationships.”

The cash flows must be appropriately attributed.

Contributory Asset Charges

Customer relationships do not generate cash flow in isolation.

They may require support from:

• working capital;
• developed technology;
• fixed assets;
• trade names;
• assembled workforce; and
• other supporting assets.

Under an excess-earnings framework, contributory asset charges (CACs) may be used to recognize the economic return required by these supporting assets.

Conceptually:

Customer Revenue
– Operating Costs
– Taxes
– Contributory Asset Charges
= Excess Earnings Attributable to Customer Relationships

Those excess earnings can then be discounted to present value using an appropriate rate.

If contributory assets are ignored, the model may attribute economic value to customer relationships that actually belongs to other assets.

Customer Relationship Discount Rate

The discount rate should reflect the risk associated with the relevant cash flows.

A common review issue occurs when one discount rate is applied mechanically across:

• the overall company;
• customer relationships;
• developed technology;
• trade names; and
• other intangible assets.

Different assets can have different risk characteristics.

The selected discount rate should therefore be considered within the broader transaction economics and valuation framework.

Illustrative Customer Relationship Conclusion

Assume the analysis produces an acquisition-date fair value for customer relationships of:

$24 million

Again, this amount is illustrative.

The important point is how the conclusion is reached:

Existing customer revenue → attrition → margins/costs → contributory asset charges → taxes → discounting → customer relationship fair value

A defensible report should allow an independent reviewer to follow that analytical chain.

Step 5: Value the Developed Technology

For a SaaS business, developed technology may be another major source of value.

The acquired technology could include:

• source code;
• software architecture;
• proprietary algorithms;
• applications;
• APIs;
• databases;
• platform functionality; and
• other technical intellectual property.

The key question is:

What economic benefit does ownership of the existing developed technology provide at the acquisition date?

Selecting a Developed Technology Valuation Method

The appropriate methodology depends on the facts.

Potential approaches can include income-based techniques or, in certain circumstances, cost-based techniques.

For this illustrative case, assume an income-based analysis is considered appropriate because the technology is integral to revenue generation.

One possible framework may estimate the economic benefit associated with owning the technology rather than licensing comparable technology from a third party.

Relevant assumptions could include:

• revenue associated with the technology;
• royalty-rate evidence;
• remaining economic life;
• technology obsolescence;
• maintenance requirements;
• taxes;
• discount rate; and
• future replacement or migration expectations.

Technology Obsolescence Matters

Technology assets are particularly sensitive to economic-life assumptions.

Software can become obsolete because of:

• product innovation;
• competitor development;
• platform migration;
• changing customer requirements;
• cybersecurity requirements;
• regulatory changes; or
• the buyer’s own product-integration roadmap.

A technology asset may continue to function technically while its economic value declines.

Therefore, useful-life analysis should not simply ask:

“How long can the software operate?”

It should ask:

“For how long is the existing technology expected to generate identifiable economic benefits?”

Illustrative Developed Technology Conclusion

Assume the developed technology analysis produces a fair value of:

$30 million

The report would document the selected methodology, underlying assumptions, supporting market evidence and sensitivity of the conclusion to significant inputs.

Step 6: Value the Trade Name

The acquired company has established recognition in a specialized software market.

Assume management expects to continue using the acquired brand for a period following the transaction.

A trade-name valuation may consider a Relief-from-Royalty framework.

Conceptually, the method asks:

What royalty payment could a market participant avoid by owning the trade name rather than licensing it?

The analysis may consider:

• revenue associated with the brand;
• comparable licensing arrangements;
• royalty-rate selection;
• expected remaining economic life;
• taxes; and
• an appropriate discount rate.

Assume the resulting illustrative fair value is:

$6 million

Step 7: Reconcile the PPA

At this point, the simplified allocation looks like this:

Asset Category	Illustrative Fair Value
Net Tangible Assets	$8M
Customer Relationships	$24M
Developed Technology	$30M
Trade Name	$6M
Total Identifiable Net Assets	$68M
Residual Goodwill	$52M
Total Purchase Consideration	$120M

This reconciliation is fundamental.

The valuation team should be able to explain both:

1. why value was attributed to each identifiable asset; and
2. why the remaining amount is reflected as goodwill.

What Does the $52 Million of Goodwill Represent?

Goodwill should not automatically be interpreted as an error or an unexplained plug.

Depending on the transaction, goodwill may reflect economic benefits that are not separately recognized as identifiable intangible assets.

These may include:

• expected synergies;
• assembled workforce;
• future customers;
• future technology development;
• broader strategic benefits;
• expansion opportunities; and
• other elements of going-concern value.

However, an unusually high goodwill balance can also cause reviewers to ask whether identifiable intangible assets were missed or undervalued.

That is why intangible-asset identification and valuation deserve careful attention.

Step 8: Perform a WARA Reasonableness Check

A purchase price allocation should not be evaluated only asset by asset.

The overall economics should also make sense.

One potential reasonableness procedure is a Weighted Average Return on Assets (WARA) analysis.

Conceptually, WARA evaluates the weighted required returns associated with the various asset categories and can be compared with the economics implied by the overall business valuation.

Different assets generally carry different levels of risk.

For example:

• working capital may require a relatively low return;
• fixed assets may require a different return;
• customer relationships may carry higher risk;
• technology may carry another risk profile;
• goodwill generally reflects residual business risk.

The purpose is not to force WARA to equal a particular number mechanically.

It is to identify whether the asset-specific returns appear internally consistent with the transaction’s overall economics.

Step 9: Reconcile the PPA With the Deal Model

Another important review is comparing the PPA with the financial analysis used to approve the acquisition.

Suppose the buyer’s investment committee approved the transaction based on:

• 20% annual revenue growth;
• improving EBITDA margins;
• $8 million of expected cost synergies;
• cross-selling opportunities; and
• a specific long-term margin profile.

But the PPA uses:

• 8% revenue growth;
• no synergies;
• materially different margins; and
• a completely different long-term forecast.

That difference is not automatically wrong.

Accounting valuation may require different treatment of certain buyer-specific assumptions.

But significant differences should be understood and documented.

A reviewer may reasonably ask:

Why was the company worth $120 million to the buyer if the PPA assumptions imply materially different economics?

A strong valuation file should be prepared to answer that question.

Step 10: Assess the Impact on Future Financial Statements

The PPA does not end on the acquisition date.

Recognized intangible assets can affect future financial reporting.

Assume:

• Customer Relationships = $24M
• Developed Technology = $30M
• Trade Name = $6M

If these assets are determined to have finite useful lives, amortization expense may affect future reported earnings.

Therefore, the allocation between:

identifiable intangible assets vs. goodwill

can influence the post-acquisition financial statements.

This is one reason CFOs should understand the PPA rather than treating it as a compliance report that only the auditors need to see.

Useful-Life Analysis: Why It Matters

Determining fair value is only part of the process.

Finance teams may also need to evaluate the useful lives of recognized intangible assets.

Factors may include:

Customer Relationships

• customer retention;
• contract duration;
• switching behavior;
• historical cohort life;
• competitive dynamics; and
• expected customer migration.

Developed Technology

• product roadmap;
• replacement cycle;
• technological obsolescence;
• maintenance requirements;
• integration plans; and
• competing technology.

Trade Name

• expected period of use;
• rebranding plans;
• market recognition; and
• brand integration strategy.

An unsupported useful-life assumption can affect amortization expense for years after the transaction closes.

What Could Auditors Challenge in This PPA?

An audit-ready PPA is not simply a valuation model with a final number.

Review questions can focus on the assumptions driving those numbers.

For this illustrative SaaS transaction, areas of scrutiny could include:

Customer Attrition

Why was 10% annual attrition selected?

Is it supported by historical cohorts?

Does revenue retention differ from logo retention?

New vs. Existing Customer Revenue

Does the MPEEM appropriately isolate cash flows from customers existing at the acquisition date?

Contributory Asset Charges

Which supporting assets were included?

How were their required returns determined?

Technology Royalty Rate

What market evidence supports the selected rate?

Are the licensing comparables genuinely relevant?

Economic Lives

Why is the customer relationship life appropriate?

How quickly could the technology become obsolete?

Discount Rates

Are asset-specific risks reflected consistently?

Forecasts

Do the projections reconcile with the transaction model and management’s operating plan?

Goodwill

Does the residual goodwill make economic sense given the expected synergies and future growth?

WARA

Are the asset returns internally consistent with the overall economics?

These questions demonstrate why the strongest PPA reports document reasoning, not merely calculations.

Common ASC 805 PPA Mistakes in SaaS Acquisitions

Mistake 1: Putting Too Much Value Into Goodwill

Failing to properly identify acquired intangible assets can leave an unsupported residual goodwill balance.

Mistake 2: Treating All SaaS Revenue as Customer Relationship Revenue

Future customers are not the same as customers acquired at closing.

Mistake 3: Using One Retention Rate Without Reviewing Cohort Data

Customer behavior can vary materially by segment.

Mistake 4: Ignoring Contributory Asset Charges

Customer relationships require other assets to generate economic benefits.

Mistake 5: Using the Same Discount Rate for Every Asset

Different assets can carry different economic risks.

Mistake 6: Using an Unsupported Technology Life

Technical functionality and economic usefulness are not necessarily the same.

Mistake 7: Failing to Reconcile With the Deal Model

Material differences between transaction assumptions and PPA assumptions should be understood.

Mistake 8: Treating Goodwill as a Plug

Residual goodwill should be explainable in the context of the acquisition economics.

Mistake 9: Starting the PPA Too Late

Data becomes harder to gather as deal teams move on and integration progresses.

Starting earlier can make management interviews, customer analysis and assumption development significantly more efficient.

Documents That Help Make a SaaS PPA More Efficient

A valuation team may request information such as:

Transaction Documents

• purchase agreement;
• closing statement;
• board or investment committee materials;
• deal model;
• due diligence reports; and
• earnout documentation.

Financial Information

• historical financial statements;
• trial balance;
• acquisition-date balance sheet;
• management forecasts;
• budget;
• revenue segmentation; and
• margin data.

Customer Information

• customer-level revenue;
• historical retention;
• churn;
• cohort analysis;
• contract terms;
• renewals; and
• customer concentration.

Technology Information

• product architecture;
• development history;
• R&D spending;
• product roadmap;
• expected replacement cycle; and
• technology dependencies.

Capital and Transaction Information

• debt;
• equity issued;
• deferred consideration;
• contingent consideration; and
• other relevant deal terms.

Providing organized data at the beginning of the engagement can reduce unnecessary back-and-forth later.

ASC 805 PPA Checklist for CFOs

Before sending a PPA to review, ask:

Transaction

• Is purchase consideration fully reconciled?
• Have contingent and deferred consideration components been evaluated?
• Is the acquisition date clearly established?

Assets and Liabilities

• Have acquired assets and assumed liabilities been identified?
• Were book-to-fair-value differences considered?
• Were potential off-balance-sheet intangibles evaluated?

Customer Relationships

• Is existing-customer revenue properly isolated?
• Is attrition supported?
• Are contributory asset charges documented?
• Is the discount rate supported?

Technology

• Is the valuation methodology appropriate?
• Is the economic life supportable?
• Is obsolescence considered?
• Are market assumptions documented?

Trade Name

• Is continued use expected?
• Is the royalty rate supported?
• Is the economic life consistent with integration plans?

Overall PPA

• Does the allocation reconcile to consideration?
• Is residual goodwill explainable?
• Has WARA or another reasonableness analysis been considered where appropriate?
• Do assumptions reconcile with transaction economics?
• Are sensitivity analyses available for significant assumptions?

Documentation

• Can an independent reviewer reproduce the logic?
• Are source documents retained?
• Are significant judgments explained?
• Are management assumptions clearly distinguished from valuation assumptions?

If several answers are “no,” the PPA may require additional analysis before review.

Why an Independent Valuation Specialist Can Help

A SaaS PPA brings together several disciplines:

• transaction accounting;
• business valuation;
• intangible asset valuation;
• financial modeling;
• market research;
• customer analytics;
• technology analysis; and
• audit documentation.

For a CFO already managing integration, reporting, close and audit requirements, performing the entire analysis internally can create a substantial workload.

An independent valuation specialist can help by providing a structured process for:

• intangible asset identification;
• customer relationship valuation;
• technology valuation;
• trade-name valuation;
• financial modeling;
• WARA analysis;
• sensitivity analysis;
• valuation documentation; and
• review support.
• Companies with broader acquisition and investment valuation needs can also explore Synpact’s Investment & Transaction Valuation Services.

How Synpact Consulting Supports ASC 805 Purchase Price Allocations

Synpact Consulting supports CFOs, finance teams, CPA firms, private equity portfolio companies and acquirers with financial-reporting valuation requirements.

Our Business Combination & Purchase Price Allocation Services can support:

• transaction consideration analysis;
• acquired intangible asset identification;
• customer relationship valuation;
• developed technology valuation;
• trade-name and trademark valuation;
• non-compete valuation;
• contingent consideration analysis;
• fair-value modeling;
• WARA and reasonableness testing;
• sensitivity analysis;
• goodwill reconciliation;
• valuation documentation; and
• responses to valuation-review questions.

The objective is not simply to allocate the purchase price.

It is to develop a transparent, supportable valuation analysis that finance teams and reviewers can follow from the underlying transaction data through the final conclusions.

Need an ASC 805 Purchase Price Allocation?

If your company recently completed an acquisition, waiting until the audit process begins to address the PPA can create unnecessary pressure.

A more efficient process starts by organizing:

• transaction documents;
• closing financials;
• forecasts;
• customer data;
• technology information; and
• relevant deal assumptions.

From there, the identifiable assets, valuation methodologies and documentation requirements can be assessed systematically.

Speak with Synpact Consulting about your ASC 805 purchase price allocation requirement.

Contact Synpact Consulting to discuss your acquisition, reporting timeline and valuation requirements.

Frequently Asked Questions

What is a purchase price allocation under ASC 805?

A purchase price allocation analyzes the acquisition-date assets acquired and liabilities assumed in a business combination, including identifiable intangible assets and residual goodwill, in accordance with the applicable financial-reporting requirements.

What intangible assets are common in a SaaS acquisition?

Depending on the transaction, common assets can include customer relationships, developed technology, trade names, customer contracts, backlog, non-compete agreements and other identifiable intangible assets.

How are customer relationships valued in an ASC 805 PPA?

An income-based methodology such as MPEEM may be considered depending on the facts. The analysis can incorporate existing-customer revenue, attrition, margins, contributory asset charges, taxes and an appropriate discount rate.

What is MPEEM?

The Multi-Period Excess Earnings Method estimates economic benefits attributable to a subject intangible asset after recognizing returns associated with other contributory assets required to generate those benefits.

What are contributory asset charges?

Contributory asset charges recognize the economic returns associated with supporting assets used to generate the cash flows attributed to the subject intangible asset.

How is developed technology valued in a PPA?

The appropriate method depends on the facts and characteristics of the technology. Income-based or, in some circumstances, cost-based techniques may be considered, with assumptions relating to economic benefit, obsolescence, useful life and risk.

What is goodwill in a purchase price allocation?

Goodwill generally represents the residual after the relevant identifiable acquired assets and assumed liabilities have been recognized and measured. Depending on the transaction, it can reflect expected synergies, assembled workforce, future growth and other economic benefits not separately recognized as identifiable intangible assets.

Why does PPA affect future earnings?

Finite-lived acquired intangible assets may be amortized over their useful lives. The values and useful lives assigned during the PPA can therefore affect post-acquisition financial reporting.

What information is needed for a SaaS PPA?

Common information includes transaction documents, closing financials, management forecasts, customer-level revenue and retention data, technology information, historical financial statements and details about the acquired assets and liabilities.

Can Synpact support an ASC 805 PPA that will be reviewed by external auditors?

Synpact provides audit-ready valuation and PPA support, including documented assumptions, valuation models, sensitivity analysis and supporting work papers designed for financial-reporting review requirements.

Final Takeaway

An ASC 805 purchase price allocation for a SaaS acquisition is not simply an exercise in dividing the purchase price between intangible assets and goodwill.

A strong PPA connects:

transaction economics → acquired assets → customer behavior → technology economics → valuation assumptions → identifiable asset values → goodwill → financial reporting.

For SaaS transactions, customer relationships and developed technology can be particularly important because small changes in attrition, economic life, margins, royalty rates, contributory asset charges or discount rates can materially affect the allocation.

That is why the quality of a PPA depends not only on the valuation model, but also on the quality of the underlying data, methodology and documentation.

Planning or reviewing an acquisition? Explore Synpact Consulting’s Purchase Price Allocation Services or contact the Synpact team to discuss your ASC 805 valuation requirements.