Reporting in Oracle Account Reconciliation

Reconciliations prove that your balances are right. Reporting is how you show that to controllers, auditors and the close team. Oracle EPM Cloud Account Reconciliation (ARCS) brings together predefined reports, custom BI Publisher reports, audit binders, dashboards and automation through EPM Automate and REST.

This practitioner's guide explains where each option fits, how to build a custom report and how to make reporting part of your close process. It also looks at what to do when you need faster, ad-hoc analysis.

Where reporting lives in Account Reconciliation

There are two main places to work:

Both Reconciliation Compliance (RC) and Transaction Matching (TM) use this reporting framework. Service Administrators can create custom reports by default. Other users need the Reconciliation Manage Reports application role. See Oracle's custom reporting guide.

Start with the predefined reports

Before building anything, check the reports Oracle provides. Open a predefined report to inspect its query and parameters. Copying a working query is usually the fastest way to start a custom report, especially when it already includes the security logic you need.

Reconciliation Compliance

Predefined RC reports are available in both sample and new applications. The Reconciliation Manager group covers core operational reporting, including Reconciliation Result, which separates the Source System Balance into reconciled, reconciled-with-adjustments and unreconciled amounts.

The sample application also includes these report groups:

The compliance reports are particularly useful at period end. Aging violations and large unexplained differences are the kinds of exceptions I would review before assembling an audit pack. Oracle lists the available content in predefined Reconciliation Compliance reports.

Transaction Matching

The predefined TM reports cover both operations and configuration:

• Reconciliation Configuration: reconciliations with their match type, preparer and description.
• Match Type Configuration, data source and rule configuration reports: useful for design documentation and change control.
• Match Metrics: counts of unmatched transactions, supported transactions and open adjustments by reconciliation, across sources.
• Supported Transactions and Closed/Open Adjustments: detail for investigating supported items and adjustment activity.

Build a custom report in four steps

When predefined reports do not answer the question, build a custom report around a query and an RTF template. Oracle's process has four parts: create the query, create the template, create a report group and create the report definition.

Step 1 — Create the query

Go to Application > Report Configuration > Queries > Actions > New. There are two query types:

• Report Query selects the records that appear in the report.
• Parameter Query supplies a list of values for a parameter, such as periods or account types.

Write SQL against the documented Account Reconciliation tables and views, use Generate Query to build it from attributes and filters, or duplicate an existing query and edit it. Many predefined queries already apply security. Preserve and test that logic so each user sees only the records they are allowed to access.

OCI Gen 2 environments can also generate an execution plan to help investigate query performance. When the query works, select Generate Sample XML to create the file that feeds the template. See Creating a Query.

Step 2 — Design the RTF template

Templates are created in Microsoft Word with Oracle BI Publisher Desktop installed:

1. Open the BI Publisher tab in Word and load your Sample XML.
2. Use Insert > Table Wizard to select fields, grouping and sorting.
3. Save the template as an .rtf file.

Add conditional formatting, subtotals and branded headers as needed. Oracle's template creation guide walks through the setup.

Step 3 — Create the report group

A report group organizes reports for users. Names such as Audit Pack, Close Status or TM Operations make their purpose clear.

Choose stable names: EPM Automate and REST calls identify reports by group name and report name. Renaming either means updating the scripts that call them.

Step 4 — Publish the report definition

In New Report, enter the report name, query, template and group. Set Display to User, select an output format, then use the Access tab to grant access by application module and role. Publishing a definition without the appropriate access does not make it available to other users. See Creating a Report Definition.

The reporting framework supports XLSX, HTML, PDF, CSV and CSV (Formatted). Choose the format for the task:

For large result sets, formatted output is slower than plain CSV. I use CSV while validating the data, then add the presentation layer once the query is right.

Test the query before polishing the layout

Two techniques from Oracle's testing best practices make iteration easier:

• Use an empty RTF template with CSV output while developing the query. This lets you test SQL before investing in layout.
• Work in two browser sessions: keep Report Configuration open in one and Reports in the other, so you can edit and rerun without repeatedly switching menus.

Check object IDs after migration

If you migrate custom reports between environments yourself, internal object IDs can change and query definitions may need updating in the target. Oracle-managed migrations preserve those IDs. Include a report validation step in your cutover runbook. Oracle describes this behavior in the custom reporting guide.

Use report binders for audit evidence

Report binders create a printable, offline copy of reconciliations in a single ZIP. They are useful when auditors need the evidence behind a balance, including workflow, comments and supporting documents. See About Report Binders.

You can generate a binder from three places:

Options include Include Alerts, Include Attachments and Include Transaction Detail. The ZIP contains:

• A Report Summary with hyperlinks to each reconciliation.
• A detail file for each reconciliation, with balance summary, warnings, workflow, history, questions, comments and attachments, much like the Reconciliation Actions dialog.
• Attachment folders, when attachments are included.

If Balance Report Summary or Balance Report Transactions reports were previously generated and attached to a reconciliation, the binder includes them too.

Use dashboards and list views during the close

Formal reports are one part of the reporting picture. Dashboards and configurable list views help the close team monitor reconciliation status, late and rejected items, and unexplained differences, with drill-down to individual reconciliations.

Saved filters in the Reconciliations list and Worklist also help define the scope of report binders. My usual split is:

Schedule and automate report delivery

EPM Automate

Account Reconciliation has dedicated commands for reporting: runComplianceReport for Reconciliation Compliance and runMatchingReport for Transaction Matching. Generate the report, then download the resulting file.

