1Z0-1087-26 Practice Questions

In Oracle Account Reconciliation, Group Reconciliations allow a parent reconciliation to aggregate and manage multiple individual child reconciliations. To utilize group reconciliation functionality for a profile, the underlying format used by that profile must have the "Allow Group Reconciliation" option explicitly enabled within its format properties.

B: Data Management can be used to import balance data for group reconciliations as well as individual reconciliations.

D: Sub-segment balance details are viewed within the reconciliation balance summary and child reconciliations, not a specific "Group Detail" tab.

E: Importing pre-mapped data is a general balance import capability across periods, not a defining characteristic unique to group reconciliations.

1. Oracle Fusion Cloud EPM

Administering Account Reconciliation

"Creating Group Reconciliations"

2. Oracle Fusion Cloud EPM

Administering Account Reconciliation

"Defining Formats: Allow Group Reconciliation"

Configuring journals in Transaction Matching involves establishing how adjustments and unmatched transactions generate journal entries. This configuration sequence specifically requires creating journal columns, mapping those journal columns to data source attribute columns, and creating journal templates to format the output entries. Defining data source filters is part of configuring data sources and match processes, not the journal configuration process itself.

A. Creating journal columns is a required initial step to define the schema and attributes of the output journal entries.

B. Mapping journal columns to data source attributes is a necessary step to populate journal entry fields with transaction data.

D. Creating journal templates is a mandatory step that defines the layout and rules for generating journal entries.

- Oracle Fusion Cloud EPM

Setting Up and Administering Account Reconciliation

Section: "Configuring Journals in Transaction Matching"

Oracle Help Center.

- Oracle Financial Consolidation and Close / Account Reconciliation Cloud Service Documentation

Chapter: "Exporting Adjustments or Transactions as Journals".

In Oracle Account Reconciliation Transaction Matching, the Auto-Match engine can be executed immediately after transactions are loaded into the reconciliation data sources. The matching process operates independently of reconciliation workflow statuses (such as "Open With Preparer"), period end dates, or scheduled start dates, allowing continuous or daily transaction matching as soon as data becomes available.

B: Auto-matching does not require waiting for period end; transactions can be loaded and matched continuously throughout the accounting period.

C: Auto-matching can run on loaded transaction data regardless of whether the reconciliation profile or instance has reached its scheduled start date.

D: Auto-matching is an automated processing engine for data sources and does not depend on the workflow status changing to Open With Preparer.

1. Oracle EPM Cloud Documentation

Administering Account Reconciliation

Section: "Transaction Matching"

Subsection: "Running Auto Match Engine". Document ID: E93805-04.

2. Oracle Cloud EPM Services Guide

Reconciliation Compliance and Transaction Matching Configuration

Chapter 8: Managing Data Sources and Auto-Match Rules.

In Oracle Account Reconciliation, administrators and authorized users can continue to add or edit user-defined attributes on formats and profiles even after reconciliations have been created for a period. Changes dynamically update across existing periods or future reconciliations. Therefore, statement D is false.

A. This is a true statement; access permissions (such as Read, Write, or Do Not Display) can be assigned to attributes based on user roles.

B. This is a true statement; user-defined attributes support scripted or calculated values using built-in functions and expressions.

C. This is a true statement; static or calculated default values can be defined for user-defined attributes during configuration.

1. Oracle Fusion Cloud EPM

Administering Account Reconciliation

Section: "Configuring Features" -> "Defining Attributes".

2. Oracle Help Center

Administering Account Reconciliation

Section: "Creating Formats" -> "Adding Attributes".

In Oracle Account Reconciliation, the Account Analysis reconciliation method is specifically designed for balance sheet accounts where the current GL balance is explained by listing individual open sub-ledger items or balance components (such as a schedule of prepaid insurance policies). Because prepaid insurance requires maintaining a detailed breakdown of items that sum to equal the current GL balance, Account Analysis is the most appropriate reconciliation method.

A. Balance Comparison is used to compare balances between two separate source systems (e.g., General Ledger vs. Subledger), not to detail explaining items.

B. Transaction Matching is designed for high-volume detail matching between two data sources (such as bank reconciliations), not period-end explanatory schedules.

C. Variance Analysis is used to explain changes in balances across periods (e.g., quarter-over-quarter flux), rather than explaining the current balance composition.

1. Oracle Fusion Cloud Enterprise Performance Management

Administering Account Reconciliation

Section: "Overview of Reconciliation Methods"

