Exam Bundle

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: Period validation may reflect both fiscal calendar status and module-specific restrictions.

Reconcile representative three-currency postings before consolidation signoff. That safeguard is aimed at a different risk: Revenue is translated correctly to accounting currency but a consolidated reporting currency variance arises because the reporting currency rate series is incomplete. It does not most directly prevent recurrence of: Period validation may reflect both fiscal calendar status and module-specific restrictions.

Review drivers and rounding before each allocation cycle. That safeguard is aimed at a different risk: The finance team needs to distribute facilities expense across departments monthly but posts manual lines using outdated allocation percentages. It does not most directly prevent recurrence of: Period validation may reflect both fiscal calendar status and module-specific restrictions.

Set up a periodic journal with the appropriate recurrence and manage its generation under monthly review. This fits a DIFFERENT issue within Implement and manage journals: Finance pays the same lease accrual every month but staff recreate its general journal manually and miss a month. It does not address the current problem, whose mechanism is: Reversal posting is subject to period controls just like ordinary journal entries.

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: Reversal posting is subject to period controls just like ordinary journal entries.

Review the journal name's voucher number sequence and the integration's numbering behavior. This fits a DIFFERENT issue within Implement and manage journals: General journals from an automated integration reuse voucher numbers and validation detects duplicates. It does not address the current problem, whose mechanism is: Reversal posting is subject to period controls just like ordinary journal entries.

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: Use a permissible reversal posting date or approved period-access adjustment under controlled close procedures.

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: Use a permissible reversal posting date or approved period-access adjustment under controlled close procedures.

The original and reversal remain audit-linked and the net accounting effect equals the correction. That would verify a different case: A posted accrual has the signs reversed, and the team proposes editing the posted voucher directly. It does not verify the required corrective action: Use a permissible reversal posting date or approved period-access adjustment under controlled close procedures.

Recurring templates carry default dimension context that may differ between units. That explains a separate case: Two business units need the same recurring adjustment but one has a different CostCenter dimension in its default template. 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.

Journal control and user posting restrictions can limit who posts specified journal types or accounts. That explains a separate case: An unauthorized journal user can enter financial adjustments to restricted ledger accounts through a general journal. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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: Reversal posting is subject to period controls just like ordinary journal entries.

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: Reversal posting is subject to period controls just like ordinary journal entries.

Require original-voucher linkage and net balance checks for correction requests. That safeguard is aimed at a different risk: A posted accrual has the signs reversed, and the team proposes editing the posted voucher directly. It does not most directly prevent recurrence of: Reversal posting is subject to period controls just like ordinary journal entries.

Configure or correct bank account and associated posting setup to target the approved cash ledger account. This fits a DIFFERENT issue within Implement and manage cash and bank: Treasury has added a new bank account but customer payments post to an unrelated cash main account. It does not address the current problem, whose mechanism is: Payment formats define external file structure independently of the approved vendor or customer payment amount.

Review imported statement identifiers and exclude the already loaded statement before retrying. This fits a DIFFERENT issue within Implement and manage cash and bank: Bank reconciliations show duplicate statement lines after an operator reimports the same bank file. It does not address the current problem, whose mechanism is: Payment formats define external file structure independently of the approved vendor or customer payment amount.

Create a specific advanced bank reconciliation matching rule or allowed manual entry for known bank fee patterns. This fits a DIFFERENT issue within Implement and manage cash and bank: An organization enables advanced bank reconciliation but cannot match statement fees because transaction matching rules omit fee patterns. It does not address the current problem, whose mechanism is: Payment formats define external file structure independently of the approved vendor or customer payment amount.

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: Update the supported payment method export format and related bank account payment settings.

The fee appears in matching/adjustment results and the statement reconciles without forced matches. That would verify a different case: An organization enables advanced bank reconciliation but cannot match statement fees because transaction matching rules omit fee patterns. It does not verify the required corrective action: Update the supported payment method export format and related bank account payment settings.

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: Update the supported payment method export format and related bank account payment settings.

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 reconciliation accounts for timing differences between recorded cash and bank clearing. That explains a separate case: Monthly bank reconciliation shows deposits in transit and outstanding checks, but finance marks every unmatched item as an error. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Foreign-currency bank accounts can require periodic revaluation separate from operational statement matching. That explains a separate case: A foreign-currency bank balance is held in GBP, and end-month EUR statements are wrong because bank currency revaluation was skipped. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Include near-match negative tests for matching-rule maintenance. That safeguard is aimed at a different risk: Automated bank statement matching closes a transaction of the wrong amount because the rule matches only reference text. It does not most directly prevent recurrence of: Payment formats define external file structure independently of the approved vendor or customer payment amount.

Separate timing items from corrective accounting entries in monthly signoff. That safeguard is aimed at a different risk: Monthly bank reconciliation shows deposits in transit and outstanding checks, but finance marks every unmatched item as an error. It does not most directly prevent recurrence of: Payment formats define external file structure independently of the approved vendor or customer payment amount.

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: Payment formats define external file structure independently of the approved vendor or customer payment amount.

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: Workflow task completion is an administrative status independent of actual journal posting success.

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: Workflow task completion is an administrative status independent of actual journal posting success.

Apply an appropriate company-specific closing schedule and task ownership mapping. This fits a DIFFERENT issue within Perform periodic processes: A new subsidiary has a fiscal-year closing template but no local task owners or due dates. It does not address the current problem, whose mechanism is: Workflow task completion is an administrative status independent of actual journal posting success.

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: Require supporting batch status and successfully posted voucher evidence before accepting task completion.

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: Require supporting batch status and successfully posted voucher evidence before accepting task completion.

The eligible counterpart transactions are marked settled without altering unmatched balances. That would verify a different case: Ledger settlement cannot find offsetting debit and credit transactions because the settlement criteria use a mismatched main account. It does not verify the required corrective action: Require supporting batch status and successfully posted voucher evidence before accepting task completion.