Exam Bundle

The generated payment file uses the approved bank and currency while the other bank remains excluded. That would verify a different case: A batch vendor payment run selects a bank account not authorized for that currency. It does not verify the required corrective action: Review invoice matching price tolerance setup and the purchase order/vendor invoice price details.

The second invoice is flagged and does not create another payable. That would verify a different case: The same vendor invoice arrives twice with different PDF filenames but the same vendor invoice number. It does not verify the required corrective action: Review invoice matching price tolerance setup and the purchase order/vendor invoice price details.

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: Review invoice matching price tolerance setup and the purchase order/vendor invoice price details.

A vendor credit memo reduces accounts payable; it is not another ordinary liability invoice. That explains a separate case: A vendor credit memo is approved for a returned service charge, but the accountant enters it as an additional debit invoice. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Recurring vendor invoices reduce manual duplication but require timing and active contract review. That explains a separate case: A regular vendor bills a fixed facilities fee monthly, but invoice staff enter it manually and miss a period. 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.

Test over-receipt and over-price invoice cases before enabling automated posting. That safeguard is aimed at a different risk: A purchased item invoice is received for 130 units while the purchase order receipt shows only 100, but the invoice posts without a warning. It does not most directly prevent recurrence of: Price tolerance comparisons should be rule-based, not manually overridden without 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: Price tolerance comparisons should be rule-based, not manually overridden without review.

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: Price tolerance comparisons should be rule-based, not manually overridden without review.

Configure separate financial and tax fixed asset books with approved depreciation profiles. This fits a DIFFERENT issue within Implement and manage fixed assets: Tax authorities require a separate accelerated depreciation calculation from financial reporting. It does not address the current problem, whose mechanism is: Fixed asset setup must map each acquisition source to the intended asset classification and books.

Assign the correct depreciation profile and calculation basis to the appropriate fixed asset book. This fits a DIFFERENT issue within Implement and manage fixed assets: Financial statements require straight-line depreciation but a fixed asset book uses reducing-balance method. It does not address the current problem, whose mechanism is: Fixed asset setup must map each acquisition source to the intended asset classification and books.

Configure the supported depreciation convention and service/start dates per financial policy. This fits a DIFFERENT issue within Implement and manage fixed assets: Fixed asset books have the correct depreciation method but no depreciation start convention, producing inconsistent first-month charges. It does not address the current problem, whose mechanism is: Fixed asset setup must map each acquisition source to the intended asset classification and books.

A new asset has the expected book records and depreciation profile automatically populated. That would verify a different case: A fixed asset group has no book mapping, so acquisitions create assets with missing depreciation settings. It does not verify the required corrective action: Configure fixed asset defaults and source transaction mappings for each approved acquisition path.

The small tool follows expense policy while machinery capitalizes through the intended posting profile. That would verify a different case: An asset group contains both small expensed tools and capital machinery, but the company wants capitalization limits by class. It does not verify the required corrective action: Configure fixed asset defaults and source transaction mappings for each approved acquisition path.

The depreciation forecast stops at the intended residual threshold. That would verify a different case: The financial accounting team sets a negative residual value in the asset book without policy support, inflating planned depreciation. It does not verify the required corrective action: Configure fixed asset defaults and source transaction mappings for each approved acquisition path.

Fixed asset disposal accounting has specialized transaction types separate from ordinary product revenue. That explains a separate case: An asset disposal gain is posted to the general sales revenue account instead of gain on disposal because its posting profile lacks the transaction mapping. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Book mapping connects asset classification to the intended accounting and depreciation books. That explains a separate case: A fixed asset group has no book mapping, so acquisitions create assets with missing depreciation settings. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Fixed asset group defaults can supply book values at asset creation without automatically rewriting all historical assets. That explains a separate case: A capitalized service vehicle has a ten-year useful life on one book but the policy changed to eight for new acquisitions. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Review derived-book mappings during capital policy maintenance. That safeguard is aimed at a different risk: An asset must track local and group reporting books, but users create two unrelated asset IDs and the underlying acquisition is duplicated. It does not most directly prevent recurrence of: Fixed asset setup must map each acquisition source to the intended asset classification and books.

Control retrospective versus prospective depreciation changes explicitly. That safeguard is aimed at a different risk: A capitalized service vehicle has a ten-year useful life on one book but the policy changed to eight for new acquisitions. It does not most directly prevent recurrence of: Fixed asset setup must map each acquisition source to the intended asset classification and books.

Use a new-asset creation test after changing book mapping. That safeguard is aimed at a different risk: A fixed asset group has no book mapping, so acquisitions create assets with missing depreciation settings. It does not most directly prevent recurrence of: Fixed asset setup must map each acquisition source to the intended asset classification and books.

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: Invoice validation policies may vary by document and procurement scenario.

Configure supported centralized vendor payment and intercompany posting relationships among the companies. This fits a DIFFERENT issue within Implement and manage accounts payable: Central finance pays invoices for subsidiary companies, but the central payment journal does not create intercompany due-to/due-from balances. It does not address the current problem, whose mechanism is: Invoice validation policies may vary by document and procurement scenario.

Configure three-way matching and relevant invoice matching tolerances for the purchase order category. This fits a DIFFERENT issue within Implement and manage accounts payable: A purchased item invoice is received for 130 units while the purchase order receipt shows only 100, but the invoice posts without a warning. It does not address the current problem, whose mechanism is: Invoice validation policies may vary by document and procurement scenario.

Revaluation vouchers update unrealized gain/loss while original invoice settlement records remain. That would verify a different case: A month-end AP foreign-currency revaluation is skipped and open vendor liabilities are understated. It does not verify the required corrective action: Configure invoice validation policy applicability to distinguish allowed non-PO processing from PO matching requirements.

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 invoice validation policy applicability to distinguish allowed non-PO processing from PO matching requirements.

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 invoice validation policy applicability to distinguish allowed non-PO processing from PO matching requirements.

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.

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.

AP foreign currency revaluation treats open obligations differently from original invoice booking. That explains a separate case: A month-end AP foreign-currency revaluation is skipped and open vendor liabilities are understated. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile due-to and due-from accounts after centralized payment batches. That safeguard is aimed at a different risk: Central finance pays invoices for subsidiary companies, but the central payment journal does not create intercompany due-to/due-from balances. It does not most directly prevent recurrence of: Invoice validation policies may vary by document and procurement scenario.

Require review of invoice count and dates prior to releasing payments. That safeguard is aimed at a different risk: A vendor payment proposal includes invoices due next quarter because payment selection ignores the due date. It does not most directly prevent recurrence of: Invoice validation policies may vary by document and procurement scenario.

Include discount opportunities and liquidity constraints in payment-run review. That safeguard is aimed at a different risk: 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. It does not most directly prevent recurrence of: Invoice validation policies may vary by document and procurement scenario.