Exam Bundle

The transaction posts to the beneficiary entity with correct due-to/due-from entries. That would verify a different case: A project consultant travels for a subsidiary company, but their expense report charges headquarters because intercompany expense configuration is missing. It does not verify the required corrective action: Update the authorized mileage expense rate and effective date in expense management.

The reimbursed amount and local accounting amount match the approved rate calculation. That would verify a different case: An employee attaches a receipt but submits a currency conversion with an incorrect reimbursement currency and exchange rate. It does not verify the required corrective action: Update the authorized mileage expense rate and effective date in expense management.

An over-limit test expense is flagged or blocked while an allowed amount proceeds. That would verify a different case: A receipt reimbursement exceeds the department's maximum hospitality allowance, but the expense report has no policy warning. It does not verify the required corrective action: Update the authorized mileage expense rate and effective date in expense management.

Per diem calculations depend on duration, destination and policy-specific allowances. That explains a separate case: A traveler claims a full-day meal per diem on a half-day trip when policy permits only a reduced amount. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Expense categories carry posting and policy treatment beyond descriptive labels. That explains a separate case: Employees submit taxi costs under a client entertainment expense category, creating incorrect tax and ledger treatment. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Intercompany expenses need explicit source and destination company accounting rules. That explains a separate case: A project consultant travels for a subsidiary company, but their expense report charges headquarters because intercompany expense configuration is missing. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Review expense legal entity when projects cross subsidiary boundaries. That safeguard is aimed at a different risk: A project consultant travels for a subsidiary company, but their expense report charges headquarters because intercompany expense configuration is missing. It does not most directly prevent recurrence of: Mileage policies apply an eligible distance and rate rather than a manual expense amount.

Reconcile sample international receipts and exchange-rate sources. That safeguard is aimed at a different risk: An employee attaches a receipt but submits a currency conversion with an incorrect reimbursement currency and exchange rate. It does not most directly prevent recurrence of: Mileage policies apply an eligible distance and rate rather than a manual expense amount.

Test expense threshold exceptions and approver authority. That safeguard is aimed at a different risk: A receipt reimbursement exceeds the department's maximum hospitality allowance, but the expense report has no policy warning. It does not most directly prevent recurrence of: Mileage policies apply an eligible distance and rate rather than a manual expense amount.

Enter the budget revision with the correct project financial dimension and budget model. This fits a DIFFERENT issue within Implement basic budgeting: A project manager submits a negative budget revision, but the register entry does not identify which project budget dimension it affects. It does not address the current problem, whose mechanism is: Budget allocation terms distribute amounts based on allocation definitions and driver percentages.

Adjust report period selection and the appropriate fiscal calendar context for the budget model. This fits a DIFFERENT issue within Implement basic budgeting: A budget model is correct, but its reporting period uses a calendar-year window that excludes the company's February fiscal-year start. It does not address the current problem, whose mechanism is: Budget allocation terms distribute amounts based on allocation definitions and driver percentages.

Create a budget transfer entry that decreases the source and increases the destination within approved rules. This fits a DIFFERENT issue within Implement basic budgeting: 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 address the current problem, whose mechanism is: Budget allocation terms distribute amounts based on allocation definitions and driver percentages.

The report contrasts actual and budgeted values for the same cost center, period and currency. That would verify a different 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. It does not verify the required corrective action: Configure allocation terms with the approved current driver basis and generate the budget allocation.

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: Configure allocation terms with the approved current driver basis and generate the budget allocation.

Project budget decreases by the approved amount and unrelated projects remain unchanged. That would verify a different case: A project manager submits a negative budget revision, but the register entry does not identify which project budget dimension it affects. It does not verify the required corrective action: Configure allocation terms with the approved current driver basis and generate the budget allocation.

Budget register entries inherit account and financial dimension context for scoped budget amounts. That explains a separate case: A project manager submits a negative budget revision, but the register entry does not identify which project budget dimension it affects. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget codes classify the type of budget register movement and may influence validation. That explains a separate 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. 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.

Cross-check budget reporting dates against company fiscal calendar configuration. That safeguard is aimed at a different risk: A budget model is correct, but its reporting period uses a calendar-year window that excludes the company's February fiscal-year start. It does not most directly prevent recurrence of: Budget allocation terms distribute amounts based on allocation definitions and driver percentages.

Record import batch IDs and reconcile register counts before acceptance. That safeguard is aimed at a different risk: A company's approved budget is in monthly amounts but the annual totals shown on a dashboard double-count copied register entries. It does not most directly prevent recurrence of: Budget allocation terms distribute amounts based on allocation definitions and driver percentages.

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 allocation terms distribute amounts based on allocation definitions and driver percentages.

Create specific budget control rules and groups with appropriate fund or program dimensions. This fits a DIFFERENT issue within Configure and manage budget controls: A government grant budget must be isolated from an operational budget, but both use one broad budget control rule. It does not address the current problem, whose mechanism is: Budget control tracking scope depends on included financial dimensions and rule combinations.

Configure controlled over-budget permission groups and thresholds for appropriate users. This fits a DIFFERENT issue within Configure and manage budget controls: Budget control warns on overspend but designated executive approvers may exceed budget up to a policy-defined amount. It does not address the current problem, whose mechanism is: Budget control tracking scope depends on included financial dimensions and rule combinations.

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

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: Configure budget control financial dimensions and groups to reflect approved department ownership.

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: Configure budget control financial dimensions and groups to reflect approved department ownership.

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: Configure budget control financial dimensions and groups to reflect approved department ownership.

Budget control rules can enforce separate available-fund pools for selected dimension combinations. That explains a separate case: A government grant budget must be isolated from an operational budget, but both use one broad budget control rule. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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.

Override permissions are an exception path that can still exhaust fiscal funds. That explains a separate case: An authorized budget override is used repeatedly on small purchases, but management cannot track the cumulative overage. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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.