Exam Bundle

The closing workspace displays outstanding and completed tasks with owners by company. That would verify a different case: A financial close team cannot determine which month-end tasks remain for each subsidiary because spreadsheets are circulated separately. It does not verify the required corrective action: Reverse or correct the inappropriate settlement under an authorized accounting procedure and reopen the correct matching process.

The consolidated cash figure reflects the finalized source trial balances and reconciliation totals. That would verify a different case: Group consolidation is run before a subsidiary posts its final bank revaluation and the consolidated cash figure is stale. It does not verify the required corrective action: Reverse or correct the inappropriate settlement under an authorized accounting procedure and reopen the correct matching process.

Task closure references posted journal IDs with zero unresolved job errors. That would verify a different case: Financial close tasks are marked Complete even though the underlying journal batches have failures. It does not verify the required corrective action: Reverse or correct the inappropriate settlement under an authorized accounting procedure and reopen the correct matching process.

An elimination company provides a controlled ledger scope for group-only adjusting entries. That explains a separate case: An elimination journal posts to an operating subsidiary rather than the designated elimination legal entity. 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.

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.

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 false ledger settlement can conceal unresolved differences without correcting source transactions.

Use a source-ledger completion gate for every consolidation cycle. That safeguard is aimed at a different risk: Group consolidation is run before a subsidiary posts its final bank revaluation and the consolidated cash figure is stale. It does not most directly prevent recurrence of: A false ledger settlement can conceal unresolved differences without correcting source transactions.

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: A false ledger settlement can conceal unresolved differences without correcting source transactions.

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: Tax calculation, sales tax settlement and remittance are distinct ledger events.

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: Tax calculation, sales tax settlement and remittance are distinct ledger events.

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 calculation, sales tax settlement and remittance are distinct ledger events.

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: Use the supported settle-and-post sales tax process and reconcile authority payment postings.

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: Use the supported settle-and-post sales tax process and reconcile authority payment postings.

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: Use the supported settle-and-post sales tax process and reconcile authority payment postings.

Posted tax liabilities require auditable correcting transactions rather than silent historical edits. That explains a separate case: A tax adjustment needs to correct a miscalculated invoice, but a user proposes editing a tax authority settlement already posted. 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.

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.

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 calculation, sales tax settlement and remittance are distinct ledger events.

Review supplier withholding classification before payment approvals. That safeguard is aimed at a different risk: A vendor invoice should withhold a statutory portion, but its withholding tax group is absent. It does not most directly prevent recurrence of: Tax calculation, sales tax settlement and remittance are distinct ledger events.

Test both taxable and exempt combinations for new products. That safeguard is aimed at a different risk: A sales invoice calculates zero tax because the customer sales tax group has no valid overlap with the item's tax group. It does not most directly prevent recurrence of: Tax calculation, sales tax settlement and remittance are distinct ledger events.

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: Intercompany invoicing links paired transactions across legal entities rather than automatically clearing them.

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: Intercompany invoicing links paired transactions across legal entities rather than automatically clearing them.

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: Intercompany invoicing links paired transactions across legal entities rather than automatically clearing them.

The payment is recognized as a prepayment liability or advance as configured until the proper invoice event. That would verify a different case: A customer pays an advance before a sales order is fulfilled, but finance books it as final earned revenue. It does not verify the required corrective action: Use the supported intercompany invoicing process and validate both company source documents.

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: Use the supported intercompany invoicing process and validate both company source documents.

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: Use the supported intercompany invoicing process and validate both company source documents.

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.

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.

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.

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: Intercompany invoicing links paired transactions across legal entities rather than automatically clearing them.

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: Intercompany invoicing links paired transactions across legal entities rather than automatically clearing them.

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: Intercompany invoicing links paired transactions across legal entities rather than automatically clearing them.