Exam Bundle

Run a recurring invoice population reconciliation each month. That safeguard is aimed at a different risk: A regular vendor bills a fixed facilities fee monthly, but invoice staff enter it manually and miss a period. It does not most directly prevent recurrence of: Payment proposals use configured invoice eligibility and due-date selection criteria.

Reconcile due-to and due-from accounts after centralized payment batches. That safeguard is aimed at a different risk: Central finance pays invoices for subsidiary companies, but the central payment journal does not create intercompany due-to/due-from balances. It does not most directly prevent recurrence of: Payment proposals use configured invoice eligibility and due-date selection criteria.

Include discount opportunities and liquidity constraints in payment-run review. That safeguard is aimed at a different risk: A supplier offers a cash discount if paid within ten days, but AP payment proposal ignores discount dates and pays full amount on day eight. It does not most directly prevent recurrence of: Payment proposals use configured invoice eligibility and due-date selection criteria.

Configure fixed asset defaults and source transaction mappings for each approved acquisition path. This fits a DIFFERENT issue within Implement and manage fixed assets: A company acquires assets using both projects and purchase orders, but some transactions post to unmatched asset groups because default asset fields are missing. It does not address the current problem, whose mechanism is: Depreciable amount depends on acquisition basis and residual value as configured in the book.

Review asset ownership and apply the supported cross-company transfer/acquisition correction process instead of a display-name change. This fits a DIFFERENT issue within Implement and manage fixed assets: An asset was created in the wrong legal entity and finance plans to fix the reporting by editing its name only. It does not address the current problem, whose mechanism is: Depreciable amount depends on acquisition basis and residual value as configured in the book.

Configure fixed asset posting profiles for acquisition and relevant asset group/book transactions. This fits a DIFFERENT issue within Implement and manage fixed assets: A newly acquired vehicle posts acquisition cost to an expense account instead of fixed asset cost because posting profiles are incomplete. It does not address the current problem, whose mechanism is: Depreciable amount depends on acquisition basis and residual value as configured in the book.

Both project and purchase order test acquisitions create the correct asset/book accounting outcomes. That would verify a different case: A company acquires assets using both projects and purchase orders, but some transactions post to unmatched asset groups because default asset fields are missing. It does not verify the required corrective action: Configure valid salvage/residual value and depreciation basis according to approved asset policy.

New machines receive unique asset numbers traceable within the owning company. That would verify a different case: A newly acquired production machine is assigned the wrong fixed asset number sequence and duplicates an existing identifier in a subsidiary. It does not verify the required corrective action: Configure valid salvage/residual value and depreciation basis according to approved asset policy.

New vehicles use an eight-year life while existing asset accounting is assessed separately. That would verify a different case: A capitalized service vehicle has a ten-year useful life on one book but the policy changed to eight for new acquisitions. It does not verify the required corrective action: Configure valid salvage/residual value and depreciation basis according to approved asset policy.

Depreciation profiles define calculation methods independently of the acquisition amount. That explains a separate case: Financial statements require straight-line depreciation but a fixed asset book uses reducing-balance method. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Depreciation start conventions determine which portion of an accounting period qualifies for expense. That explains a separate case: Fixed asset books have the correct depreciation method but no depreciation start convention, producing inconsistent first-month charges. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Accounting recognition and depreciation start are separate dates influenced by book settings. That explains a separate case: An asset is acquired but depreciation is scheduled from the purchase order date instead of the date it became available for use. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

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: Depreciable amount depends on acquisition basis and residual value as configured in the book.

Audit active asset coverage across all required books. That safeguard is aimed at a different risk: A fixed asset depreciates under one book but not under a required second book because the second book is not associated with the asset. It does not most directly prevent recurrence of: Depreciable amount depends on acquisition basis and residual value as configured in the book.

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: Depreciable amount depends on acquisition basis and residual value as configured in the book.

