FAR U.S. GAAP Hierarchy and FASB Codification Research Skills

FAR expects you to know where U.S. GAAP authority comes from and how an accountant researches a transaction without relying on memory alone. The practical skill is not memorizing every Codification paragraph. It is knowing how to define an accounting issue, find the relevant guidance, confirm the guidance applies, and document the conclusion.

The FASB Accounting Standards Codification is the central authoritative source for nongovernmental U.S. GAAP. Other materials can explain, summarize, or interpret accounting issues, but the final answer for a U.S. GAAP reporting question should be traced back to authoritative guidance.

Authoritative Guidance Map

The modern U.S. GAAP hierarchy is much simpler than the historical pre-Codification hierarchy. For nongovernmental entities, the Codification organizes authoritative GAAP into a single searchable structure. Accounting Standards Updates amend that structure rather than standing alone as permanent independent guidance.

For FAR, treat the Codification as the rule source and the Conceptual Framework as support for why rules are built the way they are.

Codification Structure

The Codification is organized from broad subject matter to specific paragraphs. The standard citation pattern is:

1Topic-Subtopic-Section-Paragraph

For example, a citation such as 350-20-35-30 points to Topic 350, Subtopic 20, Section 35, Paragraph 30.

    flowchart TB
	    A["FASB Accounting Standards Codification"] --> B["Topic"]
	    B --> C["Subtopic"]
	    C --> D["Section"]
	    D --> E["Paragraph"]
	    D --> F["Implementation guidance and illustrations"]

The Section level is especially important. Many errors occur because a candidate reads measurement guidance without first checking the scope section.

Research Workflow

Accounting research should be structured. A random keyword search can find useful text but still produce the wrong answer if the transaction is outside the scope of the topic.

The first step is defining the accounting issue. Searching before defining the issue can lead to a technically related paragraph that does not answer the actual question.

Scope Comes First

Scope is the gatekeeper. If a transaction is outside the scope of a topic, the remaining recognition, measurement, and disclosure sections may not apply.

FAR simulations may provide a Codification-style excerpt. Start by deciding whether the facts fit the scope before selecting the paragraph that sounds most familiar.

Example: Internal-Use Software Research

Assume a company is developing software for its own accounting department. Management asks whether programming costs should be expensed or capitalized.

A disciplined research approach would be:

1. Define the issue: accounting for costs of software developed for internal use.
2. Identify facts: internal use, development stage, nature of costs, and reporting period.
3. Search likely guidance: software, internal use, capitalization, application development stage.
4. Check scope: confirm the software is not intended for sale to customers.
5. Review recognition guidance: distinguish preliminary project stage, application development stage, and post-implementation activities.
6. Document conclusion: cite the relevant topic, subtopic, section, and paragraph references used.

The answer depends heavily on stage and use. A generic statement that “software costs can be capitalized” is not enough.

Example: Factoring Receivables Research

Assume a company transfers receivables to a finance company and receives cash. Management asks whether the transfer is a sale or a secured borrowing.

The research should focus on transfer and servicing guidance, then ask whether control of the receivables has been surrendered. The analysis usually considers legal isolation, the transferee’s ability to pledge or exchange the assets, and whether the transferor maintains effective control.

If control is not surrendered, the transaction is generally treated as a secured borrowing rather than a sale. This is a common FAR application of research to classification.

SEC and Public-Company Overlay

Public-company questions may require attention to SEC reporting requirements in addition to Codification guidance. SEC rules do not replace FASB accounting guidance for every issue, but they can add presentation, disclosure, filing, or public-company requirements.

The exam trap is applying public-company SEC rules to every entity or ignoring public-company facts when the question explicitly gives them.

Documentation Standard

A research conclusion should show the path from facts to authority. A concise memo does not need to quote large blocks of guidance. It should identify the question, facts, authoritative references, analysis, conclusion, and any disclosure implications.

Documentation matters because many accounting issues are not solved by a single sentence. If facts change, the conclusion may change.

Common Exam Traps

Key Takeaways

• The FASB Codification is the primary authoritative source for nongovernmental U.S. GAAP.
• ASUs update the Codification; they are not usually the end point of research after incorporation.
• The Codification is organized by Topic, Subtopic, Section, and Paragraph.
• Scope analysis comes before recognition, measurement, and disclosure analysis.
• Good research defines the issue, checks facts, follows cross-references, and documents paragraph-level support.

Quiz: GAAP Hierarchy and Codification Research