May 26

USSGL Transaction Codes: How to Research and Post Federal Journal Entries

USSGL transaction codes are pre-built journal entries published in Section 3 of the U.S. Standard General Ledger supplement to the Treasury Financial Manual. Each transaction code tells you exactly which budgetary and proprietary accounts to debit and credit for a specific federal accounting event, such as recording a continuing resolution, receiving an equipment purchase, or posting an obligation. Section 3 contains several hundred transaction codes covering most events a federal agency will encounter, and learning to navigate it is a core federal accounting skill.

Key takeaways

• Section 3 of the USSGL contains all transaction codes (journal entries) for federal accounting events.
• Transaction codes are grouped A through H by category, with A-series covering appropriations, G-series for memo entries, and so on.
• Each transaction code includes a budgetary entry, a proprietary entry, or both, plus comments that point to related transactions.
• Three research tools live in Section 3: Transactions (the main detail), Transaction Listing (a quick reference), and T-Accounts (a reverse lookup by GL account).
• Reading the comments is mandatory; they tell you about required related entries, reversals, and special circumstances.
• Where to find it: tfx.treasury.gov/tfm/supplements/ussgl, Part 1, Section 3.

Why USSGL transaction codes matter

The USSGL chart of accounts tells you which accounts to use. USSGL transaction codes tell you how to combine those accounts into actual journal entries. If you have read our USSGL pillar post and our chart of accounts walkthrough, this is the next layer. Once you can navigate transaction codes, you can record any federal accounting event with confidence that your entries comply with Treasury standards.
When you are sitting at your desk and someone asks you to record a continuing resolution or post an equipment purchase, the answer is almost always in Section 3. Knowing where to look and how to read what you find is the difference between guessing and getting it right.

How Section 3 of the USSGL is organized

Section 3 has four parts. Each one serves a different research purpose.
Part What it provides
Transaction Categories Codes A through H that group transactions by purpose (A for appropriations, G for memo entries, etc.)
Transaction Listing A simple list of every transaction code with a short description
Account Transactions (Transactions) The full detail of each transaction code, including comments, budgetary entry, and proprietary entry
Account Transaction Postings (T-Accounts) A reverse lookup showing every transaction code that posts to each GL account

The Transactions detail is your primary research tool. The T-Accounts are useful when you know the GL account but need to find the right transaction code. Together, they let you research either from the event side ("how do I record this?") or from the account side ("what posts to this account?").

How to read a USSGL transaction code

Every transaction code entry in Section 3 follows the same structure. Once you can read one, you can read them all.
• Transaction code. An alphanumeric identifier (like A102 or B402). The letter tells you the category.
• Title or purpose. A plain-language description of what the transaction accomplishes.
• Comments. Critical information about related transactions, reversals, and special circumstances. Always read these.
• Budgetary entry. The debits and credits that affect the 400000 series budgetary accounts.
• Proprietary entry. The debits and credits that affect proprietary accounts (assets, liabilities, revenue, expenses, gains, losses).
Not every transaction has both budgetary and proprietary entries. Some transactions affect only one side. Memo entries (the G-series and 800000 account series) work differently and balance to zero.
The comments are not optional. The comments section of a USSGL transaction code routinely tells you about required related entries, reversals you need to make, and special circumstances that change how the transaction posts. Skipping the comments is the most common mistake in USSGL research, and it produces journal entries that look correct but fail to capture the full economic event.

Walkthrough 1: Recording a continuing resolution

Your supervisor tells you the agency is operating under a continuing resolution and you need to record it. Here is how you would research and post this transaction using the USSGL.

Step 1: Find the right transaction code

Open Section 3 and use Control+F to search for "continuing resolution." You will get several hits. Skip past the ones about reductions or unavailable authority. What you are looking for is transaction code A196: "To record the annualized level of an appropriation provided under a continuing resolution or newly enacted appropriation awaiting a warrant." That is your primary transaction.

Step 2: Read the comments

The comments tell you three important things. First, you must also post transaction code A197. Second, if you previously posted A102 (anticipated appropriation), you need to reverse it. Third, there are references to additional guidance if you need more context.
For this example, assume no A102 was posted, so we skip that reversal.

Step 3: Post A196 (the appropriation entry)

