Showing posts with label Account Reconciliation. Show all posts
Showing posts with label Account Reconciliation. Show all posts

Saturday, 30 May 2026

Account Reconciliation AI Assistants: Most Awaited feature for Oracle EPM ARCS

 Account Reconciliation Assistants are now available as importable agents that integrate with Fusion AI Studio, enabling a chat-based experience. These assistants are exclusively available to Fusion customers and are not supported for EPM customers without Fusion Cloud subscriptions.

The following assistants are available:

  • Transaction Matching Assistant for Administrators: Helps Service Administrators run jobs like Train Match Prediction, Auto Match, Auto Alert, Archive Matched Transactions, Purge Matched Transactions, and other administrative tasks.
  • Account Reconciliation Assistant for Administrators: Helps Service Administrators runs jobs like load balances, manage periods, run the Train Predicted Matches Predict Attributes jobs, and other administrative tasks.
  • Account Reconciliation Assistant for Users: Helps users interact with reconciliations, performing such tasks as viewing reconciliation details, adding and displaying comments to a reconciliation, submit, approve, or reject a reconciliation, and other tasks.
  • Account Reconciliation Run Report Assistant for Users: Allows users to run Reconciliation Compliance and Transaction Matching related reports.

Business Benefit: 

Account Reconciliation Assistants enhance the user experience by enabling you to quickly find information and perform tasks through natural language interactions. The assistants streamline common operational tasks, thereby increasing productivity and improving operational efficiency.

Steps to enable and configure

  • Ensure that Fusion Applications environment with Fusion AI Studio is enabled
  • Assign the Service Administrator role in Cloud EPM
  • Configure federation between the Fusion Applications and Cloud EPM identity domains
  • Create a confidential application in Cloud EPM IAM (Identity and Access Management)
Thank you!

Tuesday, 7 May 2024

Introduction of new report for Cosmetic changes in Transaction Matching in ARCS

For Transaction Matching profiles that are integrated with Reconciliation Compliance, the Cosmetic Changes Report displays all cosmetic changes for a reconciliation during a specified Period. Cosmetic changes are operational changes made after a reconciliation is submitted and they do not result in the reconciliation being reopened.

What is Cosmetic and Non-Cosmetic Changes

Loading transactions into Transaction Matching may cause period-end reconciliations to be reopened. This happens automatically, without a warning message, since the importing of transactions is, typically, a scheduled job performed after business hours.

The system handles transactions differently based on how they affect the period-end reconciliation. Changes to transactions can be classified into non-cosmetic changes and Cosmetic changes.

Non-Cosmetic Cosmetic Changes to Transactions in Transaction Matching

Non-cosmetic changes automatically reopen period-end reconciliations. If the period is locked, non-cosmetic changes are not allowed.

Following is a list of non-cosmetic changes:

  • Import one or more transactions whose Accounting Date is less than or equal to the Closed Through Date
  • Delete one or more transactions whose Accounting Date is less than or equal to the Closed Through Date

    The deletion can be done from the Unmatched Transactions tab or by searching using the Job Id.

  • Unmatch a match with an adjustment, if the Accounting Date of the adjustment is less than or equal to the Closed Through Date and the Extract Status of the adjustment is Open
  • Match with Adjustment where Accounting Date of the adjustment is less than or equal to the Closed Through Date
  • Delete Support from one or more transactions with Accounting Date is less than or equal to the Closed Through Date. 

    Note: Adding Support is a cosmetic change.
  • Edit transaction Accounting Date or Balancing Amount when Accounting Date is less than or equal to the Closed Through Date

The Closed Through Date is defined as the period-end date for the last Preparer completed reconciliation. For example if the Preparer is working on April 2022, and the most recent previous reconciliation completed is March 2022, then the Closed Through Date is 31-March-2022 (assuming that’s the End Date of the March period).

Cosmetic Changes to Transactions in Transaction Matching

Cosmetic changes automatically update the subtotals on the period-end reconciliation. Because the reconciliation balancing (unexplained difference) is not affected, the reconciliation is not reopened.

