Exam Bundle

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.

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.

Global party identity and company-scoped vendor financial setup must not be conflated. That explains a separate case: A vendor is shared as a party across several entities, but one subsidiary's payment terms are accidentally overwritten globally. 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 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: Payment journal posting and bank file generation may have separate failure/retry states.

Track prepayment approvals and outstanding unallocated advances. That safeguard is aimed at a different risk: A vendor prepayment is required before delivery, but finance pays the invoice's full final balance without recording the advance. It does not most directly prevent recurrence of: Payment journal posting and bank file generation may have separate failure/retry states.

Reconcile intercompany document counts and amounts by period. That safeguard is aimed at a different risk: Intercompany vendor invoices are imported without matching seller-company sales invoice references, causing periodic reconciliation differences. It does not most directly prevent recurrence of: Payment journal posting and bank file generation may have separate failure/retry states.

Configure invoice validation policy applicability to distinguish allowed non-PO processing from PO matching requirements. This fits a DIFFERENT issue within Implement and manage accounts payable: An invoice arrives without a purchase order, but a matching-required policy is incorrectly applied to its permitted non-PO category. It does not address the current problem, whose mechanism is: Paired intercompany AR and AP documents need source references and company-specific posting accuracy.

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: Paired intercompany AR and AP documents need source references and company-specific posting accuracy.

Set appropriate payment proposal due-date criteria and review selected vendors and invoices before generation. This fits a DIFFERENT issue within Implement and manage accounts payable: A vendor payment proposal includes invoices due next quarter because payment selection ignores the due date. It does not address the current problem, whose mechanism is: Paired intercompany AR and AP documents need source references and company-specific posting accuracy.

The mismatched invoice is held or flagged, while a valid quantity/price invoice passes. That would verify a different 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. It does not verify the required corrective action: Use the supported intercompany invoice linkage and verify legal-entity transaction references.

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: Use the supported intercompany invoice linkage and verify legal-entity transaction references.

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: Use the supported intercompany invoice linkage and verify legal-entity transaction references.

Centralized payments cross legal-entity boundaries and need explicit intercompany accounting. That explains a separate case: Central finance pays invoices for subsidiary companies, but the central payment journal does not create intercompany due-to/due-from balances. 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.

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.

Reconcile bank currency and payment method before automated disbursements. That safeguard is aimed at a different risk: A batch vendor payment run selects a bank account not authorized for that currency. It does not most directly prevent recurrence of: Paired intercompany AR and AP documents need source references and company-specific posting accuracy.

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: Paired intercompany AR and AP documents need source references and company-specific posting accuracy.

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: Paired intercompany AR and AP documents need source references and company-specific posting accuracy.

Configure invoice validation policy applicability to distinguish allowed non-PO processing from PO matching requirements. This fits a DIFFERENT issue within Implement and manage accounts payable: An invoice arrives without a purchase order, but a matching-required policy is incorrectly applied to its permitted non-PO category. It does not address the current problem, whose mechanism is: Cash discounts are determined by configured terms and actual settlement timing.

Configure a recurring vendor invoice template with controlled dates and amount. This fits a DIFFERENT issue within Implement and manage accounts payable: A regular vendor bills a fixed facilities fee monthly, but invoice staff enter it manually and miss a period. It does not address the current problem, whose mechanism is: Cash discounts are determined by configured terms and actual settlement timing.

Configure the correct vendor payment method and company bank account currency/payment settings. This fits a DIFFERENT issue within Implement and manage accounts payable: A batch vendor payment run selects a bank account not authorized for that currency. It does not address the current problem, whose mechanism is: Cash discounts are determined by configured terms and actual settlement timing.

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: Review vendor cash discount terms and the eligible settlement/payment date when generating the payment proposal.

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: Review vendor cash discount terms and the eligible settlement/payment date when generating the payment proposal.

A valid non-PO expense invoice is processed with the correct controls while PO invoices retain matching. That would verify a different case: An invoice arrives without a purchase order, but a matching-required policy is incorrectly applied to its permitted non-PO category. It does not verify the required corrective action: Review vendor cash discount terms and the eligible settlement/payment date when generating the payment proposal.

Payment journal posting and bank file generation may have separate failure/retry states. That explains a separate case: A vendor payment batch is approved, but the payment file generation fails and the team plans to resubmit the journal without inspecting status. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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.

Global party identity and company-scoped vendor financial setup must not be conflated. That explains a separate case: A vendor is shared as a party across several entities, but one subsidiary's payment terms are accidentally overwritten globally. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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: Cash discounts are determined by configured terms and actual settlement timing.

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: Cash discounts are determined by configured terms and actual settlement timing.

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: Cash discounts are determined by configured terms and actual settlement timing.