How do the Core sections differ when they address the same transaction?

FAR asks how a transaction is recognized, measured, and presented under the applicable reporting framework. AUD asks what could be misstated and what evidence would support the reported amount. REG asks for its federal tax treatment, which may differ from the book treatment. For a machine purchase, FAR may calculate depreciation, AUD may test the purchase invoice and useful-life estimate, and REG may calculate tax basis and the tax effect of a later sale.

What changes when I choose BAR, ISC, or TCP?

You take one Discipline section. BAR extends financial reporting into analysis, technical accounting, and governmental reporting. ISC examines information systems, controls, security, privacy, and SOC engagements. TCP develops tax compliance and planning for individuals, entities, and property transactions. The choice changes the depth of specialized work, while AUD, FAR, and REG remain common to every candidate.

Why can an accounting answer and a tax answer both be correct for the same amount?

Financial reporting and federal taxation use different recognition and measurement rules. Suppose a company records a $12,000 warranty expense but can deduct only $3,000 of related payments in the period under the stated tax facts. Book expense exceeds the current tax deduction by $9,000. The reconciliation adds $9,000 to book income to arrive at taxable income before other adjustments; the financial statements still report the full $12,000 expense.

Uniform CPA Exam: Core and Discipline Study Guide

Start with concept 1 Choose a topic

The Uniform CPA Examination covers three Core sections, AUD, FAR, and REG, plus one Discipline section chosen from BAR, ISC, and TCP. The Core work connects naturally: financial reporting produces the amounts an auditor evaluates, while tax rules can give the same transactions a different treatment. Your Discipline choice then takes you deeper into business analysis, information systems, or tax planning. This guide follows those connections while keeping each section’s tasks distinct. You will practice choosing an audit response from an assertion, building reported amounts from transaction facts, separating book income from taxable income, and tracing the effect of a control or planning decision. Work through the arithmetic in each example, then ask what the result means for the next decision.

AUD section - Auditing and Attestation

1. Independence and professional judgment

Independence and professional judgment An auditor needs an objective relationship with the client before judging its financial statements. A direct ownership interest creates a personal financial stake in the reported results, even if the auditor believes they can remain impartial. Identify the person’s role, the relationship, and when it exists; then resolve the conflict before that person joins the engagement. Extra supervision may improve the quality of audit work, but it does not remove shares the person still owns. This differs from ordinary audit risk, such as a difficult inventory estimate. Audit risk calls for better evidence and procedures; an independence threat concerns whether the auditor can perform the engagement in the required role. The 2026 CPA Exam Blueprints place ethics and independence within AUD.

Worked example: Before joining an audit, a team member discovers they own shares in the client. Selling the shares and confirming that the interest has ended addresses the direct ownership conflict for that member. Assigning a second reviewer while the member keeps the shares does not: the financial stake remains. The team should also assess whether any other relevant relationships remain.

Watch the distinction: A tempting answer treats additional review as a cure for every independence problem. Review can detect poor work, but it cannot remove an auditor’s direct financial interest in the client.

Reference: [2]

2. Match the engagement to its conclusion

Match the engagement to its conclusion Start with what the intended user wants to receive, then choose work capable of supporting that result. A financial statement audit gathers sufficient appropriate evidence to support an opinion. A review uses principally inquiry and analytical procedures and offers a limited assurance conclusion. A compilation presents financial information using the applicable reporting framework but provides no assurance. In agreed-upon procedures, the practitioner performs specified steps and reports factual findings; users draw their own conclusions. These reports are not interchangeable merely because each involves an accountant. Ask whether the request is for an opinion, a limited conclusion, assembled statements, or findings from precisely described checks. Also identify the subject matter: checking a few invoices cannot establish that the financial statements as a whole are fairly presented.

Worked example: A lender asks for an opinion on a borrower’s financial statements. A compilation would present the statements without assurance, so it would not deliver the requested opinion; an audit is the matching engagement. If the lender instead asks the practitioner to inspect ten named invoices for matching purchase orders, agreed-upon procedures can report each result without expressing an audit opinion.

Watch the distinction: A compilation report may accompany complete financial statements, which makes it look substantial. The appearance of the statements does not change the report’s lack of assurance.

Reference: [2]

3. Plan from materiality and risk

Plan from materiality and risk Materiality helps judge whether a misstatement could influence users, while risk concerns how likely a misstatement is and whether planned procedures will detect it. Begin with the financial statements and a planning materiality amount, then assess particular accounts and assertions. A large balance with a difficult valuation can merit more persuasive evidence than a small, routine balance. Size is not the only cue: fraud susceptibility, estimation uncertainty, unusual transactions, and possible aggregation with other errors can change the response. Planning materiality guides work; it is neither a permitted error in each account nor proof that a reported balance is right. Set the nature, timing, and extent of procedures in response to the assessed risk, and revisit the plan when evidence changes the assessment. Work through more AUD study examples to practice that sequence.

Worked example: Assume planning materiality is $100,000. One estimate has a plausible $140,000 valuation error; another balance has a plausible $5,000 error. All else equal, the first needs a stronger audit response because its possible error exceeds the planning amount. Neither estimate proves an actual misstatement. The auditor still needs evidence about each balance, including whether smaller errors could accumulate.

Watch the distinction: It is easy to label every amount below planning materiality correct. Materiality measures potential significance, not accuracy, and several individually small misstatements may matter together.

Reference: [2]

4. Understand controls before relying on them

Understand controls before relying on them A control has several questions attached to it. Design asks whether the specified action could prevent or detect the relevant error if performed. Implementation asks whether the entity put it into use. Operating effectiveness asks whether it actually worked throughout the period for which the auditor plans to rely on it. Read the policy, trace a transaction through the process, and identify who performs the control and what evidence remains. To assess consistent operation, select instances across the relevant period, inspect approval evidence, and follow up on exceptions. The population must match the control’s rule: a purchase approval threshold requires attention to purchases above that threshold. A well-written policy cannot lower control risk merely by existing. If operation is unsupported, revise the reliance decision and the substantive audit response.

Worked example: A purchasing policy requires manager approval above $5,000. The auditor finds the policy and one approved $6,200 purchase. That supports the control’s design and shows it was implemented for that transaction. It does not establish consistent operation. The auditor identifies purchases above $5,000 across the relevant period, tests selected approvals, and investigates missing evidence before relying on the control.

Watch the distinction: One clean walkthrough is often mistaken for a period-wide control test. It shows how a transaction moved through the process, not how reliably approvals occurred throughout the period.

Reference: [2]

5. Choose evidence for the assertion

Choose evidence for the assertion An assertion states what management’s reported number implies. Existence or occurrence asks whether recorded items are real. Completeness asks whether items that should be recorded are present. Valuation asks whether recorded amounts are measured appropriately. Cutoff asks whether transactions entered the correct period. The starting point of a test matters. Beginning with ledger entries and finding source support tests recorded transactions; beginning with source documents and finding ledger entries searches for omissions. For valuation, inspect pricing, estimates, or later collections as relevant. For cutoff, inspect documents around year-end and compare event dates with posting periods. Decide which potential error matters before selecting the evidence. A procedure can be strong for one assertion and weak for another, even when it uses the same documents.

Worked example: A recorded $8,000 sale matches a shipping document, which supports occurrence of that recorded sale. To test completeness, the auditor selects shipping documents and traces them into the sales ledger. A shipment absent from the ledger would be found by this second direction. The first test begins with recorded sales, so it cannot find shipments that were never recorded.

Watch the distinction: Matching a ledger total to supporting invoices does not establish that every transaction entered the ledger. Omitted transactions lie outside a sample selected from recorded entries.

Reference: [2]

6. Respond with control and substantive tests

Respond with control and substantive tests A control test asks whether the control operated as planned. A substantive procedure seeks direct evidence about transaction classes, balances, or disclosures. The two can be combined in an audit strategy, but weak control evidence changes what reliance is justified. First establish the population and what counts as an exception. Calculate the observed exception rate, investigate the cause and pattern, and consider whether the exceptions affect the assessed risk of material misstatement. Then adjust substantive work where necessary, perhaps by inspecting underlying invoices, bank records, or supplier information for affected payments and expanding work in the relevant population. A sample exception rate describes the tested items; it is not automatically the population’s exact error rate. Missing approval also does not, by itself, prove that a payment amount is misstated.

Worked example: The auditor tests 20 selected payments and finds three without required approval. The observed exception rate is 3 ÷ 20 = 15%. The auditor investigates whether the approvals are genuinely absent and whether the failures cluster by user or date. Reliance on the control may need to fall, while direct testing of affected payments and related transactions provides evidence about their validity and amounts.

Watch the distinction: A failed approval control is sometimes treated as proof of a 15% monetary misstatement. The rate measures missing approvals in the sample, not dollars lost or misstated.

Reference: [2]

7. Project a sample misstatement

Project a sample misstatement When a representative sample contains monetary errors, projection estimates what similar errors might mean for the population. For a simple ratio projection, divide the sample’s net misstatement by the sample’s recorded value, then multiply that ratio by the population’s recorded value. Keep the sign of an overstatement or understatement clear, and confirm that sample and population cover the same type of invoices. The result is a point estimate, not a known population error. Sampling risk remains because different random samples could produce different results. Consider the projected error alongside sampling uncertainty, other known misstatements, and the relevant materiality measure. Unusual large errors may need separate investigation rather than mechanical extrapolation. The auditor also needs to understand causes, such as a pricing rule that could affect many invoices.