Following is a list of cosmetic changes:

  • Match Set created and all transactions have an Accounting Date that is less than or equal to the Closed Through Date

    The cosmetic effect is that the Total Unmatched and/or Unmatched Supported is reduced equally.

  • Match Set is Unmatched and all transactions have an Accounting Date that is less than or equal to the Closed Through Date

    The cosmetic effect is that the Total Unmatched and/or Unmatched Supported is increased equally.

  • Match Set created and some transactions have an Accounting Date that is less than or equal to the Closed Through Date, others have Accounting Date greater than the Closed Through Date

    The cosmetic effect is that, for the affected sources, the total Unmatched and/or Unmatched Supported is reduced, and Matched In-Transit is increased, equally.

  • Adjustment Match Set is Unmatched and Accounting Date of Adjustment is greater than the Closed Through Date

    The cosmetic effect is that, for the affected sources, the total Matched In-Transit is reduced, and the Total Unmatched is increased equally.

  • Unmatch a match with an adjustment, if the Accounting Date of the adjustment is less than or equal to the Closed Through Date and the Extract Status of the adjustment is Closed
  • Support is added to Unmatched Transactions having an Accounting Date that is less than or equal to the Closed Through Date

    The cosmetic effect is that the Total Unmatched is reduced, and Total Unmatched Supported is increased equally.

 To generate the cosmetic changes report:

  1. From the Home page, click Matching, and then select the reconciliation for which you want to generate the cosmetic changes report.
  2. In the Balancing panel of the Overview tab, select the period for which the report must be generated.
  3. Click Actions and select Cosmetic Changes Report.


  4. The Information dialog is displayed containing the Job ID of this report generation job.
                                

5. Click the link in the Information dialog to display the Jobs page.
6. For Job ID, click the Succeeded link to view the generated report.
        

The file name of the generated report is in the format Cosmetic_Changes_Report_ACCOUNT_ID_<JOBID>_<YYYYMMDD_HHMMSS> <SERVICETIMEZONE>.csv.

Business Benefit: This feature enhances usability by providing a single report containing all cosmetic changes made to a particular reconciliation. Auditors can also easily view and track changes made to a reconciliation from the time it was submitted until date.

Thank you!

Saturday, 13 April 2024

Is it possible to integrate non oracle systems to ARCS and get reconciliation done frequently without any manual intervention?

Problem Statement

Is it possible to integrate non oracle systems to ARCS and get reconciliation done frequently without any manual intervention?

ARCS Functionality

Oracle ARCS is a robust and secure solution for managing and automating account reconciliation period end processes, and performing large scale transaction matching, improving efficiency and accuracy of financial processes and statements. With ARCS key capabilities, you can perform tasks such as automate high volume transaction matching and directly integrate with period end reconciliations.

It is a purpose-built solution on the cloud for managing the global reconciliation process.

You can load transactions for past and current period and can perform complex reconciliations across unlimited data sources using unlimited attributes.

Solutions

To load data to ARCS you can use file-based integration. It does not matter what ERP system you are using be it Oracle or Non -Oracle or your non-financial data systems. You can extract data in file in required format and can automate the whole data upload process. There are various ways to load data into Oracle Account Reconciliation.

Methods of Loading Data into Account Reconciliation

There are various ways to load data:

  1. Use the Account Reconciliation user interface to load pre-mapped data.
  2. Importing Transactions directly from Excel using the Smart View Extension for Reconciliation Compliance.
  3. Use the EPM Automate Utility 
  4. Use the Data Management or Data Integration
  5. Use the EPM Integration Agent 
1. Use the Account Reconciliation user interface to load pre-mapped data
 Transactions and balances can be imported using flat files in ARCS. it allows to - 
    • Import pre-mapped balances for both Reconciliation Compliance and Transaction Matching
    • Import pre-mapped transactions for Reconciliation Compliance
    • Import pre-mapped transactions for Transaction Matching
2. Importing Transactions directly from Excel using the Smart View Extension for Reconciliation Compliance
You can use Excel to load transactions into Reconciliation Compliance by using the Smart View Account Reconciliation extension. The direct integration requires the base installation of Smart View plus the Smart View extension for Reconciliation Compliance.

3. Use the EPM Automate Utility 
EPM Automate enables users to remotely perform tasks within ARCS. EPM Automate provides the commands to import pre-mapped balances, import pre-mapped transactions, import balances using Data Management or Data integration, import mapping, import rates and import attributes values.

