Exam Bundle

Require documented netting scope and unresolved-dispute approval. That safeguard is aimed at a different risk: A high-value customer and vendor netting proposal includes a disputed invoice that should remain open. It does not most directly prevent recurrence of: Cash flow forecasting requires configured source transactions and forecast automation rules.

Test intercompany accounting generated by centralized payment processing. That safeguard is aimed at a different risk: A group company pays vendor invoices from a central payment account, but shared payment setup is not configured for the involved entities. It does not most directly prevent recurrence of: Cash flow forecasting requires configured source transactions and forecast automation rules.

Reconcile entity coverage and schedule parameters in forecast operations. That safeguard is aimed at a different risk: Treasury expects an automated cash forecast for each legal entity but the forecast job only runs in the holding company. It does not most directly prevent recurrence of: Cash flow forecasting requires configured source transactions and forecast automation rules.

Configure financial period closing templates, task owners and schedules for the target legal entities. This fits a DIFFERENT issue within Perform periodic processes: A financial close team cannot determine which month-end tasks remain for each subsidiary because spreadsheets are circulated separately. It does not address the current problem, whose mechanism is: A template does not automatically supply every company-specific close participant or deadline.

Complete and validate source-company period-end revaluations before rerunning the approved consolidation. This fits a DIFFERENT issue within Perform periodic processes: Group consolidation is run before a subsidiary posts its final bank revaluation and the consolidated cash figure is stale. It does not address the current problem, whose mechanism is: A template does not automatically supply every company-specific close participant or deadline.

Inspect the appropriate ledger settlement account and eligible transaction criteria, then settle true offsetting entries. This fits a DIFFERENT issue within Perform periodic processes: Ledger settlement cannot find offsetting debit and credit transactions because the settlement criteria use a mismatched main account. It does not address the current problem, whose mechanism is: A template does not automatically supply every company-specific close participant or deadline.

The consolidated trial balance includes each approved company exactly once. That would verify a different case: A subsidiary is included in consolidation twice because its source legal entity mapping is duplicated. It does not verify the required corrective action: Apply an appropriate company-specific closing schedule and task ownership mapping.

The consolidation shows translated amounts with reconciling translation adjustments. That would verify a different case: A consolidated balance sheet includes a company in a different reporting currency but exchange-rate configuration is missing. It does not verify the required corrective action: Apply an appropriate company-specific closing schedule and task ownership mapping.

Settlement reports show only legitimately matched entries and the remaining balance is visible for action. That would verify a different case: An operating account balance remains unreconciled because an unmatched ledger settlement was forced to close the period. It does not verify the required corrective action: Apply an appropriate company-specific closing schedule and task ownership mapping.

Consolidation results are snapshots of source ledger balances when processed, not automatic live totals. That explains a separate case: Group consolidation is run before a subsidiary posts its final bank revaluation and the consolidated cash figure is stale. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Ledger settlement links eligible ledger entries; it does not invent adjusting vouchers to make totals zero. That explains a separate case: Ledger settlement cannot find offsetting debit and credit transactions because the settlement criteria use a mismatched main account. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

A financial close workspace coordinates period close tasks independently of posting the underlying ledger entries. That explains a separate case: A financial close team cannot determine which month-end tasks remain for each subsidiary because spreadsheets are circulated separately. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile source-to-consolidated trial balances by legal entity. That safeguard is aimed at a different risk: A subsidiary is included in consolidation twice because its source legal entity mapping is duplicated. It does not most directly prevent recurrence of: A template does not automatically supply every company-specific close participant or deadline.

Test symmetric intercompany entries and unmatched exceptions before consolidation. That safeguard is aimed at a different risk: Intercompany sales and purchases inflate group revenue and costs in consolidated statements. It does not most directly prevent recurrence of: A template does not automatically supply every company-specific close participant or deadline.

Add voucher/batch proof as an attachment requirement for high-risk close tasks. That safeguard is aimed at a different risk: Financial close tasks are marked Complete even though the underlying journal batches have failures. It does not most directly prevent recurrence of: A template does not automatically supply every company-specific close participant or deadline.

Use an approved tax adjustment and reversal process with proper accounting evidence rather than mutating posted settlement history. This fits a DIFFERENT issue within Configure, collect, and report taxes: A tax adjustment needs to correct a miscalculated invoice, but a user proposes editing a tax authority settlement already posted. It does not address the current problem, whose mechanism is: Item tax groups categorize product tax treatment separately from customer/vendor tax groups.

