Exam Bundle

Unapproved bank details cannot generate a payment file until validated. That would verify a different case: A new vendor bank account is accepted from an unverified email and inserted directly into the next payment run. It does not verify the required corrective action: Configure supported centralized vendor payment and intercompany posting relationships among the companies.

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 supported centralized vendor payment and intercompany posting relationships among the companies.

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 supported centralized vendor payment and intercompany posting relationships among the companies.

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.

Invoice validation policies may vary by document and procurement scenario. That explains a separate case: An invoice arrives without a purchase order, but a matching-required policy is incorrectly applied to its permitted non-PO category. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Vendor posting profiles map operational vendor liabilities to general ledger accounts. That explains a separate case: A new vendor invoice is booked to the wrong accounts payable control account because the vendor group has an incorrect posting profile. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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: Centralized payments cross legal-entity boundaries and need explicit intercompany accounting.

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: Centralized payments cross legal-entity boundaries and need explicit intercompany accounting.

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: Centralized payments cross legal-entity boundaries and need explicit intercompany accounting.

Configure fixed asset posting profiles for acquisition and relevant asset group/book transactions. This fits a DIFFERENT issue within Implement and manage fixed assets: A newly acquired vehicle posts acquisition cost to an expense account instead of fixed asset cost because posting profiles are incomplete. It does not address the current problem, whose mechanism is: Fixed asset identifiers require governed number sequences across the relevant legal entity scope.

Update the appropriate asset group/book defaults for future assets under an approved effective date. This fits a DIFFERENT issue within Implement and manage fixed assets: 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 address the current problem, whose mechanism is: Fixed asset identifiers require governed number sequences across the relevant legal entity scope.

Set the correct service/depreciation commencement date on the applicable asset book. This fits a DIFFERENT issue within Implement and manage fixed assets: An asset is acquired but depreciation is scheduled from the purchase order date instead of the date it became available for use. It does not address the current problem, whose mechanism is: Fixed asset identifiers require governed number sequences across the relevant legal entity scope.

Test depreciation shows the intended straight-line expense pattern over useful life. That would verify a different case: Financial statements require straight-line depreciation but a fixed asset book uses reducing-balance method. It does not verify the required corrective action: Review legal-entity fixed asset number sequence setup and generate the intended unique IDs.

Both approved book records exist with distinct valuation and depreciation rules. That would verify a different case: A fixed asset depreciates under one book but not under a required second book because the second book is not associated with the asset. It does not verify the required corrective action: Review legal-entity fixed asset number sequence setup and generate the intended unique IDs.

The same asset produces separate book-specific depreciation schedules without mixing ledger layers. That would verify a different case: Tax authorities require a separate accelerated depreciation calculation from financial reporting. It does not verify the required corrective action: Review legal-entity fixed asset number sequence setup and generate the intended unique IDs.

Fixed asset posting profiles determine the ledger accounts used by asset transaction types. That explains a separate case: A newly acquired vehicle posts acquisition cost to an expense account instead of fixed asset cost because posting profiles are incomplete. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Depreciation start conventions determine which portion of an accounting period qualifies for expense. That explains a separate case: Fixed asset books have the correct depreciation method but no depreciation start convention, producing inconsistent first-month charges. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Asset creation and book association are separate operations and missing books do not self-populate. That explains a separate case: A fixed asset depreciates under one book but not under a required second book because the second book is not associated with the asset. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile intercompany asset transfers and ownership evidence. That safeguard is aimed at a different risk: An asset was created in the wrong legal entity and finance plans to fix the reporting by editing its name only. It does not most directly prevent recurrence of: Fixed asset identifiers require governed number sequences across the relevant legal entity scope.

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 identifiers require governed number sequences across the relevant legal entity scope.

Require in-service evidence before enabling depreciation. That safeguard is aimed at a different risk: An asset is acquired but depreciation is scheduled from the purchase order date instead of the date it became available for use. It does not most directly prevent recurrence of: Fixed asset identifiers require governed number sequences across the relevant legal entity scope.

Use the supported fixed asset disposal sale process linked to the appropriate free text invoice. This fits a DIFFERENT issue within Process fixed asset transactions: A company disposes of an old computer for cash, but books the sale through a free text invoice without closing its net book value. It does not address the current problem, whose mechanism is: Fixed asset budgets and operational budget registers are separate sources until transferred.

Use an approved fixed asset acquisition adjustment/additional acquisition transaction to capitalize the eligible improvement. This fits a DIFFERENT issue within Process fixed asset transactions: An asset was initially capitalized at $8,000 but a later capital improvement of $1,200 is booked as routine maintenance expense contrary to policy. It does not address the current problem, whose mechanism is: Fixed asset budgets and operational budget registers are separate sources until transferred.

Confirm the approved retirement/disposal effective date and correct processing eligibility for that asset book. This fits a DIFFERENT issue within Process fixed asset transactions: A fixed asset group includes a machine that was retired, but the depreciation run generates a charge in a period after retirement. It does not address the current problem, whose mechanism is: Fixed asset budgets and operational budget registers are separate sources until transferred.

One legitimate acquisition cost remains in the asset book and general ledger. That would verify a different case: A finance clerk manually records an asset acquisition and a later PO invoice posts the same cost again. It does not verify the required corrective action: Run the supported fixed asset budget transfer process into the designated budgeting model/register.

Net book value, sale proceeds and disposal loss reconcile under the approved posting profile. That would verify a different case: An asset is sold below net book value, yet the disposal entry credits a gain account. It does not verify the required corrective action: Run the supported fixed asset budget transfer process into the designated budgeting model/register.

Only active eligible assets receive depreciation and disposed assets remain closed. That would verify a different case: A fixed asset's monthly depreciation batch accidentally includes disposed assets. It does not verify the required corrective action: Run the supported fixed asset budget transfer process into the designated budgeting model/register.

An asset sale must derecognize the asset carrying amount in addition to recording customer proceeds. That explains a separate case: A company disposes of an old computer for cash, but books the sale through a free text invoice without closing its net book value. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Physical asset location and legal/financial asset ownership are distinct properties. That explains a separate case: A finance team changes an asset's location from one site to another and expects the general ledger to transfer its book value automatically. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Retirement timing determines when depreciation and book transactions cease. That explains a separate case: A fixed asset group includes a machine that was retired, but the depreciation run generates a charge in a period after retirement. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile disposal invoice with asset book disposal postings. That safeguard is aimed at a different risk: A company disposes of an old computer for cash, but books the sale through a free text invoice without closing its net book value. It does not most directly prevent recurrence of: Fixed asset budgets and operational budget registers are separate sources until transferred.

Reconcile fixed asset subledger balances to the general ledger after adjustments. That safeguard is aimed at a different risk: An asset has a depreciation adjustment after an approved useful-life change, but finance manually edits accumulated depreciation account balances. It does not most directly prevent recurrence of: Fixed asset budgets and operational budget registers are separate sources until transferred.

Require asset custodian and accounting signoff for intersite transfers. That safeguard is aimed at a different risk: A finance team changes an asset's location from one site to another and expects the general ledger to transfer its book value automatically. It does not most directly prevent recurrence of: Fixed asset budgets and operational budget registers are separate sources until transferred.