Exam Bundle

Track close exceptions and restore normal period permissions promptly. That safeguard is aimed at a different risk: A close checklist requires revenue reclassification after period lock, but the posting period is closed to the assigned journal user. It does not most directly prevent recurrence of: Consolidation results are snapshots of source ledger balances when processed, not automatic live totals.

Review aged unresolved ledger items separately from settlement completion rates. That safeguard is aimed at a different risk: An operating account balance remains unreconciled because an unmatched ledger settlement was forced to close the period. It does not most directly prevent recurrence of: Consolidation results are snapshots of source ledger balances when processed, not automatic live totals.

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: Consolidation results are snapshots of source ledger balances when processed, not automatic live totals.

Assign the appropriate vendor withholding tax group and valid code/authority setup. This fits a DIFFERENT issue within Configure, collect, and report taxes: A vendor invoice should withhold a statutory portion, but its withholding tax group is absent. It does not address the current problem, whose mechanism is: Tax legal entity and authority boundaries must be respected even with shared tax codes.

Change the authorized settlement period schedule to reflect the reporting authority's current monthly requirements. This fits a DIFFERENT issue within Configure, collect, and report taxes: A company reports sales tax monthly while its configured settlement period closes quarterly. It does not address the current problem, whose mechanism is: Tax legal entity and authority boundaries must be respected even with shared tax codes.

Configure the correct settlement period and tax authority associations for the applicable tax codes. This fits a DIFFERENT issue within Configure, collect, and report taxes: Sales tax settlement reports omit one country's transactions because its settlement period is mapped to the wrong authority. It does not address the current problem, whose mechanism is: Tax legal entity and authority boundaries must be respected even with shared tax codes.

A settlement run groups the intended tax transactions under the right authority and period. That would verify a different case: Sales tax settlement reports omit one country's transactions because its settlement period is mapped to the wrong authority. It does not verify the required corrective action: Scope sales tax settlement and reporting to each appropriate legal entity and tax authority.

The targeted items calculate the special code while ordinary inventory retains the default rate. That would verify a different case: A merchant uses a special tax rate for a particular item category, but all product tax items share the general tax group. It does not verify the required corrective action: Scope sales tax settlement and reporting to each appropriate legal entity and tax authority.

A taxable transaction posts liabilities or recoverables to the approved ledger accounts. That would verify a different case: Tax amounts are correct but post to an incorrect general ledger account because a tax ledger posting group mapping is stale. It does not verify the required corrective action: Scope sales tax settlement and reporting to each appropriate legal entity and tax authority.

Tax rate calculation and tax ledger posting accounts are separate configuration concerns. That explains a separate case: Tax amounts are correct but post to an incorrect general ledger account because a tax ledger posting group mapping is stale. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Free-text invoices may need explicit tax group context because no stocked item drives the line. That explains a separate case: A tax code applies to a customer but a free-text invoice does not inherit the expected item tax group. 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.

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: Tax legal entity and authority boundaries must be respected even with shared tax codes.

Compare settlement period cutoffs with regulatory filing calendars. That safeguard is aimed at a different risk: A company reports sales tax monthly while its configured settlement period closes quarterly. It does not most directly prevent recurrence of: Tax legal entity and authority boundaries must be respected even with shared tax codes.

Reconcile tax code posting accounts with the chart of accounts after tax setup changes. That safeguard is aimed at a different risk: Tax amounts are correct but post to an incorrect general ledger account because a tax ledger posting group mapping is stale. It does not most directly prevent recurrence of: Tax legal entity and authority boundaries must be respected even with shared tax codes.

Record the overpayment as a customer credit or unapplied payment and follow the authorized refund or settlement process. This fits a DIFFERENT issue within Implement and manage accounts receivable: Cash was received against a settled customer invoice, creating a residual overpayment that finance tries to hide as a forced invoice credit. It does not address the current problem, whose mechanism is: External invoice references are not globally unique account and currency identifiers.

Configure the required billing classification and apply it to the proper customer/document transactions. This fits a DIFFERENT issue within Implement and manage accounts receivable: A product invoice should use special billing classification, but the customer's default classification is absent. It does not address the current problem, whose mechanism is: External invoice references are not globally unique account and currency identifiers.

Configure a recurring free text invoice template and schedule with proper customer and date scope. This fits a DIFFERENT issue within Implement and manage accounts receivable: A monthly management fee is billed manually each month, and staff accidentally bill one client twice. It does not address the current problem, whose mechanism is: External invoice references are not globally unique account and currency identifiers.

Customer balance clearly shows the excess payment without modifying the already-settled original invoice. That would verify a different case: Cash was received against a settled customer invoice, creating a residual overpayment that finance tries to hide as a forced invoice credit. It does not verify the required corrective action: Match the receipt by verified customer, currency and eligible open transaction rather than reference alone.

The customer's receivable is reduced and the original sale is traceable from the credit. That would verify a different case: Sales returns require a credit memo, but accounting creates a negative free text invoice that does not reference the original sales order invoice. It does not verify the required corrective action: Match the receipt by verified customer, currency and eligible open transaction rather than reference alone.

The customer has an open receivable and the correct service revenue/tax postings without stock movement. That would verify a different case: Finance needs a consulting invoice without a sales order, but the team creates a fake inventory order to generate billing. It does not verify the required corrective action: Match the receipt by verified customer, currency and eligible open transaction rather than reference alone.

Customer prepayments and earned sales revenue have different accounting treatment. That explains a separate case: A customer pays an advance before a sales order is fulfilled, but finance books it as final earned revenue. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Billing classification affects transaction grouping and control independently of the inventory line text. That explains a separate case: A product invoice should use special billing classification, but the customer's default classification is absent. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

AR charges are separate invoice components whose posting and tax handling require explicit setup. That explains a separate case: An invoice includes a contractual handling charge, but the charge is missing from the posted customer transaction. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Monitor and resolve aged unapplied customer payments. That safeguard is aimed at a different risk: Cash was received against a settled customer invoice, creating a residual overpayment that finance tries to hide as a forced invoice credit. It does not most directly prevent recurrence of: External invoice references are not globally unique account and currency identifiers.

Confirm payment instructions after company banking changes. That safeguard is aimed at a different risk: A finance team sends invoices to a customer using the wrong remittance account because the customer's payment method default is stale. It does not most directly prevent recurrence of: External invoice references are not globally unique account and currency identifiers.

Review billing classifications during new product or channel rollouts. That safeguard is aimed at a different risk: A product invoice should use special billing classification, but the customer's default classification is absent. It does not most directly prevent recurrence of: External invoice references are not globally unique account and currency identifiers.

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

Use the supported intercompany invoice linkage and verify legal-entity transaction references. This fits a DIFFERENT issue within Implement and manage accounts payable: Intercompany vendor invoices are imported without matching seller-company sales invoice references, causing periodic reconciliation differences. It does not address the current problem, whose mechanism is: Centralized payments cross legal-entity boundaries and need explicit intercompany accounting.

Review vendor cash discount terms and the eligible settlement/payment date when generating the payment proposal. This fits a DIFFERENT issue within Implement and manage accounts payable: 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 address the current problem, whose mechanism is: Centralized payments cross legal-entity boundaries and need explicit intercompany accounting.

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.