Exam Bundle

The distributed amounts reconcile to the original corporate total and approved driver ratios. That would verify a different case: A company calculates departmental budgets by allocating a fixed corporate amount using headcount percentages, but an outdated driver produces distorted results. It does not verify the required corrective action: Create a budget transfer entry that decreases the source and increases the destination within approved rules.

Budget report distinguishes original, revision and transfer transactions in the correct model. That would verify a different case: An imported budget register entry has the right cost center but uses an incorrect budget code, causing the movement to appear as an original budget. It does not verify the required corrective action: Create a budget transfer entry that decreases the source and increases the destination within approved rules.

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: Create a budget transfer entry that decreases the source and increases the destination within approved rules.

Budget account dimensions must be valid under the ledger's financial dimension structure. That explains a separate case: A new cost center needs a startup budget but the financial dimension does not yet appear in budget register account combinations. 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.

Fiscal calendars govern period interpretation in budgets and general ledger. That explains a separate case: A budget model is correct, but its reporting period uses a calendar-year window that excludes the company's February fiscal-year start. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile budget model/year labels before management reports. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Budget transfers differ from original budget increases and should preserve the overall funding envelope.

Check budget codes on imported register entries before posting. That safeguard is aimed at a different risk: An imported budget register entry has the right cost center but uses an incorrect budget code, causing the movement to appear as an original budget. It does not most directly prevent recurrence of: Budget transfers differ from original budget increases and should preserve the overall funding envelope.

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 transfers differ from original budget increases and should preserve the overall funding envelope.

Review and configure the approved budget fund availability options to include applicable transfer movements. This fits a DIFFERENT issue within Configure and manage budget controls: Budget checks return an unexpected amount because budget fund availability excludes budget transfers that were already approved. It does not address the current problem, whose mechanism is: Over-budget permissions allow scoped exceptions and should not be granted to all users.

Activate the applicable budget control setup and relevant document/source coverage. This fits a DIFFERENT issue within Configure and manage budget controls: A purchase requisition exceeds its cost center budget yet receives no budget check because the budget control configuration is disabled. It does not address the current problem, whose mechanism is: Over-budget permissions allow scoped exceptions and should not be granted to all users.

Configure the approved budget control period interval and fiscal calendar range for available funding. This fits a DIFFERENT issue within Configure and manage budget controls: A capital purchase can use available annual budget, but budget checking rejects it because funds availability is limited to the current month. It does not address the current problem, whose mechanism is: Over-budget permissions allow scoped exceptions and should not be granted to all users.

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: Configure controlled over-budget permission groups and thresholds for appropriate users.

Budget availability checks separate the two departments' balances despite shared expense main accounts. That would verify a different case: The same amount appears available to two departments because budget control rules omit Department from the tracking dimension set. It does not verify the required corrective action: Configure controlled over-budget permission groups and thresholds for appropriate users.

An over-budget requisition is blocked or warned under policy and an in-budget fixture succeeds. That would verify a different case: A purchase requisition exceeds its cost center budget yet receives no budget check because the budget control configuration is disabled. It does not verify the required corrective action: Configure controlled over-budget permission groups and thresholds for appropriate users.

Budget control may validate different document stages, each requiring explicit scope and commitment handling. That explains a separate case: An AP invoice passes budget control at purchase-order approval but is blocked later due to document source scope mismatch. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget funds availability can include pre-encumbrances, encumbrances and actuals according to setup. That explains a separate case: A purchase order fails budget checking because the commitment is counted against both its requisition and the finalized purchase order. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget control should be keyed to financial transaction properties, not free-form narrative text. That explains a separate case: A buyer can bypass a budget-check failure by changing the document description, though the account and amount remain over limit. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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: Over-budget permissions allow scoped exceptions and should not be granted to all users.

Include cross-program negative transactions in grant audit checks. That safeguard is aimed at a different risk: A government grant budget must be isolated from an operational budget, but both use one broad budget control rule. It does not most directly prevent recurrence of: Over-budget permissions allow scoped exceptions and should not be granted to all users.

Test PO approval, receipt and invoice scenarios in budget control regression. That safeguard is aimed at a different risk: An AP invoice passes budget control at purchase-order approval but is blocked later due to document source scope mismatch. It does not most directly prevent recurrence of: Over-budget permissions allow scoped exceptions and should not be granted to all users.

Configure allocation/reporting to distinguish source-to-destination transfers and avoid double counting at the roll-up level. This fits a DIFFERENT issue within Configure and manage budget planning: An allocated expense appears twice in a consolidated plan because it is included as both the source corporate line and its distributed children. It does not address the current problem, whose mechanism is: Budget planning scenarios represent alternative planning measures, not versions to overwrite each other.

Update the applicable organization hierarchy used by the budget planning process. This fits a DIFFERENT issue within Configure and manage budget planning: A division was reorganized, but budget plan summaries still roll up to its old parent department. It does not address the current problem, whose mechanism is: Budget planning scenarios represent alternative planning measures, not versions to overwrite each other.

Complete the supported process to transfer approved budget plan amounts into the appropriate budget register entries. This fits a DIFFERENT issue within Configure and manage budget planning: A plan is approved but its values are not reflected in the executable budget register used by budget control. It does not address the current problem, whose mechanism is: Budget planning scenarios represent alternative planning measures, not versions to overwrite each other.

Consolidated total equals the intended corporate amount once after distribution. That would verify a different case: An allocated expense appears twice in a consolidated plan because it is included as both the source corporate line and its distributed children. It does not verify the required corrective action: Configure distinct budget planning scenarios for baseline, optimistic and conservative projections.

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: Configure distinct budget planning scenarios for baseline, optimistic and conservative projections.

The posted budget model reflects the approved planning amounts and budget control uses them. That would verify a different case: A plan is approved but its values are not reflected in the executable budget register used by budget control. It does not verify the required corrective action: Configure distinct budget planning scenarios for baseline, optimistic and conservative projections.

Budget planning allocations transform planned values according to selected methods and dimensions. That explains a separate case: A corporate budget plan should allocate a shared facilities amount by headcount, but manual spreadsheet splits are inconsistent. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget plans and budget registers are related but separate data/process stages. That explains a separate case: A plan is approved but its values are not reflected in the executable budget register used by budget control. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Plan workflow participation depends on organizational hierarchy inclusion and role assignment. That explains a separate case: The budget plan workflow applies to operating units but an unassigned regional office cannot submit its plan. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Test representative headquarters and branch records when changing planning templates. That safeguard is aimed at a different risk: HR headcount forecasts are copied into operating expense plans, but the line's financial dimension is set to headquarters for all branches. It does not most directly prevent recurrence of: Budget planning scenarios represent alternative planning measures, not versions to overwrite each other.

Archive approved plans before starting annual planning cycles. That safeguard is aimed at a different risk: One budget plan scenario carries prior-year balances, but new-year departmental plans should start with a clean approved baseline. It does not most directly prevent recurrence of: Budget planning scenarios represent alternative planning measures, not versions to overwrite each other.

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 planning scenarios represent alternative planning measures, not versions to overwrite each other.