Correct the tax ledger posting group account mappings for the affected tax codes. This fits a DIFFERENT issue within Configure, collect, and report taxes: Tax amounts are correct but post to an incorrect general ledger account because a tax ledger posting group mapping is stale. It does not address the current problem, whose mechanism is: Item tax groups categorize product tax treatment separately from customer/vendor tax groups.

Scope sales tax settlement and reporting to each appropriate legal entity and tax authority. This fits a DIFFERENT issue within Configure, collect, and report taxes: A multi-entity tax report mixes domestic and overseas tax obligations because legal entity filters are omitted. It does not address the current problem, whose mechanism is: Item tax groups categorize product tax treatment separately from customer/vendor tax groups.

A controlled invoice calculates and posts withholding under the intended tax liability account. That would verify a different case: A vendor invoice should withhold a statutory portion, but its withholding tax group is absent. It does not verify the required corrective action: Create or assign the appropriate item sales tax group to the special-rate products.

A before-effective-date invoice calculates 8% and an after-effective-date invoice calculates 9%. That would verify a different case: A jurisdiction increases tax from 8% to 9% midyear, but prior invoices must remain at historical rates. It does not verify the required corrective action: Create or assign the appropriate item sales tax group to the special-rate products.

The tax liability account and payment records reconcile to the filed period amount. That would verify a different case: A sales tax authority remittance has been recorded but the sales tax liability balance is not cleared against its settlement. It does not verify the required corrective action: Create or assign the appropriate item sales tax group to the special-rate products.

Time-valid tax rates determine transaction treatment by effective date. That explains a separate case: A jurisdiction increases tax from 8% to 9% midyear, but prior invoices must remain at historical rates. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

A tax exemption changes eligibility for specified tax treatment, not the global tax rate for all customers. That explains a separate case: A tax-exempt customer is charged standard tax because the exemption status was never assigned. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Withholding tax is driven by withholding group and code configuration, distinct from ordinary sales tax. That explains a separate case: A vendor invoice should withhold a statutory portion, but its withholding tax group is absent. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Require supporting exemption documentation before modifying customer tax setup. That safeguard is aimed at a different risk: A tax-exempt customer is charged standard tax because the exemption status was never assigned. It does not most directly prevent recurrence of: Item tax groups categorize product tax treatment separately from customer/vendor tax groups.

Document the original tax calculation and reason for every manual adjustment. That safeguard is aimed at a different risk: A tax adjustment needs to correct a miscalculated invoice, but a user proposes editing a tax authority settlement already posted. It does not most directly prevent recurrence of: Item tax groups categorize product tax treatment separately from customer/vendor tax groups.

Validate tax group inheritance on each invoice source type. That safeguard is aimed at a different risk: A tax code applies to a customer but a free-text invoice does not inherit the expected item tax group. It does not most directly prevent recurrence of: Item tax groups categorize product tax treatment separately from customer/vendor tax groups.

Assign the intended customer group and associated customer posting profile for the legal entity. This fits a DIFFERENT issue within Implement and manage accounts receivable: A newly onboarded customer is invoiced under the wrong receivables control account because its customer group default was copied from a different business line. It does not address the current problem, whose mechanism is: Customer payment methods and bank settings influence how receivables are collected.

Issue an approved free text invoice with appropriate revenue, tax and customer defaults. This fits a DIFFERENT issue within Implement and manage accounts receivable: Finance needs a consulting invoice without a sales order, but the team creates a fake inventory order to generate billing. It does not address the current problem, whose mechanism is: Customer payment methods and bank settings influence how receivables are collected.

Match the receipt by verified customer, currency and eligible open transaction rather than reference alone. This fits a DIFFERENT issue within Implement and manage accounts receivable: A customer payment import finds an existing invoice with the same external reference but wrong currency. It does not address the current problem, whose mechanism is: Customer payment methods and bank settings influence how receivables are collected.

A test posted invoice debits the correct receivables main account and retains the right customer balance. That would verify a different case: A newly onboarded customer is invoiced under the wrong receivables control account because its customer group default was copied from a different business line. It does not verify the required corrective action: Correct the customer's authorized payment method and associated company bank account setup.

The revaluation voucher posts unrealized exchange differences and AR valuation reconciles to ledger. That would verify a different case: Month-end AR aging in foreign currency disagrees with the general ledger because customer revaluation was not performed. It does not verify the required corrective action: Correct the customer's authorized payment method and associated company bank account setup.

The posted invoice and tax calculation contain the correctly categorized charge amount. That would verify a different case: An invoice includes a contractual handling charge, but the charge is missing from the posted customer transaction. It does not verify the required corrective action: Correct the customer's authorized payment method and associated company bank account setup.