Exam Bundle

A non-PO invoice cannot post before the required approval and valid coding are present. That would verify a different case: The AP department processes invoices with no purchase order, but one mandatory invoice approval workflow is bypassed. It does not verify the required corrective action: Configure a recurring vendor invoice template with controlled dates and amount.

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: Configure a recurring vendor invoice template with controlled dates and amount.

The vendor liability is reduced by the authorized credit and transaction linkage is visible. That would verify a different case: A vendor credit memo is approved for a returned service charge, but the accountant enters it as an additional debit invoice. It does not verify the required corrective action: Configure a recurring vendor invoice template with controlled dates and amount.

Global party identity and company-scoped vendor financial setup must not be conflated. That explains a separate case: A vendor is shared as a party across several entities, but one subsidiary's payment terms are accidentally overwritten globally. 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.

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.

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: Recurring vendor invoices reduce manual duplication but require timing and active contract review.

Include AP revaluation and ledger reconciliation in the close sequence. That safeguard is aimed at a different risk: A month-end AP foreign-currency revaluation is skipped and open vendor liabilities are understated. It does not most directly prevent recurrence of: Recurring vendor invoices reduce manual duplication but require timing and active contract review.

Enforce independent bank change validation and callback evidence. That safeguard is aimed at a different risk: A new vendor bank account is accepted from an unverified email and inserted directly into the next payment run. It does not most directly prevent recurrence of: Recurring vendor invoices reduce manual duplication but require timing and active contract review.

Run budget-to-actual reporting using approved budget model and actual ledger reporting dimensions. This fits a DIFFERENT issue within Implement basic budgeting: 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 address the current problem, whose mechanism is: Fiscal calendars govern period interpretation in budgets and general ledger.

Reconcile posted budget register entry IDs and remove only confirmed duplicate unposted source entries through authorized correction. This fits a DIFFERENT issue within Implement basic budgeting: 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 address the current problem, whose mechanism is: Fiscal calendars govern period interpretation in budgets and general ledger.

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: Fiscal calendars govern period interpretation in budgets and general ledger.

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: Adjust report period selection and the appropriate fiscal calendar context for the budget model.

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: Adjust report period selection and the appropriate fiscal calendar context for the budget model.

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: Adjust report period selection and the appropriate fiscal calendar context for the budget model.

Budget transfers differ from original budget increases and should preserve the overall funding envelope. That explains a separate case: Finance reallocates a portion of one cost center's budget to another, but the transfer is recorded as a new additional budget increase. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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 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.

Review allocation drivers and rounding during annual planning. That safeguard is aimed at a different risk: A company calculates departmental budgets by allocating a fixed corporate amount using headcount percentages, but an outdated driver produces distorted results. It does not most directly prevent recurrence of: Fiscal calendars govern period interpretation in budgets and general ledger.

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: Fiscal calendars govern period interpretation in budgets and general ledger.

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: Fiscal calendars govern period interpretation in budgets and general ledger.

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: Budget control should be keyed to financial transaction properties, not free-form narrative text.

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: Budget control should be keyed to financial transaction properties, not free-form narrative text.

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 should be keyed to financial transaction properties, not free-form narrative text.

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: Inspect budget control activation, document stage and financial dimension account matching rather than the text description.

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: Inspect budget control activation, document stage and financial dimension account matching rather than the text description.

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: Inspect budget control activation, document stage and financial dimension account matching rather than the text description.

Budget control tracking scope depends on included financial dimensions and rule combinations. That explains a separate case: The same amount appears available to two departments because budget control rules omit Department from the tracking dimension set. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget control only evaluates transaction sources and dimensions included in its active configuration. That explains a separate case: A purchase requisition exceeds its cost center budget yet receives no budget check because the budget control configuration is disabled. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget control rules can enforce separate available-fund pools for selected dimension combinations. That explains a separate case: A government grant budget must be isolated from an operational budget, but both use one broad budget control rule. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile transfers and revisions in budget control calculations. That safeguard is aimed at a different risk: Budget checks return an unexpected amount because budget fund availability excludes budget transfers that were already approved. It does not most directly prevent recurrence of: Budget control should be keyed to financial transaction properties, not free-form narrative text.

Run over-budget negative tests whenever enabling new purchasing document types. That safeguard is aimed at a different risk: A purchase requisition exceeds its cost center budget yet receives no budget check because the budget control configuration is disabled. It does not most directly prevent recurrence of: Budget control should be keyed to financial transaction properties, not free-form narrative text.

Document whether each fund control is annual, quarterly or monthly. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Budget control should be keyed to financial transaction properties, not free-form narrative text.