A196 has one debit option and three possible credit options. The credit you choose depends on your specific situation.
Budgetary entry:
DR 411900 Other Appropriations Realized
CR 412000, 445000, or 462000 (depending on situation)
For a standard continuing resolution, you would typically credit 445000 (Unapportioned Authority). Despite being called "Other" appropriations realized, USSGL 411900 is the most commonly used appropriation debit account.

Step 4: Post A197 (the fund balance entry)

A197 records your fund balance with Treasury while you are awaiting the warrant. This transaction has only two account options, making it straightforward.
Proprietary entry:
DR 109000 Fund Balance with Treasury While Awaiting a Warrant
CR 309000 Unexpended Appropriations - Appropriations While Awaiting a Warrant
This pairing ensures the balance sheet reflects that you have authorization but have not yet received the actual warrant. Once the warrant arrives, you will reclassify 109000 to 101000 (Fund Balance with Treasury) through a different transaction.

Walkthrough 2: Recording an equipment purchase

Now consider a different scenario. Your agency has received equipment, has not paid for it yet, and you need to record the transaction. Here is the research process.

Step 1: Identify the GL account

If you are not sure which GL account to use for equipment, check the USSGL chart of accounts in Section 1 or the definitions in Section 2. A search for "equipment" leads you to USSGL 175000 (Equipment), the main proprietary account for general equipment.

Step 2: Find the transaction code in Section 3

Back in Section 3, search for "equipment" or for transactions that involve receiving goods. You will land on transaction code B402, which records the delivery of goods or services and the accrual of a liability. This fits the scenario: equipment received but not yet paid for.

Step 3: Read the comments and identify related transactions

The B402 comments tell you that if this is funded by direct appropriation, you also need to post transaction code B134. The comments also suggest using transaction codes G120, G122, and G124 to track purchases as memo entries. For equipment (property, plant, and equipment), G120 is the right memo entry.

Step 4: Post the budgetary and proprietary entries

Budgetary entry:
DR 480100 Undelivered Orders - Obligations, Unpaid
CR 490100 Delivered Orders - Obligations, Unpaid
This reflects the movement from undelivered orders unpaid to delivered orders unpaid as the equipment has now been received. The budgetary entry tracks the obligation status as it progresses through the spending cycle.
Proprietary entry:
DR 175000 Equipment
CR 211000 Accounts Payable
This records the asset on the books and the liability owed. Notice the connection between the two entries: 490100 (delivered orders unpaid) on the budgetary side aligns with 211000 (accounts payable) on the proprietary side. Both represent the same liability viewed from different angles.

Step 5: Post the G120 memo entry

G120 records current-year purchases of property, plant, and equipment. This is a memo entry that uses the 800000 series and does not affect trial balance totals. It feeds required disclosures in the financial statements.
Memo entry:
DR 880200 Purchases of Property, Plant, and Equipment
CR 880100 Offset for Purchases of Assets
Memo entries always come in offsetting pairs that balance to zero. They provide additional tracking and reporting detail without double-counting financial statement amounts.

Research in reverse: the T-Accounts method

Sometimes you know the GL account but not which transaction codes apply. This is where T-Accounts become valuable. The T-Accounts part of Section 3 lists every GL account in the USSGL and shows which transaction codes can debit or credit each one.
Suppose you know you need to use 109000 (Fund Balance with Treasury While Awaiting a Warrant) but are not sure which transaction codes affect it. Navigate to the T-Accounts and search for 109000. You will see every transaction code that can debit or credit this account: A196, A197, A215, A224, A226, and others. From there, you can review each candidate transaction code in the Transactions detail and pick the one that fits your situation.
The T-Accounts also flag related transactions. If you see an "R" notation, it means the transaction code mentions a reversal in its comments. An "AP" notation means the transaction mentions an additional posting requirement. These notations help you find connected transactions you might otherwise miss.

Best practices for USSGL transaction research

• Always read the comments. They contain information about related transactions, reversals, and special circumstances that the transaction title alone does not capture.
• Check the references. If you are uncertain about the purpose or application of a transaction, the references provide additional context from authoritative guidance.
• Use Control+F liberally. Whether you are searching by keyword (like "continuing resolution") or by GL account number, the find function is your fastest path to the right transaction.
• Verify both budgetary and proprietary impacts. Not every transaction affects both, but you need to know which sides apply to your specific situation.
• Follow the breadcrumbs. When a transaction code tells you to also post another transaction code, do it. These connections ensure complete and accurate recording.

