Exam Bundle

Audit deliberate changes to budget account and dimension values during approval. That safeguard is aimed at a different risk: A buyer can bypass a budget-check failure by changing the document description, though the account and amount remain over limit. It does not most directly prevent recurrence of: Budget control tracking scope depends on included financial dimensions and rule combinations.

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 tracking scope depends on included financial dimensions and rule combinations.

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 tracking scope depends on included financial dimensions and rule combinations.

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 planning allocations transform planned values according to selected methods and dimensions.

Map source headcount data to correct branch financial dimensions in the planning allocation or template. This fits a DIFFERENT issue within Configure and manage budget planning: 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 address the current problem, whose mechanism is: Budget planning allocations transform planned values according to selected methods and dimensions.

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 planning allocations transform planned values according to selected methods and dimensions.

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: Set up budget planning allocation rules to distribute the shared amount to approved departments.

Each branch's planned labor cost appears under its own financial dimension combination. That would verify a different case: 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 verify the required corrective action: Set up budget planning allocation rules to distribute the shared amount to approved departments.

The regional office can submit a plan and only authorized planners may approve it. That would verify a different case: The budget plan workflow applies to operating units but an unassigned regional office cannot submit its plan. It does not verify the required corrective action: Set up budget planning allocation rules to distribute the shared amount to approved departments.

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.

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.

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.

Reconcile plan approval totals to posted budget register before enforcing controls. That safeguard is aimed at a different risk: A plan is approved but its values are not reflected in the executable budget register used by budget control. It does not most directly prevent recurrence of: Budget planning allocations transform planned values according to selected methods and dimensions.

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 allocations transform planned values according to selected methods and dimensions.

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 allocations transform planned values according to selected methods and dimensions.

Update the appropriate asset group/book defaults for future assets under an approved effective date. This fits a DIFFERENT issue within Implement and manage fixed assets: A capitalized service vehicle has a ten-year useful life on one book but the policy changed to eight for new acquisitions. It does not address the current problem, whose mechanism is: Depreciation profiles define calculation methods independently of the acquisition amount.

Configure derived fixed asset books or supported book mapping for the intended reporting relationships. This fits a DIFFERENT issue within Implement and manage fixed assets: An asset must track local and group reporting books, but users create two unrelated asset IDs and the underlying acquisition is duplicated. It does not address the current problem, whose mechanism is: Depreciation profiles define calculation methods independently of the acquisition amount.

Configure the supported depreciation convention and service/start dates per financial policy. This fits a DIFFERENT issue within Implement and manage fixed assets: Fixed asset books have the correct depreciation method but no depreciation start convention, producing inconsistent first-month charges. It does not address the current problem, whose mechanism is: Depreciation profiles define calculation methods independently of the acquisition amount.

Asset ownership and balances appear in the proper legal entity after authorized transactions. That would verify a different case: An asset was created in the wrong legal entity and finance plans to fix the reporting by editing its name only. It does not verify the required corrective action: Assign the correct depreciation profile and calculation basis to the appropriate fixed asset book.

One asset retains related book values with appropriate reporting treatment and no duplicate acquisition. That would verify a different case: An asset must track local and group reporting books, but users create two unrelated asset IDs and the underlying acquisition is duplicated. It does not verify the required corrective action: Assign the correct depreciation profile and calculation basis to the appropriate fixed asset book.

Both project and purchase order test acquisitions create the correct asset/book accounting outcomes. That would verify a different case: A company acquires assets using both projects and purchase orders, but some transactions post to unmatched asset groups because default asset fields are missing. It does not verify the required corrective action: Assign the correct depreciation profile and calculation basis to the appropriate fixed asset book.

Fixed asset group defaults can supply book values at asset creation without automatically rewriting all historical assets. That explains a separate case: A capitalized service vehicle has a ten-year useful life on one book but the policy changed to eight for new acquisitions. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Fixed asset books represent alternative valuation/depreciation bases for one asset. That explains a separate case: Tax authorities require a separate accelerated depreciation calculation from financial reporting. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Depreciable amount depends on acquisition basis and residual value as configured in the book. That explains a separate case: The financial accounting team sets a negative residual value in the asset book without policy support, inflating planned depreciation. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Require in-service evidence before enabling depreciation. That safeguard is aimed at a different risk: An asset is acquired but depreciation is scheduled from the purchase order date instead of the date it became available for use. It does not most directly prevent recurrence of: Depreciation profiles define calculation methods independently of the acquisition amount.

Review derived-book mappings during capital policy maintenance. That safeguard is aimed at a different risk: An asset must track local and group reporting books, but users create two unrelated asset IDs and the underlying acquisition is duplicated. It does not most directly prevent recurrence of: Depreciation profiles define calculation methods independently of the acquisition amount.

Reconcile intercompany asset transfers and ownership evidence. That safeguard is aimed at a different risk: An asset was created in the wrong legal entity and finance plans to fix the reporting by editing its name only. It does not most directly prevent recurrence of: Depreciation profiles define calculation methods independently of the acquisition amount.

Complete the approved purchase order invoicing and fixed asset acquisition posting workflow. This fits a DIFFERENT issue within Process fixed asset transactions: A new fixed asset purchased through a PO has been received, but no acquisition transaction exists in its book. It does not address the current problem, whose mechanism is: An asset sale must derecognize the asset carrying amount in addition to recording customer proceeds.

Review and configure the appropriate multi-company depreciation processing selection. This fits a DIFFERENT issue within Process fixed asset transactions: Monthly depreciation is run in batch for several companies, but one legal entity's book was omitted from the batch scope. It does not address the current problem, whose mechanism is: An asset sale must derecognize the asset carrying amount in addition to recording customer proceeds.

Run depreciation with the correct book, asset status and processing date eligibility filters. This fits a DIFFERENT issue within Process fixed asset transactions: A fixed asset's monthly depreciation batch accidentally includes disposed assets. It does not address the current problem, whose mechanism is: An asset sale must derecognize the asset carrying amount in addition to recording customer proceeds.

Asset cost increases by the improvement and subsequent depreciation adjusts according to book policy. That would verify a different case: An asset was initially capitalized at $8,000 but a later capital improvement of $1,200 is booked as routine maintenance expense contrary to policy. It does not verify the required corrective action: Use the supported fixed asset disposal sale process linked to the appropriate free text invoice.

Both resulting assets show reconciled carrying values and independent future depreciation schedules. That would verify a different case: A company separates a combined machine into two components with different useful lives, but accounting only changes the asset description. It does not verify the required corrective action: Use the supported fixed asset disposal sale process linked to the appropriate free text invoice.

The asset's book transactions and GL balances reconcile after a controlled correction. That would verify a different case: An asset has a depreciation adjustment after an approved useful-life change, but finance manually edits accumulated depreciation account balances. It does not verify the required corrective action: Use the supported fixed asset disposal sale process linked to the appropriate free text invoice.