Exam Bundle

Test finance journal controls against representative roles when closing periods. That safeguard is aimed at a different risk: A financial posting date falls in an open fiscal year but the user's module period is restricted. It does not most directly prevent recurrence of: Changing an exchange-rate table does not retroactively change every posted ledger transaction.

Verify rate type, date and currency pair before finance period revaluations. That safeguard is aimed at a different risk: A foreign-currency receivable revaluation is incorrect because an obsolete exchange rate type is used at month-end. It does not most directly prevent recurrence of: Changing an exchange-rate table does not retroactively change every posted ledger transaction.

Reconcile accounting entries for both gain and loss test cases. That safeguard is aimed at a different risk: The year-end currency conversion leaves a residual balance in the wrong gain/loss account. It does not most directly prevent recurrence of: Changing an exchange-rate table does not retroactively change every posted ledger transaction.

Use the supported journal Excel template with correct entity and financial-dimension mapping fields. This fits a DIFFERENT issue within Implement and manage journals: An Excel-imported journal has valid amounts but the financial dimension columns were renamed, so import fails mapping. It does not address the current problem, whose mechanism is: Journal configuration and ledger posting layers carry accounting intent that must be consistently governed.

Use the supported reversal workflow for the original posted financial transaction and then enter the corrected voucher. This fits a DIFFERENT issue within Implement and manage journals: A posted accrual has the signs reversed, and the team proposes editing the posted voucher directly. It does not address the current problem, whose mechanism is: Journal configuration and ledger posting layers carry accounting intent that must be consistently governed.

Configure journal controls and posting restriction rules appropriate for the adjustment journal. This fits a DIFFERENT issue within Implement and manage journals: An unauthorized journal user can enter financial adjustments to restricted ledger accounts through a general journal. It does not address the current problem, whose mechanism is: Journal configuration and ledger posting layers carry accounting intent that must be consistently governed.

New journal lines receive valid unique vouchers and can post without sequence conflicts. That would verify a different case: General journals from an automated integration reuse voucher numbers and validation detects duplicates. It does not verify the required corrective action: Restrict or configure the appropriate journal names and posting-layer controls for the intended use.

An unprivileged user fails the protected posting test while a designated accountant succeeds. That would verify a different case: An unauthorized journal user can enter financial adjustments to restricted ledger accounts through a general journal. It does not verify the required corrective action: Restrict or configure the appropriate journal names and posting-layer controls for the intended use.

The intercompany entry posts balanced company-specific vouchers with reconciling intercompany balances. That would verify a different case: 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 verify the required corrective action: Restrict or configure the appropriate journal names and posting-layer controls for the intended use.

Intercompany accounting generates counterpart entries across legal entities using defined relationships. That explains a separate case: Legal entity A books an expense owed by legal entity B, but the accountant inserts offset accounts manually and intercompany balances disagree. 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.

Reversal posting is subject to period controls just like ordinary journal entries. That explains a separate case: A reversal is scheduled for the following period, but its reversal date lies in a period closed for adjustment posting. 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: Journal configuration and ledger posting layers carry accounting intent that must be consistently governed.

Compare transaction and accounting currency totals in integration QA. That safeguard is aimed at a different risk: An imported general journal has debits and credits in different currencies with no correct accounting-currency balancing. It does not most directly prevent recurrence of: Journal configuration and ledger posting layers carry accounting intent that must be consistently governed.

Require journal rationale and supporting documents for manual year-end entries. That safeguard is aimed at a different risk: An auditor requests an explanation for a year-end manual journal, but the voucher has no supporting description or documentation reference. It does not most directly prevent recurrence of: Journal configuration and ledger posting layers carry accounting intent that must be consistently governed.

Update the supported payment method export format and related bank account payment settings. This fits a DIFFERENT issue within Implement and manage cash and bank: A bank payment file is rejected by the bank because an outdated payment export format is still used. It does not address the current problem, whose mechanism is: Bank statement import controls must prevent repeated processing of the same source data.

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: Bank statement import controls must prevent repeated processing of the same source data.

Configure and process customer-vendor netting under the approved shared-party and netting setup. This fits a DIFFERENT issue within Implement and manage cash and bank: 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 address the current problem, whose mechanism is: Bank statement import controls must prevent repeated processing of the same source data.

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: Review imported statement identifiers and exclude the already loaded statement before retrying.

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: Review imported statement identifiers and exclude the already loaded statement before retrying.

An equal-reference wrong-amount fixture remains unmatched while the true statement line matches. That would verify a different case: Automated bank statement matching closes a transaction of the wrong amount because the rule matches only reference text. It does not verify the required corrective action: Review imported statement identifiers and exclude the already loaded statement before retrying.

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.

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.

Payment formats define external file structure independently of the approved vendor or customer payment amount. That explains a separate case: A bank payment file is rejected by the bank because an outdated payment export format is still used. 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: Bank statement import controls must prevent repeated processing of the same source data.

Test intercompany accounting generated by centralized payment processing. That safeguard is aimed at a different risk: A group company pays vendor invoices from a central payment account, but shared payment setup is not configured for the involved entities. It does not most directly prevent recurrence of: Bank statement import controls must prevent repeated processing of the same source data.

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: Bank statement import controls must prevent repeated processing of the same source data.

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

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

Configure financial period closing templates, task owners and schedules for the target legal entities. This fits a DIFFERENT issue within Perform periodic processes: A financial close team cannot determine which month-end tasks remain for each subsidiary because spreadsheets are circulated separately. It does not address the current problem, whose mechanism is: An elimination company provides a controlled ledger scope for group-only adjusting entries.

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.