The Most Misunderstood Transaction: Are You Posting It Correctly?

Back to Topics

Part I: Prior-Year Adjustments to Undelivered Orders

Few transactions in federal accounting appear as straightforward — and are treated as inconsistently — as an adjustment to a prior-year obligation.

An obligation was recorded correctly.

The fiscal year closed.

Then something changed.

A contract modification increased the requirement. Another reduced it. An estimate changed. The amount ultimately required no longer matched what was originally obligated.

The accounting response can sound deceptively simple:

Increase the obligation.

Decrease the obligation.

Post the adjustment.

Move on.

Except this is where some of the most persistent accounting errors can begin.

A prior-year obligation adjustment is not simply a change to an existing balance. It represents a new accounting event affecting an obligation established in a prior period.

That distinction matters.

Because the transaction can process.

The general ledger can balance.

And the accounting treatment can still tell the wrong story.

The Original Obligation and the Adjustment Are Not the Same Event

Consider an obligation properly recorded during its original accounting period.

At year-end, the remaining unpaid obligation becomes part of the financial position carried into the next fiscal year.

Then the underlying business activity changes.

Perhaps a contract modification increases the amount required. Perhaps another reduces an amount that is no longer needed.

Those changes relate to the original obligation, but they are not the original obligation.

For an unpaid undelivered order, three USSGL accounts help preserve that distinction:

Why separate them?

Because simply changing the original obligation balance can obscure something financially important:

How did the obligation get from where it was to where it is today?

The accounting should preserve that answer.

Let's Start With an Expired Fund

Consider a simplified example using Fund 1112222-2525. The fund has reached its expired phase.

For purposes of this example, we'll focus exclusively on the budgetary accounts necessary to illustrate the transactions.

At the beginning of the period, our simplified trial balance looks like this:

The trial balance balances, and our $1,000 of budgetary resources is completely accounted for by the status of those resources.

Then Period 02 arrives. Two contract modifications hit the accounting office.

Modification #1: Increase an Obligation by $200

The first modification relates to an unpaid undelivered order established in the prior year. The modification requires the agency to increase that obligation by $200.

Because we're dealing with an expired fund and a prior-year unpaid undelivered obligation, the simplified budgetary entry is:

Why not simply increase 480100 by another $200?

Because the $200 represents something different.

The balance in 480100 represents the underlying unpaid undelivered obligation carried forward. The amount recorded in 488100 tells us that a prior-year obligation was subsequently increased.

We aren't simply changing a number.

We're preserving what happened to the obligation.

Modification #2: Decrease Another Obligation by $50

Now consider a second unpaid undelivered order. A separate contract modification determines that $50 of the previously obligated amount is no longer required.

For the expired fund:

The 487100 debit separately identifies the $50 as a downward adjustment to a prior-year unpaid undelivered obligation rather than simply reducing the original 480100 balance.

We now know two distinct things happened: obligation 1 increased by $200, and obligation 2 decreased by $50.

Now Look at the Expired Fund Again

After both modifications:

The net effect on expired authority was $150. Mathematically: $200 − $50 = $150.

But from an accounting-information perspective:

A $200 upward adjustment and a $50 downward adjustment do not equal one $150 accounting event.

One transaction consumed additional expired authority. The other recovered previously obligated authority.

Netting them may produce the correct mathematical result, but it does not preserve the same financial information.

Budgetary Resources Didn't Change. Their Status Did.

Before we look at the numbers again, it's worth pausing on a concept the rest of this article depends on.

The federal government keeps two sets of books: proprietary and budgetary. Each nets to zero independently, but the budgetary side follows its own governing equation:

Budgetary Resources = Status of Budgetary Resources.

Budgetary resources are what an agency has to work with — appropriations, collections, and similar authority. The status of those resources tells you what has happened to them: how much is unapportioned, allotted, obligated, or otherwise accounted for.

As a general rule, resource accounts — the accounts numbered below 4450, Unapportioned Authority — are normal debit-balance accounts. Status accounts, beginning at 4450 and moving forward, are normal credit-balance accounts.

Like most rules in federal accounting, this one has nuances. A status account can carry a debit balance when it represents a decrease being moved somewhere else in the status structure — exactly what 487100 does in this article, debiting to reduce one status account so the recovered authority can land in another.

Keep that equation in mind. It's what makes the next set of numbers make sense.

Our 420100 balance remains $1,000.

The ending balances representing the status of those resources are: 465000: ($350), 480100: ($250), 487100: $50, 488100: ($200), 490100: ($250). Together: ($1,000).

Therefore: Budgetary Resources of $1,000, Status of Budgetary Resources of ($1,000), for a difference of $0.

The resources-to-status relationship remains intact. 420100 never moved.

The modifications did not create additional budgetary resources. They changed the status of resources that already existed. The $200 upward adjustment consumed additional expired authority. The $50 downward adjustment restored previously obligated expired authority.

Prior-year obligation adjustments change the status of budgetary resources; they do not, by themselves, create new budgetary resources.

Now Change One Thing: The Authority Is Still Available

Let's apply the same business events to Fund 3334444 — 2526/No-Year.

We again have a $200 upward adjustment to a prior-year unpaid undelivered obligation, and a $50 downward adjustment to another prior-year unpaid undelivered obligation.

The adjustment accounts don't change simply because the authority remains available. But the authority side of the transaction can.

The $200 Upward Adjustment

For our available authority:

Compare the two:

488100 stays the same because the underlying business event stays the same.

What changes is the status of the authority supporting the adjustment.

The Downward Adjustment Is Where Things Get Interesting

Now reduce another prior-year unpaid undelivered obligation by $50. We know one side:

But what receives the credit?

This is where memorizing "downward adjustment = debit 487100" isn't enough. We also need to answer: what happens to the recovered budgetary authority?