Worked example: A random invoice sample has $40,000 of recorded value and $1,200 of overstatements. The sample error ratio is $1,200 ÷ $40,000 = 3%. Applied to a matching $600,000 recorded population, the point projection is 3% × $600,000 = $18,000 of overstatement. That estimate excludes a quantified allowance for sampling uncertainty, so it is not the final audit conclusion.

Watch the distinction: Multiplying the sample’s error ratio by the population gives a useful estimate, not an exact count of errors. Sampling uncertainty and unusual errors still need evaluation.

Reference: [2]

8. Validate data before using analytics

Validate data before using analytics An analytic result is only as useful as its input population. Before interpreting a sales trend or flagging unusual transactions, determine which records should be included, how the extract was produced, and whether its key fields are accurate. Reconcile control totals and record counts to a dependable source, inspect query filters and date boundaries, and trace selected rows back to original transactions. Check for duplicates, missing records, reversed entries, and unit or currency differences. A difference may be legitimate, such as an extract excluding a separately identified category, but it must be explained. After the population is validated, analytical patterns can direct audit attention. A smooth trend built from incomplete data can conceal precisely the transactions the auditor needs to examine.

Worked example: A sales extract sums to $9.7 million, while the reconciled ledger shows $10.0 million. The gap is $10.0 million − $9.7 million = $0.3 million, or $300,000. The auditor compares query dates, entity filters, and excluded transaction codes, then reconciles the missing records before trusting a trend chart or selecting exceptions from the extract.

Watch the distinction: A polished dashboard can make an extract seem reliable. Visual clarity says nothing about whether the query captured the full transaction population or measured fields correctly.

Reference: [2]

9. Evaluate events after year-end

Evaluate events after year-end Later events can change how year-end statements are prepared or disclosed. Ask when the underlying condition arose. If an event after year-end provides evidence about a condition already present at year-end, use that evidence when assessing the reported amount. A later customer bankruptcy, supported by earlier distress, may illuminate whether the year-end receivable was collectible. If the condition first arose after year-end, it ordinarily does not change the year-end measurement, though a significant event may require disclosure. Examine dates, correspondence, payment history, and other evidence rather than relying on the announcement date alone. The auditor considers events through the relevant audit period and evaluates whether management’s accounting and disclosure reflect the evidence. This is a question about conditions and financial reporting, not a rule that every later event changes prior balances.

Worked example: A customer owed $50,000 on December 31 and entered bankruptcy in January. December correspondence shows it was already unable to pay. The bankruptcy supplies evidence for assessing the December receivable and its loss allowance. A warehouse fire that first occurs in January concerns a new condition; assess its significance for disclosure rather than automatically reducing December assets.

Watch the distinction: The date an event becomes public is not necessarily the date its underlying condition began. Treating every January event alike can misstate December balances.

Reference: [2]

10. Form and communicate the audit conclusion

Form and communicate the audit conclusion Separate a departure from the reporting framework from an inability to obtain evidence. For a known misstatement, evaluate whether it is material and whether its effects are pervasive across the statements. An immaterial problem may leave the opinion unmodified. A material but confined misstatement can lead to a qualified opinion, describing the exception. A material and pervasive misstatement calls for an adverse opinion because the statements as a whole are misleading. If sufficient appropriate evidence cannot be obtained, the possible effects drive a different qualified-or-disclaimer analysis. Quantify the error, identify affected line items and disclosures, consider related effects, and communicate proposed corrections to management. An opinion follows the evaluated reporting problem; it is not a penalty for management’s refusal by itself.

Worked example: Management leaves a $200,000 inventory overstatement uncorrected. Assume it is material and confined to inventory and related cost of sales and income effects, without pervasive consequences. A qualified opinion can describe that departure and its effects. If the misstatement instead makes the financial statements broadly unreliable, the appropriate conclusion becomes adverse. The $200,000 figure alone does not determine pervasiveness.

Watch the distinction: Material and pervasive are different judgments. Calling every material error adverse overlooks whether the problem is confined; calling a pervasive error qualified understates its reach.

Reference: [2]

FAR section - Financial Accounting and Reporting

11. Build the primary statements

Build the primary statements The balance sheet presents assets, liabilities, and ending equity at a date; the income statement reports revenues and expenses over a period. First classify each balance by what it represents. Cash and receivables are assets, amounts owed are liabilities, and rent consumed during the period is an expense. Then calculate net income as revenues less expenses and carry it through the equity rollforward. With no owner transactions or other equity changes, ending equity equals beginning equity plus net income, and assets must equal liabilities plus ending equity. This relationship is a cross-check, not a substitute for classifying transactions correctly: an incorrectly capitalized expense can preserve the equation while overstating both assets and income. Practice tracing entries through the statements in the FAR study guide.

Worked example: Assets at year-end are $500,000 and liabilities are $310,000, so ending equity is $500,000 − $310,000 = $190,000. Beginning equity was $140,000. Assuming no owner transactions or other equity changes, net income is $190,000 − $140,000 = $50,000. The check is $310,000 + $190,000 = $500,000.

Watch the distinction: An expense is not a liability merely because it reduces equity. The expense belongs in period income; an unpaid amount arising from it may also create a liability.

Reference: [2]

12. Reconcile operating cash flow

Reconcile operating cash flow Accrual net income includes revenues before collection and expenses before payment. Under the indirect method, begin with net income, reverse noncash charges included in it, and adjust for operating asset and liability changes. Add depreciation because it reduced income without using cash in the current period. An increase in receivables means recognized revenue exceeded cash collected from customers, so subtract it. An increase in operating payables means some recognized costs remain unpaid, so add it. Apply the sign from the cash effect, not from a memorized account label: a decrease in receivables generally adds cash, while a decrease in payables generally uses cash. Check whether changes arise from operating transactions; acquisitions or reclassifications can require separate treatment.

Worked example: Net income is $80,000. Add $12,000 of depreciation, subtract a $9,000 increase in operating receivables, and add a $4,000 increase in operating payables. Operating cash flow is $80,000 + $12,000 − $9,000 + $4,000 = $87,000. The receivables increase means $9,000 of recognized net activity has not yet produced cash under these assumptions.

Watch the distinction: Adding every increase in a balance sheet account reverses the receivables adjustment. More receivables generally means less cash collected than the revenue recognized.

Reference: [2]

13. Track donor restrictions

Track donor restrictions For a nongovernmental not-for-profit, first read the donor’s terms. A purpose restriction limits how a contribution may be used and affects its classification in the statement of activities. When qualifying spending fulfills that purpose, report a release from donor restrictions: decrease the with-donor-restrictions class and increase the without-donor-restrictions class. The release changes classification rather than creating another contribution or another cash receipt. Keep a schedule by donor purpose so spending for one program is not used to release a different restriction. Also distinguish a restriction from a genuine condition that must be met before contribution recognition; the example assumes the gift is already recognized and carries a purpose restriction. Reconcile opening restricted balances, new restricted support, releases, and closing balances.

Worked example: A donor gives a nongovernmental not-for-profit $30,000 restricted to a program. The organization spends $18,000 on qualifying program costs. Assuming the contribution was recognized, no other activity occurred, and the spending fulfills the restriction, release $18,000. The restricted balance remaining is $30,000 − $18,000 = $12,000. The release reclassifies support; it is not a second $18,000 gift.

Watch the distinction: Spending restricted cash does not erase the original contribution revenue. The release changes its donor-restriction classification when the stated purpose is satisfied.

Reference: [2]

14. Choose a governmental reporting basis

Choose a governmental reporting basis Governmental fund statements emphasize current financial resources and use modified accrual accounting. Government-wide statements use the economic resources focus and accrual accounting. That difference changes how a long-lived purchase appears. A governmental fund generally records the use of current resources as a capital outlay expenditure; it does not carry the vehicle as a fund capital asset. In the government-wide view, the vehicle is a capital asset, with its cost allocated over useful periods through depreciation when applicable. Trace the same transaction through both views and reconcile their different measures of change. Do not assume that an expenditure means an asset has no service potential. The two presentations answer different questions: what happened to spendable fund resources and how the government’s overall economic position changed.

Worked example: A city pays $100,000 of current resources for a service vehicle. Its governmental fund records a $100,000 capital outlay expenditure, reducing fund resources. In government-wide statements, the city recognizes a $100,000 capital asset at acquisition, assuming the vehicle qualifies for capitalization. Later depreciation affects government-wide expense over its service life; the purchase is not immediately a $100,000 government-wide expense.

Watch the distinction: A capital outlay expenditure in a governmental fund does not mean the government-wide statements must expense the whole vehicle immediately. The reporting views use different measurement focuses.

Reference: [2]

15. Measure receivables and expected losses

Measure receivables and expected losses Gross trade receivables represent amounts billed or otherwise recorded as owed. The allowance estimates the portion expected not to be collected, so the reported net amount equals gross receivables less the ending allowance. Build the gross receivables rollforward from opening balance, credit sales, collections, write-offs, and other adjustments; reconcile it to the subledger before estimating losses. Then determine the required ending allowance from relevant evidence, such as aging and collection experience. The adjusting expense is the amount needed to move the existing allowance balance to that required ending balance. It is not necessarily equal to the total expected loss. A prior credit balance reduces the current adjustment, while a prior debit balance would increase it. Keep measurement of gross receivables separate from the allowance estimate.

