Exam Bundle

Reconcile intercompany asset transfers and ownership evidence. That safeguard is aimed at a different risk: An asset was created in the wrong legal entity and finance plans to fix the reporting by editing its name only. It does not most directly prevent recurrence of: Fixed asset groups define classification and default values affecting subsequent asset processing.

Compare planned depreciation under each book to approved accounting policy. That safeguard is aimed at a different risk: Financial statements require straight-line depreciation but a fixed asset book uses reducing-balance method. It does not most directly prevent recurrence of: Fixed asset groups define classification and default values affecting subsequent asset processing.

Test beginning, middle and end-of-month acquisitions. That safeguard is aimed at a different risk: Fixed asset books have the correct depreciation method but no depreciation start convention, producing inconsistent first-month charges. It does not most directly prevent recurrence of: Fixed asset groups define classification and default values affecting subsequent asset processing.

Process a supported fixed asset reclassification with appropriate book and posting controls. This fits a DIFFERENT issue within Process fixed asset transactions: A subsidiary decides an asset was misclassified from furniture to IT equipment but attempts to fix this by deleting historical depreciation vouchers. It does not address the current problem, whose mechanism is: Physical receipt and fixed asset acquisition accounting can occur at different source document stages.

Use an approved fixed asset acquisition adjustment/additional acquisition transaction to capitalize the eligible improvement. This fits a DIFFERENT issue within Process fixed asset transactions: An asset was initially capitalized at $8,000 but a later capital improvement of $1,200 is booked as routine maintenance expense contrary to policy. It does not address the current problem, whose mechanism is: Physical receipt and fixed asset acquisition accounting can occur at different source document stages.

Use the supported fixed asset disposal sale process linked to the appropriate free text invoice. This fits a DIFFERENT issue within Process fixed asset transactions: A company disposes of an old computer for cash, but books the sale through a free text invoice without closing its net book value. It does not address the current problem, whose mechanism is: Physical receipt and fixed asset acquisition accounting can occur at different source document stages.

Only active eligible assets receive depreciation and disposed assets remain closed. That would verify a different case: A fixed asset's monthly depreciation batch accidentally includes disposed assets. It does not verify the required corrective action: Complete the approved purchase order invoicing and fixed asset acquisition posting workflow.

No post-retirement depreciation remains and final disposal value reconciles. That would verify a different case: A fixed asset group includes a machine that was retired, but the depreciation run generates a charge in a period after retirement. It does not verify the required corrective action: Complete the approved purchase order invoicing and fixed asset acquisition posting workflow.

Net book value, sale proceeds and disposal loss reconcile under the approved posting profile. That would verify a different case: An asset is sold below net book value, yet the disposal entry credits a gain account. It does not verify the required corrective action: Complete the approved purchase order invoicing and fixed asset acquisition posting workflow.

Company and book selection determine the scope of multi-company depreciation runs. That explains a separate case: Monthly depreciation is run in batch for several companies, but one legal entity's book was omitted from the batch scope. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Gain or loss on disposal is the difference between proceeds and carrying amount. That explains a separate case: An asset is sold below net book value, yet the disposal entry credits a gain account. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Cross-company fixed asset movements require balanced accounting at both company boundaries. That explains a separate case: An asset is transferred between two companies, but one company posts the disposal while the other fails to recognize the corresponding acquisition. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Test profitable and loss-making disposals before posting-profile changes. That safeguard is aimed at a different risk: An asset is sold below net book value, yet the disposal entry credits a gain account. It does not most directly prevent recurrence of: Physical receipt and fixed asset acquisition accounting can occur at different source document stages.

Reconcile combined pre-split and post-split book values. That safeguard is aimed at a different risk: A company separates a combined machine into two components with different useful lives, but accounting only changes the asset description. It does not most directly prevent recurrence of: Physical receipt and fixed asset acquisition accounting can occur at different source document stages.

Require asset custodian and accounting signoff for intersite transfers. That safeguard is aimed at a different risk: A finance team changes an asset's location from one site to another and expects the general ledger to transfer its book value automatically. It does not most directly prevent recurrence of: Physical receipt and fixed asset acquisition accounting can occur at different source document stages.

Configure an applicable main-account posting control or restriction to limit unauthorized journal entries to the protected account. This fits a DIFFERENT issue within Design and configure the chart of accounts and financial dimensions: Accounts used for payroll liabilities must not be cleared by ordinary manual posting, but users currently select them freely. It does not address the current problem, whose mechanism is: An account structure controls which financial dimensions and values are required for a posting account.

Configure derived financial dimension rules mapping eligible CostCenter values to the appropriate Department values. This fits a DIFFERENT issue within Design and configure the chart of accounts and financial dimensions: A company requires a Department dimension to derive from CostCenter for known responsibility centers, but staff manually pick inconsistent departments. It does not address the current problem, whose mechanism is: An account structure controls which financial dimensions and values are required for a posting account.