A Recovery Does Not Automatically Mean You Have Money to Spend

The agency legitimately reduced a prior-year obligation by $50. The recovery exists.

But that does not automatically mean another $50 is immediately available for obligation.

Depending on the circumstances, the other side of the transaction can reflect very different statuses of budgetary authority:

Same $50 recovery. Same 487100.

Very different implications for what the agency can do next.

This is where prior-year obligation adjustments stop being merely an accounting exercise and become a budget execution and funds-control issue.

Anticipated Recoveries Matter

For available multi-year and no-year authority, agencies may anticipate recoveries of prior-year obligations as part of budget execution.

That's where 431000 — Anticipated Recoveries of Prior-Year Obligations enters the story.

An agency may have already incorporated expected recoveries into its apportionment structure. When an anticipated recovery is realized, the accounting needs to recognize that relationship.

But what if the recovery wasn't anticipated? Or what if the terms of the approved apportionment don't permit the realized recovery to become immediately available for further obligation?

Now the answer becomes more complicated.

The SF-132 Matters More Than You Might Think

This is where the accounting office and budget office need to be telling the same story.

The terms of an agency's approved SF-132, Apportionment and Reapportionment Schedule, including applicable footnotes and conditions, can affect the treatment of realized recoveries.

Depending on the approved apportionment, recoveries may have been anticipated or otherwise addressed in a manner permitting them to become available when realized.

If not, recovered authority may need to remain unapportioned until the necessary apportionment or reapportionment occurs.

In our simplified example: Dr 487100, Cr 445000 — Unapportioned — Unexpired Authority.

The obligation has decreased. The recovery is real.

But the authority has not necessarily become available for another obligation.

That distinction is critical.

And Then There's the Exception

Some budgetary resources are exempt from apportionment.

Where the authority is legally exempt, 462000 — Unobligated Funds Exempt From Apportionment can become relevant: Dr 487100, Cr 462000.

Same recovery. Different funds-control environment.

This is why understanding the USSGL account without understanding the underlying authority is not enough.

The $50 Question Every CFO Should Ask

Suppose the accounting office processes the $50 downward adjustment. The obligation decreased. The recovery is legitimate.

Someone sees $50 of recovered authority and concludes: "Great. We just freed up another $50."

Maybe.

The better question is: "Is that $50 actually available for us to obligate again?"

If recovered authority has not been properly apportioned — or otherwise made available for subsequent obligation — the agency cannot simply treat the recovery as immediately available funding.

And this is where a technical accounting issue can become much more serious.

If an agency incurs subsequent obligations against authority that has not been properly apportioned or otherwise made available, the issue can potentially implicate the Antideficiency Act.

What began as a $50 downward adjustment has now crossed four disciplines: accounting, budget execution, apportionment, and funds control.

That's why this transaction deserves more attention than it often receives.

The Blind Spot Isn't 487100

An accountant may correctly identify the downward adjustment. They may correctly debit 487100. The entry may balance.

And the organization can still get the broader transaction wrong.

Because the next question isn't: "What account makes my entry balance?"

It's: "What is the legal and budgetary status of the authority we just recovered?"

An agency can understand the obligation side of the transaction while misunderstanding whether the resulting recovery is available for subsequent obligation.

For federal CFO organizations, that distinction matters.

A recovery of budgetary authority is an accounting event. The availability of that authority for another obligation is a funds-control question.

Confusing the two can have consequences far beyond an incorrect USSGL posting.

Same Transaction Type. Multiple Questions.

We started with something that sounded simple: adjust a prior-year obligation.

But getting it right requires answering several different questions:

What happened to the obligation? Upward or downward?

Where is the obligation in its financial lifecycle? Is it still an unpaid undelivered order?

What is the status of the underlying authority? Available or expired?

If authority was recovered, what is its apportionment status? Anticipated? Unapportioned? Exempt from apportionment? Otherwise available under the approved apportionment?

And ultimately: can the agency actually use that authority for another obligation?

Only after answering those questions does the accounting begin to tell the complete story.

A Balanced Trial Balance Isn't the Finish Line

An organization can post a transaction that balances. The accounting system can accept it. The trial balance can net to zero.

And the accounting can still fail to properly communicate — or properly control — what happened.

That's why "Does it balance?" isn't enough. The better questions are:

What happened to the underlying obligation? Did we distinguish the adjustment from the original obligation? What happened to the authority as a result? And is that authority actually available for what we intend to do next?

Those questions connect accounting to budget execution, budget execution to funds control, and funds control to legal availability.

That's the real financial story.

Undelivered Is Only the Beginning

We've intentionally limited Part I to unpaid undelivered orders: 480100, the underlying unpaid undelivered obligation; 487100, the downward adjustment to a prior-year unpaid undelivered obligation; and 488100, the upward adjustment to a prior-year unpaid undelivered obligation.

But correctly identifying 487100 or 488100 is only part of the job.

The status of the supporting authority matters. The apportionment status of a recovery matters. And whether that recovered authority can legally support another obligation matters.

But obligations don't remain undelivered forever. Goods arrive. Services are performed. Liabilities are established. Payments are made.

And as the underlying business event moves through that lifecycle, the accounting for its prior-year adjustments changes with it.

In Part II, we'll move from undelivered orders to delivered but unpaid obligations and introduce the next set of prior-year adjustment accounts.

Because knowing whether an adjustment is upward or downward is only part of the answer. You also have to know where the obligation — and the authority supporting it — are in their financial lifecycle.

The views expressed in this article are those of the author and do not necessarily reflect the views of any employer, client, agency, or organization. The account structures and examples referenced are simplified for illustrative purposes and do not represent guidance for any specific agency's accounting treatment.