Exam Bundle

Generated entries appear for intended periods without duplicated accrual vouchers. That would verify a different case: Finance pays the same lease accrual every month but staff recreate its general journal manually and miss a month. It does not verify the required corrective action: Create company- or unit-appropriate periodic journal/default dimensions and validate each destination before posting.

A sampled voucher includes the documented purpose, support and approved posting identity. That would verify a different case: An auditor requests an explanation for a year-end manual journal, but the voucher has no supporting description or documentation reference. It does not verify the required corrective action: Create company- or unit-appropriate periodic journal/default dimensions and validate each destination before posting.

A test journal adopts only the allowed layer for its company and entry type. That would verify a different case: Financial vouchers use a shared journal name but different posting layers across two subsidiaries without approval. It does not verify the required corrective action: Create company- or unit-appropriate periodic journal/default dimensions and validate each destination before posting.

Journal configuration and ledger posting layers carry accounting intent that must be consistently governed. That explains a separate case: Financial vouchers use a shared journal name but different posting layers across two subsidiaries without approval. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Journal balance validation evaluates accounting currency, not merely the displayed sum of foreign amounts. That explains a separate case: An imported general journal has debits and credits in different currencies with no correct accounting-currency balancing. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Periodic journals reuse recurring entry definitions but still require schedule and posting review. That explains a separate case: Finance pays the same lease accrual every month but staff recreate its general journal manually and miss a month. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile due-to and due-from balances every close. That safeguard is aimed at a different risk: Legal entity A books an expense owed by legal entity B, but the accountant inserts offset accounts manually and intercompany balances disagree. It does not most directly prevent recurrence of: Recurring templates carry default dimension context that may differ between units.

Compare scheduled and actual accruals in the month-end checklist. That safeguard is aimed at a different risk: Finance pays the same lease accrual every month but staff recreate its general journal manually and miss a month. It does not most directly prevent recurrence of: Recurring templates carry default dimension context that may differ between units.

Check batch status and voucher posting evidence before retrying failed jobs. That safeguard is aimed at a different risk: A large approved journal can be validated manually, but synchronous posting times out during a close window. It does not most directly prevent recurrence of: Recurring templates carry default dimension context that may differ between units.

Match cleared statement items against bank transactions and identify legitimate outstanding/open items before posting adjustments. This fits a DIFFERENT issue within Implement and manage cash and bank: Monthly bank reconciliation shows deposits in transit and outstanding checks, but finance marks every unmatched item as an error. It does not address the current problem, whose mechanism is: Netting eligibility and dispute status must be checked at transaction level.

Enable appropriate cash flow forecasting source configuration and automation for the expected payables. This fits a DIFFERENT issue within Implement and manage cash and bank: Central treasury needs cash flow forecasts, but no vendor due-date payment data reaches the forecast. It does not address the current problem, whose mechanism is: Netting eligibility and dispute status must be checked at transaction level.

Run the approved bank foreign currency revaluation with valid effective exchange rates. This fits a DIFFERENT issue within Implement and manage cash and bank: A foreign-currency bank balance is held in GBP, and end-month EUR statements are wrong because bank currency revaluation was skipped. It does not address the current problem, whose mechanism is: Netting eligibility and dispute status must be checked at transaction level.

A test customer receipt updates the intended bank account and reconciles to its main account. That would verify a different case: Treasury has added a new bank account but customer payments post to an unrelated cash main account. It does not verify the required corrective action: Exclude the ineligible disputed invoice and process netting only for approved eligible open transactions.

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: Exclude the ineligible disputed invoice and process netting only for approved eligible open transactions.

Forecast output includes the planned companies without cross-entity duplication. That would verify a different case: Treasury expects an automated cash forecast for each legal entity but the forecast job only runs in the holding company. It does not verify the required corrective action: Exclude the ineligible disputed invoice and process netting only for approved eligible open transactions.

Automated forecasts are sensitive to the configured organization and data source scope. That explains a separate case: Treasury expects an automated cash forecast for each legal entity but the forecast job only runs in the holding company. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Centralized payments require company and payment setup rather than selecting an arbitrary foreign bank account. That explains a separate case: A group company pays vendor invoices from a central payment account, but shared payment setup is not configured for the involved entities. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Cash flow forecasting requires configured source transactions and forecast automation rules. That explains a separate case: Central treasury needs cash flow forecasts, but no vendor due-date payment data reaches the forecast. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile forecast sources to underlying accounts payable schedules. That safeguard is aimed at a different risk: Central treasury needs cash flow forecasts, but no vendor due-date payment data reaches the forecast. It does not most directly prevent recurrence of: Netting eligibility and dispute status must be checked at transaction level.

Confirm counterparty and legal-entity eligibility before netting open items. That safeguard is aimed at a different risk: 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 most directly prevent recurrence of: Netting eligibility and dispute status must be checked at transaction level.

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: Netting eligibility and dispute status must be checked at transaction level.

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

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

Reverse or correct the inappropriate settlement under an authorized accounting procedure and reopen the correct matching process. This fits a DIFFERENT issue within Perform periodic processes: An operating account balance remains unreconciled because an unmatched ledger settlement was forced to close the period. It does not address the current problem, whose mechanism is: Consolidation results are snapshots of source ledger balances when processed, not automatic live totals.

The operating company remains unchanged and eliminating entries appear in the intended consolidation company. That would verify a different case: An elimination journal posts to an operating subsidiary rather than the designated elimination legal entity. It does not verify the required corrective action: Complete and validate source-company period-end revaluations before rerunning the approved consolidation.

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: Complete and validate source-company period-end revaluations before rerunning the approved consolidation.

The consolidation shows translated amounts with reconciling translation adjustments. That would verify a different case: A consolidated balance sheet includes a company in a different reporting currency but exchange-rate configuration is missing. It does not verify the required corrective action: Complete and validate source-company period-end revaluations before rerunning the approved consolidation.

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.

A template does not automatically supply every company-specific close participant or deadline. That explains a separate case: A new subsidiary has a fiscal-year closing template but no local task owners or due dates. 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.

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.