Exam Bundle

Review duplicates across manual and electronic AP intake channels. That safeguard is aimed at a different risk: The same vendor invoice arrives twice with different PDF filenames but the same vendor invoice number. It does not most directly prevent recurrence of: Vendor posting profiles map operational vendor liabilities to general ledger accounts.

Check legal-entity field scope before bulk vendor updates. That safeguard is aimed at a different risk: A vendor is shared as a party across several entities, but one subsidiary's payment terms are accidentally overwritten globally. It does not most directly prevent recurrence of: Vendor posting profiles map operational vendor liabilities to general ledger accounts.

Require source invoice and reason codes on vendor credit notes. That safeguard is aimed at a different risk: A vendor credit memo is approved for a returned service charge, but the accountant enters it as an additional debit invoice. It does not most directly prevent recurrence of: Vendor posting profiles map operational vendor liabilities to general ledger accounts.

Check expense transaction currency, reimbursement currency, company setup and rate for the transaction date. This fits a DIFFERENT issue within Configure expense management: An employee attaches a receipt but submits a currency conversion with an incorrect reimbursement currency and exchange rate. It does not address the current problem, whose mechanism is: Expense categories carry posting and policy treatment beyond descriptive labels.

Configure expense report policy limits for the applicable category and employee group. This fits a DIFFERENT issue within Configure expense management: A receipt reimbursement exceeds the department's maximum hospitality allowance, but the expense report has no policy warning. It does not address the current problem, whose mechanism is: Expense categories carry posting and policy treatment beyond descriptive labels.

Repair expense approval workflow participant mapping and reassign eligible pending submissions appropriately. This fits a DIFFERENT issue within Configure expense management: Expense reports stay in Submitted status because workflow approval roles were changed and no approver is assigned. It does not address the current problem, whose mechanism is: Expense categories carry posting and policy treatment beyond descriptive labels.

An example trip calculates reimbursement from the current rate and distance. That would verify a different case: An employee submits mileage reimbursement using a stale flat rate despite a newly approved per-distance schedule. It does not verify the required corrective action: Configure the appropriate expense category and associated main account, tax and policy mapping.

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: Configure the appropriate expense category and associated main account, tax and policy mapping.

The corporate card liability is recorded correctly and the employee is not reimbursed twice. That would verify a different case: An employee pays a reimbursable expense with a corporate card, yet the system also schedules the employee for direct cash reimbursement. It does not verify the required corrective action: Configure the appropriate expense category and associated main account, tax and policy mapping.

Expense policies constrain reimbursement based on category and configured employee eligibility. That explains a separate case: A receipt reimbursement exceeds the department's maximum hospitality allowance, but the expense report has no policy warning. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Mileage policies apply an eligible distance and rate rather than a manual expense amount. That explains a separate case: An employee submits mileage reimbursement using a stale flat rate despite a newly approved per-distance schedule. 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 rates and effective dates during annual travel policy updates. That safeguard is aimed at a different risk: An employee submits mileage reimbursement using a stale flat rate despite a newly approved per-distance schedule. It does not most directly prevent recurrence of: Expense categories carry posting and policy treatment beyond descriptive labels.

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 categories carry posting and policy treatment beyond descriptive labels.

Audit orphaned workflow assignments after organization changes. That safeguard is aimed at a different risk: Expense reports stay in Submitted status because workflow approval roles were changed and no approver is assigned. It does not most directly prevent recurrence of: Expense categories carry posting and policy treatment beyond descriptive labels.

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 models and periods distinguish alternative budget sets and fiscal years.

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 models and periods distinguish alternative budget sets and fiscal years.

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 models and periods distinguish alternative budget sets and fiscal years.

Budget report distinguishes original, revision and transfer transactions in the correct model. That would verify a different 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. It does not verify the required corrective action: Create or select the approved budget model and register entries for the correct fiscal period.

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 or select the approved budget model and register entries for the correct fiscal period.

Monthly budget sums equal the approved annual plan without duplicated transactions. That would verify a different case: 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 verify the required corrective action: Create or select the approved budget model and register entries for the correct fiscal period.

Budget revisions change the funding envelope, whereas transfers redistribute existing funds. That explains a separate 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. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Fiscal calendars govern period interpretation in budgets and general ledger. That explains a separate case: A budget model is correct, but its reporting period uses a calendar-year window that excludes the company's February fiscal-year start. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget allocation terms distribute amounts based on allocation definitions and driver percentages. That explains a separate case: A company calculates departmental budgets by allocating a fixed corporate amount using headcount percentages, but an outdated driver produces distorted results. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Distinguish transfer and revision approval types in budget workflows. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Budget models and periods distinguish alternative budget sets and fiscal years.

Require consistent period/dimension filters in variance reports. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Budget models and periods distinguish alternative budget sets and fiscal years.

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 models and periods distinguish alternative budget sets and fiscal years.

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 only evaluates transaction sources and dimensions included in its active configuration.

Review the budget funds availability calculation and document commitment stages for appropriate source selection. This fits a DIFFERENT issue within Configure and manage budget controls: A purchase order fails budget checking because the commitment is counted against both its requisition and the finalized purchase order. It does not address the current problem, whose mechanism is: Budget control only evaluates transaction sources and dimensions included in its active configuration.

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 only evaluates transaction sources and dimensions included in its active configuration.

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: Activate the applicable budget control setup and relevant document/source coverage.

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: Activate the applicable budget control setup and relevant document/source coverage.

Budget availability checks separate the two departments' balances despite shared expense main accounts. That would verify a different case: The same amount appears available to two departments because budget control rules omit Department from the tracking dimension set. It does not verify the required corrective action: Activate the applicable budget control setup and relevant document/source coverage.