Use the supported fixed asset split transaction allocating original acquisition cost and accumulated depreciation appropriately. This fits a DIFFERENT issue within Process fixed asset transactions: A company separates a combined machine into two components with different useful lives, but accounting only changes the asset description. It does not address the current problem, whose mechanism is: Company and book selection determine the scope of multi-company depreciation runs.

Run depreciation with the correct book, asset status and processing date eligibility filters. This fits a DIFFERENT issue within Process fixed asset transactions: A fixed asset's monthly depreciation batch accidentally includes disposed assets. It does not address the current problem, whose mechanism is: Company and book selection determine the scope of multi-company depreciation runs.

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: Company and book selection determine the scope of multi-company depreciation runs.

Asset cost increases by the improvement and subsequent depreciation adjusts according to book policy. That would verify a different case: 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 verify the required corrective action: Review and configure the appropriate multi-company depreciation processing selection.

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: Review and configure the appropriate multi-company depreciation processing selection.

The asset's book transactions and GL balances reconcile after a controlled correction. That would verify a different case: An asset has a depreciation adjustment after an approved useful-life change, but finance manually edits accumulated depreciation account balances. It does not verify the required corrective action: Review and configure the appropriate multi-company depreciation processing selection.

An asset sale must derecognize the asset carrying amount in addition to recording customer proceeds. That explains a separate case: A company disposes of an old computer for cash, but books the sale through a free text invoice without closing its net book value. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Retirement timing determines when depreciation and book transactions cease. That explains a separate case: A fixed asset group includes a machine that was retired, but the depreciation run generates a charge in a period after retirement. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Asset book history is an accounting subledger that should remain aligned with posted depreciation journals. That explains a separate case: An asset has a depreciation adjustment after an approved useful-life change, but finance manually edits accumulated depreciation account balances. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Cross-check existing asset acquisition transactions before posting a new source. That safeguard is aimed at a different risk: A finance clerk manually records an asset acquisition and a later PO invoice posts the same cost again. It does not most directly prevent recurrence of: Company and book selection determine the scope of multi-company depreciation runs.

Reconcile fixed asset subledger balances to the general ledger after adjustments. That safeguard is aimed at a different risk: An asset has a depreciation adjustment after an approved useful-life change, but finance manually edits accumulated depreciation account balances. It does not most directly prevent recurrence of: Company and book selection determine the scope of multi-company depreciation runs.

Reconcile intercompany asset transfers before consolidation. That safeguard is aimed at a different risk: An asset is transferred between two companies, but one company posts the disposal while the other fails to recognize the corresponding acquisition. It does not most directly prevent recurrence of: Company and book selection determine the scope of multi-company depreciation runs.

Add CostCenter to the applicable ledger account structure and require an allowed dimension combination for the expense account range. This fits a DIFFERENT issue within Design and configure the chart of accounts and financial dimensions: Purchase expenses need a mandatory CostCenter on posting, but users can save journal lines without one. It does not address the current problem, whose mechanism is: Activating a financial dimension alone does not automatically require it for ledger account combinations.

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: Activating a financial dimension alone does not automatically require it for ledger account combinations.

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: Activating a financial dimension alone does not automatically require it for ledger account combinations.

Transactions using a mapped cost center derive the correct department and exception values are reviewed. That would verify a different case: A company requires a Department dimension to derive from CostCenter for known responsibility centers, but staff manually pick inconsistent departments. It does not verify the required corrective action: Review the dimension activation and attach it to the relevant approved account structure, then activate the structure as required.

Sample journal entry applies the expected default dimension combination and validation remains enforced. That would verify a different case: A finance team enters many identical financial dimension combinations across budget journals, causing frequent transcription errors. It does not verify the required corrective action: Review the dimension activation and attach it to the relevant approved account structure, then activate the structure as required.

An invalid Department and CostCenter pairing fails validation while approved combinations post. That would verify a different case: Account structures for a shared chart allow every Department with every CostCenter, creating invalid combinations in posted expenses. It does not verify the required corrective action: Review the dimension activation and attach it to the relevant approved account structure, then activate the structure as required.