Exam Bundle

An eligible half-day trip calculates only the permitted per diem amount. That would verify a different case: A traveler claims a full-day meal per diem on a half-day trip when policy permits only a reduced amount. It does not verify the required corrective action: Repair expense approval workflow participant mapping and reassign eligible pending submissions appropriately.

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: Repair expense approval workflow participant mapping and reassign eligible pending submissions appropriately.

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: Repair expense approval workflow participant mapping and reassign eligible pending submissions appropriately.

Corporate card and personal out-of-pocket expenses have different settlement counterparties. That explains a separate case: An employee pays a reimbursable expense with a corporate card, yet the system also schedules the employee for direct cash reimbursement. 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.

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: Expense report workflow identity rules determine who may authorize employee costs.

Audit frequently confused categories and train submitters on usage. That safeguard is aimed at a different risk: Employees submit taxi costs under a client entertainment expense category, creating incorrect tax and ledger treatment. It does not most directly prevent recurrence of: Expense report workflow identity rules determine who may authorize employee costs.

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: Expense report workflow identity rules determine who may authorize employee costs.

Select the appropriate budget code indicating a revision or transfer rather than an original budget. This fits a DIFFERENT issue within Implement basic budgeting: 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 address the current problem, whose mechanism is: Budget revisions change the funding envelope, whereas transfers redistribute existing funds.

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 revisions change the funding envelope, whereas transfers redistribute existing funds.

Configure allocation terms with the approved current driver basis and generate the budget allocation. This fits a DIFFERENT issue within Implement basic budgeting: A company calculates departmental budgets by allocating a fixed corporate amount using headcount percentages, but an outdated driver produces distorted results. It does not address the current problem, whose mechanism is: Budget revisions change the funding envelope, whereas transfers redistribute existing funds.

The budget-to-actual report includes all approved fiscal periods with matching ledger actuals. That would verify a different case: 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 verify the required corrective action: Create the approved budget increase/revision instead of a fictitious balanced budget transfer.

Total budget remains unchanged while the two cost centers show the intended shift. That would verify a different case: 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 verify the required corrective action: Create the approved budget increase/revision instead of a fictitious balanced budget transfer.

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 the approved budget increase/revision instead of a fictitious balanced budget transfer.

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 registers can contain separate approved versions and reposted entries; aggregation requires correct selection. That explains a separate case: A company's approved budget is in monthly amounts but the annual totals shown on a dashboard double-count copied register entries. 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.

Preflight dimension structure changes before new departmental budget creation. That safeguard is aimed at a different risk: A new cost center needs a startup budget but the financial dimension does not yet appear in budget register account combinations. It does not most directly prevent recurrence of: Budget revisions change the funding envelope, whereas transfers redistribute existing funds.

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 revisions change the funding envelope, whereas transfers redistribute existing funds.

Require balanced source and destination amounts for every transfer. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Budget revisions change the funding envelope, whereas transfers redistribute existing funds.

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 rules can enforce separate available-fund pools for selected dimension 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 rules can enforce separate available-fund pools for selected dimension combinations.

Inspect budget control activation, document stage and financial dimension account matching rather than the text description. This fits a DIFFERENT issue within Configure and manage budget controls: A buyer can bypass a budget-check failure by changing the document description, though the account and amount remain over limit. It does not address the current problem, whose mechanism is: Budget control rules can enforce separate available-fund pools for selected dimension combinations.

The invoice receives the intended control treatment and no legitimate commitment is charged twice. That would verify a different case: An AP invoice passes budget control at purchase-order approval but is blocked later due to document source scope mismatch. It does not verify the required corrective action: Create specific budget control rules and groups with appropriate fund or program dimensions.

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: Create specific budget control rules and groups with appropriate fund or program dimensions.

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: Create specific budget control rules and groups with appropriate fund or program dimensions.

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.

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 availability can be checked over a configured time span distinct from the posting month. That explains a separate case: A capital purchase can use available annual budget, but budget checking rejects it because funds availability is limited to the current month. 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 rules can enforce separate available-fund pools for selected dimension 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 rules can enforce separate available-fund pools for selected dimension combinations.

Test an end-to-end requisition-to-invoice lifecycle under budget controls. That safeguard is aimed at a different risk: A purchase order fails budget checking because the commitment is counted against both its requisition and the finalized purchase order. It does not most directly prevent recurrence of: Budget control rules can enforce separate available-fund pools for selected dimension combinations.