Exam Bundle

An executive within limit can proceed with audit evidence while ordinary users cannot bypass. That would verify a different case: Budget control warns on overspend but designated executive approvers may exceed budget up to a policy-defined amount. It does not verify the required corrective action: Review and configure the approved budget fund availability options to include applicable transfer movements.

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: Review and configure the approved budget fund availability options to include applicable transfer movements.

The control evaluates the authorized annual allocation while retaining period rules for other budgets. That would verify a different case: 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 verify the required corrective action: Review and configure the approved budget fund availability options to include applicable transfer movements.

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.

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.

Over-budget permissions allow scoped exceptions and should not be granted to all users. That explains a separate case: Budget control warns on overspend but designated executive approvers may exceed budget up to a policy-defined amount. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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: Fund availability definitions determine which budget register movement types are included.

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: Fund availability definitions determine which budget register movement types are included.

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: Fund availability definitions determine which budget register movement types are included.

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: Planning import and allocation dimension mappings determine reporting ownership.

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: Planning import and allocation dimension mappings determine reporting ownership.

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: Planning import and allocation dimension mappings determine reporting ownership.

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: Map source headcount data to correct branch financial dimensions in the planning allocation or template.

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: Map source headcount data to correct branch financial dimensions in the planning allocation or template.

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: Map source headcount data to correct branch financial dimensions in the planning allocation or template.

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.

Budget planning allocations require net-zero redistribution or source exclusion depending on the reporting model. That explains a separate case: An allocated expense appears twice in a consolidated plan because it is included as both the source corporate line and its distributed children. 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.

Review hierarchy effective dates before reforecast runs. That safeguard is aimed at a different risk: A division was reorganized, but budget plan summaries still roll up to its old parent department. It does not most directly prevent recurrence of: Planning import and allocation dimension mappings determine reporting ownership.

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: Planning import and allocation dimension mappings determine reporting ownership.

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: Planning import and allocation dimension mappings determine reporting ownership.

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: Fixed asset group defaults can supply book values at asset creation without automatically rewriting all historical assets.

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: Fixed asset group defaults can supply book values at asset creation without automatically rewriting all historical assets.

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: Fixed asset group defaults can supply book values at asset creation without automatically rewriting all historical assets.

The same asset produces separate book-specific depreciation schedules without mixing ledger layers. That would verify a different case: Tax authorities require a separate accelerated depreciation calculation from financial reporting. It does not verify the required corrective action: Update the appropriate asset group/book defaults for future assets under an approved effective date.

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: Update the appropriate asset group/book defaults for future assets under an approved effective date.

The first depreciation period aligns with the approved in-service date. That would verify a different case: 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 verify the required corrective action: Update the appropriate asset group/book defaults for future assets under an approved effective date.

Depreciation profiles define calculation methods independently of the acquisition amount. That explains a separate case: Financial statements require straight-line depreciation but a fixed asset book uses reducing-balance method. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Accounting recognition and depreciation start are separate dates influenced by book settings. That explains a separate case: An asset is acquired but depreciation is scheduled from the purchase order date instead of the date it became available for use. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Book mapping connects asset classification to the intended accounting and depreciation books. That explains a separate case: A fixed asset group has no book mapping, so acquisitions create assets with missing depreciation settings. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Review number sequence configuration during subsidiary onboarding. That safeguard is aimed at a different risk: A newly acquired production machine is assigned the wrong fixed asset number sequence and duplicates an existing identifier in a subsidiary. It does not most directly prevent recurrence of: Fixed asset group defaults can supply book values at asset creation without automatically rewriting all historical assets.

Compare planned depreciation under each book to approved accounting policy. That safeguard is aimed at a different risk: Financial statements require straight-line depreciation but a fixed asset book uses reducing-balance method. It does not most directly prevent recurrence of: Fixed asset group defaults can supply book values at asset creation without automatically rewriting all historical assets.

Test threshold boundaries and exceptions with accounting policy owners. That safeguard is aimed at a different risk: An asset group contains both small expensed tools and capital machinery, but the company wants capitalization limits by class. It does not most directly prevent recurrence of: Fixed asset group defaults can supply book values at asset creation without automatically rewriting all historical assets.