Exam Bundle

Budget-to-actual reporting uses the current-year approved budget while prior-year data remains available separately. That would verify a different case: A department has an approved annual operating budget, but its expenses are compared against a budget model for the prior fiscal year. It does not verify the required corrective action: Reconcile posted budget register entry IDs and remove only confirmed duplicate unposted source entries through authorized correction.

Total budget remains unchanged while the two cost centers show the intended shift. That would verify a different case: Finance reallocates a portion of one cost center's budget to another, but the transfer is recorded as a new additional budget increase. It does not verify the required corrective action: Reconcile posted budget register entry IDs and remove only confirmed duplicate unposted source entries through authorized correction.

Total authorized budget increases by exactly the approved supplemental amount. That would verify a different case: A department requests additional spending for an unforeseen event but finance enters it as a transfer from another cost center with no source budget. It does not verify the required corrective action: Reconcile posted budget register entry IDs and remove only confirmed duplicate unposted source entries through authorized correction.

Budget transfers differ from original budget increases and should preserve the overall funding envelope. That explains a separate case: Finance reallocates a portion of one cost center's budget to another, but the transfer is recorded as a new additional budget increase. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget-to-actual comparison needs aligned accounting periods and dimension contexts. That explains a separate case: A new quarter's approved forecast should be compared with actual expenses, but finance exports general ledger actuals into a separate spreadsheet without budget linkage. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget revisions change the funding envelope, whereas transfers redistribute existing funds. That explains a separate case: A department requests additional spending for an unforeseen event but finance enters it as a transfer from another cost center with no source budget. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Preflight dimension structure changes before new departmental budget creation. That safeguard is aimed at a different risk: A new cost center needs a startup budget but the financial dimension does not yet appear in budget register account combinations. It does not most directly prevent recurrence of: Budget registers can contain separate approved versions and reposted entries; aggregation requires correct selection.

Test project dimension selection in budget upload routines. That safeguard is aimed at a different risk: A project manager submits a negative budget revision, but the register entry does not identify which project budget dimension it affects. It does not most directly prevent recurrence of: Budget registers can contain separate approved versions and reposted entries; aggregation requires correct selection.

Require consistent period/dimension filters in variance reports. That safeguard is aimed at a different risk: A new quarter's approved forecast should be compared with actual expenses, but finance exports general ledger actuals into a separate spreadsheet without budget linkage. It does not most directly prevent recurrence of: Budget registers can contain separate approved versions and reposted entries; aggregation requires correct selection.

Review override transaction history and restrict over-budget permissions to the designated exception workflow. This fits a DIFFERENT issue within Configure and manage budget controls: An authorized budget override is used repeatedly on small purchases, but management cannot track the cumulative overage. It does not address the current problem, whose mechanism is: Budget control may validate different document stages, each requiring explicit scope and commitment handling.

Configure budget control financial dimensions and groups to reflect approved department ownership. This fits a DIFFERENT issue within Configure and manage budget controls: The same amount appears available to two departments because budget control rules omit Department from the tracking dimension set. It does not address the current problem, whose mechanism is: Budget control may validate different document stages, each requiring explicit scope and commitment handling.

Review the budget funds availability calculation and document commitment stages for appropriate source selection. This fits a DIFFERENT issue within Configure and manage budget controls: A purchase order fails budget checking because the commitment is counted against both its requisition and the finalized purchase order. It does not address the current problem, whose mechanism is: Budget control may validate different document stages, each requiring explicit scope and commitment handling.

The same over-limit transaction remains blocked regardless of description edits. That would verify a different case: A buyer can bypass a budget-check failure by changing the document description, though the account and amount remain over limit. It does not verify the required corrective action: Trace the budget control rule and source-document coverage for invoices versus purchase orders.

Available funds reflect committed amounts only as intended, without double-counting the requisition and PO. That would verify a different case: A purchase order fails budget checking because the commitment is counted against both its requisition and the finalized purchase order. It does not verify the required corrective action: Trace the budget control rule and source-document coverage for invoices versus purchase orders.

The exception report attributes cumulative overages by user and cost center. That would verify a different case: An authorized budget override is used repeatedly on small purchases, but management cannot track the cumulative overage. It does not verify the required corrective action: Trace the budget control rule and source-document coverage for invoices versus purchase orders.

