Exam Bundle

The expected bank file is generated once with traceable payment references and no duplicate settlement. That would verify a different case: A vendor payment batch is approved, but the payment file generation fails and the team plans to resubmit the journal without inspecting status. It does not verify the required corrective action: Apply the correct approved accounts payable charges code with the required posting/tax treatment.

Only invoices due in the authorized payment window appear in the proposal. That would verify a different case: A vendor payment proposal includes invoices due next quarter because payment selection ignores the due date. It does not verify the required corrective action: Apply the correct approved accounts payable charges code with the required posting/tax treatment.

The mismatched invoice is held or flagged, while a valid quantity/price invoice passes. That would verify a different case: A purchased item invoice is received for 130 units while the purchase order receipt shows only 100, but the invoice posts without a warning. It does not verify the required corrective action: Apply the correct approved accounts payable charges code with the required posting/tax treatment.

Vendor payment methods determine eligible payment instruments and bank account selection. That explains a separate case: A batch vendor payment run selects a bank account not authorized for that currency. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Vendor posting profiles map operational vendor liabilities to general ledger accounts. That explains a separate case: A new vendor invoice is booked to the wrong accounts payable control account because the vendor group has an incorrect posting profile. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Paired intercompany AR and AP documents need source references and company-specific posting accuracy. That explains a separate case: Intercompany vendor invoices are imported without matching seller-company sales invoice references, causing periodic reconciliation differences. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile bank currency and payment method before automated disbursements. That safeguard is aimed at a different risk: A batch vendor payment run selects a bank account not authorized for that currency. It does not most directly prevent recurrence of: Invoice charges add line/header costs outside the base purchase price and need explicit mapping.

Track prepayment approvals and outstanding unallocated advances. That safeguard is aimed at a different risk: A vendor prepayment is required before delivery, but finance pays the invoice's full final balance without recording the advance. It does not most directly prevent recurrence of: Invoice charges add line/header costs outside the base purchase price and need explicit mapping.

Require review of invoice count and dates prior to releasing payments. That safeguard is aimed at a different risk: A vendor payment proposal includes invoices due next quarter because payment selection ignores the due date. It does not most directly prevent recurrence of: Invoice charges add line/header costs outside the base purchase price and need explicit mapping.

Configure the appropriate expense category and associated main account, tax and policy mapping. This fits a DIFFERENT issue within Configure expense management: Employees submit taxi costs under a client entertainment expense category, creating incorrect tax and ledger treatment. It does not address the current problem, whose mechanism is: Expense policies constrain reimbursement based on category and configured employee eligibility.

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 policies constrain reimbursement based on category and configured employee eligibility.

Configure expense management per diem rules with applicable trip duration and meal reductions. This fits a DIFFERENT issue within Configure expense management: A traveler claims a full-day meal per diem on a half-day trip when policy permits only a reduced amount. It does not address the current problem, whose mechanism is: Expense policies constrain reimbursement based on category and configured employee eligibility.

A taxi test receipt posts to the intended travel account and is reported under the correct category. That would verify a different case: Employees submit taxi costs under a client entertainment expense category, creating incorrect tax and ledger treatment. It does not verify the required corrective action: Configure expense report policy limits for the applicable category and employee group.

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: Configure expense report policy limits for the applicable category and employee group.

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 expense report policy limits for the applicable category and employee group.

Expense reporting may involve distinct transaction and reimbursement currencies with currency conversion. That explains a separate case: An employee attaches a receipt but submits a currency conversion with an incorrect reimbursement currency and exchange rate. 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.

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.

Reconcile corporate card statements against reimbursed expenses. That safeguard is aimed at a different risk: An employee pays a reimbursable expense with a corporate card, yet the system also schedules the employee for direct cash reimbursement. It does not most directly prevent recurrence of: Expense policies constrain reimbursement based on category and configured employee eligibility.

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 policies constrain reimbursement based on category and configured employee eligibility.

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 policies constrain reimbursement based on category and configured employee eligibility.

Create or select the approved budget model and register entries for the correct fiscal period. This fits a DIFFERENT issue within Implement basic budgeting: 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 address the current problem, whose mechanism is: Budget codes classify the type of budget register movement and may influence validation.

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

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

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: Select the appropriate budget code indicating a revision or transfer rather than an original budget.

The budget line validates with the new cost center and appears in the intended budget report. That would verify a different case: A new cost center needs a startup budget but the financial dimension does not yet appear in budget register account combinations. It does not verify the required corrective action: Select the appropriate budget code indicating a revision or transfer rather than an original budget.

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: Select the appropriate budget code indicating a revision or transfer rather than an original budget.

Budget models and periods distinguish alternative budget sets and fiscal years. That explains a separate case: A department has an approved annual operating budget, but its expenses are compared against a budget model for the prior fiscal year. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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.

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.

Test project dimension selection in budget upload routines. That safeguard is aimed at a different risk: A project manager submits a negative budget revision, but the register entry does not identify which project budget dimension it affects. It does not most directly prevent recurrence of: Budget codes classify the type of budget register movement and may influence validation.

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

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