Worked example: Gross receivables are $200,000, and the required ending allowance is an $8,000 credit. Net receivables are $200,000 − $8,000 = $192,000. If the allowance already has a $3,000 credit balance, record $8,000 − $3,000 = $5,000 of additional credit loss expense and an equal allowance credit. The resulting allowance is $8,000.

Watch the distinction: Recording the full $8,000 estimate as new expense would leave an $11,000 allowance when a $3,000 credit already exists. Adjust to the required ending balance.

Reference: [2]

16. Cost and write down inventory

Cost and write down inventory An inventory cost flow method assigns costs to units remaining and units sold. Under FIFO, the earliest costs flow to cost of goods sold first, leaving later layers in ending inventory. Identify quantities and unit costs in the remaining layers, multiply each pair, and sum them. Then apply the measurement comparison required by the stated facts. Net realizable value is the expected selling amount less relevant completion and selling costs; when the applicable lower-of-cost-and-net-realizable-value approach yields an amount below cost, reduce inventory and recognize the write-down in income. Avoid using a selling price alone as net realizable value unless the problem says those other costs are zero. Confirm that the comparison is applied at the appropriate level for the stated inventory facts and that quantities reconcile.

Worked example: Assume FIFO leaves 40 units from a $12-per-unit layer and 60 from a $15-per-unit layer. Ending cost is 40 × $12 + 60 × $15 = $480 + $900 = $1,380. If the applicable net realizable value for those units is $1,300, the write-down is $1,380 − $1,300 = $80. Report inventory at $1,300.

Watch the distinction: FIFO determines assigned cost; it does not guarantee that cost is the final carrying amount. A lower applicable net realizable value can require a write-down.

Reference: [2]

17. Depreciate and dispose of equipment

Depreciate and dispose of equipment At disposal, first bring depreciation current through the sale date under the asset’s depreciation method. Subtract accumulated depreciation and any other applicable carrying adjustments from original cost to obtain carrying amount. Compare net sale proceeds with that carrying amount to determine gain or loss. Cash received and gain answer different questions: cash is the amount collected, while gain measures how much that collection exceeds the asset’s book value. Remove both the equipment’s cost and accumulated depreciation from the accounts, record the proceeds, and recognize the difference. Check whether selling costs reduce proceeds and whether the stated accumulated depreciation already includes the period up to disposal. Using stale depreciation produces an incorrect carrying amount even if the cash figure is known.

Worked example: Equipment cost $100,000 and has $65,000 accumulated depreciation through its sale date. Its carrying amount is $100,000 − $65,000 = $35,000. With no selling costs, cash proceeds of $42,000 produce a $42,000 − $35,000 = $7,000 gain. The entry removes $100,000 of equipment and $65,000 of accumulated depreciation while recording $42,000 cash and $7,000 gain.

Watch the distinction: The $42,000 receipt is not a $42,000 gain. Most of that cash recovers the asset’s remaining $35,000 carrying amount.

Reference: [2]

18. Amortize a bond discount

Amortize a bond discount A bond issued below its face amount has a discount embedded in its opening carrying amount. Under the effective-interest method, compute each period’s interest expense by multiplying the beginning carrying amount by the effective rate for that period. Separately calculate or use the stated coupon cash payment. For a discount, effective interest expense exceeds cash interest; the difference amortizes the discount and increases the bond’s carrying amount toward its maturity amount. For a premium, the direction reverses. Keep the rate period consistent with the payment period: an annual rate cannot be applied to a half-year period without adjustment. A schedule should show opening carrying amount, interest expense, cash payment, amortization, and closing carrying amount, with each closing amount becoming the next period’s opening amount.

Worked example: A bond’s opening carrying amount is $95,000. Assume 6% is the effective rate for this payment period, and the coupon pays $5,000 for the same period. Interest expense is $95,000 × 6% = $5,700. Discount amortization is $5,700 − $5,000 = $700, increasing the closing carrying amount to $95,000 + $700 = $95,700.

Watch the distinction: Using the $5,000 cash coupon as interest expense ignores the discount’s financing cost. The effective rate applies to carrying amount, and the difference changes that amount.

Reference: [2]

19. Recognize revenue by performance

Recognize revenue by performance For a contract containing distinct promises, identify each performance obligation and allocate the transaction price using relative standalone selling prices. Add the standalone prices, divide each obligation’s price by that total, and apply each fraction to the contract price. The allocation determines how much revenue belongs to each promise; it does not make all revenue recognizable at contract signing. Recognize the assigned amount when, or as, the corresponding obligation is satisfied. A delivered device and a later service period can therefore have different recognition dates. Check whether the promises are actually distinct under the facts before splitting them. For practice, use CPA practice questions to trace both the allocation and the timing, since a correct allocation with premature recognition still overstates current revenue.

Worked example: A $900 contract includes a distinct device with an $800 standalone price and distinct service with a $200 standalone price. The total standalone price is $1,000. Allocate $900 × $800 ÷ $1,000 = $720 to the device and $900 × $200 ÷ $1,000 = $180 to service. If only the device has been delivered, recognize $720 then; recognize the $180 as the service obligation is satisfied.

Watch the distinction: Receiving all $900 in cash does not establish that all $900 is earned. Cash collection and satisfaction of the device and service promises can occur at different times.

Reference: [2]

20. Measure a lease after commencement

Measure a lease after commencement A lease liability tracks the present obligation for future lease payments. After commencement, accrue interest on the opening liability using the applicable periodic discount rate, then subtract the cash payment to find the closing liability. Equivalently, split the payment into interest and principal: payment less interest is the principal reduction. Confirm whether payment occurs at the beginning or end of the period, because that changes which balance earns interest. Keep the liability schedule distinct from accounting for the right-of-use asset and from the pattern of lease expense, which depends on the lease’s classification and other facts. A liability rollforward should reconcile opening balance, interest, payment, and closing balance. If a payment is smaller than accrued interest, the liability could rise despite cash being paid.

Worked example: Assume a $50,000 opening lease liability, a 5% rate for the period, and a $12,000 payment at period-end. Interest is $50,000 × 5% = $2,500. Principal repaid is $12,000 − $2,500 = $9,500. The closing liability is $50,000 + $2,500 − $12,000 = $40,500, which agrees with $50,000 − $9,500.

Watch the distinction: Subtracting the entire $12,000 payment from principal would understate the liability. The first $2,500 covers interest accrued during the period.

Reference: [2]

REG section - Taxation and Regulation

21. Resolve a tax return discrepancy

A return preparer may generally use information supplied by a client, but a visible inconsistency calls for reasonable inquiry. Compare the amounts, identify the period and transactions each source covers, and ask whether refunds, fees, cash receipts, or duplicate entries explain the difference. Then inspect records that can support the explanation, such as invoices, bank deposits, and the payment processor’s transaction detail. A processor’s net deposit can differ from gross receipts because it withholds fees, so matching deposits alone may not settle the issue. Document the reconciliation and carry the supported tax amount into the return. If the evidence remains unresolved, the preparer cannot make the discrepancy disappear by choosing the more favorable figure. This reasoning belongs to the tax practice and return preparation areas of the 2026 CPA Exam blueprints.

Worked example: A client’s receipts ledger totals $70,000, while a payment report totals $76,000 for the same period. The gap is $76,000 − $70,000 = $6,000. Transaction detail shows $6,000 of card sales absent from the ledger, with no refunds or duplicate entries. Assuming these are taxable business receipts, include $76,000 and correct the ledger reconciliation. If the detail instead shows duplicated transactions, substantiate and remove them before reporting.

Watch the distinction: Choosing the ledger’s $70,000 because it is the client’s record overlooks contrary evidence. The preparer must investigate the $6,000 difference and support the amount reported.

Reference: [2]

22. Determine whether a contract was formed

An offer proposes terms on which the offeror is willing to be bound. Acceptance ordinarily communicates agreement to those terms; changing a material term generally creates a counteroffer instead. Price is usually material, so a reply offering a different price does not accept the original proposal. Follow the sequence of communications: identify the live offer, ask whether the next response accepts it as presented, and then see whether the other party accepts any counteroffer. Consideration and other formation requirements still matter, and additional terms or special transaction rules can change the analysis. In a short business law problem, make the governing assumptions explicit and avoid treating every negotiation message as a contract. The decisive cue is mutual assent to the same essential bargain, shown through words or conduct under the stated facts.

Worked example: A seller offers equipment for $8,000. The buyer replies, “I will pay $7,500.” Because the buyer changed the price, the reply is a $7,500 counteroffer, not acceptance of the $8,000 offer. The seller then writes, “Agreed at $7,500.” Assuming the other formation requirements are met and no special rule alters the result, an agreement forms at $7,500.

Watch the distinction: A lower-price reply does not bind the seller to the original $8,000 proposal. It proposes a new bargain that the seller must accept before this simplified agreement forms.

Reference: [2]

23. Trace a creditor’s claim