Oracle Help Center.

2. Oracle Cloud Enterprise Performance Management

Reconciliation Compliance Concepts

Chapter 2: "Selecting Reconciliation Methods".

When a period status is changed to Closed in Oracle Account Reconciliation, workflow actions for preparers are locked. Preparers are explicitly prevented from submitting reconciliations with Open status during a Closed period. However, reviewers can still approve reconciliations that were submitted prior to closing the period.

B. This statement is true because reviewers retain permission to review and approve reconciliations submitted before period closure.

C. This statement is true because system execution and balance updates can trigger pending reconciliations to start.

D. This statement is true because administrators can perform authorized data loads into a closed period if required.

- Oracle Fusion Cloud EPM

Administering Account Reconciliation

Section: "Managing Periods"

Subsection: "Period Statuses".

- Oracle Fusion Cloud EPM

Reconciling Accounts with Account Reconciliation

Section: "Understanding Reconciliation Workflow Statuses".

In Oracle Account Reconciliation, preparers can carry forward explanatory transactions and their associated attachments from the previous period into the active reconciliation. On the Balance Explanations tab of the current period reconciliation, selecting 'Copy Transactions from Prior Reconciliation' automatically copies prior period transactions and attachments into the current period.

B. 'Include Prior Period Transactions' is not a valid profile setting for bringing forward explanatory items and attachments.

C. Reconciliations cannot be copied and pasted between periods directly within the Reconciliations list interface.

D. Exporting and importing transactions manually is inefficient and fails to carry over file attachments directly attached to transactions.

Oracle Help Center: Reconciling Accounts with Oracle Account Reconciliation

"Working with Balance Explanations

" Section: Copying Prior Period Transactions.

Oracle Cloud Documentation: Reconciling Accounts User Guide

"Managing Reconciliation Explanations and Attachments."

When a preparer needs to hand off reconciliations they currently own (open with them), they use the Request Reassignment action from the Actions menu. This sends a reassignment request that transfers responsibility for the selected reconciliations to another user (the backup preparer). This is the workflow-driven mechanism for a preparer to reassign responsibility for reconciliations that are actively assigned to them, which is exactly the vacation-coverage scenario described.

A. The Backup Preparer field is configured by administrators/power users in profiles/formats, not by the preparer within an individual reconciliation's Workflow tab as a self-service handoff.

B. Oracle Account Reconciliation does not use an "Out of Office" status in User Preferences to transfer reconciliation ownership.

D. "Release" applies to claimed/locked items or shared workflow claiming; it does not reassign responsibility to a specific backup preparer.

1. Oracle Fusion Cloud EPM — Administering Account Reconciliation

Chapter "Managing Reconciliations

" section "Reassigning Preparers or Reviewers / Requesting Reassignment" (Oracle Documentation

part number applicable to current release; Actions menu → Request Reassignment).

2. Oracle Fusion Cloud EPM — Using Account Reconciliation (Reconciliation Compliance)

section "Performing Actions on Reconciliations" — describes Actions menu options available to preparers including Request Reassignment.

3. Oracle Fusion Cloud EPM — Administering Account Reconciliation

section "Creating Profiles" / "Assigning Preparers and Reviewers" — describes Backup Preparer assignment as an administrative/profile-level configuration (relevant to why A is incorrect).

Verification note: I want to be transparent — I could not retrieve the exact current page/section numbers from Oracle's official documentation to cite with the precision your format requires

and I should not fabricate specific page numbers or DOIs. The answer (C

Request Reassignment) reflects the documented Oracle Account Reconciliation workflow behavior

but I recommend confirming against the live Administering Account Reconciliation guide on Oracle Help Center (docs.oracle.com) for your specific release before relying on it for exam preparation.

To configure security access and permissions for Power Users regarding profiles in Oracle Account Reconciliation, administrators must navigate through the system configuration settings. The standard navigation path is to open the Application card from the Home page, select Configuration, and then click on System Settings, where Power User security rules and profile access options are maintained.

B. Power User profile access configuration is located under Application Configuration, not under Tools Access Control.

C. Profile Segments is used for configuring segment account structures, not for managing Power User security settings.

D. Navigating directly to Application > Profiles allows managing profile instances, not global Power User security rules.

- Oracle Fusion Cloud EPM

Setting Up and Administering Account Reconciliation

"Configuring System Settings"

Section: Power User Security.

- Oracle EPM Cloud Documentation

"Administering Profile Security and Access Settings"

Chapter 3.