Common pitfalls to avoid

• Ignoring memo entries. Memo entries balance to zero, but they are not optional. They feed required disclosures and reporting lines.
• Skipping reversals. If a transaction code tells you to reverse a previous entry (like A102 when posting A196), failing to do so creates inaccurate balances.
• Assuming transaction titles tell the whole story. The title gives you the general idea, but the comments contain the critical details about how to apply the transaction correctly.
• Not verifying your GL accounts. When you see multiple debit or credit options in a transaction, make sure you are selecting the accounts that match your specific situation.
• Using outdated transaction codes. Like the chart of accounts, transaction codes can be added, retired, or modified between fiscal years. Always work from the current Part 1.

Frequently asked questions about USSGL transaction codes

What is a USSGL transaction code?

A USSGL transaction code is a pre-built journal entry published by Treasury in Section 3 of the USSGL supplement to the Treasury Financial Manual. Each code specifies which accounts to debit and credit for a specific federal accounting event, along with comments about related transactions and special circumstances. Transaction codes use alphanumeric identifiers like A196 or B402, where the letter indicates the category of transaction.

How are USSGL transaction codes organized?

USSGL transaction codes are grouped into categories A through H based on purpose. A-series codes cover appropriations and other funding sources. B-series codes cover obligations and goods or services. C-series codes cover collections. F-series codes cover year-end entries. G-series codes are memo entries. The category letter tells you the general purpose; the three digits identify the specific transaction within that category.

What is the difference between Transactions and T-Accounts in Section 3?

Transactions and T-Accounts are two different ways to navigate Section 3 of the USSGL. The Transactions detail shows you the full information for each transaction code: the title, comments, budgetary entry, and proprietary entry. The T-Accounts show you, for each GL account, every transaction code that can debit or credit it. Use Transactions when you know the event but need the right journal entry. Use T-Accounts when you know the GL account but need to identify the right transaction code.

What does USSGL transaction code A196 do?

USSGL transaction code A196 records the annualized level of an appropriation provided under a continuing resolution or a newly enacted appropriation awaiting a warrant. The budgetary entry debits USSGL 411900 (Other Appropriations Realized) and credits one of three accounts depending on the situation, most commonly 445000 (Unapportioned Authority). The comments require that you also post A197 to record the fund balance, and that you reverse A102 if it was previously posted.

Do all USSGL transactions have both budgetary and proprietary entries?

No. Some transaction codes have only a budgetary entry (because the event affects budget authority but not assets or liabilities). Some have only a proprietary entry. Many have both. Memo transactions in the G-series have only memo entries in the 800000 series and balance to zero. Always check both sides when researching a transaction to confirm what is required.

Why are the comments on a USSGL transaction code important?

The comments tell you about required related transactions (you may need to post a second or third transaction code along with the primary one), required reversals of previously posted transactions, references to additional Treasury guidance, and special circumstances that affect how the transaction posts. Skipping the comments is the most common research mistake in USSGL work because it produces journal entries that look correct in isolation but fail to capture the full economic event.

What to learn next

Once you can navigate transaction codes confidently, the next layer is account attributes and crosswalks. Section 4 of the USSGL defines the attributes that refine how each account is reported (begin/end indicators, debit/credit indicators, reimbursable flags, BEA categories, and others). Sections 5 and 6 crosswalk every account to specific lines of the federal financial statements. These layers become essential when you start working on financial statement preparation, GTAS submissions, or audit support.
• What Is the USSGL? A Complete Guide to the U.S. Standard General Ledger 
• The USSGL Chart of Accounts: A Walkthrough of Sections 1 and 2
• USSGL Account Attributes and Crosswalks: How Sections 4, 5, and 6 Drive Financial Reporting

Build USSGL research confidence with structured training

The first few times you navigate USSGL transaction codes, the process feels slow. With practice, you start recognizing patterns: A-series for appropriations, B-series for goods and services, G-series for memo entries. You learn which comments typically matter. You develop shortcuts for finding information quickly. The Introduction to U.S. Standard General Ledger course accelerates that learning curve. It walks through all seven sections with worked examples, knowledge checks, and earns NASBA-approved CPE credit.

Sources

• Treasury Financial Manual, USSGL Supplement, Part 1, Section 3
• Federal Financial Management Improvement Act of 1996 (FFMIA)
• FASAB Handbook