A secured creditor has a claim tied to identified collateral when the security interest is valid and enforceable under the facts. The collateral offers a source of recovery that a general unsecured creditor lacks. Start by identifying the obligation, the collateral, and the amount realized from it. Apply the collateral proceeds to the secured claim, subject to any superior claims and transaction costs stated in the problem. If the proceeds fall short, the unpaid balance is a deficiency. That balance does not automatically retain a claim against other property ahead of unsecured creditors. Its recovery depends on the debtor’s remaining assets, other creditors, and the applicable priority rules. A balance sheet value is also different from actual sale proceeds, so use the figure the scenario says is realized. Avoid promising full collection merely because a security agreement exists.

Worked example: A lender is owed $55,000 and has a valid security interest in equipment that realizes $40,000. Assuming no senior claim or sale cost, $40,000 pays down the secured debt. The deficiency is $55,000 − $40,000 = $15,000. The lender can seek that unpaid amount, but actual recovery depends on the debtor’s other assets and applicable priority rules.

Watch the distinction: Calling the entire $55,000 debt secured by equipment worth $40,000 confuses the claim with its collateral coverage. The $15,000 shortfall requires separate recovery analysis.

Reference: [2]

24. Calculate tax basis and gain

Tax basis tracks the taxpayer’s unrecovered investment in property. Begin with original cost or another basis supplied by the facts, add capital improvements and other stated increases, and subtract allowable reductions such as depreciation. On a taxable sale, amount realized generally starts with proceeds and subtracts selling costs specified in the problem. Gain or loss is amount realized minus adjusted basis. Do that arithmetic before analyzing whether the result is capital or ordinary, or whether a special rule changes recognition. The property’s cash proceeds alone are not taxable gain because part may recover basis. Also distinguish a basis adjustment from an expense deduction: both can affect tax, but they operate at different points in the calculation. The REG study guide is a useful companion for practicing the order of these steps.

Worked example: A taxable asset cost $80,000 and has $18,000 of allowable basis reductions. Adjusted basis is $80,000 − $18,000 = $62,000. It sells for $75,000, with $3,000 of selling costs, so amount realized is $72,000. Gain is $72,000 − $62,000 = $10,000. That is the total gain; its tax character requires additional facts about the asset and prior deductions.

Watch the distinction: Subtracting basis directly from the $75,000 sale price overstates gain because it ignores $3,000 of selling costs. Determine amount realized first, then compare it with adjusted basis.

Reference: [2]

25. Build individual gross income

Gross income analysis asks what portion of a receipt represents an economic gain under the stated tax facts. Interest is generally income when recognized under the applicable method. By contrast, money received from selling property includes recovery of the taxpayer’s adjusted basis; only the excess of amount realized over basis is gain. Work item by item rather than adding every cash inflow. For a sale, establish proceeds, subtract any selling costs, compare the resulting amount realized with adjusted basis, and then decide whether special exclusions, deferrals, or character rules apply. A loan receipt or repayment of principal also illustrates why cash received need not equal income: an offsetting obligation or return of capital changes the result. For an individual return, the final inclusion may depend on timing and other facts, so state the assumptions before totaling the items.

Worked example: A taxpayer receives $4,000 of taxable interest and sells property for $9,000. The property’s adjusted basis is $7,000, and there are no selling costs or special rules. Sale gain is $9,000 − $7,000 = $2,000. The two items add $4,000 + $2,000 = $6,000 to gross income, while the other $7,000 of sale proceeds recovers basis.

Watch the distinction: Reporting the entire $9,000 sale receipt as income taxes the taxpayer’s recovered $7,000 investment. Calculate gain from amount realized and adjusted basis before adding it to gross income.

Reference: [2]

26. Apply deductions and credits in order

A deduction and a credit enter a tax calculation at different stages. First determine the relevant income base and subtract allowable deductions to arrive at taxable income under the problem’s assumptions. Then apply the supplied tax schedule or computed tax amount. Finally, apply an allowed credit against that tax, subject to any limits stated in the facts. A deduction reduces the income exposed to tax, so its value depends on the applicable rate and other calculation features. A credit reduces calculated tax directly, though it may be limited or refundable only when a rule says so. When comparing two proposed benefits, do not call equal dollar amounts equally valuable without knowing where each enters the calculation. Keep the steps in order, label each subtotal, and avoid importing current tax brackets into a hypothetical problem.

Worked example: Assume $90,000 of income and $15,000 of allowable deductions. Taxable income is $90,000 − $15,000 = $75,000. The problem supplies $12,000 of tax under its assumed schedule and a fully allowed $2,000 credit. Tax after the credit is $12,000 − $2,000 = $10,000. The deduction changes the taxable base; the credit reduces the computed tax.

Watch the distinction: Subtracting the $2,000 credit from income would produce the wrong taxable base. Apply deductions before calculating tax, then subtract allowed credits from the resulting tax.

Reference: [2]

27. Track a partner’s outside basis

Outside basis is a partner’s tax basis in the partnership interest, distinct from the partnership’s basis in its individual assets. It begins with the partner’s contribution or acquisition basis, then changes as tax items and transactions are allocated to that partner. Allocated income generally increases outside basis even if the partnership retains the cash. A cash distribution generally reduces basis, subject to rules for distributions exceeding basis. Partnership liabilities and other allocations may also change the figure, so a short problem must state whether to ignore them. Use a rollforward: opening basis, plus increases, minus decreases, equals ending basis. This sequence helps test whether a later loss or distribution can be absorbed. Do not equate basis with the partner’s capital account or with the market value of the ownership interest; those measures answer different questions.

Worked example: A partner begins with $30,000 of outside basis. The partnership allocates $8,000 of income to that partner, increasing basis to $38,000. A $5,000 cash distribution then reduces it to $33,000. Assuming no liability changes or other basis items, the rollforward is $30,000 + $8,000 − $5,000 = $33,000 of ending outside basis.

Watch the distinction: Ignoring the $8,000 income allocation because no cash was received understates basis. Allocated taxable income can raise outside basis even when the partnership retains its cash.

Reference: [2]

28. Apply an S corporation loss limit

An S corporation shareholder must check basis before using an allocated loss. Available stock basis and qualifying debt basis can provide capacity, but the debt basis must arise from a qualifying obligation to the shareholder under the facts. Determine the bases immediately before the loss after accounting for relevant changes, then compare their sum with the allocated loss. The portion exceeding basis is suspended under the basis limitation rather than deducted in the current period on that ground. Other limits, including at-risk and passive activity rules where applicable, may restrict even the amount that passes the basis test. The order matters: passing one gate does not establish a final deduction. Keep stock and debt basis records separate because later income, repayments, distributions, and losses can affect them differently.

Worked example: Before an allocated $25,000 loss, a shareholder has $18,000 of stock basis and $4,000 of qualifying debt basis. Total basis capacity is $22,000. Assuming no other changes, $22,000 passes the basis test and $25,000 − $22,000 = $3,000 exceeds basis for this period. Other applicable loss limitations still need to be checked before treating the $22,000 as currently deductible.

Watch the distinction: Deducting all $25,000 because the corporation incurred the loss ignores the shareholder-level basis limit. Only $22,000 passes that first test under the stated facts.

Reference: [2]

29. Reconcile corporate book and tax income

Book income and taxable income can differ because financial reporting and tax rules recognize some items differently. Start with book income and identify every item included there that receives different tax treatment. Add back a book expense that is nondeductible for tax; subtract income included in books but excluded from taxable income when the facts support it. Timing differences reverse in another period, while permanent differences do not. A reconciliation should name the item, its treatment in each system, and the direction of the adjustment. The direction is easier to see by asking whether the book item made book income lower or higher than taxable income. Do not assume that every book-to-tax adjustment changes cash taxes immediately; tax attributes and other return items may affect the final liability.

Worked example: A corporation reports $100,000 of book income after recording a $6,000 expense. The problem states that this expense is entirely nondeductible for tax, with no other differences. Add it back: $100,000 + $6,000 = $106,000 of taxable income. The addback reverses its reduction of book income; it does not mean the corporation received another $6,000 of cash.

Watch the distinction: Subtracting the nondeductible expense again reverses the adjustment. Because it already reduced book income but cannot reduce taxable income, add it back in the reconciliation.

Reference: [2]

30. Check an entity return against its records

An entity return should reconcile to the records that support each reported amount. Begin with the draft return line and the corresponding ledger balance, then compare periods, accounts, and transaction sources. A difference may reflect omitted receipts, duplicated imports, refunds, reclassifications, or amounts that belong elsewhere on the return. Trace it to source records before posting an adjustment. For receipts, establish whether the missing register contains taxable revenue, whether its transactions already appear under another account, and whether reported figures are gross or net of fees. Then update the return and retain a reconciliation that explains the bridge from records to reported amounts. An automated diagnostic can flag a mismatch, but the CPA still has to determine its cause. The goal is a supported return, not a forced agreement between two totals.

Worked example: A business ledger reports $240,000 of gross receipts; its draft return shows $228,000. The difference is $240,000 − $228,000 = $12,000. Source tracing finds a separate $12,000 receipt register omitted from the return. If those transactions are taxable and not recorded elsewhere on it, add $12,000 to report $240,000. Verify the register against invoices or deposits and document the reconciliation.

