Exam Bundle

Require source invoice and reason codes on vendor credit notes. That safeguard is aimed at a different risk: A vendor credit memo is approved for a returned service charge, but the accountant enters it as an additional debit invoice. It does not most directly prevent recurrence of: Vendor master bank changes are high-risk payment data and distinct from invoice approval.

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: Vendor master bank changes are high-risk payment data and distinct from invoice approval.

Run a recurring invoice population reconciliation each month. That safeguard is aimed at a different risk: A regular vendor bills a fixed facilities fee monthly, but invoice staff enter it manually and miss a period. It does not most directly prevent recurrence of: Vendor master bank changes are high-risk payment data and distinct from invoice approval.

Configure derived fixed asset books or supported book mapping for the intended reporting relationships. This fits a DIFFERENT issue within Implement and manage fixed assets: 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 address the current problem, whose mechanism is: Accounting recognition and depreciation start are separate dates influenced by book settings.

Configure disposal transaction posting accounts for gain, loss, proceeds and asset balances. This fits a DIFFERENT issue within Implement and manage fixed assets: 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. It does not address the current problem, whose mechanism is: Accounting recognition and depreciation start are separate dates influenced by book settings.

Review legal-entity fixed asset number sequence setup and generate the intended unique IDs. This fits a DIFFERENT issue within Implement and manage fixed assets: A newly acquired production machine is assigned the wrong fixed asset number sequence and duplicates an existing identifier in a subsidiary. It does not address the current problem, whose mechanism is: Accounting recognition and depreciation start are separate dates influenced by book settings.

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: Set the correct service/depreciation commencement date on the applicable asset book.

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: Set the correct service/depreciation commencement date on the applicable asset book.

Asset ownership and balances appear in the proper legal entity after authorized transactions. That would verify a different case: An asset was created in the wrong legal entity and finance plans to fix the reporting by editing its name only. It does not verify the required corrective action: Set the correct service/depreciation commencement date on the applicable asset book.

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.

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

Run source-channel-specific capitalization test cases. That safeguard is aimed at a different risk: A company acquires assets using both projects and purchase orders, but some transactions post to unmatched asset groups because default asset fields are missing. It does not most directly prevent recurrence of: Accounting recognition and depreciation start are separate dates influenced by book settings.

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: Accounting recognition and depreciation start are separate dates influenced by book settings.

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: Accounting recognition and depreciation start are separate dates influenced by book settings.

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: Asset book history is an accounting subledger that should remain aligned with posted depreciation journals.

Review and configure the appropriate multi-company depreciation processing selection. This fits a DIFFERENT issue within Process fixed asset transactions: Monthly depreciation is run in batch for several companies, but one legal entity's book was omitted from the batch scope. It does not address the current problem, whose mechanism is: Asset book history is an accounting subledger that should remain aligned with posted depreciation journals.

Run depreciation with the correct book, asset status and processing date eligibility filters. This fits a DIFFERENT issue within Process fixed asset transactions: A fixed asset's monthly depreciation batch accidentally includes disposed assets. It does not address the current problem, whose mechanism is: Asset book history is an accounting subledger that should remain aligned with posted depreciation journals.

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: Use the supported depreciation adjustment/transaction workflow for the affected book rather than manual balance edits.

All eligible books across the intended entities are processed once with audit vouchers. That would verify a different case: Monthly depreciation is run in batch for several companies, but one legal entity's book was omitted from the batch scope. It does not verify the required corrective action: Use the supported depreciation adjustment/transaction workflow for the affected book rather than manual balance edits.

The asset book shows acquisition cost and the corresponding ledger voucher without duplicate capitalization. That would verify a different case: A new fixed asset purchased through a PO has been received, but no acquisition transaction exists in its book. It does not verify the required corrective action: Use the supported depreciation adjustment/transaction workflow for the affected book rather than manual balance edits.

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.

Gain or loss on disposal is the difference between proceeds and carrying amount. That explains a separate case: An asset is sold below net book value, yet the disposal entry credits a gain account. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Asset disposal/status and depreciation eligibility determine which assets are included in period processing. That explains a separate case: A fixed asset's monthly depreciation batch accidentally includes disposed assets. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile intercompany asset transfers before consolidation. That safeguard is aimed at a different risk: An asset is transferred between two companies, but one company posts the disposal while the other fails to recognize the corresponding acquisition. It does not most directly prevent recurrence of: Asset book history is an accounting subledger that should remain aligned with posted depreciation journals.

Document rationale and reconcile reclassification postings. That safeguard is aimed at a different risk: A subsidiary decides an asset was misclassified from furniture to IT equipment but attempts to fix this by deleting historical depreciation vouchers. It does not most directly prevent recurrence of: Asset book history is an accounting subledger that should remain aligned with posted depreciation journals.

Review company list and book filters before batch approval. That safeguard is aimed at a different risk: Monthly depreciation is run in batch for several companies, but one legal entity's book was omitted from the batch scope. It does not most directly prevent recurrence of: Asset book history is an accounting subledger that should remain aligned with posted depreciation journals.

Run the approved vendor foreign currency revaluation for eligible open vendor balances. This fits a DIFFERENT issue within Implement and manage accounts payable: A month-end AP foreign-currency revaluation is skipped and open vendor liabilities are understated. It does not address the current problem, whose mechanism is: Price tolerance comparisons should be rule-based, not manually overridden without review.

Use the authorized vendor prepayment process with correct liability/asset treatment and subsequent settlement. This fits a DIFFERENT issue within Implement and manage accounts payable: A vendor prepayment is required before delivery, but finance pays the invoice's full final balance without recording the advance. It does not address the current problem, whose mechanism is: Price tolerance comparisons should be rule-based, not manually overridden without review.

Review payment journal and file generation state, repair the failing format issue and reprocess only as permitted. This fits a DIFFERENT issue within Implement and manage accounts payable: 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 address the current problem, whose mechanism is: Price tolerance comparisons should be rule-based, not manually overridden without review.

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.