Government finance starts with authority: who may raise money, who may authorize its use, and who must account for the result. From there, the accounting depends on the government and the question being answered. A state general fund emphasizes resources available for current spending, while government-wide statements show longer-term assets and obligations. Federal reporting also connects budget authority and obligations to accrual-based costs. This guide follows those relationships across the three CGFM examinations. You will work through classifications, entries, reconciliations, financing choices, controls, performance measures, and audit findings. The examples use stated facts so you can practice reaching a conclusion, including when a transaction has a different budgetary and financial reporting effect.
Governmental Environment
1. Three levels of government
A public service can involve several governments without becoming the exclusive responsibility of the one that meets residents. Trace three questions separately: who has legal authority to establish the program, who supplies or controls its funding, and who performs the work. A federal government may set conditions and provide funds, a state may design an administrative process, and counties may process applications. The governing statute, award terms, and agreements determine their respective duties. Follow the money in both directions: identify where it originates and who must account for its use. Then follow decisions, such as eligibility rules, approvals, and appeals. This approach helps you identify the right party when a payment is improper or service falls short. The AGA examination outline includes these intergovernmental relationships.
Worked example: A federal agency awards $8 million to a state for a hypothetical benefits program. The state assigns counties to verify applications and issue benefits. The federal agency supplies funding and sets award conditions; the state administers the program and accounts for the award; counties deliver the service and document their work. A county error calls for investigation through those assigned responsibilities, even though residents dealt only with the county.
Watch the distinction: A county office providing the service does not make the program solely local. Delivery location cannot establish who set the rules, supplied the funds, or remains accountable for them.
Reference: [1]
2. Branches and checks
Separate the power to authorize spending from the power to carry it out. A legislature enacts laws, appropriates resources, and can attach conditions to their use. Executive officials administer programs, allocate available resources under applicable controls, and make authorized purchases or awards. Courts resolve legal disputes and may invalidate a law or action that supported spending. A judicial ruling does not itself rewrite the budget; it changes the legal position that managers must use when deciding whether obligations and payments can continue. For any financial event, ask what authority existed at the time, which branch acted, and what subsequent decision changed that authority. Also distinguish a valid appropriation from permission to use it for every purpose. Spending may satisfy the amount limit while violating a restriction on use.
Worked example: A legislature appropriates $3 million for a program, and an agency awards a $900,000 contract under the program's enabling law. A court later invalidates that law. The legislature supplied spending authority, and the agency exercised executive authority. The agency must assess the ruling's effect on future work, existing obligations, and lawful remedies before paying further invoices; the unused $2.1 million is not automatically available for another purpose.
Watch the distinction: An appropriation alone does not settle legality after the governing law is invalidated. Managers must reassess the authority for continued performance and payment, including any existing contractual duties.
Reference: [1]
3. Sources of legal authority
Government officials need authority for both a program and the particular action they propose. Start with the applicable constitution, then statutes and valid local charters, followed by subordinate rules such as regulations, ordinances, and executive directives. The exact hierarchy depends on the government and the power involved, but a lower-level rule cannot override a controlling higher-level rule. A charter may grant a city powers within state limits; an ordinance implements those powers. A regulation usually details how a statute operates rather than creating an independent power the statute withheld. Identify the actor, action, and relevant restriction before deciding whether a fee, tax, contract, or expenditure is authorized. If two provisions appear inconsistent, check their scope and enabling authority. A useful answer states which rule controls and what lawful change would be needed.
Worked example: Assume a state law authorizes a city to charge permit fees but expressly prohibits a fee for a specified inspection. The city council adopts an ordinance charging $40 for that inspection. The ordinance conflicts with the controlling state restriction, so the city cannot rely on it to collect the $40. It must remove the charge or obtain a valid change in state authority.
Watch the distinction: A locally adopted ordinance is not sufficient simply because council approved it. Approval establishes who enacted the rule; it does not cure a conflict with controlling state law.
Reference: [1]
4. Tribal sovereignty
Tribal governments exercise sovereign governmental authority, so a tribal program should not be classified as a city or county activity based on geography. The specific issue determines which legal relationships matter: tribal law and governing documents, federal law, applicable agreements, and the terms of any assistance award. State or local authority cannot be assumed from proximity to a municipality. For a financial management question, identify who established the program, who controls its spending, who receives an award, and who must provide financial and performance records. An award may impose reporting and eligible-cost duties without changing the tribe's governmental identity. Likewise, cooperation with nearby governments can allocate tasks without merging their authority. When jurisdiction is uncertain, reason from the stated legal relationship and avoid treating all tribal programs as governed by one universal arrangement.
Worked example: A tribal health program operates near a city and receives a hypothetical $600,000 federal award. The tribe governs the program; the federal award establishes conditions for its use and reporting. The city has no oversight role merely because the office is within the surrounding area. If the city supplies transport under an agreement, assess that agreed task separately from oversight of the tribal program.
Watch the distinction: Physical location does not convert a tribal program into a municipal department. Assign oversight from the governing relationship and award terms, not from a street address.
Reference: [1]
5. General and special governments
General-purpose governments serve broad populations across many functions, such as public safety, roads, and health. Special-purpose governments or authorities concentrate on a defined function or area. Quasi-governmental entities may combine public purposes with distinct corporate powers; their classification depends on their legal design. A jointly governed organization brings multiple governments into a shared arrangement, but its board and funding rules may differ substantially from those of its sponsors. Begin with the creating law or agreement: does it establish a separate legal body, who appoints its leaders, who can set rates or incur debt, and who bears financial risk? Then identify each government's continuing duties. The number of participating governments does not determine whether the organization is general-purpose. Nor does a separate board alone establish how its finances appear in a sponsoring government's statements.
Worked example: Two counties create a transit authority with its own board to run buses. Each county remains a general-purpose government; the authority has a specific transit purpose. Suppose the agreement requires each county to contribute $1 million annually. Both counties must budget their contributions, while the authority manages transit operations. Its separate board does not eliminate the counties' contractual commitments.
Watch the distinction: Do not classify a transit authority as general-purpose because two counties created it. Examine the service it was formed to provide and the agreement allocating control and financial responsibility.
Reference: [1]
6. What a budget decides
A budget converts policy choices into a financial and operating plan. It identifies priorities, estimates revenue, allocates resources, and communicates what the government intends to deliver. Once adopted under the applicable legal process, it may also establish enforceable spending limits at specified control levels, such as a fund, department, or purpose. Those levels matter: unused money in one line is not automatically transferable to another. During execution, managers compare actual revenue, obligations, spending, and service results with the adopted plan. A strategic goal can explain why a service deserves funding, but it does not itself confer spending authority. Read a budget proposal by asking what service changes, how they are financed, which officials can spend, and which amendments require approval. The CGFM Exam 1 study guide provides a focused route through this governmental environment material.
Worked example: A proposed budget adds $2 million to inspections and forecasts $2 million in new fee revenue. The proposal expresses a service priority and a financing assumption. If adopted with a $2 million inspection appropriation, it also gives managers an operating ceiling at the stated control level. If fees later produce only $1.5 million, managers must address the $500,000 funding gap under applicable budget rules.
Watch the distinction: A stated goal to inspect more facilities does not authorize purchases. Find the adopted appropriation, its purpose and control level, and the revenue assumptions supporting the plan.
Reference: [1]
7. Spending control stages
Spending controls narrow authority as resources move toward use. An appropriation establishes legislative authority for a purpose and period. An apportionment distributes available authority across time or activities; an allotment assigns a portion to an operating unit. A commitment reserves room for a planned purchase, while an obligation records a binding commitment under the applicable budget rules. Payment, or outlay, settles some or all of an obligation. To find room for a new action, use the most restrictive applicable limit and subtract amounts already committed or obligated against it, taking care not to count the same transaction twice. Payments reduce unpaid obligations but do not replenish the authority used to incur them. Dates, purpose restrictions, and any permitted adjustments can also limit the apparently unused balance. These stages help prevent managers from promising more than they are allowed to spend.
Worked example: Assume a $5 million appropriation, a $4 million apportionment, and a $3 million allotment for one unit. It has $1.5 million in obligations and a separate $1 million commitment. Free allotment is $3 million minus $1.5 million minus $1 million, or $0.5 million. Paying $0.4 million of an existing obligation lowers the unpaid balance, but free authority for another commitment remains $0.5 million.
Watch the distinction: Do not add payments back to available spending authority. A payment settles an obligation already charged to that authority; it does not undo the underlying use of the allotment.
Reference: [1]
8. Dedicated revenue and earmarks
A dedicated revenue rule restricts how an identified stream of money may be used. Legislative earmarking directs funds to a stated purpose, project, or recipient through the controlling legal instrument. First identify the source, calculation base, percentage or amount, eligible uses, and period. Then determine whether the rule is a binding restriction or a planning preference. The label placed on an account is less important than the authority that restricts it. A restricted share may need separate tracking so transfers, commitments, and reports show that it served the required purpose. Revenue above or below forecast changes the dollars produced by a percentage dedication, but it does not normally erase the restriction. When another program faces a shortfall, the financial manager must look for funds legally available to that program or seek a valid change in authority.
Worked example: Under a hypothetical law, 25% of a $12 million tax collection must support transit. Transit receives $12 million × 0.25 = $3 million; $9 million remains outside this particular dedication, subject to any other restrictions. A parks program has a $1 million shortfall. Managers cannot redirect the $3 million transit share solely because parks needs money.
Watch the distinction: A dedicated amount is not freely transferable because both activities serve the public. Trace the binding restriction and eligible uses before treating any balance as available.
Reference: [1]
9. The management cycle
Government management links a desired result to resources, work, evidence, and revision. Planning sets objectives; programming chooses activities; budgeting supplies authority and resources; operations deliver services. Accounting records financial events, reporting combines financial and service information, and auditing tests selected claims and controls. Each stage should feed the next. A target without a measurable output makes later evaluation weak, while expenditure data without service data cannot show what residents received. Compare actual results with both the service target and the capacity assumed in the budget. Investigate differences through workload, staffing, demand, eligibility, and process data before changing funding. A shortfall may reflect an unrealistic target, poor workflow, vacancies, or lower demand. The management cycle is useful because it turns reported variance into a question about causes and future choices.
Worked example: An inspection program sets a target of 800 completed inspections, budgets capacity for 1,000, and completes 700. It achieves 700 ÷ 800 = 87.5% of the target and 700 ÷ 1,000 = 70% of budgeted capacity. Managers should investigate why planned capacity produced fewer inspections before assuming that another appropriation would solve the shortfall.
Watch the distinction: The 70% figure compares actual work with budgeted capacity, not the 800-inspection target. Using the wrong denominator can misstate performance and lead to the wrong remedy.
Reference: [1]
10. Tax policy choices
Analyze a tax proposal by separating what is taxed, who legally owes it, the rate, its intended purpose, and any limits or exclusions. The tax base is the value or activity to which the rate applies; revenue is approximately base multiplied by rate before collection losses, behavior changes, and administrative effects. An exclusion narrows the base. A rate change alters the amount collected from the remaining base. Taxpayer incidence can differ from legal liability if sellers, employers, or property owners pass costs along. Governments also compare revenue stability, administration, equity, and economic effects, not just the headline yield. Income, wealth, and consumption taxes expose different bases to economic changes. For calculations, state whether the base is already taxable and whether compliance and behavior are held constant; those assumptions make a simple estimate interpretable.
Worked example: Assume taxable sales of $50 million and a 2% tax, with full collection and no behavior change. Estimated revenue is $50 million × 0.02 = $1 million. Excluding $10 million of sales leaves a $40 million base and $800,000 of revenue. The exclusion reduces the estimate by $200,000, although actual collections could differ if purchasing behavior changes.
Watch the distinction: Do not apply the 2% rate to all sales after part of the base is excluded. Identify the taxable base first, then multiply by the rate.
Reference: [1]
11. Tax expenditures
A tax expenditure gives a selected group relief through the tax system, commonly by an exclusion, deduction, exemption, preferential rate, or credit. It advances a policy objective while reducing revenue relative to a stated baseline tax structure. The baseline matters: without it, a claimed cost may be ambiguous. A credit generally reduces tax liability directly, while a deduction reduces the amount subject to tax, so equal nominal amounts need not have equal revenue effects. Compare the preference with a direct appropriation by identifying beneficiaries, eligibility tests, administrative costs, visibility, and how the benefit changes with tax liability. Estimate cost using eligible taxpayers and the effective benefit each can actually claim, allowing for any stated limits. Reports of forgone revenue help legislators see a policy commitment that may otherwise be less visible than a spending line.
Worked example: Assume 600 eligible taxpayers each owe at least $500 before a hypothetical $500 credit, and all claim it. Revenue falls by 600 × $500 = $300,000. The benefit reaches taxpayers through reduced bills rather than 600 agency checks. If some taxpayers owe less and the credit cannot exceed liability, the actual revenue reduction would be smaller.
Watch the distinction: A tax preference is not costless because no payment leaves the treasury. Its fiscal effect is revenue forgone, measured against a clearly stated tax baseline.
Reference: [1]
12. Intergovernmental funding
Intergovernmental cash can represent different relationships, so classify the transaction by substance. Shared revenue distributes collections under an allocation rule. A procurement contract buys specified goods or services for the purchaser's own use. A grant supports a recipient's public purpose under award conditions; a cooperative agreement also anticipates substantial involvement by the awarding government. A loan creates a repayment obligation, unlike nonrepayable assistance. Read the arrangement for its principal purpose, deliverables, discretion over the program, performance conditions, repayment terms, and who benefits from the output. The document's title alone may be misleading. Classification affects how managers budget, monitor, account for, and close out the arrangement. Where assistance flows onward, determine whether the next organization is carrying out part of the public program or merely selling goods and services to its administrator.
Worked example: A state pays a county $700,000 to build a specified data system that the state will own and use. On those facts, the county supplies a procured deliverable. If the state instead awards $700,000 for the county to operate its own eligible outreach program and report results, analyze it as assistance. A repayable $700,000 advance would require separate loan analysis.
Watch the distinction: Calling every government-to-government payment a grant hides the governing obligations. Identify whether the payer is buying an output, sharing revenue, supporting a program, or expecting repayment.
Reference: [1]
13. Grant design and stewardship
Grant design affects both selection and stewardship. A formula grant allocates funds using stated factors; a discretionary grant involves selection among applications; a block grant supports a broader defined area of activity. The grantor sets award conditions and monitors the recipient. A recipient that passes funds to subrecipients must identify their duties, communicate applicable conditions, evaluate risk, monitor performance and spending, and resolve issues through closeout. The applicable Uniform Guidance framework is relevant to federal awards, but the particular award and relationship still determine which requirements apply. Follow a dollar from authorization to expenditure support, reimbursement or reporting, and final reconciliation. Passing funds onward does not transfer away the recipient's own accountability. Distinguish a subrecipient carrying out part of the program from a contractor selling goods or services to it.
Worked example: A state receives a hypothetical $4 million federal award and passes it to local providers. They document $3.5 million of eligible program costs, leaving $0.5 million unspent under these facts. The state should support the $3.5 million it reports, monitor provider results and compliance, and reconcile the remaining $0.5 million according to the award terms at closeout.
Watch the distinction: A recipient cannot treat a pass-through award as finished when money leaves its account. It still needs evidence of subrecipient activity, eligible spending, and resolution of outstanding balances.
Reference: [1]
14. Fees and alternative financing
A user fee connects a charge to a service or privilege, but the desired recovery level must be explicit. Possible objectives include direct cost, operating cost, full cost, or another authorized measure. Estimate the relevant annual cost, divide by expected service volume, and check whether the resulting price affects access or demand. If the fee is set below cost, identify the subsidy rather than assuming the service costs less. Other revenue sources may spread costs across taxpayers or beneficiaries differently. A lease can spread payments over time and allocate ownership or maintenance duties. A public-private partnership can shift selected construction, operating, or demand risks, but it also creates long-term commitments that need evaluation. Compare financing options on total cost, service quality, flexibility, and who bears each risk, as well as immediate cash needs.
Worked example: A permit office expects $900,000 of attributable annual cost and 3,000 permits. Full recovery at that volume suggests $900,000 ÷ 3,000 = $300 per permit. A $240 fee would yield $720,000 and leave $180,000 to finance elsewhere, assuming volume stays fixed. Leasing equipment may change payment timing, but it does not remove the office's underlying service cost.
Watch the distinction: A lower fee is not proof of greater efficiency if costs and volume are unchanged. Show the resulting financing gap and identify who bears it.
Reference: [1]
15. Debt purpose and repayment
Borrowing can align the cost of a long-lived asset with future users, cover permitted short-term timing needs, or finance another authorized purpose. Start with the purpose and useful life, then identify the repayment source, expected cash flows, and exposure to revenue shortfalls. Compare financing forms such as notes, bonds, and lease-purchase arrangements under the relevant authority. Debt policy and legal limits may constrain amount, maturity, and permitted security; bond covenants can add continuing tests or reserves. Coverage measures available pledged revenue against scheduled debt service, but a ratio is only as reliable as its revenue forecast and definition. Credit ratings, insurance, or guarantees can affect access and price, yet they do not create operating cash. Test stress cases, competing obligations, and whether future budgets can sustain both repayment and essential services.
Worked example: A hypothetical project requires $20 million and is expected to produce $3 million of dedicated annual revenue. Scheduled annual debt service is $2 million, so coverage is $3 million ÷ $2 million = 1.5 times, leaving $1 million before other uses. If revenue falls to $1.8 million, coverage drops to 0.9 times and falls short of debt service by $200,000.
Watch the distinction: A 1.5-times coverage forecast does not by itself make borrowing sound. Check the legal limits, covenant definition, revenue volatility, and other claims on the pledged funds.
Reference: [1]
16. Layers of accountability
Public accountability asks several distinct questions. Policy accountability concerns whether elected choices reflect public priorities. Program accountability asks whether resources support the intended program. Performance concerns outputs and outcomes; process concerns how work was done; probity and legality concern integrity and compliance with governing rules. Different stakeholders need different evidence: legislators may examine appropriations and results, managers need operating measures, and residents need understandable service and financial information. Start by naming the claim being tested. Spending within a ceiling is evidence about budget control, but it does not prove every expenditure was eligible or that the program worked. Conversely, strong results cannot excuse an unlawful payment. Reports, hearings, evaluations, and audits serve different questions and can reveal tensions among them. Good analysis states both what the evidence answers and what remains unresolved.
Worked example: A benefits program has a $5 million appropriation, spends $4.8 million, and delivers 7,000 of 10,000 planned services. It remains $200,000 below its spending ceiling, while delivery reaches 70% of plan. Managers and legislators need to investigate the service shortfall; an auditor may separately test whether the $4.8 million was spent for authorized purposes.
Watch the distinction: Spending below an appropriation does not establish successful performance or complete legal compliance. Match each accountability conclusion to evidence that actually addresses it.
Reference: [1]
17. Fiscal sustainability
Short-term solvency concerns whether cash and near-term inflows can meet bills when due. Fiscal sustainability asks whether a government can maintain services and meet commitments over many periods without repeatedly consuming reserves, deferring maintenance, or adding unsupportable debt. Analyze both the balance sheet date and the recurring operating pattern. A cash balance may include restricted amounts, so test what is available for the bills in question. Then compare recurring revenue with recurring service costs, debt service, and long-term obligations under plausible conditions. One-time proceeds may bridge a temporary gap but cannot permanently finance a recurring deficit. Population, tax base, infrastructure needs, and benefit obligations can change the outlook. A useful assessment identifies the gap's cause and whether a proposed remedy changes the ongoing relationship between resources and commitments.
Worked example: Assume $15 million of unrestricted cash and $10 million of bills due soon. The immediate cash margin is $5 million. Recurring annual revenue is $90 million while recurring cost is $100 million, creating a $10 million annual gap. The government can pay today's bills, but using the $5 million margin would cover only half of one year's gap under these simplified assumptions.
Watch the distinction: A positive cash balance is not proof of long-term sustainability. Test whether recurring revenue covers recurring costs and whether cash is legally available for the obligations considered.
Reference: [1]
18. Open financial information
Open financial information helps residents inspect decisions and results, but a transaction list alone rarely explains value. A useful disclosure connects amounts to purpose, period, program, vendor, and available performance evidence. Open data should define fields and update timing so readers can distinguish a payment from a contract ceiling or an obligation. Hearings and program evaluations add context about choices, results, and alternatives. Before publishing, classify sensitive fields, remove protected personal information, and check whether combining apparently harmless fields could identify a person. Reconcile released figures to authoritative records and correct errors visibly. For a public question, choose the smallest set of reliable data that answers it, then explain limitations such as incomplete work or delayed reporting. Transparency depends on understandable context and trustworthy controls as much as access.
Worked example: An open checkbook lists a $200,000 contractor payment. The agency links it to a $500,000 contract for 1,000 inspections and reports that 400 were accepted to date. The $200,000 payment equals $500 per accepted inspection under this simplified arrangement. Readers can assess progress, while published records omit protected personal details about inspected residents.
Watch the distinction: A payment amount alone does not show whether a contractor delivered value. Connect it to contract terms and accepted results, while screening personal data before release.
Reference: [1]
19. Ethics and independence
Public financial decisions require both impartial judgment and credible independence. An actual conflict may give an official a direct personal interest; an apparent conflict can reasonably make others question the decision even if no favoritism occurs. Identify relationships, financial interests, gifts, and outside roles before an assignment begins. Disclose a relevant interest promptly, remove the person from affected decisions when warranted, and document reassignment so the process remains reviewable. Objectivity means evaluating evidence under the stated criteria. Due care means doing competent, sufficiently thorough work and recognizing when specialized advice is needed. A technically defensible score cannot cure an undisclosed relationship that undermines confidence in the process. Ethical analysis should address the public's interest and the appearance of improper use of office, not just whether a rule expressly forbids a payment.
Worked example: A procurement evaluator learns that their sibling works for one bidder. Before viewing proposals, the evaluator discloses the relationship and withdraws from scoring and related discussions. Another qualified evaluator applies the published criteria and records the decision. This protects the evaluation's credibility even if the first evaluator believed they could assign a fair score.
Watch the distinction: Good intentions do not remove an apparent conflict. Disclosure and recusal address the relationship's effect on trust and decision authority, not merely the evaluator's confidence in personal fairness.
Reference: [1]
20. Digital service controls
Online services can shorten queues and make records available sooner, but each new access path changes the risk of unauthorized disclosure or disruption. Identify the data a user may see, authenticate that user, and authorize only the functions needed for the role. Protect sensitive information in transit and storage, log material actions, and review unusual access. Staff permissions should follow job duties and be removed when duties change. Plan for outages with backups, recovery procedures, and a way to continue essential service. Timely public reporting also needs data validation and privacy review before release. Convenience and security can be designed together: residents should have a usable method to verify identity and correct errors, while the system limits exposure if an account or device is compromised.
Worked example: An agency moves benefit applications online. It verifies an applicant before displaying a case record, encrypts transmitted data, and gives caseworkers access only to assigned functions. If service fails, a documented recovery process restores applications from backups. A public dashboard may show aggregate processing times, but individual application status remains behind authenticated access.
Watch the distinction: Real-time access does not justify publishing individual benefit records openly. Separate public aggregate reporting from private case information, then apply authentication and role-based access to the latter.
Reference: [1]
Governmental Accounting, Financial Reporting and Budgeting
21. Reporting purposes and standard setters
Government reports answer different accountability questions. A budget comparison tests whether spending followed authorized limits; operating results show the cost of services; a statement of financial position shows resources and obligations. First identify the reporting government, then its applicable standards. GASB sets generally accepted accounting principles for U.S. state and local governments, while FASAB develops federal financial accounting standards. FASB serves nongovernmental entities, including many private contractors. IPSASB develops international public sector standards, which do not automatically govern a U.S. city or federal agency. Standard setters use public due process to consider proposed requirements. The applicable GAAP hierarchy helps resolve a transaction when guidance differs in authority. The 2026 CGFM content outline identifies these distinctions as part of the accounting examination.
Worked example: A city buys maintenance services from a private company. The city applies GASB guidance to its governmental statements and checks the contract against its authorized budget. The contractor may prepare its own statements under FASB guidance. If a federal agency buys the same service, its financial reporting starts with FASAB standards. The seller's accounting framework does not determine either government's reporting.
Watch the distinction: A tempting shortcut is to apply FASB rules because the transaction involves a business. Identify whose statements are being prepared before selecting a standard setter.
Reference: [1]
22. Interperiod equity
Interperiod equity asks whether the people receiving services in a period bear their cost through that period's revenue. It is a useful sustainability question, not a rule that every annual result must be zero. Compare revenue attributable to current services with the full cost of those services, including relevant accrual expenses. Then investigate the reason for any gap: a planned use of accumulated resources, a temporary shock, or a recurring structural shortfall have different implications. Borrowing supplies cash and creates a repayment obligation; it does not turn a service cost into revenue. Likewise, selling an asset may finance spending once without providing an enduring revenue stream. When interpreting the result, distinguish the government-wide operating view from a governmental fund's focus on resources available for current spending.
Worked example: Assume a government earns $90 million of current-period revenue and incurs $100 million of service expense. The current-period gap is $100 million minus $90 million, or $10 million. Borrowing $10 million may cover the immediate cash need, but future periods must service the debt. If the same operating gap recurs, borrowing alone cannot make services self-financing.
Watch the distinction: Counting bond proceeds as earned revenue makes the period appear balanced while shifting repayment to future taxpayers. Test service revenue against service cost separately from cash financing.
Reference: [1]
23. Full cost and user charges
A fee calculation begins with its objective: recover direct cost, operating cost, full cost, or another defined amount. Direct costs can be traced to a service, such as permit staff time. Indirect costs, such as shared payroll support, need a reasonable allocation basis that reflects use. For federal managerial cost information, full cost can also include relevant services supplied by another federal entity, even when the issuing office pays no invoice for them. Divide the chosen cost pool by expected service volume to obtain a unit charge; revisit both assumptions if volume changes. A price below full cost implies financing from another source, while a full-cost figure is not automatically the legally authorized fee. For grants or reimbursement contracts, distinguish a sound cost estimate from costs allowable under the particular award.
Worked example: A hypothetical federal office issues 2,000 permits. Direct processing costs are $600,000, allocated support is $200,000, and another agency supplies $100,000 of relevant services. Full cost is $900,000, so full cost per permit is $900,000 ÷ 2,000 = $450. A $300 fee covers only the $600,000 direct cost, leaving $300,000 of full cost to finance elsewhere.
Watch the distinction: Using only invoices paid by the permit office understates full cost when shared and inter-entity services support the output. State the recovery objective before choosing the numerator.
Reference: [1]
24. Budget design and forecasts
Budget formats highlight different decisions. Line-item budgets control spending by object, such as salaries or equipment. Program budgets group resources around a service or objective. A baseline starts with continuing operations and identifies changes; zero-base analysis asks decision makers to justify activities from a fresh starting point. Performance budgets connect funding to expected outputs or outcomes. None removes the need for forecasts. Revenue estimates depend on a base, rates, collections, and economic conditions; spending estimates depend on workload, unit costs, timing, and existing commitments. Test sensitive assumptions, then monitor actual results against the adopted plan. An attractive cost per added service is only part of the decision: ask whether the additional services meet a useful goal and whether the forecast includes support costs. The Exam 2 study guide provides a focused path through this accounting and budgeting domain.
Worked example: A program's continuing baseline is $4 million. Managers request another $500,000 to deliver 1,000 additional services, taking the proposed budget to $4.5 million. The forecast incremental cost is $500,000 ÷ 1,000 = $500 per added service. Decision makers should compare that cost and the expected result with alternatives, then track actual added services during execution.
Watch the distinction: Treating last year's appropriation as proof that every activity remains necessary confuses a baseline with justification. Equally, a low unit cost does not prove the added service has value.
Reference: [1]
25. Measurement focus and basis
Measurement focus determines what resources a statement portrays; the accounting basis determines when transactions enter it. Cash basis records cash movements. Accrual recognizes assets, liabilities, revenues, and expenses when earned or incurred, subject to the relevant standards. Modified accrual in governmental funds emphasizes current financial resources: revenues generally must be measurable and available, and expenditures usually arise when a current liability is incurred, with specific exceptions. Government-wide statements use the economic resources focus and accrual basis, so they include capital assets and long-term obligations. For each transaction, ask two questions in order: does this statement include the item, and when is it recognized? A cash payment can therefore be a fund expenditure while contributing to an asset in the government-wide statements. The distinction is about the reporting lens, not inconsistent bookkeeping.
Worked example: Assume a city receives a building measured at $1 million and pays $100,000 to install it for use. Its governmental fund records the $100,000 current outlay and does not report the building as a fund capital asset. If installation is a necessary capitalizable cost, government-wide reporting measures the asset at $1.1 million and recognizes depreciation after it enters service.
Watch the distinction: Recording every cash payment as an expense in every statement ignores measurement focus. Check whether the payment creates a capital asset and which statements report that asset.
Reference: [1]
26. Recognition judgments
Recognition starts with the transaction, because one rule cannot settle every asset or liability. Exchange revenue and nonexchange revenue have different recognition considerations. A receivable allowance estimates the portion unlikely to be collected; the required ending balance under a percentage-of-receivables method must be compared with the allowance already recorded. Inventory valuation requires a consistent cost-flow assumption, such as FIFO or average cost, that affects ending inventory and expense. A capital asset's cost is allocated over its useful life through depreciation when applicable. A legal claim calls for a separate assessment of likelihood, estimability, recognition, and disclosure under the applicable framework. Work through these judgments independently: identify the item, select its measurement rule, calculate the adjustment, then decide where it appears. A correct receivable estimate cannot resolve an unrelated contingency.
Worked example: Assume exchange-service receivables total $500,000 and an ending allowance equal to 4% is appropriate. The required allowance is $500,000 × 0.04 = $20,000. Because the account already has a $7,000 credit balance, increase it by $13,000. Net receivables become $480,000. A separate lawsuit still requires its own likelihood and amount assessment.
Watch the distinction: Charging the full $20,000 again ignores the existing allowance. The percentage-of-receivables method targets an ending balance, so calculate the difference before recording an adjustment.
Reference: [1]
27. Fund categories and purposes
Classify a state or local activity by whom it serves, how it is financed, and whose resources the government controls. Governmental funds primarily report tax-supported activities with a current financial resources focus. Proprietary funds use accrual accounting for business-type operations: enterprise funds serve external users, while internal service funds principally serve other government departments. Fiduciary funds report qualifying resources held for beneficiaries outside the government's own programs; assess the applicable control and beneficiary criteria before assigning that label. Within governmental funds, a special revenue fund tracks eligible restricted or committed revenue for specified purposes, a capital projects fund tracks qualifying construction resources, and a debt service fund tracks resources for principal and interest. The general fund holds activities not required in another fund. The fund label should explain the resource's purpose, rather than follow the department's name.
Worked example: A city operates water service for residents and intends charges to finance its operations. That pattern points to an enterprise fund with accrual reporting. Separately, suppose the city controls assets solely for beneficiaries outside its own programs and the fiduciary criteria are met. Those assets belong in fiduciary reporting. Putting both activities in the general fund would hide their different purposes.
Watch the distinction: Charging a fee does not automatically create an enterprise fund, and holding assets for others does not automatically establish a fiduciary fund. Test the activity's purpose and governing criteria.
Reference: [1]
28. The state or local reporting entity
A state or local reporting entity may extend beyond the primary government's legal shell. For a legally separate organization, examine who appoints its governing majority and whether the primary government can impose its will or faces financial benefit or burden; other applicable inclusion tests can also matter. If inclusion is required, presentation depends on the relationship, so do not assume every component unit merges into the same columns. Readers then need the basic government-wide and fund statements, their notes, and required supplementary information to interpret accounting policies, obligations, and trends. A broader annual comprehensive financial report can add introductory and statistical material; popular reporting offers a shorter public-facing view. First settle the boundary of the reporting entity, then locate the statement or disclosure that answers the user's question.
Worked example: A city appoints the voting majority of a legally separate authority's board, and the authority can impose financial burdens on the city. Those facts support assessing the authority as a component unit under GASB criteria. The accountant documents the appointment and burden evidence, determines the required presentation, and explains the relationship in the appropriate statements and notes. Separate incorporation alone does not end the analysis.
Watch the distinction: Excluding an authority merely because it has its own charter can omit a government for which the city is financially accountable. Examine governance and financial relationships.
Reference: [1]
29. Fund versus government-wide statements
Governmental fund statements answer a near-term question: what current financial resources came in, went out, and remain spendable under constraints? Their modified accrual approach reports capital spending as expenditure and generally does not place the resulting long-lived asset in the fund balance sheet. Government-wide statements answer a broader question about the government's economic resources and service cost. They recognize qualifying capital assets, long-term liabilities, and expenses such as depreciation. Reconciliation explains why the two views differ; it is essential when comparing results. For a capital project, distinguish the current financing burden from the asset's later consumption. Neither view replaces the other: a government can acquire valuable infrastructure while drawing down current fund resources. Use CGFM practice questions to rehearse the statement choice before calculating.
Worked example: Assume a city spends $2 million of governmental fund resources on a qualifying road and places it in service. The fund records $2 million of capital outlay expenditure this year. Government-wide statements initially report a $2 million capital asset under these assumptions, then allocate its cost through depreciation over its useful life. The current fund balance falls even though the government acquires an asset.
Watch the distinction: Calling the road purchase a $2 million government-wide operating expense overlooks capitalization. Conversely, showing the road as a governmental fund asset ignores that fund's current-resources focus.
Reference: [1]
30. Modified accrual revenue
Governmental fund revenue under modified accrual generally must be measurable and available to finance current-period expenditures. Measurable means the amount can be reasonably determined; available concerns collection within the period or soon enough afterward under the applicable revenue rule and stated availability policy. A valid receivable can therefore exist without equal current fund revenue. Identify the revenue type first, because property taxes, grants, and other nonexchange resources have distinct eligibility and timing considerations. Next establish the measurable amount, determine which portion meets availability, and classify the remainder as required, often as a deferred inflow when unavailable. Government-wide accrual reporting may recognize revenue on a different timetable. Do not confuse a budgeted levy, a billed amount, a receivable, and revenue recognized in the fund; they answer different questions.
Worked example: Assume a hypothetical property-tax levy has $150,000 measurable for the period, with $100,000 collected within the government's stated availability window. Under these simplified facts, the governmental fund recognizes $100,000 of revenue. The remaining $50,000 is measurable but unavailable and is reported as a deferred inflow under the applicable rules. Its later collection can change fund revenue timing without changing the original levy.
Watch the distinction: Recognizing all measurable taxes as current fund revenue skips the availability test. Cash collection matters to that test, but cash basis and modified accrual are still different.
Reference: [1]
31. Capital purchases and long-term debt
A governmental fund treats a qualifying capital purchase as capital outlay expenditure because current financial resources are spent. Bond proceeds are generally an other financing source in that fund, not tax revenue earned from operations. Principal and interest paid from current resources become debt service expenditures when recognized under the applicable rules. At the government-wide level, the purchase establishes a capital asset and the bond issue establishes a long-term liability. Later periods report depreciation, interest expense, and changes in the liability as appropriate. A principal repayment reduces that liability; it is not a second expense for the borrowed amount. The decision sequence is to identify the fund's cash and current-resource effects, then translate the same transaction into assets, liabilities, and expenses for governmental activities. This prevents debt financing from masquerading as improved operating performance.
Worked example: A city issues $600,000 of bonds and spends $1 million, including $400,000 of existing resources, on a qualifying asset. Its governmental fund reports $600,000 of other financing sources and $1 million of capital outlay expenditure, a net $400,000 resource decrease from these events. Government-wide statements report a $600,000 liability and a $1 million asset, with later interest and depreciation.
Watch the distinction: Treating the $600,000 bond proceeds as government-wide revenue inflates operating results. Borrowing exchanges a repayment promise for financing; the asset purchase is analyzed separately.
Reference: [1]
32. Fund balance constraints
Governmental fund balance classifications show how strongly remaining resources are constrained. Nonspendable amounts cannot be spent in their current form, such as inventory. Restricted amounts face externally imposed or qualifying legal constraints. Committed amounts are constrained by formal action of the government's highest decision-making authority under its applicable procedures. Assigned amounts reflect an intended use without reaching the committed level. Unassigned is the residual in the general fund after the other classifications; treatment outside the general fund requires care. Classify by the source and force of the constraint, not merely by a manager's preferred project. When amounts can meet several purposes, apply the government's disclosed spending-order policy consistently. The classifications describe available fund resources; they are not a cash balance or a complete measure of fiscal health.
Worked example: Assume a general fund has $1 million total balance: $50,000 of inventory, $300,000 externally restricted, $200,000 formally committed, and $100,000 assigned. Those categories total $650,000. The remaining $1,000,000 minus $650,000 = $350,000 is unassigned. This does not mean the government has $350,000 of cash free from every practical demand.
Watch the distinction: Calling a department's preferred purchase 'restricted' exaggerates its legal force. Identify who imposed the constraint and whether formal action was taken before choosing the category.
Reference: [1]
33. Budgetary entries and encumbrances
The adopted budget can be represented as estimated inflows plus planned use of existing resources equaling appropriations and other planned uses. Budgetary entries record this legal plan separately from GAAP transaction entries. During execution, an encumbrance records a commitment against spending authority when a purchase order is issued under the government's control system. It helps prevent managers from promising the same authority twice, but it is not itself a GAAP expenditure or a payable. When goods arrive and the government incurs the liability, reverse or liquidate the encumbrance as appropriate and record the actual expenditure and payable. Compare budget and actual results using the legally adopted basis, then reconcile material differences from GAAP reporting. The AGA CGFM examinations page identifies this as one of three separate examinations.
Worked example: A hypothetical budget estimates $8 million of revenue and plans to use $1 million of available fund balance to support $9 million of appropriations, so sources and uses both equal $9 million. A $200,000 purchase order reserves $200,000 of authority. If conforming goods worth $200,000 arrive, the government records the expenditure and payable, while releasing the associated encumbrance.
Watch the distinction: Recording the purchase order as both an encumbrance and a GAAP expenditure counts the same planned purchase too early. Receipt or another liability-creating event drives expenditure recognition.
Reference: [1]
34. Interfund flows and reconciliation
Interfund activity needs a substance test. A transfer moves resources without a direct exchange of equivalent value; an exchange-like charge pays one fund for services or goods supplied by another. Loans create interfund receivables and payables rather than immediate transfers. Classifying each correctly preserves the meaning of program costs and fund results. Governmental fund results then require reconciliation to government-wide governmental activities. Add capital outlays that became assets, remove debt proceeds that became liabilities, and recognize accrual expenses such as depreciation that governmental funds omit. Also consider other long-term obligations, timing differences, and eliminations when present. Show each bridge item once with a clear sign. A reconciliation is a change in reporting perspective, not a claim that the fund's cash or legally available resources were misstated.
Worked example: Assume a fund reports a $400,000 decrease, including $1 million of qualifying capital outlay and $600,000 of bond proceeds. For this simplified reconciliation, add back $1 million because it became an asset, subtract $600,000 because borrowing is a liability, and subtract $100,000 of depreciation. The government-wide change is negative $400,000 + $1,000,000 − $600,000 − $100,000 = negative $100,000.
Watch the distinction: Leaving bond proceeds in government-wide income treats borrowed money as earned. A reliable bridge states the fund result first, then adjusts each capital, debt, and accrual item once.
Reference: [1]
35. State and local disclosure choices
State and local statements need context that the main numbers cannot carry alone. Notes can explain accounting policies, deposit and investment exposures, debt terms, and relationships that affect interpretation. Required supplementary information can present prescribed trends or schedules alongside the basic statements. For eligible infrastructure, GASB's modified approach permits preservation costs to be reported under its criteria instead of depreciating the qualifying network or subsystem. The government must manage the asset using an established asset-management system, assess condition consistently, and document preservation at or above its established condition level. Compare actual preservation spending with estimated needs and examine condition results; skipping depreciation is a consequence of meeting the criteria, not a policy preference by itself. Government combinations likewise need analysis of whether activities merged, were acquired, or were transferred, because the relationship affects presentation.
Worked example: A city elects the modified approach for a qualifying road network. It has condition assessments, a stated target condition, estimated preservation needs, and reported actual preservation spending. If assessments show condition below the target and documentation cannot support the approach's criteria, simply omitting depreciation is not justified. The accountant evaluates the evidence and the required supplementary information before accepting the treatment.
Watch the distinction: Assuming all infrastructure can avoid depreciation because maintenance is budgeted confuses intent with evidence. The modified approach depends on qualifying assets, systematic assessments, and documented condition maintenance.
Reference: [1]
36. Federal accounting architecture
Federal accounting has distinct but connected roles. FASAB develops federal financial accounting standards. OMB provides executive branch financial reporting direction and coordination, while Treasury maintains government-wide financial information and supports the consolidated financial report. GAO provides oversight and audits the federal consolidated statements. The U.S. Standard General Ledger supplies a common account structure and transaction framework so agencies can classify and transmit information consistently. That structure improves comparability, but correct account codes cannot cure an incorrect recognition decision. Federal accountants also distinguish budgetary records, which track legal resource use, from proprietary records, which track accrual-based financial position and cost. When a transaction is unclear, identify the applicable federal standard, determine both accounting effects, map them to the ledger, and verify the resulting statement presentation. Do not import state and local GASB treatment into a federal agency.
Worked example: A federal agency maps a purchased service to U.S. Standard General Ledger accounts and sends reporting data to Treasury. Suppose its internal policy would delay recognizing a payable after the service has been received. The accountant first evaluates applicable FASAB recognition guidance, records the liability if required, then checks the ledger mapping. A valid account number cannot make an invalid timing choice correct.
Watch the distinction: Treating the Standard General Ledger as a substitute for accounting standards reverses their roles. The ledger organizes entries; FASAB guidance determines the federal reporting treatment.
Reference: [1]
37. Federal budget authority
Federal budget execution moves through controls with different purposes. An appropriation supplies budget authority under its terms. Apportionment distributes authority over time or activities, and an allotment delegates a further spending limit within the agency. A commitment reserves capacity for an anticipated action; a valid obligation records a binding legal commitment. An outlay occurs when payment is made. Each stage limits or describes a different amount, so do not infer cash paid from obligations or treat an unpaid obligation as free authority. Calculate unobligated authority from available authority less valid obligations, while checking any narrower apportionment or allotment limit before making another commitment. Calculate obligated but unpaid amounts from obligations less related outlays, assuming no opening balances or adjustments. Purpose, time, and amount restrictions still govern whether authority can be used.
Worked example: Assume an agency has $10 million of available authority, $7 million of valid obligations, and $5 million paid against those obligations, with no opening balances. Unobligated authority is $10 million − $7 million = $3 million. Obligated but unpaid is $7 million − $5 million = $2 million. The $5 million paid is outlays; it does not restore the $5 million of obligation authority.
Watch the distinction: Subtracting only payments from authority would suggest $5 million remains available to obligate. The agency already promised $2 million more, so obligations control that calculation.
Reference: [1]
38. Budgetary and proprietary accounts
Federal budgetary and proprietary accounts answer two simultaneous questions. Budgetary accounting tracks how authority is made available, reserved, obligated, and used under legal limits. Proprietary accounting uses accrual concepts to show assets, liabilities, financing sources, and costs. A contract can create a budgetary obligation before the government receives the goods; receipt can establish a proprietary asset or expense and a payable; payment then creates an outlay and settles that payable. The amounts may agree across stages, but their timing and meaning differ. Reconcile the transaction trail from authorization through acceptance and payment, especially when supplies remain on hand at period end. An unpaid bill is not evidence that no service was consumed, and a paid bill alone is not proof that the expenditure was legally authorized.
Worked example: A federal office validly orders $400,000 of supplies, then accepts all of them before paying the vendor. The order creates a $400,000 budgetary obligation. At receipt, assuming the supplies remain on hand, proprietary records show $400,000 of supplies and a $400,000 payable. Cash outlays are still $0. When the vendor is paid, outlays rise by $400,000 and the payable is cleared.
Watch the distinction: Waiting for payment to record every effect hides both an existing obligation and an unpaid liability. Follow the order, receipt, and payment as separate events.
Reference: [1]
39. Federal agency reporting
Federal agency reports need a defined boundary before transactions can be interpreted. Determine which operations are part of the reporting entity, which are disclosed separately, and which are related parties under applicable federal guidance. Basic statements then present financial position, net cost, changes in net position, and budgetary resources as required for the entity; notes explain significant policies and balances. Required supplementary information adds prescribed context, while agency financial or performance and accountability reporting connects financial information with performance and management discussion. When one federal entity supplies another, identify inter-entity cost and intragovernmental receivables or payables as applicable. Those balances matter to each agency's accountability even though matching amounts may be eliminated in the U.S. consolidated report. Start with the boundary, then trace the service, cost, balance, and disclosure.
Worked example: A federal agency controls a service operation and buys $200,000 of support from another federal agency, unpaid at year-end. It assesses whether the operation belongs within its reporting boundary, reports the relevant cost, and identifies the $200,000 intragovernmental payable if applicable. The supplying agency reports the matching receivable. In government-wide consolidation, matching internal balances are eliminated so they are not portrayed as external debt.
Watch the distinction: Omitting an internal payable because it will disappear on consolidation confuses agency reporting with government-wide reporting. Each entity first reports its own accountable position.
Reference: [1]
40. Treasury balances, credit, and consolidation
Fund Balance with Treasury represents a federal entity's recorded balance available through Treasury under applicable authority; it is not the same as cash in a commercial checking account or unlimited permission to spend. Interpret it alongside budgetary restrictions and reconciliations. Federal credit-program analysis uses present-value estimates to compare expected cash outflows with recoveries and other relevant cash flows under stated assumptions. The result changes when projected defaults, timing, interest, or recoveries change, so label assumptions and avoid presenting an estimate as cash already lost. In consolidation, intragovernmental receivables, payables, revenue, and expense must be matched and eliminated to portray the federal government as one reporting entity. The entity-level records remain necessary for accountability even though internal claims cannot increase the government's net external resources.
Worked example: Assume a hypothetical loan program has discounted expected cash outflows of $12 million and discounted recoveries of $4 million, with no other relevant flows in this simplified estimate. Net present-value cost is $12 million − $4 million = $8 million. Separately, two federal entities report a matching $2 million receivable and payable. Consolidation eliminates both $2 million balances; it does not erase either agency's underlying records.
Watch the distinction: Treating Fund Balance with Treasury as unrestricted cash or counting internal federal claims as external assets overstates available resources. Check authority and eliminate matching intragovernmental balances.
Reference: [1]
Governmental Financial Management and Control
41. Cash collections and payments
Cash management starts by matching the collection or payment method to the transaction while keeping a clear record of who authorized it. Electronic collections can shorten the time between a customer’s payment and available cash, but the agency must match receipts to accounts and bank deposits. For payments, approved invoices should be checked against purchase orders, evidence of receipt, vendor details, and prior payments before release. Separate the people who approve, execute, and reconcile payments where practical. Reconciliation then compares the agency ledger with the bank record and investigates timing differences or unexplained items. In AGA’s CGFM program, these are financial management decisions: faster processing is useful only when authorization, error detection, and recovery of improper payments remain effective.
Worked example: An agency schedules 10,000 payments of $200 each, or $2,000,000. A screen flags 30 apparent duplicates, worth 30 × $200 = $6,000. Staff confirm they are duplicates and stop them before release. The approved batch is 9,970 payments totaling $1,994,000. Reconciliation should match that amount to the bank’s cleared payments, allowing for documented payments still in transit.
Watch the distinction: A payment screen does not prove every flag is improper. Staff must verify the underlying transactions; otherwise, legitimate payees may be denied payment while true duplicates remain undetected.
Reference: [1]
42. Investment objectives and fiduciary care
Operating cash and pension assets serve different purposes. Cash needed soon for payroll or vendors should emphasize principal protection and access when bills fall due; a higher stated yield cannot compensate for funds being unavailable on payment day. An investment policy translates those needs into permitted holdings, maturity and concentration limits, authorized decision makers, and monitoring duties. Pension trustees face a longer investment horizon but must act for beneficiaries, use prudent care, diversify appropriately, and review managers and risks. They assess a portfolio’s role as well as each holding. A liquid operating account may accept a lower return because it protects service continuity. A pension portfolio can bear different market risks when its obligations, cash needs, and governing policy support them.
Worked example: A government needs $3 million for payroll in one month and has $5 million available. A one-year holding offers more yield but cannot supply the imminent $3 million. Place at least that $3 million in a permitted holding available by payroll day. The remaining $2 million can be assessed against later cash needs. Pension assets require a separate fiduciary assessment; they are not spare operating cash.
Watch the distinction: Maximizing yield is not the investment objective by itself. An asset can offer an attractive return yet be unsuitable because its maturity, credit risk, or concentration conflicts with the funds’ purpose.
Reference: [1]
43. Loans and delinquent debt
A public credit program begins with an authorized purpose and a decision about who qualifies for credit. After disbursement, servicing tracks balances, payment dates, borrower contact, and changes in collectibility. Aging separates newly late accounts from long-overdue ones because collection prospects and appropriate actions can differ. A delinquency rate is a useful portfolio signal, but it does not identify which borrowers need a reminder, a repayment arrangement, or an authorized collection action. Report both amounts and aging trends, and evaluate recoveries and program outcomes against the resources used. A write-off changes accounting treatment when recovery is unlikely under the applicable rules; it need not cancel the legal claim. Keep the decision to write off an amount separate from any decision to stop collection.
Worked example: A hypothetical loan portfolio has $2,000,000 outstanding, including $300,000 past due. Its delinquency rate is $300,000 ÷ $2,000,000 = 15%. Suppose $100,000 is recently late and $200,000 is much older. Staff examine each group’s payment history and prospects before choosing authorized collection steps. Writing off an uncollectible balance would not, by itself, forgive the borrower’s debt.
Watch the distinction: Treating all past-due dollars alike hides important differences. The age, cause, and recoverability of a debt matter more to collection decisions than the portfolio delinquency rate alone.
Reference: [1]
44. Public procurement
Public procurement converts a service need into an enforceable purchase. Start with specifications that describe the required result without unnecessarily excluding suppliers, then use the authorized competition method and publish the evaluation criteria. An invitation to bid often suits clearly defined requirements; a request for proposals permits assessment of stated factors such as approach, past performance, delivery, and price. First determine whether an offer meets mandatory requirements, then compare eligible offers under the announced criteria. Document the award and contract terms, including deliverables and acceptance conditions. During performance, compare what the vendor supplies with those terms before approving payment. Competition is weakened if an agency changes decisive criteria after seeing offers or accepts a shortfall without an authorized contract change.
Worked example: An invitation requires 100 devices meeting fixed specifications. Bid A offers 100 at $900 each, for $90,000. Bid B offers only 80 at $850 each, for $68,000. If delivery of all 100 is mandatory, B fails that requirement. A may be evaluated against other eligible bids; B’s lower unit price does not make its offer acceptable.
Watch the distinction: The lowest quoted unit price is not automatically the winning bid. Quantity, specifications, delivery, and other published requirements determine whether a bid can be considered at all.
Reference: [1]
45. Property and inventory stewardship
Property stewardship links an item’s record to its custodian, location, condition, and eventual disposal. Tagging helps identify equipment, while access restrictions and periodic counts test whether recorded items still exist. A difference between the count and the ledger is an investigation cue, not permission to erase an asset immediately: transfers, repairs, losses, and unrecorded disposals can produce the same difference. For supplies, classify items by use and consumption, monitor quantities, and set reorder points that account for demand and delivery time. An excessively low reorder point can interrupt service; excessive stock ties up funds and raises loss risk. Disposal should be authorized, documented, and reflected in both property and financial records as applicable.
Worked example: The asset register lists 500 tagged laptops, but staff find 493 during a physical count. The initial difference is seven laptops. They trace custody assignments, transfer forms, repair records, and disposal approvals. If four were documented transfers and three remain unexplained, update locations for the four and investigate the three; do not record all seven as losses without evidence.
Watch the distinction: A clean asset register is not proof that assets are present. Counts must be compared with records, and unexplained differences need investigation before balances or custody assignments are changed.
Reference: [1]
46. Financial systems and shared services
An integrated financial system shares transaction data across functions, reducing duplicate entry but increasing the importance of access rules and consistent data definitions. A stand-alone system may fit a narrow need yet require controlled interfaces and reconciliations to the central ledger. Sourcing choices include commercial software, custom development, and shared services; hosting may be on premises, in the cloud, or mixed. Compare them using functional requirements, security, total costs, transition effort, and recovery needs. A provider can operate payroll or another process, but management retains responsibility for approving its own inputs and assessing outputs. Identify which controls the provider performs, which remain with the agency, and how errors or outages will be reported and resolved.
Worked example: An agency transfers payroll processing to a shared cloud service. The provider calculates a proposed $2.4 million payroll from approved data. Agency staff verify employee changes and compare the total with expected staffing and prior payrolls before authorizing payment. They reconcile the processed amount to ledger and bank records, then review provider control evidence for the service they use.
Watch the distinction: Outsourcing processing does not transfer management’s accountability. If the agency sends an unauthorized employee change or ignores an exception report, a provider’s accurate processing will not correct that failure.
Reference: [1]
47. Project delivery constraints
A project plan links scope, schedule, cost, testing, deployment, and expected benefits. Changing one can affect the others: adding a feature requires design and testing time, may delay benefits, and can exceed authorized funding. Assess a proposed change against the approved baseline, the problem it solves, its full cost, dependencies, and the consequences of delay. Document who can approve revised scope and funding before committing resources. Testing is part of delivery, not an optional activity to recover lost time; a system that launches on schedule but cannot process valid transactions has not met its purpose. After deployment, compare actual costs and service results with the business case so future decisions use observed performance rather than the original estimate alone.
Worked example: A system has an approved $4 million budget. A feature would add $600,000 and delay launch. The revised estimate is $4.6 million, an increase of $600,000 ÷ $4,000,000 = 15%. Decision makers should compare the documented benefit with that cost and delay, then approve or reject a formal change before the team builds it. Testing and deployment plans also need revision.
Watch the distinction: Calling a feature useful does not establish that it belongs in the project. Its incremental benefit, cost, delay, and effect on required testing must be assessed together.
Reference: [1]
48. Time value and payback
Simple payback asks how long undiscounted cash savings take to recover an initial cost. It is easy to calculate but ignores the value of time and savings after recovery. Present value discounts each future cash flow by when it occurs: for a payment at the end of year t, divide it by (1 + r)^t, where r is the stated annual discount rate. Subtract the initial cost from the sum of discounted savings to obtain net present value. Use consistent units and timing assumptions, and include operating costs, residual value, and risk where material. A positive calculated value supports a financial case under the assumptions; it does not establish that the project is legally authorized or superior on service and public value grounds.
Worked example: A hypothetical project costs $900,000 now and saves $300,000 at each of four year ends. Simple payback is $900,000 ÷ $300,000 = three years. At 5% annually, savings have present value of $300,000 × (1/1.05 + 1/1.05² + 1/1.05³ + 1/1.05⁴), about $1,063,785. Net present value is about $163,785 before omitted costs or risks.
Watch the distinction: Payback and net present value answer different questions. A three-year payback does not mean savings equal the initial cost in today’s dollars or capture fourth-year value.
Reference: [1]
49. Comparative and project analysis
Choose an analysis method for the decision at hand. Trends show how a measure changes over time; ratios compare related quantities; sourcing analysis compares the full costs and performance of supply options. Regression can estimate a relationship, but an observed association alone does not prove that changing one factor will cause a result. Flowcharts expose handoffs, approvals, and rework in a process. Earned value adds a disciplined project view: planned value is the budgeted value of work scheduled, earned value is the budgeted value of work completed, and actual cost is what that work cost. Schedule variance equals earned minus planned value; cost variance equals earned value minus actual cost. The Exam 3 study guide can help connect these methods to financial management decisions.
Worked example: A project has $400,000 planned value, $300,000 earned value, and $360,000 actual cost. Schedule variance is $300,000 − $400,000 = negative $100,000, so completed work trails the plan. Cost variance is $300,000 − $360,000 = negative $60,000, so work completed has cost more than its budgeted value. Neither figure alone identifies the cause; investigate staffing, scope, and rework.
Watch the distinction: Comparing actual cost only with planned value can mislead. A project may spend less than planned simply because it has completed less work; earned value supplies the missing progress measure.
Reference: [1]
50. Data quality and forensic patterns
Analytics is only as reliable as its source data. Before using a payment file, check whether it covers the full period, whether identifiers are consistent, whether adjustments and reversals are included, and whether fields can be traced to source records. Duplicate amounts, unusual timing, split purchases, or repeated bank details can highlight transactions for review. A forensic approach preserves the original data, records the tests applied, and follows each flag through invoices, approvals, receipts, and payment evidence. The aim is to distinguish an error, a legitimate repeated transaction, and possible misconduct. A flag is a reason to investigate, not a finding of fraud. Consider the cost of false positives when designing rules and protect sensitive records during review.
Worked example: A file shows three invoices from one vendor on the same date, each for $9,800. Their apparent total is $29,400. Analysts compare invoice numbers, purchase orders, receiving records, and payment destinations. If the invoices cover three separately received shipments, matching amounts may be legitimate. If all refer to one shipment and two were paid, document the duplicate payments and pursue recovery; amount matching alone cannot establish intent.
Watch the distinction: A repeated amount is not proof of fraud. Common prices and scheduled billing create legitimate matches, while fraud can occur through transactions with different amounts.
Reference: [1]
51. Internal control frameworks
Internal control provides reasonable assurance that operations work, reporting is reliable, and applicable requirements are met. The COSO framework organizes control thinking into the control environment, risk assessment, control activities, information and communication, and monitoring. Federal managers also consider applicable GAO and OMB control standards. Use the components together: a payment approval rule has limited value if roles are unclear, risks are ignored, system logs are unavailable, or exceptions receive no follow-up. Assess the likelihood and impact of a failure, then choose controls whose expected benefit justifies their cost. Separation of duties is powerful because it prevents one person from initiating and completing a risky transaction without review, but small offices may need a documented supervisory review as a compensating control.
Worked example: One employee can create a vendor and approve that vendor’s $12,000 invoice. The manager removes one permission, requires independent approval of new vendor records, and reviews exception logs for changes before payment. These measures reduce the chance of a fictitious vendor payment. The manager still monitors exceptions because errors, collusion, and control failures remain possible.
Watch the distinction: A documented control is not necessarily an operating control. Its owner must perform it, retain useful evidence, and respond to exceptions; reasonable assurance never means zero risk.
Reference: [1]
52. Controls across objectives
Start a control decision by naming the objective. An operations control protects timely, economical service; a reporting control protects the accuracy and completeness of records; a compliance control checks conditions attached to authority or funding. Fraud risk can threaten all three. Preventive controls act before a transaction, such as access restrictions, eligibility checks, and approval limits. Detective controls identify problems afterward, such as reconciliations, exception reports, and sample reviews. Information technology can enforce rules consistently, but its configuration, user access, and data inputs also need control. Design a sequence that answers who is allowed to act, what evidence is required, how the system records the action, and who reviews exceptions. An available budget is one necessary check for many payments, not proof that the underlying activity qualifies.
Worked example: A grant has $100,000 of budget remaining, and an invoice for $8,000 passes the budget check. The file lacks evidence that the billed service was delivered to eligible participants. Hold payment until staff verify eligibility and receipt. Afterward, sample paid invoices to detect recurring gaps. The $100,000 balance establishes capacity to spend, not that this $8,000 charge is allowable.
Watch the distinction: Relying only on a preventive system rule can miss bad input or a wrongly configured rule. Pair important automated checks with access oversight and review of exceptions.
Reference: [1]
53. Control evaluation and risk response
Evaluating control begins with a clear description of the risk, the control owner, its timing, and the evidence it should leave. Test both design and operation: a well-designed access removal process can still fail if notifications arrive late or staff do not act. When exceptions appear, assess their cause, duration, affected transactions, and possible exposure before judging severity. Remediation should change the process, assign an owner, and include a retest. A service provider’s control report can help identify controls the provider performed and controls the agency must perform itself; it does not cover every agency risk automatically. Feed significant findings into broader risk planning, including staffing, system resilience, and continuity of operations. A sample exception rate describes the sample unless the selection method supports wider inference.
Worked example: In a sample of 50 former users, 10 accounts were removed late: 10 ÷ 50 = 20% of the sample. Management checks whether any of those accounts accessed sensitive data after departure, determines why notices or removals lagged, and fixes the handoff. It then tests later removals. A provider report may inform this review, but the agency must assess its own access process.
Watch the distinction: A 20% sample exception rate does not automatically mean 20% of every account was late. Sampling method, population, timing, and the seriousness of affected access all matter.
Reference: [1]
54. Inputs, outputs, outcomes
Performance measures answer different questions depending on what they count. Inputs are resources such as labor hours and dollars; outputs are delivered services; outcomes are changes experienced by the people served. Efficiency relates output to input, often as cost per service or services per staff hour. Define the denominator and observation period before calculating a rate. An outcome measure also needs a clear population and a stated success criterion. Link measures to the program’s goal, then interpret them together: a lower cost per visit is less persuasive if service quality or access falls. Public managers use these measures to allocate resources and explain results, but a measure rarely proves the program caused an outcome without considering other influences and differences among clients.
Worked example: Assume a clinic spends $600,000 during a year, completes 3,000 visits for 3,000 distinct patients, and 2,100 of those patients meet a stated follow-up goal. Cost per visit is $600,000 ÷ 3,000 = $200. The follow-up rate is 2,100 ÷ 3,000 = 70%. These describe efficiency and one outcome; they do not show whether access or care quality was equitable.
Watch the distinction: Visits are outputs, not outcomes. Counting more visits cannot by itself establish better patient results, and cost per visit cannot reveal whether the visits met the program’s purpose.
Reference: [1]
55. Useful performance evidence
A baseline is the starting level against which change is measured; a benchmark is a chosen comparison, such as a peer result or service goal. Define each measure consistently so changes in case mix, data capture, or calculation do not masquerade as improvement. Use timely, verifiable data and record what the measure leaves out. Median processing time describes a typical case, while a long tail may still burden some applicants. Stakeholder feedback helps expose problems that a speed measure cannot see, such as confusing decisions or repeated requests for documents. Interpret results through a decision sequence: verify the data, compare like cases, examine related quality and access measures, then decide what operational change is justified. Publishing both favorable and unfavorable results strengthens accountability.
Worked example: A city’s median permit time falls from 20 to 14 days, an improvement of six days or 6 ÷ 20 = 30%. Applicants now report more incomplete decisions. Staff verify how time was measured, compare case types before and after, and review rework rates. The city can claim faster median processing, but should investigate quality before claiming an overall service improvement.
Watch the distinction: A favorable movement against a baseline is not the whole performance story. A faster median can coexist with worse accuracy, unequal delays, or changed case mix.
Reference: [1]
56. Audit objectives and evidence
An audit objective determines the evidence needed and the kind of conclusion possible. A financial audit addresses whether financial statements are fairly presented under the applicable reporting framework; auditors test amounts, disclosures, and relevant controls to obtain evidence for an opinion. An attestation engagement addresses a defined subject matter or assertion and follows the engagement’s specified level and form of assurance. A performance audit asks about issues such as economy, efficiency, effectiveness, or compliance within its stated scope. It may combine financial records with interviews, observations, and service data. Before gathering evidence, define the criteria, condition, period, and users of the report. CGFM practice questions are useful when you identify the objective first, then decide which evidence could support it.
Worked example: A legislature asks whether an agency’s statements are fairly presented and whether its permit service is timely at reasonable cost. The first question calls for a financial audit using accounting evidence and reporting criteria. The second calls for a performance audit using processing times, costs, and service criteria. Payroll records may inform both, but the reports answer different questions.
Watch the distinction: An unmodified financial audit opinion does not establish that a program is effective. Fair presentation of statements and achievement of service results require different criteria and evidence.
Reference: [1]
57. Auditor judgment and independence
Auditors plan work using professional judgment about risk and materiality: an amount or omission matters when it could reasonably influence users’ decisions in context. They also need the competence and quality processes to gather sufficient, appropriate evidence and review conclusions. Independence requires freedom from interests or responsibilities that could compromise objective judgment, including when the auditor offers other services to the auditee. Designing a client’s control creates a serious problem if the auditor later evaluates that same control, because management must own its design and operation. Before accepting a proposed service, identify the responsibilities involved, applicable independence requirements, and any permitted safeguards. Document the conclusion and decline work that would make the auditor assume management’s role.
Worked example: An audit firm is asked to design an agency’s invoice approval control and then audit it. If the firm chooses approvers, sets the rule, and implements it, it has taken on management’s design responsibility and would later review its own work. The agency should design and approve the control. The firm evaluates whether any narrower advisory service is permitted before accepting it.
Watch the distinction: A small fee or a well-intentioned service does not remove an independence threat. The auditor’s actual responsibilities and the work later audited matter more than the service’s price.
Reference: [1]
58. The auditee’s responsibilities
The auditee owns its records, financial statements, representations, and corrective actions. Before an audit, management should organize ledgers, award records, reconciliations, approvals, and explanations so transactions can be traced to source evidence. During fieldwork, it should answer requests accurately, investigate apparent exceptions, and distinguish missing evidence from evidence that the activity did not occur. An audit committee or similar oversight body can help monitor auditor selection, access, significant findings, and management’s response without taking over daily management. Written representations confirm certain management assertions but do not replace independent evidence. When auditors identify a problem, management should establish its scope and root cause, assign a remedy, and provide a realistic completion date. Later evidence should show that the remedy actually operated.
Worked example: Auditors find unsupported costs in 12 sampled transactions. Management retrieves invoices, receipt records, approvals, and grant coding for each transaction. It determines which costs remain unsupported and checks whether the issue affects other transactions. Its corrective action plan addresses the cause, such as a missing receipt check. A representation letter stating that all costs were valid cannot substitute for the records.
Watch the distinction: The auditor does not become the owner of the auditee’s books or corrective action. Management must prepare support, assess the finding, and operate the fix.
Reference: [1]
59. Single Audit and federal awards
A Single Audit examines an entity’s financial reporting and compliance with requirements applicable to its federal awards, using the governing audit framework. Its purpose is broader than checking a single spending total: auditors need to identify awards, expenditures, applicable compliance requirements, and controls over those requirements. A recipient that passes an award to subrecipients must retain enough information to identify the funds and monitor subrecipient activity. Award-level records connect charges to the correct program and period; monitoring records show whether issues were identified and addressed. Procurement payments for goods or services and subawards for program delivery have different roles, so classification matters. The applicable audit and reporting obligations depend on the governing requirements and period; do not infer a current numeric trigger from a general description.
Worked example: A state administers three federal awards and passes part of one award to counties. It records expenditures separately by award and retains county agreements, reports, monitoring reviews, and follow-up. If the state reports only a $9 million combined federal spending total, auditors cannot tell which award funded a charge or whether county requirements were monitored. The total must be supported by award-level detail.
Watch the distinction: Passing funds to counties does not end the state’s stewardship duty. It still needs records and oversight evidence appropriate to its role in the award.
Reference: [1]
60. Audit findings and follow-up
An audit finding should lead from an observed condition to its cause and a verifiable correction. First identify the criterion and what happened, then assess the effect or risk. Ask why the process failed: unclear ownership, missing information, inadequate staffing, or a review that existed only on paper require different remedies. A corrective action plan names an owner, specific action, completion date, and evidence that will demonstrate operation. Management should track overdue actions and report progress to the appropriate oversight body. Follow-up goes beyond confirming that a policy was issued; it tests whether people performed the revised process and whether the original risk declined. If exceptions persist, revisit the root cause and adjust the response rather than closing the finding administratively.
Worked example: An audit finds five late bank reconciliations in 12 months, a rate of 5 ÷ 12, or about 41.7% of those months. Management assigns an owner, sets a monthly completion and review deadline, and provides three later reconciliations with dated signatures. Follow-up verifies those months were timely and investigates any remaining gaps. Three successful months show improvement, though continued monitoring is warranted.
Watch the distinction: Rewriting a procedure is not the same as correcting a finding. Closure requires evidence that the new control operated and addressed the reason the failures occurred.
Reference: [1]
Official references and further reading
- AGA 2026 CGFM: Governmental Environment
- Current AGA CGFM programme and tested regulation basis
- Historical AGA format description: question-type corroboration only