Watch the distinction: Automatically adding the $12,000 difference could duplicate revenue if the register is already included under another return line. Trace its transactions before changing the return.

Reference: [2]

BAR discipline - Business Analysis and Reporting

31. Read liquidity and leverage together

Liquidity and leverage ratios answer different questions even when their numerical results match. The current ratio divides current assets by current liabilities and gives a broad view of resources classified for near-term use relative to near-term obligations. It does not show how quickly inventory can be sold or receivables collected. Debt-to-equity divides the debt measure specified in the problem by equity, describing how much debt financing stands behind each dollar of book equity. It says little by itself about payment timing or borrowing terms. Before comparing periods or companies, check consistent definitions, reporting dates, and unusual balances. A strong current ratio can coexist with substantial leverage, and either ratio can hide concentrated risks. Read the underlying accounts, maturities, and cash flows alongside the ratios.

Worked example: A company has $300,000 of current assets and $150,000 of current liabilities. Its current ratio is $300,000 ÷ $150,000 = 2.0, or $2 of current assets per $1 of current liabilities. Total debt is $500,000 and equity is $250,000, giving debt-to-equity of $500,000 ÷ $250,000 = 2.0. The equal results describe different exposures, not equivalent financial strength.

Watch the distinction: Calling both 2.0 ratios evidence of the same condition confuses coverage with financing. Inspect asset convertibility for liquidity and debt terms and equity for leverage.

Reference: [2]

32. Normalize data for comparison

A comparison is meaningful only when the figures use compatible periods, units, definitions, and populations. A quarterly total will usually exceed a monthly total simply because it includes more time. Normalize to a common period before describing growth, then ask whether seasonality makes a straight monthly average misleading. Currency, unit counts, gross versus net sales, and changes in entity scope can create similar distortions. A useful sequence is to identify what each figure measures, convert units where justified, verify that underlying data are complete, and only then calculate the difference or percentage change. For a quarterly average, divide by three months; that calculation is descriptive and does not prove every month had the same sales. When a trend remains, separate a real operational change from an accounting or extraction change.

Worked example: This year’s quarterly sales are $1.2 million, while the comparable prior-year monthly figure is $400,000. The quarter averages $1.2 million ÷ 3 = $400,000 per month. On an equal-period basis, the difference is $0 and percentage growth is 0%, assuming the months are comparable and sales are evenly distributed. Monthly detail could still reveal seasonality concealed by the average.

Watch the distinction: Comparing $1.2 million directly with $400,000 suggests a threefold increase caused entirely by period length. Convert both figures to the same time basis first.

Reference: [2]

33. Separate price and quantity effects

Sales revenue changes because of selling price, units sold, or both. To explain the change without double counting, hold one factor constant in each step. One valid bridge measures the price effect at actual quantity: actual units multiplied by actual price minus planned price. It measures the volume effect at planned price: actual units minus planned units, multiplied by planned price. Add the two effects and check that their sum equals actual revenue minus planned revenue. A favorable price effect can be more than offset by fewer units sold. The bridge describes arithmetic drivers, not why customers bought fewer units or whether the higher price caused the volume decline. Investigate discounts, mix, capacity, demand, and data consistency before making a managerial claim. More BAR study guide problems can reinforce this reconciliation.

Worked example: Plan: 1,000 units × $20 = $20,000. Actual: 900 units × $22 = $19,800. Price effect is 900 × ($22 − $20) = $1,800 favorable. Volume effect is (900 − 1,000) × $20 = $2,000 unfavorable. The net is $200 unfavorable, matching $19,800 − $20,000 = −$200.

Watch the distinction: Using planned units for the price effect and actual price for the volume effect can produce a different bridge if mixed carelessly. State one consistent method and reconcile it to total revenue.

Reference: [2]

34. Find the contribution break-even point

Contribution margin is sales price less variable cost per unit. Each unit sold contributes that amount toward fixed costs; after fixed costs are covered, further units contribute toward operating profit under the assumed cost pattern. Divide fixed costs by unit contribution margin to find the break-even volume, rounding up to a whole unit when necessary. Check the result by multiplying units by contribution and subtracting fixed costs. This model assumes a relevant range in which price, unit variable cost, fixed costs, and sales mix remain as stated. It does not include financing costs or taxes unless the problem directs you to. If a target profit is given, add it to fixed costs before dividing. A zero or negative unit contribution margin means additional sales at those economics will not cover fixed costs.

Worked example: A product sells for $50 and incurs $30 of variable cost per unit, giving $20 of contribution. With $40,000 of fixed costs, break-even volume is $40,000 ÷ $20 = 2,000 units. Check: 2,000 × $20 − $40,000 = $0. At 2,100 units, operating profit is 2,100 × $20 − $40,000 = $2,000.

Watch the distinction: Dividing fixed costs by the $50 selling price ignores variable costs. Only the $20 remaining after each unit’s variable cost is available to cover fixed costs.

Reference: [2]

35. Compare an investment with its cost

Net present value compares a project’s cost now with the present value of its expected future cash flows. Discount each future flow at the assumed rate to reflect timing and required return, then sum those present values and subtract the initial investment. A positive NPV means the forecasted flows exceed the cost by that amount under those assumptions. It is a decision signal, not a guaranteed profit or cash balance. Before relying on it, check that cash flows and the discount rate use consistent tax, inflation, and risk assumptions, and that the project horizon includes relevant terminal effects. When present value is supplied directly, do not discount it a second time. If alternatives differ in scale or constraints, compare the full decision context rather than treating the largest positive NPV as an automatic answer.

Worked example: A project requires $100,000 now. The problem gives $112,000 as the present value of its future cash flows at the assumed discount rate. NPV is $112,000 − $100,000 = $12,000. It is positive, so the project exceeds the required return by $12,000 in present-value terms if the forecasts and discount rate hold.

Watch the distinction: Calling the $12,000 NPV this year’s cash profit confuses a discounted comparison with an accounting period result. NPV combines flows from different future dates in today’s dollars.

Reference: [2]

36. Build a cash forecast

A cash forecast starts with cash available at the beginning of a period, adds expected collections, and subtracts scheduled payments. The resulting balance is the amount before any new borrowing or other financing. Compare it with management’s stated minimum cash requirement to identify a projected financing gap. Distinguish this from profit: a profitable business can need cash when customers pay later than its bills come due. Timing within the period matters too. A month-end balance above the minimum does not rule out a midmonth shortage, so a tighter daily or weekly forecast may be needed for volatile cash flows. Test collection assumptions and payment dates, and keep uncertain financing sources separate from committed cash. The arithmetic gives a planning amount, not proof that funding will be available.

Worked example: Opening cash is $25,000. Expected collections add $80,000 and scheduled payments use $95,000, leaving $25,000 + $80,000 − $95,000 = $10,000 before financing. Management’s stated minimum is $18,000. The forecast gap is $18,000 − $10,000 = $8,000, so at least $8,000 of additional cash is needed to meet that period-end minimum under these assumptions.

Watch the distinction: Reporting the $10,000 closing forecast as the financing need reverses the comparison. The need is the $8,000 shortfall between projected closing cash and the stated minimum.

Reference: [2]

37. Allocate a business combination price

In a business combination, goodwill is a residual after measuring the consideration and the identifiable net assets acquired under the stated acquisition facts. First total the identifiable assets at their assigned fair values, then subtract assumed liabilities to obtain identifiable net assets. Compare that net amount with consideration; an excess can be goodwill. This simple calculation assumes a full acquisition with no noncontrolling interest, previously held interest, or other consideration adjustments. In a fuller case, those elements must be included, and an apparent bargain purchase requires reassessment of measurements before recognizing a gain. Do not label an unidentified balancing amount goodwill until the asset and liability measurements are complete. Goodwill represents benefits that are not separately recognized as identifiable assets, so it should not be used to hide an omitted asset or liability.

Worked example: Assume a buyer acquires 100% of a business for $500,000, with no other consideration components. Identifiable assets have a stated fair value of $440,000 and assumed liabilities are $90,000. Identifiable net assets are $440,000 − $90,000 = $350,000. Goodwill is $500,000 − $350,000 = $150,000. The FAR study guide supports practice with related asset and liability measurements.

Watch the distinction: Subtracting $440,000 of assets from the price ignores $90,000 of assumed liabilities. Calculate net identifiable assets first; otherwise goodwill is understated by $90,000.

Reference: [2]

38. Eliminate an internal sale

Consolidated statements present a parent and subsidiary as one economic entity. A sale between them has not created revenue for that combined entity, so eliminate the intercompany sale and corresponding purchase or cost of sales. If some transferred inventory remains unsold to outsiders, it still contains internal profit above the group’s original cost. Remove that unrealized profit from consolidated inventory and profit. Calculate it from the seller’s markup on the transferred goods multiplied by the portion still held within the group. If the sale remains unpaid, also eliminate the matching intercompany receivable and payable. Track the inventory when it is later sold externally so the deferred profit enters consolidated results then. Distinguish the full internal sale elimination from the smaller inventory profit adjustment; they address separate effects of the same transaction.

Worked example: Parent sells inventory costing $60,000 to its subsidiary for $80,000. Consolidation eliminates the $80,000 internal sale and related purchase or cost of sales. Half the goods remain unsold externally, so unrealized profit is ($80,000 − $60,000) × 50% = $10,000. Reduce consolidated inventory and profit by $10,000. If the sale is unpaid, eliminate the $80,000 intercompany receivable and payable too.

