Payment extinguishes a liability, but it doesn't end the story. Part III follows prior-year delivered orders through payment and recovery — and asks whether a recovery is the same thing as available authority.
Once delivery occurs, a prior-year obligation adjustment has a proprietary story, not just a budgetary one. The budgetary and proprietary sides have to tell the same story.
September 30 shouldn't be your first test. It should be your final exam. Why year-end readiness is proven throughout the year, not established in September.
Validity controls need two things: a real grant of authority and access controls that stay in sync with it. Here's why many organizations build one without fully testing the other.
Accuracy controls that only check whether data is correct are testing half the Green Book definition. Here's the half most agencies miss, and why it matters at year-end.
A prior-year obligation adjustment sounds simple. Getting it right requires connecting accounting to budget execution, apportionment, and funds control.
Completeness controls can fail when they're built to examine transactions without testing whether the population itself is complete. Here's the difference — and what can actually catch missing records.
A balanced general ledger can provide confidence. But balance alone does not prove that the underlying financial activity was accounted for correctly.
A well-prepared work paper should answer three questions before an auditor ever asks them. If it can't, it isn't complete — it leaves room for assumptions.
The debate over extending the federal reporting timeline from 45 to 120 days asks the wrong question. The real question is whether agencies are practicing good stewardship before September 30.
Without a shared definition of what readiness actually is, agencies end up chasing the wrong thing — and they only find out at the worst possible moment.
The federal government doesn't manage public resources one year at a time. It shouldn't report on them that way either. Why comparative financial reporting is an essential element of federal stewardship.
Poor data quality is often treated as the problem. What if it's actually the symptom? Understanding the relationship between governance, technical debt, and data quality in federal financial management.
Organizations spend months selecting software before they can clearly explain how the business process they intend to transform actually works. Process discovery belongs in the business case — not after contract award.
USSGL posting logic isn't really an accounting exercise — it exists to keep budgetary and proprietary accounting telling the same story. When that link breaks, you stop reconciling accounts and start reconciling multiple versions of reality.
Independent, practitioner-written analysis on federal finance, systems, and audit readiness — delivered before it hits your feed.