Exam Bundle

Validate milestone acceptance and billing triggers against the signed agreement. That safeguard is aimed at a different risk: A three-phase implementation contract requires billing milestones, but invoices are generated on a flat monthly frequency. It does not most directly prevent recurrence of: Price updates to billing schedules need effective dates and historical invoice preservation.

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: Price updates to billing schedules need effective dates and historical invoice preservation.

Use positive and negative item tests before enabling default deferral behavior. That safeguard is aimed at a different risk: A finance admin marks every expense of one vendor as deferred, even though only certain item classes require deferral. It does not most directly prevent recurrence of: Price updates to billing schedules need effective dates and historical invoice preservation.

Apply shared vendor party management while retaining the intended company-specific payment defaults. This fits a DIFFERENT issue within Implement and manage accounts payable: A vendor is shared as a party across several entities, but one subsidiary's payment terms are accidentally overwritten globally. It does not address the current problem, whose mechanism is: Three-way matching compares invoice details to the purchase order and product receipt within allowed tolerances.

Run the approved vendor foreign currency revaluation for eligible open vendor balances. This fits a DIFFERENT issue within Implement and manage accounts payable: A month-end AP foreign-currency revaluation is skipped and open vendor liabilities are understated. It does not address the current problem, whose mechanism is: Three-way matching compares invoice details to the purchase order and product receipt within allowed tolerances.

Configure the appropriate vendor posting profile and vendor group for the legal entity. This fits a DIFFERENT issue within Implement and manage accounts payable: A new vendor invoice is booked to the wrong accounts payable control account because the vendor group has an incorrect posting profile. It does not address the current problem, whose mechanism is: Three-way matching compares invoice details to the purchase order and product receipt within allowed tolerances.

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: Configure three-way matching and relevant invoice matching tolerances for the purchase order category.

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: Configure three-way matching and relevant invoice matching tolerances for the purchase order category.

A valid non-PO expense invoice is processed with the correct controls while PO invoices retain matching. That would verify a different case: An invoice arrives without a purchase order, but a matching-required policy is incorrectly applied to its permitted non-PO category. It does not verify the required corrective action: Configure three-way matching and relevant invoice matching tolerances for the purchase order category.

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.

Cash discounts are determined by configured terms and actual settlement timing. That explains a separate case: A supplier offers a cash discount if paid within ten days, but AP payment proposal ignores discount dates and pays full amount on day eight. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Price tolerance comparisons should be rule-based, not manually overridden without review. That explains a separate case: A two-way invoice matching policy flags a purchase price difference that is within contract tolerance, but AP users force approval without checking configuration. 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: Three-way matching compares invoice details to the purchase order and product receipt within allowed tolerances.

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: Three-way matching compares invoice details to the purchase order and product receipt within allowed tolerances.

Reconcile vendor group posting profiles against the financial statements before activation. That safeguard is aimed at a different risk: A new vendor invoice is booked to the wrong accounts payable control account because the vendor group has an incorrect posting profile. It does not most directly prevent recurrence of: Three-way matching compares invoice details to the purchase order and product receipt within allowed tolerances.

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: Per diem calculations depend on duration, destination and policy-specific allowances.

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: Per diem calculations depend on duration, destination and policy-specific allowances.

Configure payment method and personal-versus-corporate transaction handling on expense reports. This fits a DIFFERENT issue within Configure expense management: An employee pays a reimbursable expense with a corporate card, yet the system also schedules the employee for direct cash reimbursement. It does not address the current problem, whose mechanism is: Per diem calculations depend on duration, destination and policy-specific allowances.

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: Configure expense management per diem rules with applicable trip duration and meal reductions.

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 management per diem rules with applicable trip duration and meal reductions.

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 expense management per diem rules with applicable trip duration and meal reductions.

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.

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.

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: Per diem calculations depend on duration, destination and policy-specific allowances.

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: Per diem calculations depend on duration, destination and policy-specific allowances.

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: Per diem calculations depend on duration, destination and policy-specific allowances.

Create the approved budget increase/revision instead of a fictitious balanced budget transfer. This fits a DIFFERENT issue within Implement basic budgeting: 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 address the current problem, whose mechanism is: Budget transfers differ from original budget increases and should preserve the overall funding envelope.

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 transfers differ from original budget increases and should preserve the overall funding envelope.

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 transfers differ from original budget increases and should preserve the overall funding envelope.

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 a budget transfer entry that decreases the source and increases the destination within approved rules.

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 a budget transfer entry that decreases the source and increases the destination within approved rules.

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: Create a budget transfer entry that decreases the source and increases the destination within approved rules.