Exam Bundle

A forecast run includes upcoming eligible vendor payments with the intended timing. That would verify a different case: Central treasury needs cash flow forecasts, but no vendor due-date payment data reaches the forecast. It does not verify the required corrective action: Run the approved bank foreign currency revaluation with valid effective exchange rates.

Approved offsets reduce eligible customer and vendor open balances while retaining traceable settlement records. That would verify a different case: Customer A owes an invoice while vendor A is owed a payable for the same legal party, but finance creates cash payments in both directions. It does not verify the required corrective action: Run the approved bank foreign currency revaluation with valid effective exchange rates.

The statement imports with matching dates, references and amounts into bank reconciliation. That would verify a different case: A bank statement import rejects transactions because its electronic format differs from the configured payment/bank statement format. It does not verify the required corrective action: Run the approved bank foreign currency revaluation with valid effective exchange rates.

Automated matching rules need transaction-specific criteria and may require fee adjustments. That explains a separate case: An organization enables advanced bank reconciliation but cannot match statement fees because transaction matching rules omit fee patterns. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Netting settles opposing receivable and payable obligations without unnecessary cash movements. That explains a separate case: Customer A owes an invoice while vendor A is owed a payable for the same legal party, but finance creates cash payments in both directions. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Bank account posting setup connects operational receipts to general ledger accounts. That explains a separate case: Treasury has added a new bank account but customer payments post to an unrelated cash main account. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Test unmatched fees and legitimate exceptions when tuning reconciliation rules. That safeguard is aimed at a different risk: An organization enables advanced bank reconciliation but cannot match statement fees because transaction matching rules omit fee patterns. It does not most directly prevent recurrence of: Foreign-currency bank accounts can require periodic revaluation separate from operational statement matching.

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: Foreign-currency bank accounts can require periodic revaluation separate from operational statement matching.

Validate each bank format change with a known-good statement. That safeguard is aimed at a different risk: A bank statement import rejects transactions because its electronic format differs from the configured payment/bank statement format. It does not most directly prevent recurrence of: Foreign-currency bank accounts can require periodic revaluation separate from operational statement matching.

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: Closed financial periods protect ledger integrity and exceptions require constrained access.

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: Closed financial periods protect ledger integrity and exceptions require constrained access.

Correct consolidation source-company selection and ownership settings before running Consolidation online. This fits a DIFFERENT issue within Perform periodic processes: A subsidiary is included in consolidation twice because its source legal entity mapping is duplicated. It does not address the current problem, whose mechanism is: Closed financial periods protect ledger integrity and exceptions require constrained access.

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: Use approved adjustment period access or controlled authorization rather than changing all close periods to Open.

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: Use approved adjustment period access or controlled authorization rather than changing all close periods to Open.

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: Use approved adjustment period access or controlled authorization rather than changing all close periods to Open.

Year-end ledger closing depends on configured profit and loss transfer accounts. That explains a separate case: Year-end closing creates retained earnings using the wrong target main account. 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 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.

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: Closed financial periods protect ledger integrity and exceptions require constrained access.

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: Closed financial periods protect ledger integrity and exceptions require constrained access.

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: Closed financial periods protect ledger integrity and exceptions require constrained access.

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: A tax exemption changes eligibility for specified tax treatment, not the global tax rate for all customers.

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: A tax exemption changes eligibility for specified tax treatment, not the global tax rate for all customers.

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: A tax exemption changes eligibility for specified tax treatment, not the global tax rate for all customers.

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: Record the approved exemption for the correct customer and relevant tax code/group configuration.

A controlled taxable invoice calculates the correct tax amount while an exempt customer remains exempt. That would verify a different case: 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 verify the required corrective action: Record the approved exemption for the correct customer and relevant tax code/group configuration.

New settlement runs cover the intended one-month date windows with no missing transactions. That would verify a different case: A company reports sales tax monthly while its configured settlement period closes quarterly. It does not verify the required corrective action: Record the approved exemption for the correct customer and relevant tax code/group configuration.

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.

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 calculation, sales tax settlement and remittance are distinct ledger events. That explains a separate case: A sales tax authority remittance has been recorded but the sales tax liability balance is not cleared against its settlement. 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: A tax exemption changes eligibility for specified tax treatment, not the global tax rate for all customers.

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: A tax exemption changes eligibility for specified tax treatment, not the global tax rate for all customers.

Regression-test boundary dates for every statutory tax change. That safeguard is aimed at a different risk: A jurisdiction increases tax from 8% to 9% midyear, but prior invoices must remain at historical rates. It does not most directly prevent recurrence of: A tax exemption changes eligibility for specified tax treatment, not the global tax rate for all customers.