Exam Bundle

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: Correct approved year-end closing account mappings before rerunning under proper control.

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: Correct approved year-end closing account mappings before rerunning under proper control.

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: Correct approved year-end closing account mappings before rerunning under proper control.

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.

Consolidation requires precise source-company scope and elimination setup; duplicate sources double count. That explains a separate case: A subsidiary is included in consolidation twice because its source legal entity mapping is duplicated. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Multicurrency consolidation depends on translation policy and exchange rates, not raw addition of local currencies. That explains a separate case: A consolidated balance sheet includes a company in a different reporting currency but exchange-rate configuration is missing. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Require company context validation before elimination posting. That safeguard is aimed at a different risk: An elimination journal posts to an operating subsidiary rather than the designated elimination legal entity. It does not most directly prevent recurrence of: Year-end ledger closing depends on configured profit and loss transfer accounts.

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: Year-end ledger closing depends on configured profit and loss transfer accounts.

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: Year-end ledger closing depends on configured profit and loss transfer accounts.

Configure a date-effective rate change for the tax code without overwriting historical treatment. This fits a DIFFERENT issue within Configure, collect, and report taxes: A jurisdiction increases tax from 8% to 9% midyear, but prior invoices must remain at historical rates. It does not address the current problem, whose mechanism is: Withholding tax is driven by withholding group and code configuration, distinct from ordinary sales tax.

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: Withholding tax is driven by withholding group and code configuration, distinct from ordinary sales tax.

Create or assign the appropriate item sales tax group to the special-rate products. This fits a DIFFERENT issue within Configure, collect, and report taxes: 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 address the current problem, whose mechanism is: Withholding tax is driven by withholding group and code configuration, distinct from ordinary sales tax.

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: Assign the appropriate vendor withholding tax group and valid code/authority setup.

A sample free-text invoice calculates the correct code and rate under the intended groups. That would verify a different case: A tax code applies to a customer but a free-text invoice does not inherit the expected item tax group. It does not verify the required corrective action: Assign the appropriate vendor withholding tax group and valid code/authority setup.

Each tax return includes only its applicable company's tax transactions and currency. That would verify a different case: A multi-entity tax report mixes domestic and overseas tax obligations because legal entity filters are omitted. It does not verify the required corrective action: Assign the appropriate vendor withholding tax group and valid code/authority setup.

Tax legal entity and authority boundaries must be respected even with shared tax codes. That explains a separate case: A multi-entity tax report mixes domestic and overseas tax obligations because legal entity filters are omitted. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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.

Applicable sales tax codes derive from transaction-related group combinations and tax setup. That explains a separate case: A sales invoice calculates zero tax because the customer sales tax group has no valid overlap with the item's tax group. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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: Withholding tax is driven by withholding group and code configuration, distinct from ordinary sales tax.

Review tax authorities and settlement mapping at company onboarding. That safeguard is aimed at a different risk: Sales tax settlement reports omit one country's transactions because its settlement period is mapped to the wrong authority. It does not most directly prevent recurrence of: Withholding tax is driven by withholding group and code configuration, distinct from ordinary sales tax.

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: Withholding tax is driven by withholding group and code configuration, distinct from ordinary sales tax.

Record and settle the approved customer prepayment through the supported sales/prepayment workflow. This fits a DIFFERENT issue within Implement and manage accounts receivable: A customer pays an advance before a sales order is fulfilled, but finance books it as final earned revenue. It does not address the current problem, whose mechanism is: Receivables cash posting and open-invoice settlement are related but distinct operations.

Use an approved sales order credit note or return invoicing process linked to the original transaction. This fits a DIFFERENT issue within Implement and manage accounts receivable: 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 address the current problem, whose mechanism is: Receivables cash posting and open-invoice settlement are related but distinct operations.

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: Receivables cash posting and open-invoice settlement are related but distinct operations.

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: Process a customer payment and apply partial settlement to the intended open invoice.

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: Process a customer payment and apply partial settlement to the intended open invoice.

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: Process a customer payment and apply partial settlement to the intended open invoice.

Customer posting profiles map operational customer transactions to general ledger accounts, and customer groups can influence defaults. That explains a separate 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. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Party sharing and company-specific customer financial settings occupy different configuration scopes. That explains a separate case: A shared customer master is maintained in a centralized group, but one legal entity needs different payment terms. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

External invoice references are not globally unique account and currency identifiers. That explains a separate case: A customer payment import finds an existing invoice with the same external reference but wrong currency. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile matched AR/AP documents in the intercompany close. That safeguard is aimed at a different risk: An intercompany sale is invoiced in the selling company but the buying company has no corresponding vendor invoice. It does not most directly prevent recurrence of: Receivables cash posting and open-invoice settlement are related but distinct operations.

Reconcile advances against fulfilled orders and final invoices. That safeguard is aimed at a different risk: A customer pays an advance before a sales order is fulfilled, but finance books it as final earned revenue. It does not most directly prevent recurrence of: Receivables cash posting and open-invoice settlement are related but distinct operations.

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: Receivables cash posting and open-invoice settlement are related but distinct operations.