Exam Bundle

A test vendor invoice credits the correct AP control account and appears as an open vendor balance. That would verify a different case: 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 verify the required corrective action: Post the vendor credit memo through the supported vendor transaction workflow and settle with the original open invoice.

The same vendor party exists in approved companies with correct local terms on invoices. That would verify a different case: A vendor is shared as a party across several entities, but one subsidiary's payment terms are accidentally overwritten globally. It does not verify the required corrective action: Post the vendor credit memo through the supported vendor transaction workflow and settle with the original open invoice.

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: Post the vendor credit memo through the supported vendor transaction workflow and settle with the original open invoice.

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.

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.

Vendor advances need distinct posting and settlement rather than being treated as final goods receipt. That explains a separate case: A vendor prepayment is required before delivery, but finance pays the invoice's full final balance without recording the advance. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Review policy scope after adding new AP invoice types. That safeguard is aimed at a different risk: An invoice arrives without a purchase order, but a matching-required policy is incorrectly applied to its permitted non-PO category. It does not most directly prevent recurrence of: A vendor credit memo reduces accounts payable; it is not another ordinary liability invoice.

Review expected landed and invoice charges before matching exceptions are overridden. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: A vendor credit memo reduces accounts payable; it is not another ordinary liability invoice.

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: A vendor credit memo reduces accounts payable; it is not another ordinary liability invoice.

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 account dimensions must be valid under the ledger's financial dimension structure.

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: Budget account dimensions must be valid under the ledger's financial dimension structure.

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 account dimensions must be valid under the ledger's financial dimension structure.

Project budget decreases by the approved amount and unrelated projects remain unchanged. That would verify a different case: A project manager submits a negative budget revision, but the register entry does not identify which project budget dimension it affects. It does not verify the required corrective action: Verify the active account structures and required dimension values before entering the budget register amount.

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: Verify the active account structures and required dimension values before entering the budget register amount.

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: Verify the active account structures and required dimension values before entering the budget register amount.

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.

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.

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.

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: Budget account dimensions must be valid under the ledger's financial dimension structure.

Require balanced source and destination amounts for every transfer. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Budget account dimensions must be valid under the ledger's financial dimension structure.

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: Budget account dimensions must be valid under the ledger's financial dimension structure.

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: Override permissions are an exception path that can still exhaust fiscal funds.

Create specific budget control rules and groups with appropriate fund or program dimensions. This fits a DIFFERENT issue within Configure and manage budget controls: A government grant budget must be isolated from an operational budget, but both use one broad budget control rule. It does not address the current problem, whose mechanism is: Override permissions are an exception path that can still exhaust fiscal funds.

Review the budget funds availability calculation and document commitment stages for appropriate source selection. This fits a DIFFERENT issue within Configure and manage budget controls: A purchase order fails budget checking because the commitment is counted against both its requisition and the finalized purchase order. It does not address the current problem, whose mechanism is: Override permissions are an exception path that can still exhaust fiscal funds.

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 override transaction history and restrict over-budget permissions to the designated exception workflow.

Grant spending is checked against grant funds and does not consume ordinary operations budget. That would verify a different case: A government grant budget must be isolated from an operational budget, but both use one broad budget control rule. It does not verify the required corrective action: Review override transaction history and restrict over-budget permissions to the designated exception workflow.

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 override transaction history and restrict over-budget permissions to the designated exception workflow.

Budget funds availability can include pre-encumbrances, encumbrances and actuals according to setup. That explains a separate case: A purchase order fails budget checking because the commitment is counted against both its requisition and the finalized purchase order. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget control should be keyed to financial transaction properties, not free-form narrative text. That explains a separate case: A buyer can bypass a budget-check failure by changing the document description, though the account and amount remain over limit. 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.

Audit deliberate changes to budget account and dimension values during approval. That safeguard is aimed at a different risk: A buyer can bypass a budget-check failure by changing the document description, though the account and amount remain over limit. It does not most directly prevent recurrence of: Override permissions are an exception path that can still exhaust fiscal funds.

Test PO approval, receipt and invoice scenarios in budget control regression. That safeguard is aimed at a different risk: An AP invoice passes budget control at purchase-order approval but is blocked later due to document source scope mismatch. It does not most directly prevent recurrence of: Override permissions are an exception path that can still exhaust fiscal funds.

Include cross-program negative transactions in grant audit checks. That safeguard is aimed at a different risk: A government grant budget must be isolated from an operational budget, but both use one broad budget control rule. It does not most directly prevent recurrence of: Override permissions are an exception path that can still exhaust fiscal funds.