Exam Bundle

Reconcile transfers and revisions in budget control calculations. That safeguard is aimed at a different risk: Budget checks return an unexpected amount because budget fund availability excludes budget transfers that were already approved. It does not most directly prevent recurrence of: Budget control should be keyed to financial transaction properties, not free-form narrative text.

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 should be keyed to financial transaction properties, not free-form narrative text.

Document whether each fund control is annual, quarterly or monthly. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Budget control should be keyed to financial transaction properties, not free-form narrative text.

Configure a budget planning process with an appropriate organization hierarchy and participant stages. This fits a DIFFERENT issue within Configure and manage budget planning: An organization wants department managers to submit annual planning numbers but every department edits a single shared worksheet without workflow. It does not address the current problem, whose mechanism is: Budget planning allocations require net-zero redistribution or source exclusion depending on the reporting model.

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 allocations require net-zero redistribution or source exclusion depending on the reporting model.

Add the office to the approved hierarchy and correct planning participant access for its stage. This fits a DIFFERENT issue within Configure and manage budget planning: The budget plan workflow applies to operating units but an unassigned regional office cannot submit its plan. It does not address the current problem, whose mechanism is: Budget planning allocations require net-zero redistribution or source exclusion depending on the reporting model.

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 allocation/reporting to distinguish source-to-destination transfers and avoid double counting at the roll-up level.

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: Configure allocation/reporting to distinguish source-to-destination transfers and avoid double counting at the roll-up level.

Allocated plan amounts reconcile to the corporate source and specified percentages. That would verify a different case: A corporate budget plan should allocate a shared facilities amount by headcount, but manual spreadsheet splits are inconsistent. It does not verify the required corrective action: Configure allocation/reporting to distinguish source-to-destination transfers and avoid double counting at the roll-up level.

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.

Budget planning processes coordinate distributed contributors through organization hierarchy and workflows. That explains a separate case: An organization wants department managers to submit annual planning numbers but every department edits a single shared worksheet without workflow. 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.

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 require net-zero redistribution or source exclusion depending on the reporting model.

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 planning allocations require net-zero redistribution or source exclusion depending on the reporting model.

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 planning allocations require net-zero redistribution or source exclusion depending on the reporting model.

Set the correct service/depreciation commencement date on the applicable asset book. This fits a DIFFERENT issue within Implement and manage fixed assets: 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 address the current problem, whose mechanism is: Legal entity ownership of a fixed asset is not determined by its description.

Review legal-entity fixed asset number sequence setup and generate the intended unique IDs. This fits a DIFFERENT issue within Implement and manage fixed assets: A newly acquired production machine is assigned the wrong fixed asset number sequence and duplicates an existing identifier in a subsidiary. It does not address the current problem, whose mechanism is: Legal entity ownership of a fixed asset is not determined by its description.

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: Legal entity ownership of a fixed asset is not determined by its description.

The test acquisition debits the approved fixed asset account with appropriate offsets. That would verify a different case: A newly acquired vehicle posts acquisition cost to an expense account instead of fixed asset cost because posting profiles are incomplete. It does not verify the required corrective action: Review asset ownership and apply the supported cross-company transfer/acquisition correction process instead of a display-name change.

The depreciation forecast stops at the intended residual threshold. That would verify a different case: The financial accounting team sets a negative residual value in the asset book without policy support, inflating planned depreciation. It does not verify the required corrective action: Review asset ownership and apply the supported cross-company transfer/acquisition correction process instead of a display-name change.

New vehicles use an eight-year life while existing asset accounting is assessed separately. That would verify a different case: 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 verify the required corrective action: Review asset ownership and apply the supported cross-company transfer/acquisition correction process instead of a display-name change.

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 disposal accounting has specialized transaction types separate from ordinary product revenue. That explains a separate case: An asset disposal gain is posted to the general sales revenue account instead of gain on disposal because its posting profile lacks the transaction mapping. 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.

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: Legal entity ownership of a fixed asset is not determined by its description.

Control retrospective versus prospective depreciation changes explicitly. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Legal entity ownership of a fixed asset is not determined by its description.

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: Legal entity ownership of a fixed asset is not determined by its description.

Use the supported depreciation adjustment/transaction workflow for the affected book rather than manual balance edits. This fits a DIFFERENT issue within Process fixed asset transactions: An asset has a depreciation adjustment after an approved useful-life change, but finance manually edits accumulated depreciation account balances. It does not address the current problem, whose mechanism is: Retirement timing determines when depreciation and book transactions cease.

Use an authorized fixed asset transfer procedure and determine whether a financial-dimension or ownership transfer is necessary. This fits a DIFFERENT issue within Process fixed asset transactions: A finance team changes an asset's location from one site to another and expects the general ledger to transfer its book value automatically. It does not address the current problem, whose mechanism is: Retirement timing determines when depreciation and book transactions cease.

Use the appropriate supported intercompany asset transfer and acquisition process for both entities. This fits a DIFFERENT issue within Process fixed asset transactions: An asset is transferred between two companies, but one company posts the disposal while the other fails to recognize the corresponding acquisition. It does not address the current problem, whose mechanism is: Retirement timing determines when depreciation and book transactions cease.

Only active eligible assets receive depreciation and disposed assets remain closed. That would verify a different case: A fixed asset's monthly depreciation batch accidentally includes disposed assets. It does not verify the required corrective action: Confirm the approved retirement/disposal effective date and correct processing eligibility for that asset book.

One legitimate acquisition cost remains in the asset book and general ledger. That would verify a different case: A finance clerk manually records an asset acquisition and a later PO invoice posts the same cost again. It does not verify the required corrective action: Confirm the approved retirement/disposal effective date and correct processing eligibility for that asset book.

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: Confirm the approved retirement/disposal effective date and correct processing eligibility for that asset book.