4. Use the Data Management or Data Integration
ARCS provides the flexibility to import balances and transactions by using Data Management or Data Integration.
    5. Use the EPM Integration Agent 
    Data and Metadata can be extracted from on-premises data source and then load the data directly to the ARCS using the EPM Integration Agent. The EPM Integration Agent executes a query against an on-premises relational database and then loads the data or metadata to the EPM Cloud. The EPM Integration Agent is defined as a data source for an integration. The EPM Integration Agent may also be extended by way of scripting to access other data sources including third-party REST APIs, non-relational sources, or any system or systems that can be accessed using a Jython, Groovy, or Java program.

    Thank you!

    Monday, 25 March 2024

    Transaction Matching module of ARCS: How and When can it help?

    Problem Statement

    What is Transaction matching, why is it required and How ARCS can help?

    ARCS Functionality

    Oracle ARCS is a robust and secure solution for managing and automating account reconciliation period end processes and performing large scale transaction matching; improving efficiency and accuracy of financial processes and statements. With ARCS key capabilities, you can perform tasks such as automate high volume transaction matching and directly integrate with period end reconciliations.

    It is a purpose-built solution on the cloud for managing the global reconciliation process.

    ARCS offers two modules- 

    What is Transaction Matching

    In layman terms Transaction Matching itself indicates matching of transactions between different systems.

    It allows organizations to automate the preparation of high volume, labor- intensive and complex reconciliations. These reconciliations can then be integrated with the tracking features within Reconciliation Compliance.

    The goal of Transaction Matching is to load transactions from one or more data sources, match the transactions using predefined rules in ARCS, identify exceptions and explain the exceptions. Typically, the frequency of preparing reconciliations in Reconciliation Compliance is lesser than or equal to the frequency at which transactions are loaded.

    For example, if balances are compared and reconciliations prepared every month, then transactions can be loaded daily, weekly, or monthly.

    You can also use Transaction Matching for non-balance sheet reconciliations across disparate sources, also referred to as operational reconciliations.

    Examples include system to system reconciliations, inventory/stock or share settlements, expense reimbursements and so on.

    Note

    Transaction Matching functionality is provided with Oracle Enterprise Performance Management Enterprise Cloud Service (EPM Enterprise Cloud Service) only.

    Why you need Transaction Matching in day-to-day business

    When you study your total number of reconciliations, you will find that a small number of reconciliations are the reason for most of the reconciliation work in your organization. This is why Transaction Matching functionality of ARCS is a perfect complement to Reconciliation Compliance.

    ARCS has the tools to make those complex reconciliations simpler and then integrate the period-end results into the Reconciliation Compliance period-end process.

    Benefits of Transaction Matching

    The benefits of using Transaction Matching include the following:

    • Saves the additional time and labor spent on manual preparation of complex reconciliations
    • Reduces risks and improves the quality of the reconciliation process
    • Removes inefficiencies in the process of preparing reconciliations
    • Reduces human errors and speeds up the reconciliation process
    • Reduces time taken for financial close
    • Improves trust and reliability while providing accurate numbers
    • There is no need to make any changes in ERP system for source data extraction as it adapts existing environments
    • Millions of transactions can be matched in minutes
    • It offers competitive advantage as organizations can deploy resources to high value activities such as analytics

    Scenarios for Which Transaction Matching is Beneficial

    • Balance sheet-related reconciliations
      • Suspense and Clearing Accounts
      • Intercompany
      • Cash
      • Credit card receivables
      • Detailed Subledger reconciliation
    • Operational, off-balance sheet, reconciliations
      • System to System reconciliations (which typically involve two third-parties whose accounts must be in sync with each other)
      • Stock or share settlements
      • Expense reimbursements

    Transaction Matching Workflow

    The workflow for using Transaction Matching includes multiple steps that must be performed for each account reconciled. The steps must be repeated each time new data becomes available.

    Transactions can be imported from any source. The import process can be run on demand or scheduled to run automatically.

    The Auto Match process matches transactions according to predefined rules and users need to focus only on the exceptions. Auto Match creates:

    •      Confirmed Matches, where no further action is required
    •      Suggested Matches, where the user can either confirm or discard the match.

    Period-end reconciliation is performed at a frequency that depends on your business requirement.

    Reconciliation Methods for Transaction Matching

    Transaction Matching formats are based on one of the following reconciliation methods:

     Balance comparison with Transaction Matching

     This method is used to compare balances and match transactions between two distinct sources, such as source systems and subsystems.

            For example-

        • Match point of sale system vs a merchant transaction system, or
        • Match the transactions between accounts payable and journal entries within the general ledger.
     Account analysis with Transaction Matching

    This method is used to match transactions within a single data source.

    For example-

    Debit and credit matching. The most common use case is if you are netting off transactions within a single data source to determine the net balance for an account, such as a clearing account.

    Transaction matching only

    This method is used primarily to match transactions between two systems, without a period-end reconciliation.


    Thank you!


    Sunday, 28 May 2023

    Introduction to Account Reconciliation

     Account Reconciliation process gives finance teams confidence that their information is reliable and provide an opportunity to see any discrepancies that happen. In this article, we will talk about Account reconciliation (i.e., What, Why) and tool offered by Oracle EPM Cloud (Oracle Account Reconciliation Cloud Service (ARCS) to help Account reconciliation.






    Thank you!

    Created by - Mohit Jain & Megha Gupta

    Ability to Create and Manage External Users

    Service Administrators can now use the Manage Users tab under Access Control to create, edit, and delete external users (users who are not p...