Watch the distinction: Removing only the $80,000 intercompany sale leaves $10,000 of internal profit in ending inventory. The unsold portion needs its own consolidation adjustment.

Reference: [2]

39. Reconcile a plan’s assets

An employee benefit plan asset rollforward tests whether beginning assets and period activity explain the closing balance. Add contributions and investment gains; subtract benefits paid and any other outflows specified. Compare the expected result with the reported closing assets. A difference is a diagnostic cue, not an automatic adjustment: it may arise from an omitted transaction, a valuation error, a timing difference, or a classification issue. Check that all figures cover the same plan, period, and measurement basis. Then trace contributions to remittance records, benefits to payment detail, and investment changes to custodian statements. If the sources show that one activity amount is wrong or missing, correct the relevant record and recompute the rollforward. Avoid plugging the unexplained difference into investment gain merely to make the total balance.

Worked example: Plan assets begin at $1,000,000. Contributions add $120,000, benefits paid subtract $80,000, and investment gain adds $50,000. Expected closing assets are $1,000,000 + $120,000 − $80,000 + $50,000 = $1,090,000. The statement reports $1,070,000, a $20,000 shortfall. Investigate transaction and valuation records before deciding which figure requires correction.

Watch the distinction: Treating the $20,000 difference as an investment loss without evidence makes the rollforward agree but may conceal a missing benefit payment or contribution error.

Reference: [2]

40. Account for a government encumbrance

A governmental fund encumbrance records a commitment against budgeted spending when a purchase order is issued. It helps show resources committed, although an order alone is not the same as receiving goods and incurring an expenditure. When the goods arrive and the government owes the supplier, reverse the related encumbrance and record the expenditure and payable for the actual invoice under the stated governmental fund facts. Compare ordered and invoiced amounts to determine whether an unfilled commitment remains. If the order is complete, release any unused encumbrance; if goods are still outstanding, retain or adjust the commitment for that portion. This budgetary entry differs from the financial event recorded on receipt. Always identify whether the question asks about fund budgetary records or a different reporting view before choosing the entries.

Worked example: A city issues a $30,000 purchase order and records a $30,000 encumbrance. The order is fully fulfilled, and the supplier invoices $28,000 when the goods arrive. Reverse the full $30,000 encumbrance, releasing its unused $2,000. Record a $28,000 governmental fund expenditure and $28,000 payable. The expenditure follows receipt and the actual obligation, not the original order amount.

Watch the distinction: Recording a $30,000 expenditure when the order is issued treats a commitment as goods received. Under these facts, the expenditure and payable arise for the $28,000 invoice.

Reference: [2]

ISC discipline - Information Systems and Control

41. Trace a transaction through a system

Follow a transaction through four stages: the original source, application processing, stored records, and the report. Give each transaction a stable identifier so you can check whether it passed from one stage to the next. A source record proves the order was entered, but it does not prove the order reached the transaction table. A transfer log can show whether an interface accepted or rejected it; the table shows what was stored; report criteria determine what appears to a reader. Compare record counts and monetary control totals at each handoff, then inspect individual exceptions. Also check whether a report uses order date, posting date, or another field, since a valid transaction can fall outside a filter. This reasoning supports the information systems and data management area of the 2026 ISC blueprint.

Worked example: Order 481 for $750 appears in the sales application and the transfer log shows successful delivery. Its row is in the transaction table, but the revenue report excludes it. The report filters on posting date; the order posted on January 2 while the report ends December 31. The order reached storage, so investigate the posting date and report period rather than the transfer.

Watch the distinction: Seeing a source order and calling the report complete skips two handoffs. Trace the identifier into storage and through the report filter before concluding where an omission occurred.

Reference: [2]

42. Join records with reliable keys

A primary key identifies one row in its table; a foreign key points to a related row elsewhere. Before joining tables, identify each table's grain: one row per order, line item, customer, or payment. A one-to-many join repeats fields from the one side on every matching detail row. That repetition is useful for examining lines but dangerous when summing header amounts. Check that primary keys are unique and foreign keys match valid records. Then calculate amounts at the correct grain: sum line amounts, or aggregate lines by order ID before comparing them with order headers. If an order has no detail row, an inner join will drop it, so choose the join type according to the question. Reconcile row counts and totals before using the result as evidence.

Worked example: Order 204 has a $100 header and two detail rows of $50 each. Joining on order ID returns two rows, each displaying the $100 header, so summing that column gives a false $200. Summing details gives $50 + $50 = $100. Alternatively, group by unique order ID and take its single $100 header value. The order total remains $100.

Watch the distinction: A duplicated header after a join does not mean two orders were placed. It reflects the one-to-many relationship; summing at the wrong grain doubles the amount.

Reference: [2]

43. Limit logical access

Start with the job a user must perform, then compare it with the transactions that the user's permissions allow. A conflict arises when one person can initiate and complete a sensitive transaction without an independent check. Creating suppliers and approving their payments is one example: a false supplier could be added and paid through the same account. Prefer separate roles with only the permissions each role needs. If staffing makes separation impractical, a review can reduce risk when an independent person examines complete, timely evidence and can investigate unusual changes or payments. Access reviews should cover privileged accounts, shared accounts, terminated users, and changes in duties. Logs help only if actions can be attributed to a user and someone actually examines relevant exceptions. Evaluate the path a user could take through the system, not merely the names of assigned roles.

Worked example: A purchasing clerk can create supplier 881 and approve its $4,600 payment. The clerk therefore controls both the payee record and authorization. Remove one privilege, or require an independent reviewer to examine new suppliers and their first payments before release. A report that excludes supplier changes would miss this risk even if it lists all approved payments.

Watch the distinction: A supervisor's general awareness of payments does not automatically resolve conflicting access. The review must cover the relevant supplier changes and payments, with enough detail and timing to detect misuse.

Reference: [2]

44. Control software changes

A reliable change trail links the request, authorized specification, code version, test results, approval, and production deployment. Each stage answers a different question. Approval shows the change was permitted; testing shows a particular version behaved as expected in a test environment; deployment records show what actually entered production. Match version identifiers, build hashes, or other release evidence across those stages. Check whether test cases cover both the intended calculation and likely error conditions, then look for failures, fixes, and retests. Emergency changes deserve the same trace even when approval occurs through an expedited process. A production version that differs from the tested version breaks the evidence chain. Determine what changed, obtain evidence of testing for the deployed version, and assess whether affected transactions require correction.

Worked example: A revised tax calculation was approved as version 3.2 and passed staging tests. Deployment records show version 3.3 in production. The matching approval and staging result establish nothing about the added changes in 3.3. Compare the versions, identify the differences, and test the deployed calculation. If 3.3 processed returns, examine those results for errors before relying on the control.

Watch the distinction: Passing staging tests does not prove the production calculation works when a different build was installed. Tie the test evidence to the deployed version and inspect any intervening change.

Reference: [2]

45. Plan recovery from an outage

Separate how much data the organization can afford to lose from how long it can afford to be without the system. Backup frequency affects the first question; restoration capacity, dependencies, and rehearsals affect the second. Identify the last usable copy, its location, and what transactions occurred afterward. A completed backup job is evidence that a process ran, but the copy may be corrupt, inaccessible, or missing a required database component. A restoration test checks that data can be recovered and the application can use it. Consider whether backups share the failed system's location or credentials, and whether a recovered system can reconcile reconstructed transactions. Match the plan to the business need stated in the scenario instead of assuming a nightly backup is automatically adequate.

Worked example: A sales database is backed up at midnight and fails at 4 p.m. With no later recoverable copy, as much as 16 hours of changes may need reconstruction. If the stated tolerance is eight hours of lost data, this schedule falls short. A successful backup message does not settle recovery time; restore a copy and measure when the application becomes usable.

Watch the distinction: Backup frequency alone cannot establish recovery readiness. It estimates possible data loss; only a usable copy, restoration steps, and tested dependencies show whether service can resume within the stated need.

Reference: [2]

46. Respond to a security event

Treat unfamiliar privileged logins as a possible incident and preserve the ability to determine what happened. First contain active access by disabling the account, revoking sessions, or isolating affected systems as appropriate. Preserve logs, relevant system state, and a record of response actions. Then establish the time window, accounts and systems reached, and whether data or settings changed. Compare login events with authorized work and investigate linked activity, such as new accounts or unusual exports. Recovery requires trusted credentials, corrected vulnerabilities, restored data where needed, and monitoring for recurrence. The order matters: broad cleanup before preserving evidence can erase the very records needed to define the incident. Conclusions about scope should follow the available evidence; one suspicious login does not by itself prove that data was taken.

Worked example: At 9:10 a.m., an administrator account logs in from an unfamiliar location and exports a customer file at 9:18 a.m. Disable the account and preserve authentication and export logs. Check whether the login was authorized, which file was accessed, and whether other actions occurred. Reset access through a trusted process. Deleting the logs first would prevent a reliable scope assessment.

Watch the distinction: Immediately erasing suspicious logs may appear to clean the system, but it destroys the event trail. Contain access while preserving evidence, then investigate before declaring the incident resolved.