Budget control only evaluates transaction sources and dimensions included in its active configuration. That explains a separate case: A purchase requisition exceeds its cost center budget yet receives no budget check because the budget control configuration is disabled. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Fund availability definitions determine which budget register movement types are included. That explains a separate case: Budget checks return an unexpected amount because budget fund availability excludes budget transfers that were already approved. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget availability can be checked over a configured time span distinct from the posting month. That explains a separate case: A capital purchase can use available annual budget, but budget checking rejects it because funds availability is limited to the current month. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Review exception users and approval thresholds quarterly. That safeguard is aimed at a different risk: Budget control warns on overspend but designated executive approvers may exceed budget up to a policy-defined amount. It does not most directly prevent recurrence of: Budget control may validate different document stages, each requiring explicit scope and commitment handling.

Run over-budget negative tests whenever enabling new purchasing document types. That safeguard is aimed at a different risk: A purchase requisition exceeds its cost center budget yet receives no budget check because the budget control configuration is disabled. It does not most directly prevent recurrence of: Budget control may validate different document stages, each requiring explicit scope and commitment handling.

Review aggregate over-budget approvals against revised funding plans. That safeguard is aimed at a different risk: An authorized budget override is used repeatedly on small purchases, but management cannot track the cumulative overage. It does not most directly prevent recurrence of: Budget control may validate different document stages, each requiring explicit scope and commitment handling.

Create the intended new-cycle budget planning scenario and controlled initial amounts rather than editing the prior-year approved plan. This fits a DIFFERENT issue within Configure and manage budget planning: One budget plan scenario carries prior-year balances, but new-year departmental plans should start with a clean approved baseline. It does not address the current problem, whose mechanism is: Budget plans and budget registers are related but separate data/process stages.

Configure the appropriate budget planning stage transitions, role assignment and review workflow. This fits a DIFFERENT issue within Configure and manage budget planning: A planning workflow advances before the manager reviews the department's numbers because no approval stage exists. It does not address the current problem, whose mechanism is: Budget plans and budget registers are related but separate data/process stages.

Configure distinct budget planning scenarios for baseline, optimistic and conservative projections. This fits a DIFFERENT issue within Configure and manage budget planning: The planning team needs optimistic and conservative scenarios, but overwrites the base scenario each cycle. It does not address the current problem, whose mechanism is: Budget plans and budget registers are related but separate data/process stages.

The plan cannot advance to finance consolidation without the intended manager approval. That would verify a different case: A planning workflow advances before the manager reviews the department's numbers because no approval stage exists. It does not verify the required corrective action: Complete the supported process to transfer approved budget plan amounts into the appropriate budget register entries.

The new planning year contains separate baseline values and the prior year's approved plan stays intact. That would verify a different case: One budget plan scenario carries prior-year balances, but new-year departmental plans should start with a clean approved baseline. It does not verify the required corrective action: Complete the supported process to transfer approved budget plan amounts into the appropriate budget register entries.

Each department has its scoped planning responsibility and a consolidated review stage receives submissions. That would verify a different case: An organization wants department managers to submit annual planning numbers but every department edits a single shared worksheet without workflow. It does not verify the required corrective action: Complete the supported process to transfer approved budget plan amounts into the appropriate budget register entries.

Budget planning scenarios represent alternative planning measures, not versions to overwrite each other. That explains a separate case: The planning team needs optimistic and conservative scenarios, but overwrites the base scenario each cycle. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget planning periods and scenarios partition versions of financial forecasts. That explains a separate case: One budget plan scenario carries prior-year balances, but new-year departmental plans should start with a clean approved baseline. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Organization hierarchies define budget planning aggregation and participant structures. That explains a separate case: A division was reorganized, but budget plan summaries still roll up to its old parent department. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Compare totals and allocation drivers after each hierarchy change. That safeguard is aimed at a different risk: A corporate budget plan should allocate a shared facilities amount by headcount, but manual spreadsheet splits are inconsistent. It does not most directly prevent recurrence of: Budget plans and budget registers are related but separate data/process stages.

Test rejection and resubmission paths with actual planning roles. That safeguard is aimed at a different risk: A planning workflow advances before the manager reviews the department's numbers because no approval stage exists. It does not most directly prevent recurrence of: Budget plans and budget registers are related but separate data/process stages.

Protect approved baseline scenario values during reforecasting. That safeguard is aimed at a different risk: The planning team needs optimistic and conservative scenarios, but overwrites the base scenario each cycle. It does not most directly prevent recurrence of: Budget plans and budget registers are related but separate data/process stages.