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: AP foreign currency revaluation treats open obligations differently from original invoice booking.

Test boundary tolerance values and capture override approvals. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: AP foreign currency revaluation treats open obligations differently from original invoice booking.

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: AP foreign currency revaluation treats open obligations differently from original invoice booking.

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: Intercompany expenses need explicit source and destination company accounting rules.

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: Intercompany expenses need explicit source and destination company accounting rules.

Update the authorized mileage expense rate and effective date in expense management. This fits a DIFFERENT issue within Configure expense management: An employee submits mileage reimbursement using a stale flat rate despite a newly approved per-distance schedule. It does not address the current problem, whose mechanism is: Intercompany expenses need explicit source and destination company accounting rules.

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 appropriate intercompany expense management setup and legal entity accounting controls.

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 appropriate intercompany expense management setup and legal entity accounting controls.

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 appropriate intercompany expense management setup and legal entity accounting controls.

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.

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.

Per diem calculations depend on duration, destination and policy-specific allowances. That explains a separate case: A traveler claims a full-day meal per diem on a half-day trip when policy permits only a reduced amount. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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: Intercompany expenses need explicit source and destination company accounting rules.

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: Intercompany expenses need explicit source and destination company accounting rules.

Test representative trip lengths against the published travel policy. That safeguard is aimed at a different risk: A traveler claims a full-day meal per diem on a half-day trip when policy permits only a reduced amount. It does not most directly prevent recurrence of: Intercompany expenses need explicit source and destination company accounting rules.

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 register entries inherit account and financial dimension context for scoped budget amounts.

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 register entries inherit account and financial dimension context for scoped budget amounts.

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 register entries inherit account and financial dimension context for scoped budget amounts.

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: Enter the budget revision with the correct project financial dimension and budget model.

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: Enter the budget revision with the correct project financial dimension and budget model.

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: Enter the budget revision with the correct project financial dimension and budget model.

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 account dimensions must be valid under the ledger's financial dimension structure. That explains a separate case: A new cost center needs a startup budget but the financial dimension does not yet appear in budget register account combinations. 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.

Cross-check budget reporting dates against company fiscal calendar configuration. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Budget register entries inherit account and financial dimension context for scoped budget amounts.

Record import batch IDs and reconcile register counts before acceptance. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Budget register entries inherit account and financial dimension context for scoped budget amounts.

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 register entries inherit account and financial dimension context for scoped budget amounts.

Configure the approved budget control period interval and fiscal calendar range for available funding. This fits a DIFFERENT issue within Configure and manage budget controls: 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 address the current problem, whose mechanism is: Fund availability definitions determine which budget register movement types are included.

Review override transaction history and restrict over-budget permissions to the designated exception workflow. This fits a DIFFERENT issue within Configure and manage budget controls: An authorized budget override is used repeatedly on small purchases, but management cannot track the cumulative overage. It does not address the current problem, whose mechanism is: Fund availability definitions determine which budget register movement types are included.

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: Fund availability definitions determine which budget register movement types are included.

An executive within limit can proceed with audit evidence while ordinary users cannot bypass. That would verify a different case: Budget control warns on overspend but designated executive approvers may exceed budget up to a policy-defined amount. It does not verify the required corrective action: Review and configure the approved budget fund availability options to include applicable transfer movements.

Available funds reflect committed amounts only as intended, without double-counting the requisition and PO. That would verify a different case: A purchase order fails budget checking because the commitment is counted against both its requisition and the finalized purchase order. It does not verify the required corrective action: Review and configure the approved budget fund availability options to include applicable transfer movements.

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: Review and configure the approved budget fund availability options to include applicable transfer movements.