Reference: [2]

47. Protect sensitive data through its life cycle

Confidentiality concerns who can read information; privacy also concerns why information is collected, how it is used, how long it is retained, and when it is disclosed. Encryption protects data from unauthorized reading when implemented and managed effectively, but it does not justify collecting unnecessary fields or using data beyond its stated purpose. Map each field to a business purpose, restrict access by role, and identify where copies travel through exports, backups, and service providers. Set retention and deletion practices consistent with the applicable requirements and stated purpose. Check that access logs and permissions cover copies as well as the main application. In a scenario, ask two separate questions: is access controlled, and is the collection and use appropriate? A positive answer to one cannot substitute for the other.

Worked example: A customer file is encrypted but contains birth dates and purchase histories. The stated service requires purchase histories only. Encryption reduces unauthorized reading risk; it does not explain the birth dates. Confirm whether another stated purpose supports that field. If none does, remove it from collection and existing copies under the applicable retention process, while limiting access to the histories.

Watch the distinction: Calling encrypted data private confuses protection against reading with permission to collect and use it. Privacy analysis still requires a purpose for each field and appropriate retention and disclosure.

Reference: [2]

48. Validate data quality

An automated report is useful only if its input represents the intended population. Completeness asks whether expected records are present; accuracy asks whether fields agree with reliable sources; uniqueness asks whether an entity appears once when one row per entity is intended. Start by defining the report's grain and period. Compare row counts, unique IDs, and monetary control totals with the source, then investigate exceptions instead of silently deleting them. Duplicate rows can arise from a faulty export, a join, or legitimate multiple records per customer. Missing IDs may reveal filtering or transfer problems. After correction, rerun the checks and retain the reconciliation so another person can follow the result. A valid count is not enough when an amount field can still be wrong.

Worked example: An export has 10,000 rows and 9,950 unique customer IDs. The difference is 50 extra rows, but it does not yet prove 50 duplicate customers: some customers may have several extra rows. Inspect the repeated IDs and source records. If the intended grain is one row per customer, produce 9,950 verified records and reconcile their count and relevant totals to the source.

Watch the distinction: Removing every repeated ID without investigation may discard legitimate transactions. Establish the intended grain, determine why rows repeat, and reconcile the corrected export before treating its counts as evidence.

Reference: [2]

49. Choose the relevant SOC report

Begin with the assertion or control question you need answered. A SOC 1 report addresses controls at a service organization that are relevant to user entities' internal control over financial reporting. A SOC 2 report addresses controls against its stated trust services criteria, such as security or availability. The report label alone is insufficient: read the system description, services covered, period, control objectives or criteria, and the auditor's opinion. For a financial statement audit involving outsourced payroll, ask whether the report covers controls that affect wages, deductions, and payables. A security-focused report may offer useful context yet leave those financial reporting assertions unanswered. The 2026 CPA Exam blueprints identify SOC engagements as an ISC area; the relevant report still depends on the specific service and question.

Worked example: A processor calculates a company's wages and payroll payable. The auditor needs evidence about controls over those amounts. A SOC 1 report covering payroll processing may be relevant if its controls and period match the audit. A SOC 2 report focused on system security does not, by its title alone, answer whether wage calculations and postings were controlled.

Watch the distinction: Treating SOC 2 as an upgraded SOC 1 mistakes different reporting purposes for quality levels. Match the report's covered controls and criteria to the financial reporting assertion being assessed.

Reference: [2]

50. Read the limits of SOC evidence

Once a report appears relevant, determine exactly what it establishes. Check the covered service, report period, opinion, control tests, exceptions, and any complementary user entity controls. An exception may be isolated or may affect the control you intend to use; examine its nature and frequency before deciding. A report covering January through September does not establish operation during October through December. Obtain suitable evidence for the gap, such as later testing or other relevant information, and assess changes in the service or controls. Complementary controls describe actions the customer must perform for the service organization's controls to achieve their objectives; verify that the user entity actually performs them. Do not convert a favorable report opinion into blanket assurance over every transaction or every month.

Worked example: A payroll service's SOC report covers January 1 through September 30, while the user entity reports through December 31. The last three months are outside the tested period. The report also assumes the user approves payroll changes. Verify that approval control at the user entity, assess reported exceptions, and obtain evidence about October through December before relying on the service controls for the full year.

Watch the distinction: A favorable SOC opinion cannot fill an uncovered period or supply missing customer controls. Read the dates, exceptions, and complementary controls before deciding what evidence the report provides.

Reference: [2]

TCP discipline - Tax Compliance and Planning

51. Compare income timing choices

For a permitted deferral, compare the tax on the same income in each possible year using the problem's stated marginal rates. Multiplying the deferred amount by each rate gives the immediate tax difference. Then consider when the tax is paid: even equal nominal tax amounts can differ in present value if payment moves to a later year. A rate change can strengthen or reverse that timing benefit. Confirm that the item can legally be recognized in the later period under the facts; a preference to pay later does not create a deferral election. Also check whether shifting income changes other deductions, credits, or limitations. The REG study guide provides related tax foundations; here the planning decision rests on the stated timing permission and assumptions.

Worked example: Assume $10,000 of income can lawfully be deferred. At hypothetical marginal rates of 30% now and 20% next year, tax attributable to it is $10,000 × 30% = $3,000 now or $10,000 × 20% = $2,000 next year. The nominal saving is $1,000. Time value and interactions with other tax items could change the overall comparison.

Watch the distinction: Deferring income is not always beneficial just because tax is paid later. Compare the applicable rates and other effects, and first establish that the stated item qualifies for deferral.

Reference: [2]

52. Distinguish proceeds from investment gain

A sale's gross proceeds are the amount the buyer pays. Amount realized generally reflects those proceeds less selling costs borne by the seller under the stated facts. Gain or loss is the amount realized minus adjusted basis, which tracks the taxpayer's unrecovered investment after relevant adjustments. Keep these quantities in separate lines so a commission is not mistakenly deducted twice. Once the amount is calculated, identify the asset, holding period, and other facts needed to determine character and tax treatment; the arithmetic alone does not establish the applicable rate. For planning, compare the after-tax result of the sale with alternatives using explicit assumptions. A decline in cash after fees does not necessarily mean a tax loss when the amount realized still exceeds basis.

Worked example: An investor sells shares for $18,000 and pays $500 in selling costs. Amount realized is $18,000 − $500 = $17,500. With $14,000 adjusted basis, gain is $17,500 − $14,000 = $3,500. The investor receives $17,500 in net sale cash, but only $3,500 is gain under these assumptions. Tax treatment requires the remaining character and holding-period facts.

Watch the distinction: Treating the full $18,000 sale price as taxable gain ignores the $14,000 investment and selling costs. Calculate amount realized and subtract adjusted basis before considering character or rate.

Reference: [2]

53. Compare retirement contributions

Separate the current tax effect from later taxation. If a contribution is deductible under the problem's assumptions, multiply it by the current marginal rate to estimate the immediate tax reduction. A contribution that receives no current deduction has no such immediate reduction, but its later treatment may differ. A meaningful comparison tracks the same out-of-pocket cost or the same contribution amount, then states assumptions about growth, withdrawal timing, and future tax rates. Do not infer that the choice with the larger current refund has the larger lifetime value. Eligibility, contribution limits, and account rules can change the outcome, so use only the facts supplied in a calculation. When a problem provides no future rate or withdrawal facts, report the current effect and identify the missing inputs.

Worked example: Assume a $5,000 contribution is fully deductible and the taxpayer's hypothetical current marginal rate is 24%. Immediate tax reduction is $5,000 × 24% = $1,200, so current after-tax cost is $3,800. A $5,000 nondeductible contribution yields $0 current deduction and costs $5,000 now. Which produces more after-tax retirement value cannot be determined without later tax and growth assumptions.

Watch the distinction: A $1,200 current tax saving does not prove the deductible contribution is best overall. Future withdrawals and tax rates matter, and the two choices should be compared on consistent cash assumptions.

Reference: [2]

54. Include partnership liabilities in basis

A partner's outside basis begins with the partner's investment and changes as partnership items and liabilities are allocated. Under partnership tax rules, an increase in the partner's share of liabilities generally increases outside basis, while a decrease generally reduces it as a deemed distribution. The classification and allocation of liabilities matter: do not assume every partnership debt belongs entirely to one partner. First establish the partner's basis before the liability change, then determine the amount properly allocated to that partner, and finally apply any other stated basis adjustments. Basis helps determine how much loss may pass one limitation and whether a distribution exceeds the partner's investment. It does not by itself prove a loss is deductible, because other limitations may still apply.

Worked example: A partner has $40,000 outside basis before a liability allocation change. The problem states that the partner's share of partnership liabilities rises by $6,000, with no other changes. Revised outside basis is $40,000 + $6,000 = $46,000. The increase affects the partner's tax basis even though the partner received no $6,000 cash payment.

Watch the distinction: Adding the partnership's entire loan to every partner's basis overstates each investment. Use only the liability share allocated to the partner and account for any later decrease separately.

Reference: [2]

55. Analyze a partnership cash distribution

