Exam Bundle

Run overlap detection before subscription renewals and upgrades. That safeguard is aimed at a different risk: A customer upgrades from a monthly to an annual plan, but its old schedule continues billing and overlaps the new contract. It does not most directly prevent recurrence of: Expense deferral allocates incurred prepaid costs over their benefit period.

Require a signed amendment before changing schedule pricing. That safeguard is aimed at a different risk: A subscription customer receives a new contracted unit price midterm, but the billing schedule keeps the old amount. It does not most directly prevent recurrence of: Expense deferral allocates incurred prepaid costs over their benefit period.

Reconcile deferral schedules to invoicing and general ledger balances. That safeguard is aimed at a different risk: A prepaid annual license is invoiced today, but accounting books all recognized revenue immediately. It does not most directly prevent recurrence of: Expense deferral allocates incurred prepaid costs over their benefit period.

Set appropriate payment proposal due-date criteria and review selected vendors and invoices before generation. This fits a DIFFERENT issue within Implement and manage accounts payable: A vendor payment proposal includes invoices due next quarter because payment selection ignores the due date. It does not address the current problem, whose mechanism is: Vendor advances need distinct posting and settlement rather than being treated as final goods receipt.

Post the vendor credit memo through the supported vendor transaction workflow and settle with the original open invoice. This fits a DIFFERENT issue within Implement and manage accounts payable: A vendor credit memo is approved for a returned service charge, but the accountant enters it as an additional debit invoice. It does not address the current problem, whose mechanism is: Vendor advances need distinct posting and settlement rather than being treated as final goods receipt.

Review invoice matching price tolerance setup and the purchase order/vendor invoice price details. This fits a DIFFERENT issue within Implement and manage accounts payable: A two-way invoice matching policy flags a purchase price difference that is within contract tolerance, but AP users force approval without checking configuration. It does not address the current problem, whose mechanism is: Vendor advances need distinct posting and settlement rather than being treated as final goods receipt.

The vendor liability records the intended currency and correct accounting currency equivalent. That would verify a different case: A vendor invoice is received in EUR but its liability is initially valued in USD at the wrong exchange rate. It does not verify the required corrective action: Use the authorized vendor prepayment process with correct liability/asset treatment and subsequent settlement.

The posted invoice includes the freight fee and reconciles to the expected expense account and tax. That would verify a different case: A vendor charges an agreed freight fee, but the AP invoice amount differs from the purchase order because the charge code is missing. It does not verify the required corrective action: Use the authorized vendor prepayment process with correct liability/asset treatment and subsequent settlement.

A test payment settles subsidiary vendor invoices and creates reconciling intercompany entries. That would verify a different case: Central finance pays invoices for subsidiary companies, but the central payment journal does not create intercompany due-to/due-from balances. It does not verify the required corrective action: Use the authorized vendor prepayment process with correct liability/asset treatment and subsequent settlement.

Invoice charges add line/header costs outside the base purchase price and need explicit mapping. That explains a separate case: A vendor charges an agreed freight fee, but the AP invoice amount differs from the purchase order because the charge code is missing. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Centralized payments cross legal-entity boundaries and need explicit intercompany accounting. That explains a separate case: Central finance pays invoices for subsidiary companies, but the central payment journal does not create intercompany due-to/due-from balances. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Payment proposals use configured invoice eligibility and due-date selection criteria. That explains a separate case: A vendor payment proposal includes invoices due next quarter because payment selection ignores the due date. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile foreign-currency invoice values and rates at approval. That safeguard is aimed at a different risk: A vendor invoice is received in EUR but its liability is initially valued in USD at the wrong exchange rate. It does not most directly prevent recurrence of: Vendor advances need distinct posting and settlement rather than being treated as final goods receipt.

Reconcile intercompany document counts and amounts by period. That safeguard is aimed at a different risk: Intercompany vendor invoices are imported without matching seller-company sales invoice references, causing periodic reconciliation differences. It does not most directly prevent recurrence of: Vendor advances need distinct posting and settlement rather than being treated as final goods receipt.

Run a recurring invoice population reconciliation each month. That safeguard is aimed at a different risk: A regular vendor bills a fixed facilities fee monthly, but invoice staff enter it manually and miss a period. It does not most directly prevent recurrence of: Vendor advances need distinct posting and settlement rather than being treated as final goods receipt.

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 reporting may involve distinct transaction and reimbursement currencies with currency conversion.

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 reporting may involve distinct transaction and reimbursement currencies with currency conversion.

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 reporting may involve distinct transaction and reimbursement currencies with currency conversion.

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: Check expense transaction currency, reimbursement currency, company setup and rate for the transaction date.

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: Check expense transaction currency, reimbursement currency, company setup and rate for the transaction date.

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: Check expense transaction currency, reimbursement currency, company setup and rate for the transaction date.

Expense report workflow identity rules determine who may authorize employee costs. That explains a separate case: Expense reports stay in Submitted status because workflow approval roles were changed and no approver is assigned. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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.

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.

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 reporting may involve distinct transaction and reimbursement currencies with currency conversion.

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 reporting may involve distinct transaction and reimbursement currencies with currency conversion.

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 reporting may involve distinct transaction and reimbursement currencies with currency conversion.

Verify the active account structures and required dimension values before entering the budget register amount. This fits a DIFFERENT issue within Implement basic budgeting: A new cost center needs a startup budget but the financial dimension does not yet appear in budget register account combinations. It does not address the current problem, whose mechanism is: Budget registers can contain separate approved versions and reposted entries; aggregation requires correct selection.

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 registers can contain separate approved versions and reposted entries; aggregation requires correct selection.

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 registers can contain separate approved versions and reposted entries; aggregation requires correct selection.

Budget-to-actual reporting uses the current-year approved budget while prior-year data remains available separately. That would verify a different case: 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 verify the required corrective action: Reconcile posted budget register entry IDs and remove only confirmed duplicate unposted source entries through authorized correction.

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: Reconcile posted budget register entry IDs and remove only confirmed duplicate unposted source entries through authorized correction.

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: Reconcile posted budget register entry IDs and remove only confirmed duplicate unposted source entries through authorized correction.