Exam Bundle

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.

Configure valid salvage/residual value and depreciation basis according to approved asset policy. This fits a DIFFERENT issue within Implement and manage fixed assets: The financial accounting team sets a negative residual value in the asset book without policy support, inflating planned depreciation. It does not address the current problem, whose mechanism is: Fixed asset disposal accounting has specialized transaction types separate from ordinary product revenue.

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: Fixed asset disposal accounting has specialized transaction types separate from ordinary product revenue.

Create or correct an appropriate fixed asset group and its required default properties. This fits a DIFFERENT issue within Implement and manage fixed assets: A company capitalizes laptops as machinery because the laptop asset group was copied from an industrial equipment template. It does not address the current problem, whose mechanism is: Fixed asset disposal accounting has specialized transaction types separate from ordinary product revenue.

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: Configure disposal transaction posting accounts for gain, loss, proceeds and asset balances.

New vehicles use an eight-year life while existing asset accounting is assessed separately. That would verify a different case: 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 verify the required corrective action: Configure disposal transaction posting accounts for gain, loss, proceeds and asset balances.

The first depreciation period aligns with the approved in-service date. That would verify a different case: 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 verify the required corrective action: Configure disposal transaction posting accounts for gain, loss, proceeds and asset balances.

Fixed asset identifiers require governed number sequences across the relevant legal entity scope. That explains a separate case: A newly acquired production machine is assigned the wrong fixed asset number sequence and duplicates an existing identifier in a subsidiary. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Accounting recognition and depreciation start are separate dates influenced by book settings. That explains a separate case: An asset is acquired but depreciation is scheduled from the purchase order date instead of the date it became available for use. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Fixed asset books represent alternative valuation/depreciation bases for one asset. That explains a separate case: Tax authorities require a separate accelerated depreciation calculation from financial reporting. 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 disposal accounting has specialized transaction types separate from ordinary product revenue.

Review number sequence configuration during subsidiary onboarding. That safeguard is aimed at a different risk: A newly acquired production machine is assigned the wrong fixed asset number sequence and duplicates an existing identifier in a subsidiary. It does not most directly prevent recurrence of: Fixed asset disposal accounting has specialized transaction types separate from ordinary product revenue.

Compare planned depreciation under each book to approved accounting policy. That safeguard is aimed at a different risk: Financial statements require straight-line depreciation but a fixed asset book uses reducing-balance method. It does not most directly prevent recurrence of: Fixed asset disposal accounting has specialized transaction types separate from ordinary product revenue.

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: Global party identity and company-scoped vendor financial setup must not be conflated.

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: Global party identity and company-scoped vendor financial setup must not be conflated.

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: Global party identity and company-scoped vendor financial setup must not be conflated.

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: Apply shared vendor party management while retaining the intended company-specific payment defaults.

An approved early payment realizes the correct contractual cash discount and records its accounting entries. That would verify a different 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. It does not verify the required corrective action: Apply shared vendor party management while retaining the intended company-specific payment defaults.

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: Apply shared vendor party management while retaining the intended company-specific payment defaults.

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.

Three-way matching compares invoice details to the purchase order and product receipt within allowed tolerances. That explains a separate case: A purchased item invoice is received for 130 units while the purchase order receipt shows only 100, but the invoice posts without a warning. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Invoice charges add line/header costs outside the base purchase price and need explicit mapping. That explains a separate case: A vendor charges an agreed freight fee, but the AP invoice amount differs from the purchase order because the charge code is missing. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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: Global party identity and company-scoped vendor financial setup must not be conflated.

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: Global party identity and company-scoped vendor financial setup must not be conflated.

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: Global party identity and company-scoped vendor financial setup must not be conflated.

Validate the AP transaction currency, exchange-rate type and effective rate before posting. This fits a DIFFERENT issue within Implement and manage accounts payable: A vendor invoice is received in EUR but its liability is initially valued in USD at the wrong exchange rate. It does not address the current problem, whose mechanism is: Payment journal posting and bank file generation may have separate failure/retry states.

Post the vendor credit memo through the supported vendor transaction workflow and settle with the original open invoice. This fits a DIFFERENT issue within Implement and manage accounts payable: A vendor credit memo is approved for a returned service charge, but the accountant enters it as an additional debit invoice. It does not address the current problem, whose mechanism is: Payment journal posting and bank file generation may have separate failure/retry states.

Review invoice matching price tolerance setup and the purchase order/vendor invoice price details. This fits a DIFFERENT issue within Implement and manage accounts payable: 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 address the current problem, whose mechanism is: Payment journal posting and bank file generation may have separate failure/retry states.

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: Review payment journal and file generation state, repair the failing format issue and reprocess only as permitted.

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: Review payment journal and file generation state, repair the failing format issue and reprocess only as permitted.

AP and AR documents match across entities and elimination reconciliation balances. That would verify a different case: Intercompany vendor invoices are imported without matching seller-company sales invoice references, causing periodic reconciliation differences. It does not verify the required corrective action: Review payment journal and file generation state, repair the failing format issue and reprocess only as permitted.