Correct the source default dimensions and validate them against the active account structure before posting. This fits a DIFFERENT issue within Design and configure the chart of accounts and financial dimensions: A dimension hierarchy was revised, but a vendor invoice uses a default Department value no longer valid for its main account. It does not address the current problem, whose mechanism is: An account structure controls which financial dimensions and values are required for a posting account.

An unauthorized general journal cannot post to the controlled account while approved source transactions remain possible. That would verify a different case: Accounts used for payroll liabilities must not be cleared by ordinary manual posting, but users currently select them freely. It does not verify the required corrective action: Add CostCenter to the applicable ledger account structure and require an allowed dimension combination for the expense account range.

Selecting the alias resolves to the correct main account and dimensions without manual guessing. That would verify a different case: The month-end posting team repeatedly chooses the wrong main account for office supplies because account names are similar. It does not verify the required corrective action: Add CostCenter to the applicable ledger account structure and require an allowed dimension combination for the expense account range.

The adjustment stores the campaign tag while the valid ledger account dimension combination is unchanged. That would verify a different case: A customer discount adjustment should carry financial tags for campaign reporting, but the team tries to create a new financial dimension for an informational label not needed in account combinations. It does not verify the required corrective action: Add CostCenter to the applicable ledger account structure and require an allowed dimension combination for the expense account range.

Advanced account structure rules constrain dimensions for qualifying accounts rather than globally expanding all combinations. That explains a separate case: Only capital-expenditure accounts need a Project financial dimension, but including Project for all operating expenses creates unnecessary entry. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Financial dimensions classify transactions without multiplying the chart of accounts into redundant department-specific main accounts. That explains a separate case: A multinational legal entity needs profit-and-loss reports by business unit, but its chart of accounts has a separate expense main account for every department. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Shared main account definitions may have company-specific overrides controlling posting behavior. That explains a separate case: Two legal entities use a common account chart, but one entity must prohibit posting to an inactive local account. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Audit aliases and associated dimensions after account redesigns. That safeguard is aimed at a different risk: The month-end posting team repeatedly chooses the wrong main account for office supplies because account names are similar. It does not most directly prevent recurrence of: An account structure controls which financial dimensions and values are required for a posting account.

Revalidate default templates whenever a cost-center hierarchy changes. That safeguard is aimed at a different risk: A finance team enters many identical financial dimension combinations across budget journals, causing frequent transcription errors. It does not most directly prevent recurrence of: An account structure controls which financial dimensions and values are required for a posting account.

Define governance distinguishing financial tags from posting dimensions. That safeguard is aimed at a different risk: A customer discount adjustment should carry financial tags for campaign reporting, but the team tries to create a new financial dimension for an informational label not needed in account combinations. It does not most directly prevent recurrence of: An account structure controls which financial dimensions and values are required for a posting account.

Review allocation rule rounding and distribution configuration so generated debit and credit lines balance. This fits a DIFFERENT issue within Configure ledgers and currencies: A test allocation produces a small unbalanced amount after percentage distribution due to rounding. It does not address the current problem, whose mechanism is: Exchange rate types identify different rate series; a valid rate in the wrong series produces incorrect translation.

Set the appropriate ledger calendar fiscal period to the intended restricted status for affected users and modules. This fits a DIFFERENT issue within Configure ledgers and currencies: Finance closed a fiscal period but a journal can still post there because its ledger period status allows entry. It does not address the current problem, whose mechanism is: Exchange rate types identify different rate series; a valid rate in the wrong series produces incorrect translation.

Use the appropriate controlled correction or revaluation procedure rather than assume a rate maintenance edit rewrites posted vouchers. This fits a DIFFERENT issue within Configure ledgers and currencies: A finance analyst changes today's market rate but a previously posted voucher is expected to automatically recalculate historical accounting values. It does not address the current problem, whose mechanism is: Exchange rate types identify different rate series; a valid rate in the wrong series produces incorrect translation.

The allocation journal debits destination cost centers and credits the source using the approved proportion. That would verify a different case: The finance team needs to distribute facilities expense across departments monthly but posts manual lines using outdated allocation percentages. It does not verify the required corrective action: Review the configured exchange rate type and rate records used by the approved revaluation process.

A controlled revaluation posts gains and losses to the expected accounts and reconciles the source balances. That would verify a different case: The year-end currency conversion leaves a residual balance in the wrong gain/loss account. It does not verify the required corrective action: Review the configured exchange rate type and rate records used by the approved revaluation process.

Unauthorized historical-period posting is blocked while an open test period accepts the journal. That would verify a different case: Finance closed a fiscal period but a journal can still post there because its ledger period status allows entry. It does not verify the required corrective action: Review the configured exchange rate type and rate records used by the approved revaluation process.