epmautomate runMatchingReport "MatchTypes.html" "Transaction Matching" "Match Type Configuration" HTML "status=Approved"
epmautomate downloadFile "MatchTypes.html"

The runMatchingReport command supports PDF, HTML, XLSX, CSV and CSV2. HTML does not support graphs and charts, and XLSX does not support graphs. CSV2 is formatted CSV and takes longer to generate than CSV.

A report on the server with the same file name is overwritten. Add a date stamp to output names when you need to retain each run.

A close-day workflow might load balances and TM transactions, run runAutoMatch, generate Match Metrics, generate Aging Violations, then download or copy the outputs to object storage. Adapt the sequence to your application's dependencies and check each job's result before starting the next. See Oracle's Account Reconciliation command reference.

REST API

The report-generation endpoint is:

POST /arm/rest/fcmapi/{api_version}/report

It can generate predefined RC reports, predefined TM reports and custom reports. The key fields include:

Example request body:

{
  "groupName": "Reconciliation Manager",
  "reportName": "Balance by Account Type",
  "format": "PDF",
  "module": "RC",
  "runAsync": true
}

Supply any parameters required by the chosen report. Oracle documents the request fields and response in Generate Report for Account Reconciliation.

For a final compliance pack, combine reporting with MONITOR_RECONCILIATIONS. The Monitor Reconciliations job returns status 0 when all reconciliations in the specified period and filter are closed, and -1 when any are still open. Use that result to decide whether downstream delivery should proceed.

Where scheduling runs

The EPM Platform Job Scheduler console is not available for Account Reconciliation customers. Oracle directs customers to schedule EPM Automate or REST calls from outside Account Reconciliation. An enterprise scheduler, OCI-based orchestration, cron or Windows Task Scheduler can run that process. See Oracle's scheduling considerations.

You can also automate Account Reconciliation tasks from another EPM application that supports the EPM Platform Job Scheduler. Configure a remote connection to your Account Reconciliation instance, then create and schedule a pipeline from that application. Contact Newarc if you'd like help setting this up.

Account Reconciliation pipeline job types include Generate Reports. Oracle describes this approach in About Using Data Integration and Data Management.

Upcoming changes and reporting regression checks

Monthly updates can affect extracts, identifiers and downstream scripts. Review upcoming changes before they reach your environment, and keep a regression pack for the reports your close depends on.

Previous changes to keep in your regression pack

These 2025 changes are useful examples of what to include in reporting checks:

The source notes are linked below: February updates, Group Assignment Audit Report changes, match type integration changes and profile validation and subsegment considerations. These are historical changes, rather than a complete list of current functionality.

Read each month's Oracle EPM Cloud readiness documents and check custom queries against Tables and Views for Account Reconciliation when the data model changes. Run key reports in Test before the update reaches Production.

Practical tips from the field

1. Start from a predefined report. Duplicate the query, preserve its security logic and test as the intended users.
2. Use CSV for data and PDF for presentation. A 40-column report belongs in XLSX or HTML rather than on a fixed-width PDF page.
3. Plan report groups for automation. Treat group and report names as dependencies used by scripts.
4. Use parameter queries. Let one report serve multiple periods, account types or regions instead of maintaining copies.
5. Version-control RTF templates and SQL outside the application. Keep a record of what changed and why.
6. Run large REST reports asynchronously. Poll job status and check completion before retrieving output.
7. Scope binders. Use filters and include attachments when the audit request calls for them.
8. Maintain a regression pack. Run the reports that matter to your close after each monthly update in Test.

Beyond native reporting with Data Collage

Native Account Reconciliation reporting is designed for repeatable, governed output. Ad-hoc questions can involve more setup: “Which reconciliations have had unexplained differences three periods in a row?” or “How do TM unmatched counts compare with last quarter?”

To turn an exploratory query into a published native report, you work through the query, Sample XML, template and report definition. That process is useful when the output needs to be reusable, but it adds steps while you are still investigating the question.

At Newarc, we built Data Collage, a desktop data workbench for Windows and macOS, to support this kind of iteration in Oracle Fusion. It runs read-only SELECT/WITH queries through Fusion's BI Publisher reporting layer and includes a SQL editor with bind parameters, a results grid with formula columns, CSV/XLSX/JSON exports and portable .dcanalysis files.

For details about ARCS connectivity, email datacollage@newarcinc.com or visit datacollage.app and mention ARCS. For implementation or ongoing support, talk to Newarc. You can also explore our Account Reconciliation training.

Sources and further reading

1. Generating Custom Reports
2. About Predefined Reports in Reconciliation Compliance
3. About Predefined Reports in Transaction Matching
4. Creating a Query
5. Best Practices for Testing Custom Reports
6. Creating a Template
7. Creating a Report Definition
8. About Report Binders in Reconciliation Compliance
9. Generating Report Binders
10. EPM Automate — Account Reconciliation Commands
11. EPM Automate — runMatchingReport
12. REST — Generate Report for Account Reconciliation
13. REST — Monitor Reconciliations
14. EPM Cloud April 2025 — Important Actions and Considerations
15. Oracle Proactive Support EPM — Account Reconciliation February 2025 Cloud Updates
16. Oracle EPM November 2025 — Updates to Match Types Reflected in Data Integration
17. EPM Cloud September 2025 — Important Actions and Considerations
18. Oracle EPM Cloud Readiness
19. Data Collage
20. About Using Data Integration and Data Management
21. EPM Cloud October 2026 — TM_AUDIT_TRAIL Changes and Other Considerations