Federal GAAP Explained: Standards, Hierarchy & Key Differences

Federal financial reporting needs its own GAAP because the federal government is not a corporation and not a state government. Federal entities deal with things the private sector does not, like:

• budget authority and appropriations as a central operating constraint,

• intragovernmental activity at massive scale,

• sovereign responsibilities and unique federal missions.

FASAB was created to set standards built for those realities. The sponsors (Treasury, OMB, and GAO) jointly agreed to sponsor FASAB in 1990 through a memorandum of understanding.

FASAB develops the standards and guidance that constitute federal GAAP. The FASAB Handbook is the key “single source” to treat as authoritative.

AICPA Council designated FASAB as the body to establish accounting principles for federal government entities under the Accounting Principles Rule (the professional GAAP designation mechanism).

This is why an auditor can say an agency’s statements are “in conformity with GAAP” when they follow FASAB standards.

Not all “guidance” has the same authority. Federal GAAP includes a hierarchy that tells you what sources count first when you are resolving an accounting issue. FASAB incorporated that hierarchy into its authoritative literature in SFFAS 34.

Here is the hierarchy, from highest to lowest authority (as presented in SFFAS 34):

1. SFFAS and Interpretations

2. Technical Bulletins (and certain AICPA guides only if made applicable and cleared)

3. Technical Releases (AAPC technical releases)

4. FASAB staff implementation guides and widely recognized federal practice

If you are writing a position memo or responding to an auditor, cite your support in that order. If you start with “common practice” when a SFFAS answers the question, you are building your house on sand.

Federal GAAP gets confused with other federal reporting rules because federal reporting is a “stack” of authorities. Federal GAAP is one layer.

Federal GAAP is not:

• “whatever our agency manual says” (agency manuals should implement GAAP, not override it)

• “whatever format OMB requires” (format guidance is important, but it is not the GAAP standard setter)

• “whatever Treasury needs for a submission” (Treasury reporting rules support governmentwide compilation, but do not replace GAAP recognition rules)

This confusion is a top source of avoidable audit friction.

Treating a lower authority source as if it overrides a SFFAS
Fix: follow the SFFAS 34 hierarchy.

Using the wrong question for the wrong authority
Recognition and measurement = Federal GAAP (FASAB).
Reporting packaging and required report sections = reporting instructions.
Governmentwide submission mechanics = governmentwide reporting requirements.

Citing old stand-alone standards instead of the current Handbook
Fix: use the current FASAB Handbook as the authoritative source.

When you see a new transaction or a weird edge case:

1. Define the accounting question (recognition, measurement, disclosure).

2. Start in the FASAB Handbook (search the relevant SFFAS and interpretations).

3. Apply the SFFAS 34 hierarchy if you need supplemental guidance.

4. Document the conclusion with citations in hierarchy order.

That is the audit-ready workflow.