The cost benefit principle is the rule that financial information should be required and produced only where the benefits of reporting it justify the costs of providing and using it. It is not one of the qualities that make information useful, it is a limit that sits over all of them, which is why the US framework calls it the cost constraint rather than a characteristic. The constraint is applied when a reporting requirement is written, and the body that applies it is the standard setter.
Where the Principle Is Written Down
The Financial Accounting Standards Board states it in two sentences at the top of its own section on the subject. Cost is a pervasive constraint on the information that can be provided by financial reporting, and reporting financial information imposes costs, and it is important that those costs are justified by the benefits of reporting that information (FASB Statement of Financial Accounting Concepts No. 8, Chapter 3 (As Amended), paragraph QC35).
The same chapter had already placed it. The qualitative characteristics of useful financial information apply to financial information provided in financial statements, as well as to financial information provided in other ways, and cost, which is a pervasive constraint on the reporting entity’s ability to provide useful financial information, applies similarly (the same chapter, paragraph QC3). The characteristics the constraint is weighed against are relevance and faithful representation, plus the four that enhance those two, and what the enhancing four can and cannot do is set out in understandability.
Whose Costs, and Whose Benefits
The costs are not the preparer’s bookkeeping bill, and reading them that way is the most common mistake made with this principle. The framework counts four flows, and only the first sits with the preparer.
- Providers of financial information expend most of the effort involved in collecting, processing, verifying and disseminating financial information.
- Users ultimately bear those costs, in the form of reduced returns.
- Users of financial information also incur costs of analyzing and interpreting the information provided.
- If needed information is not provided, users incur additional costs to obtain that information elsewhere or to estimate it (FASB Concepts Statement No. 8, Chapter 3 (As Amended), paragraph QC36).
The last of those is what stops the principle collapsing into an argument for reporting less. Withholding information does not remove the cost of producing it, it moves that cost onto the people who now have to estimate what they were not told.
On the benefit side the framework claims something wider than a better decision for one reader. Reporting information that is relevant and faithfully represents what it purports to represent helps users make decisions with more confidence, and that results in more efficient functioning of capital markets and a lower cost of capital for the economy as a whole, though it is not possible for general purpose financial reports to provide all the information that every user finds relevant (paragraph QC37).
The Test Belongs to the Board, Not to Your Ledger
This is the part the short definitions leave out, and the framework is explicit about it.
In applying the cost constraint, the Board assesses whether the benefits of reporting particular information are likely to justify the costs incurred to provide and use that information, and in developing a proposed standard it seeks information from providers, users, auditors, academics and others about the expected nature and quantity of those benefits and costs (paragraph QC38).
Then the scope of the assessment, stated directly. Because of the inherent subjectivity, different individuals’ assessments of the costs and benefits of reporting particular items will vary, so the Board seeks to consider costs and benefits in relation to financial reporting generally, and not just in relation to individual reporting entities (paragraph QC39).
So the principle is not a switch a preparer throws in its own ledger. The weighing that could have justified an exemption is done once, at the level of financial reporting as a whole, and it is done before the requirement is written. The same constraint applied specifically to what the notes have to carry is covered in the full disclosure principle.
Where Entity-Level Differences Are Allowed
The constraint does allow the answer to differ between entities. It just does not let the entity be the one who decides.
That does not mean assessments of costs and benefits always justify the same reporting requirements for all entities, and differences may be appropriate because of different sizes of entities, different ways of raising capital, publicly or privately, different users’ needs, or other factors (paragraph QC39).
That sentence is the conceptual authority for every scaled requirement in US GAAP. Where a private company reports less than a public one, the differential was written into the standard by the body that applied the constraint, not claimed by the company afterwards.
What the Cost Benefit Principle Is Not
Materiality
The two get run together because both end in something being left out, and the framework separates them on exactly the ground the section above set out. A standard setter does not consider materiality when developing standards because it is an entity-specific consideration, so entity-specific assessments of materiality are not directly relevant to the Board’s assessments, and the Board instead evaluates the potential relevance of its guidance in the context of a broader financial reporting environment rather than on the materiality of the information to individual entities (FASB Concepts Statement No. 8, Chapter 3 (As Amended), paragraph BC3.18). Materiality is the entity’s test and the cost constraint is the Board’s, and the entity-specific one sits in materiality.
Cost-Benefit Analysis
Cost-benefit analysis is a decision framework that prices both sides of a choice in money and compares them, and it is used to appraise projects rather than to write reporting requirements. Its two decision criteria and the discounting behind them are in cost-benefit analysis. The shared name is a coincidence of vocabulary, not a shared method.
Common Questions
The rule that financial information is required only where its benefits justify the costs of providing and using it. The framework calls it the cost constraint, treats it as pervasive across all financial reporting, and applies it when standards are set.
Not as a licence to skip a requirement that already exists. A business does weigh cost against benefit constantly in choosing how much internal detail to keep, which systems to buy and how granular its own reporting should be, and none of that is governed by this principle. The principle governs what the standard setter asks for.
Because it does not make information better. Relevance and faithful representation describe what useful information looks like, and cost describes the limit on how much of it can be demanded, so it applies to the whole set rather than sitting inside it.
Accountably places trained offshore accountants and tax preparers inside US CPA and EA firms, and a firm can grade a real block of that work on its own files through a trial task before any client file moves.
