Exam Bundle

The period closing workspace shows the subsidiary's tasks with assigned owners and deadlines. That would verify a different case: A new subsidiary has a fiscal-year closing template but no local task owners or due dates. It does not verify the required corrective action: Choose the configured elimination company and validate elimination journal posting context.

The elimination entries offset intra-group revenue and costs while group external totals remain. That would verify a different case: Intercompany sales and purchases inflate group revenue and costs in consolidated statements. It does not verify the required corrective action: Choose the configured elimination company and validate elimination journal posting context.

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: Choose the configured elimination company and validate elimination journal posting context.

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.

Workflow task completion is an administrative status independent of actual journal posting success. That explains a separate case: Financial close tasks are marked Complete even though the underlying journal batches have failures. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Consolidation elimination reverses intercompany effects at reporting-group level rather than in operating company books. That explains a separate case: Intercompany sales and purchases inflate group revenue and costs in consolidated statements. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Review task assignments after acquisitions and new legal entities. That safeguard is aimed at a different risk: A new subsidiary has a fiscal-year closing template but no local task owners or due dates. It does not most directly prevent recurrence of: An elimination company provides a controlled ledger scope for group-only adjusting entries.

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: An elimination company provides a controlled ledger scope for group-only adjusting entries.

Audit translation methodology and period-end rate dates before signoff. That safeguard is aimed at a different risk: A consolidated balance sheet includes a company in a different reporting currency but exchange-rate configuration is missing. It does not most directly prevent recurrence of: An elimination company provides a controlled ledger scope for group-only adjusting entries.

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: Tax settlements follow configured reporting intervals independent of ledger journal frequency.

Record the approved exemption for the correct customer and relevant tax code/group configuration. This fits a DIFFERENT issue within Configure, collect, and report taxes: A tax-exempt customer is charged standard tax because the exemption status was never assigned. It does not address the current problem, whose mechanism is: Tax settlements follow configured reporting intervals independent of ledger journal frequency.

Select the correct line-level item tax group and customer sales tax group for the free-text invoice context. This fits a DIFFERENT issue within Configure, collect, and report taxes: A tax code applies to a customer but a free-text invoice does not inherit the expected item tax group. It does not address the current problem, whose mechanism is: Tax settlements follow configured reporting intervals independent of ledger journal frequency.

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: Change the authorized settlement period schedule to reflect the reporting authority's current monthly requirements.

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: Change the authorized settlement period schedule to reflect the reporting authority's current monthly requirements.

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: Change the authorized settlement period schedule to reflect the reporting authority's current monthly requirements.

Tax settlement periods and authorities control reporting and remittance of tax obligations. That explains a separate case: Sales tax settlement reports omit one country's transactions because its settlement period is mapped to the wrong authority. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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.

Require company and authority filters on standardized tax reports. That safeguard is aimed at a different risk: A multi-entity tax report mixes domestic and overseas tax obligations because legal entity filters are omitted. It does not most directly prevent recurrence of: Tax settlements follow configured reporting intervals independent of ledger journal frequency.

Review product tax classification during item master maintenance. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Tax settlements follow configured reporting intervals independent of ledger journal frequency.

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 settlements follow configured reporting intervals independent of ledger journal frequency.

Correct the customer's authorized payment method and associated company bank account setup. This fits a DIFFERENT issue within Implement and manage accounts receivable: 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 address the current problem, whose mechanism is: Open foreign-currency receivables require period-specific revaluation separate from original invoice conversion.

Configure the appropriate AR charges code and apply the approved charge at invoice level before posting. This fits a DIFFERENT issue within Implement and manage accounts receivable: An invoice includes a contractual handling charge, but the charge is missing from the posted customer transaction. It does not address the current problem, whose mechanism is: Open foreign-currency receivables require period-specific revaluation separate from original invoice conversion.

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: Open foreign-currency receivables require period-specific revaluation separate from original invoice conversion.

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: Execute the approved accounts receivable foreign currency revaluation for eligible open balances.

The exact intended invoice is settled and the currency mismatch fixture remains open for investigation. That would verify a different case: A customer payment import finds an existing invoice with the same external reference but wrong currency. It does not verify the required corrective action: Execute the approved accounts receivable foreign currency revaluation for eligible open balances.

The expected customer has one new invoice for the period and no duplicated fee invoices. That would verify a different case: A monthly management fee is billed manually each month, and staff accidentally bill one client twice. It does not verify the required corrective action: Execute the approved accounts receivable foreign currency revaluation for eligible open balances.

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.

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.

Receivables cash posting and open-invoice settlement are related but distinct operations. That explains a separate case: A customer pays part of an overdue invoice but the receipt is posted against the customer's account without marking the invoice settled. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Use the correct invoice source and document service fulfillment evidence. That safeguard is aimed at a different risk: Finance needs a consulting invoice without a sales order, but the team creates a fake inventory order to generate billing. It does not most directly prevent recurrence of: Open foreign-currency receivables require period-specific revaluation separate from original invoice conversion.

Reconcile recurring invoice generation counts to active contracts. That safeguard is aimed at a different risk: A monthly management fee is billed manually each month, and staff accidentally bill one client twice. It does not most directly prevent recurrence of: Open foreign-currency receivables require period-specific revaluation separate from original invoice conversion.

Review settlement application and unapplied payments after bank imports. That safeguard is aimed at a different risk: A customer pays part of an overdue invoice but the receipt is posted against the customer's account without marking the invoice settled. It does not most directly prevent recurrence of: Open foreign-currency receivables require period-specific revaluation separate from original invoice conversion.