Compare cash received with the partner's outside basis immediately before the distribution, after any other required adjustments specified in the facts. A cash distribution generally reduces outside basis, but basis cannot fall below zero. When cash exceeds that basis, the excess is generally recognized as gain under the simplified cash-only facts. Calculate the remaining basis as the larger of zero and pre-distribution basis minus cash. Keep the partnership's income allocation separate from its cash movement: a partner may be taxed on allocated income without receiving cash, and a cash distribution does not automatically create income. Noncash property, liability changes, and special rules can alter a fuller problem, so do not extend the simplified result without checking those facts.

Worked example: A partner's outside basis is $30,000 immediately before a $24,000 cash distribution, with no other changes. Basis falls to $30,000 − $24,000 = $6,000; no cash exceeds basis. If the distribution were $34,000 instead, basis would fall to $0 and $34,000 − $30,000 = $4,000 would exceed basis and generally be gain under these assumptions.

Watch the distinction: Calling the entire distribution taxable income ignores the partner's outside basis. First reduce basis; only cash above available basis produces gain in this simplified cash distribution.

Reference: [2]

56. Order S corporation basis changes

Shareholder stock basis changes as stated income, distributions, and losses are applied in the required order. Begin with opening stock basis, add allocated income and other increases, then reduce it for distributions and applicable items before testing a loss. Losses cannot reduce stock basis below zero. Qualifying direct debt basis may permit additional loss after stock basis is used, but a shareholder guarantee alone should not be assumed to create that basis. Even a loss within stock and debt basis can face other limits, so identify which limitation the question asks about. Keep stock basis and debt basis in separate schedules, since repayments and later income can affect them differently. The decision sequence prevents a distribution or loss from being counted against basis that has already been used.

Worked example: Stock basis opens at $20,000. Allocated income adds $7,000, giving $27,000. A $5,000 cash distribution reduces stock basis to $22,000. A later $24,000 allocated loss uses at most $22,000 of stock basis, leaving $2,000 beyond stock basis. Qualifying debt basis or other facts must be examined before concluding how much loss is currently usable.

Watch the distinction: Applying the $24,000 loss before the distribution misstates available stock basis. Increase basis for income, account for the distribution, and then test the loss against the remaining basis.

Reference: [2]

57. Compare entity cash to owner cash

Keep taxable income, tax paid, and cash distributed in distinct columns. A corporation's $100,000 taxable income is measured from its tax items, not by subtracting cash sent to an owner. The owner's tax treatment of a distribution depends on entity type and, where relevant, earnings and profits, basis, and other facts. In a C corporation setting, an ordinary cash distribution is generally not a deduction that reduces corporate taxable income. In a pass-through setting, income can be allocated to owners even when retained by the entity. Therefore, identify the entity first, compute its taxable income, then separately analyze what the owner received and how it is characterized. This sequence avoids treating one dollar of cash movement as an expense without support.

Worked example: Assume a corporation has $100,000 taxable income before a $30,000 cash distribution to its shareholder. The distribution leaves corporate taxable income at $100,000 under the stated facts, not $70,000. Corporate cash falls by $30,000. Analyze the shareholder's receipt separately using the entity type and relevant distribution facts; the cash amount alone does not establish its tax character.

Watch the distinction: Subtracting an owner distribution from corporate income confuses a transfer of cash with a deductible business expense. Compute entity income first, then determine the distribution's consequences to the owner.

Reference: [2]

58. Model an entity choice

Compare structures using a consistent set of assumptions about income, deductions, distributions, owner compensation, and taxes at both entity and owner levels. Add all tax costs borne across those levels before comparing totals. A low entity rate can be misleading if distributions trigger additional owner tax; a structure with no entity tax can still produce a substantial owner bill. Separate tax cost from cash available to owners, because the same nominal tax result may involve different payment timing or retained cash. Change one assumption at a time to see whether the preferred result is robust. Non-tax factors, including liability arrangements, financing, and administrative costs, may also matter. A single numerical example supports a conditional conclusion about those facts, not a universal entity recommendation.

Worked example: Under hypothetical facts, Structure A incurs $24,000 entity tax and $6,000 owner tax, totaling $30,000. Structure B incurs no entity tax and $28,000 owner tax, totaling $28,000. B is $30,000 − $28,000 = $2,000 lower on these assumptions. If distributions or income change, recompute both levels before choosing; the example does not establish a general advantage.

Watch the distinction: Comparing only $24,000 of entity tax with $28,000 of owner tax omits A's additional $6,000 owner tax. Add entity and owner costs for each structure before drawing a conclusion.

Reference: [2]

59. Separate depreciation from sale gain

Calculate total gain before classifying it. Begin with original cost, subtract allowed or allowable depreciation and make any other stated basis adjustments. Then subtract adjusted basis from amount realized, which reflects proceeds and relevant selling costs. Prior depreciation can affect the character of recognized gain on business property; it does not create an additional gain on top of the total calculated amount. Asset type, use, holding period, and depreciation history determine the applicable character rules. If a problem supplies only cost, depreciation, and price, you can compute total gain but should not assign a final character without the required facts. This topic sits in the property transactions area of the 2026 TCP blueprint.

Worked example: Business equipment cost $90,000 and has $30,000 of allowed depreciation. Adjusted basis is $90,000 − $30,000 = $60,000. It sells for $75,000 with no selling costs, so amount realized is $75,000 and total gain is $75,000 − $60,000 = $15,000. The $30,000 depreciation history may affect character, but total gain remains $15,000.

Watch the distinction: Adding prior depreciation to the $15,000 sale gain double counts it. Depreciation already lowered adjusted basis; use the resulting total gain as the amount whose character must be analyzed.

Reference: [2]

60. Measure gain on an installment sale

Under a simplified installment example, calculate gross profit as selling price minus adjusted basis, then divide gross profit by the contract price stated in the problem to obtain a gross profit percentage. Apply that percentage to principal collected during the period. The remainder of that principal payment recovers basis. Track interest separately because it is not part of the gross profit percentage. For a fuller tax calculation, debt assumed by a buyer, selling expenses, depreciation-related rules, and exceptions can change the figures or timing. Do not apply the percentage to the whole sale price each time cash arrives; use it on the relevant principal collection. A schedule that separates principal, gain, basis recovery, and interest makes the calculation auditable.

Worked example: Assume property with $60,000 adjusted basis sells for $100,000, with no selling costs, debt, interest, or other adjustments in this calculation. Gross profit is $100,000 − $60,000 = $40,000, so the gross profit percentage is $40,000 ÷ $100,000 = 40%. A $25,000 principal collection contains $25,000 × 40% = $10,000 gain and $15,000 basis recovery.

Watch the distinction: Reporting the entire $25,000 collection as gain ignores basis recovery. Apply the 40% gross profit percentage to principal, and account for any interest separately when the facts include it.

Reference: [2]

Official references and further reading

All study guides

Choose your exam version

CPA AUD

CPA FAR

CPA REG

CPA BAR

CPA ISC

CPA TCP

AUD section - Auditing and Attestation

1. Independence and professional judgment

2. Match the engagement to its conclusion

3. Plan from materiality and risk

4. Understand controls before relying on them

5. Choose evidence for the assertion

6. Respond with control and substantive tests

7. Project a sample misstatement

8. Validate data before using analytics

9. Evaluate events after year-end

10. Form and communicate the audit conclusion

FAR section - Financial Accounting and Reporting

11. Build the primary statements

12. Reconcile operating cash flow

13. Track donor restrictions

14. Choose a governmental reporting basis

15. Measure receivables and expected losses

16. Cost and write down inventory

17. Depreciate and dispose of equipment

18. Amortize a bond discount

19. Recognize revenue by performance

20. Measure a lease after commencement

REG section - Taxation and Regulation

21. Resolve a tax return discrepancy

22. Determine whether a contract was formed

23. Trace a creditor’s claim

24. Calculate tax basis and gain

25. Build individual gross income

26. Apply deductions and credits in order

27. Track a partner’s outside basis

28. Apply an S corporation loss limit

29. Reconcile corporate book and tax income

30. Check an entity return against its records

BAR discipline - Business Analysis and Reporting

31. Read liquidity and leverage together

32. Normalize data for comparison

33. Separate price and quantity effects

34. Find the contribution break-even point

35. Compare an investment with its cost

36. Build a cash forecast

37. Allocate a business combination price

38. Eliminate an internal sale

39. Reconcile a plan’s assets

40. Account for a government encumbrance

ISC discipline - Information Systems and Control

41. Trace a transaction through a system

42. Join records with reliable keys

43. Limit logical access

44. Control software changes

45. Plan recovery from an outage

46. Respond to a security event

47. Protect sensitive data through its life cycle

48. Validate data quality

49. Choose the relevant SOC report

50. Read the limits of SOC evidence

TCP discipline - Tax Compliance and Planning

51. Compare income timing choices

52. Distinguish proceeds from investment gain

53. Compare retirement contributions

54. Include partnership liabilities in basis

55. Analyze a partnership cash distribution

56. Order S corporation basis changes

57. Compare entity cash to owner cash

58. Model an entity choice

59. Separate depreciation from sale gain

60. Measure gain on an installment sale

Official references and further reading

Frequently Asked Questions

Related Study Guides

Certified Management Accountant (CMA)

Association of Chartered Certified Accountants Qualification (ACCA)

Certified Anti-Money Laundering Specialist (CAMS)