Skip to content

Deal economics

Can you put company data on the balance sheet?

By SourceX Editorial · Reviewed by Noah Loul ·

Short answer

Generally, no: company data created through your own operations stays off the balance sheet under US GAAP, because the costs of producing it are expensed as incurred. Data acquired in a business combination or bought from a third party can be recognized as an intangible asset. Owners usually realize internal data's value through licensing revenue instead.

Key takeaways

  • Internally generated data, such as support tickets or job records, is generally not recognized as an asset under US GAAP.
  • Data acquired in a business combination can be recognized at fair value as an identifiable intangible when it meets the recognition criteria.
  • An appraisal or valuation report does not change how internally generated data is recorded.
  • Licensing revenue, signed contracts and documented rights are how internal data shows up in the numbers investors read.
  • Disclosure can describe record families, history and rights without assigning the records a value.

Can company data go on the balance sheet?#

Company data generally cannot go on the balance sheet when the company created it itself. Under US GAAP, the costs of developing and maintaining intangibles internally are generally expensed as incurred, so the support tickets, CRM histories and job records your teams built carry no book value.

Data reaches the balance sheet in two main situations: when it is acquired as part of a business combination, and when it is purchased or licensed in from a third party on terms that create an asset. In both cases a transaction sets a cost or a fair value.

The gap between book value and economic value is common for intangibles generally. Brands, customer relationships and know-how built internally are also usually missing from the balance sheet.

Why internally generated data stays off#

Internally generated data stays off because its cost cannot be separated reliably from the cost of running the business. ASC 350-30-25-3 requires costs of internally developing, maintaining or restoring intangibles that are not specifically identifiable, have indeterminate lives or are inherent in a continuing business to be expensed when incurred. The salaries, systems and time that produced years of dispatch records were spent to serve customers, not to build a data asset, and the accounting treats them that way.

Measurement is the other obstacle. Without a transaction there is no reliable figure for what the records are worth, and estimates based on hoped-for licensing revenue are not the kind of evidence recognition requires.

Some related costs can be capitalized. Under the internal-use software rules, certain costs of building the systems that store and process data may qualify. The records inside those systems still do not.

When data does appear as an asset#

Data appears as an asset when a transaction gives it a measurable cost or fair value. The table summarizes common situations; the right treatment depends on the contract and should be confirmed with your accountants.

When data does appear as an asset
SituationTypical treatmentWhat to check
Records created in your own operationsNot recognized; costs expensedWhether any system development costs qualify for capitalization
Dataset purchased outright from a third partyMay be recognized as an intangible asset at costOwnership, useful life and impairment indicators
Dataset licensed in for your own useDepends on terms; may be an asset, a prepayment or an expenseWhether the contract is a license, a service or a hosting arrangement
Database acquired in a business combinationMay be recognized at fair value apart from goodwillWhether it arises from legal rights or can be separated
Your records licensed out to a buyerNo asset created; license fees recorded as revenueRecognition timing and any continuing delivery obligations

What happens to data in an acquisition#

In an acquisition, the buyer measures identifiable intangible assets at fair value under ASC 805, and an intangible is recognized separately from goodwill when it arises from contractual or legal rights or is separable. The Codification's illustrative examples list databases, including title plants, among technology-based intangibles and customer lists among customer-related intangibles. Anything not recognized separately folds into goodwill.

That is why the same records can be off one company's books and on another's. The seller never recorded its support archive; the acquirer may record it in its purchase price allocation if valuation specialists can identify and measure it.

Licensing history helps here. A record of licenses granted for a body of records is evidence that it can be separated and licensed and that buyers will pay for it, which supports both recognition and measurement in the acquirer's allocation.

Book value is not economic value#

Book value and economic value diverge sharply for data, and experienced investors know it. A company with no data on its balance sheet can still command a better price because its records support products, pricing decisions or licenses.

For an owner, licensing is the practical way to turn that economic value into reported results. License fees appear as revenue, the contracts can be shown to buyers and lenders, and diligence teams can test them. A valuation report alone does none of that.

Explaining why the records matter in qualitative terms is more credible than offering a number you cannot support. Describe what the records capture, how far back they go and what rights you hold, and let signed contracts carry the figures.

