Exam Bundle

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: Periodic journals reuse recurring entry definitions but still require schedule and posting review.

Version-control journal templates after finance app updates. That safeguard is aimed at a different risk: An Excel-imported journal has valid amounts but the financial dimension columns were renamed, so import fails mapping. It does not most directly prevent recurrence of: Periodic journals reuse recurring entry definitions but still require schedule and posting review.

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: Periodic journals reuse recurring entry definitions but still require schedule and posting review.

Exclude the ineligible disputed invoice and process netting only for approved eligible open transactions. This fits a DIFFERENT issue within Implement and manage cash and bank: A high-value customer and vendor netting proposal includes a disputed invoice that should remain open. It does not address the current problem, whose mechanism is: Bank reconciliation accounts for timing differences between recorded cash and bank clearing.

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 reconciliation accounts for timing differences between recorded cash and bank clearing.

Configure the automation scope and legal entity inclusion for the intended entities. This fits a DIFFERENT issue within Implement and manage cash and bank: Treasury expects an automated cash forecast for each legal entity but the forecast job only runs in the holding company. It does not address the current problem, whose mechanism is: Bank reconciliation accounts for timing differences between recorded cash and bank clearing.

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: Match cleared statement items against bank transactions and identify legitimate outstanding/open items before posting adjustments.

The disputed item remains open and eligible balances settle to the approved net amount. That would verify a different case: A high-value customer and vendor netting proposal includes a disputed invoice that should remain open. It does not verify the required corrective action: Match cleared statement items against bank transactions and identify legitimate outstanding/open items before posting adjustments.

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: Match cleared statement items against bank transactions and identify legitimate outstanding/open items before posting adjustments.

Bank statement import controls must prevent repeated processing of the same source data. That explains a separate case: Bank reconciliations show duplicate statement lines after an operator reimports the same bank file. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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.

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 reconciliation accounts for timing differences between recorded cash and bank clearing.

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: Bank reconciliation accounts for timing differences between recorded cash and bank clearing.

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: Bank reconciliation accounts for timing differences between recorded cash and bank clearing.

Require supporting batch status and successfully posted voucher evidence before accepting task completion. This fits a DIFFERENT issue within Perform periodic processes: Financial close tasks are marked Complete even though the underlying journal batches have failures. It does not address the current problem, whose mechanism is: Consolidation elimination reverses intercompany effects at reporting-group level rather than in operating company books.

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: Consolidation elimination reverses intercompany effects at reporting-group level rather than in operating company books.

Correct approved year-end closing account mappings before rerunning under proper control. This fits a DIFFERENT issue within Perform periodic processes: Year-end closing creates retained earnings using the wrong target main account. It does not address the current problem, whose mechanism is: Consolidation elimination reverses intercompany effects at reporting-group level rather than in operating company books.

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: Configure and execute applicable consolidation elimination rules for matching intercompany accounts.

Year-end results transfer net profit to the intended retained earnings account with audit evidence. That would verify a different case: Year-end closing creates retained earnings using the wrong target main account. It does not verify the required corrective action: Configure and execute applicable consolidation elimination rules for matching intercompany accounts.

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: Configure and execute applicable consolidation elimination rules for matching intercompany accounts.

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.

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.

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.

Review settlement selection by account, amount, date and legal entity. That safeguard is aimed at a different risk: Ledger settlement cannot find offsetting debit and credit transactions because the settlement criteria use a mismatched main account. It does not most directly prevent recurrence of: Consolidation elimination reverses intercompany effects at reporting-group level rather than in operating company books.

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: Consolidation elimination reverses intercompany effects at reporting-group level rather than in operating company books.

Add voucher/batch proof as an attachment requirement for high-risk close tasks. That safeguard is aimed at a different risk: Financial close tasks are marked Complete even though the underlying journal batches have failures. It does not most directly prevent recurrence of: Consolidation elimination reverses intercompany effects at reporting-group level rather than in operating company books.

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 settlement periods and authorities control reporting and remittance of tax obligations.

Use the supported settle-and-post sales tax process and reconcile authority payment postings. This fits a DIFFERENT issue within Configure, collect, and report taxes: A sales tax authority remittance has been recorded but the sales tax liability balance is not cleared against its settlement. It does not address the current problem, whose mechanism is: Tax settlement periods and authorities control reporting and remittance of tax obligations.

Review customer sales tax group and item sales tax group intersections and attach the appropriate authorized tax code. This fits a DIFFERENT issue within Configure, collect, and report taxes: 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 address the current problem, whose mechanism is: Tax settlement periods and authorities control reporting and remittance of tax obligations.

A sample free-text invoice calculates the correct code and rate under the intended groups. That would verify a different case: A tax code applies to a customer but a free-text invoice does not inherit the expected item tax group. It does not verify the required corrective action: Configure the correct settlement period and tax authority associations for the applicable tax codes.

A qualifying invoice excludes tax while an ordinary customer still incurs tax. That would verify a different case: A tax-exempt customer is charged standard tax because the exemption status was never assigned. It does not verify the required corrective action: Configure the correct settlement period and tax authority associations for the applicable tax codes.

A taxable transaction posts liabilities or recoverables to the approved ledger accounts. That would verify a different case: Tax amounts are correct but post to an incorrect general ledger account because a tax ledger posting group mapping is stale. It does not verify the required corrective action: Configure the correct settlement period and tax authority associations for the applicable tax codes.