What disclosure can say instead#

Disclosure can describe data accurately without putting a figure on it. In board packs, investor updates, lender reports and sale documents, describe what the records are and how they are controlled, and keep valuation language out unless a qualified valuation supports it.

Keep the language consistent with the financial statements. If the statements carry no data asset, a separate document that implies one invites questions from auditors and buyers.

  • Record families held, such as support tickets, CRM activity, dispatch records or quality logs
  • Years of history still accessible and the systems that hold them
  • Rights status: customer contract terms, vendor terms and known restrictions
  • Licenses granted, their scope and whether any are exclusive
  • Licensing revenue recognized, presented consistently with the financial statements
  • Privacy and preparation controls applied before any release

Illustrative: a distributor's board asks to book its data#

Illustrative: a fictional industrial distributor runs on Epicor with years of order histories, return authorizations and customer service email threads. After reading about AI developers' interest in operational records, a board member asks the CFO to record the archive as an asset.

The CFO explains that internally generated records are not recognized and that an appraisal would not change that. Instead, the company builds an inventory of record families, years and restrictions, adds a short data section to the board pack, and starts a metadata-only fit check on whether the records could be licensed.

When the company later signs a non-exclusive license, the fees are recognized as revenue under its policy, and the board pack reports the license and its scope. The balance sheet is unchanged; the value is now visible in a contract and in revenue.

How SourceX frames data value#

SourceX frames data value with the SourceX Enterprise Data Value Framework, a SourceX-developed qualitative methodology rather than an accounting or industry standard. It treats uniqueness, domain expertise, human-generated signal, scale, recency, data cleanliness, rights and AI utility as drivers that increase value, exclusivity as a driver that increases price, reproducibility as a factor that reduces value, and preparation cost and privacy burden as factors that reduce net value.

The framework publishes no prices or index values and does not produce a figure for a balance sheet. Value becomes concrete only when a buyer engages and a license is signed.

Frequently asked questions

Can a third-party appraisal let us book our data as an asset?

No. An appraisal can inform a sale, a financing or a tax position, but it does not change the accounting for internally generated intangibles. The records stay off the balance sheet unless a transaction, such as an acquisition of the company, creates a recognized asset.

Can lenders lend against our data?

Some loan agreements include intangibles, including data and IP, in the collateral package, but whether a lender will advance funds based on data is a separate credit decision. The credit agreement may also restrict licensing the records, so check its covenants before signing a license.

Are the costs of preparing data for a license capitalized?

It depends on the costs and the contract. Some costs to fulfill a contract can be capitalized when specific criteria are met, while most internal preparation work is expensed. Ask your accountants to set a policy before the first license so the treatment is consistent.

Are purchased datasets amortized?

Generally, a purchased dataset recognized as an intangible asset with a finite useful life is amortized over that life and tested for impairment when indicators arise. Records can go stale quickly, so your accountants should set the life and method based on how long the data is expected to produce benefits.

Does licensing data out reduce an asset on our books?

No, because internally generated data was never recorded. Licensing can still affect economic value: an exclusive or long license limits what you can do with the records later, and an acquirer will weigh that when valuing the business.

Does IFRS treat internal data differently?

IFRS reaches a broadly similar result. IAS 38 expenses research costs and capitalizes development costs only when six criteria are met, and paragraph 63 bars recognition of internally generated brands, mastheads, publishing titles, customer lists and items similar in substance. Companies that report under IFRS, or expect a foreign acquirer, should confirm treatment with accountants who work in both frameworks.

Sources

  • ASC 350-30-25-3 requires costs of internally developing, maintaining or restoring intangible assets that are not specifically identifiable, have indeterminate lives, or are inherent in a continuing business and related to the entity as a whole to be expensed when incurred. Source
  • Under ASC 805, an intangible asset acquired in a business combination is recognized separately from goodwill if it arises from contractual or legal rights or is separable; illustrative examples list databases, including title plants, and customer lists. Source
  • IAS 38 expenses research costs and capitalizes development costs only if six criteria are met; paragraph 63 bars recognition of internally generated brands, mastheads, publishing titles, customer lists and items similar in substance. Source

Related resources

See if your company qualifies

A short company assessment. No data uploads are needed.

See if you qualify