Customers Using Account Reconciliation

The process to implement an integration to Account Reconciliation, is to first test the import and validation steps in Data Management, and when satisfied with the results, launch the actual integration from within the Account Reconciliation.

The actual loading of the data is executed in the Account Reconciliation. For more information, see Importing Data Using Data Management.

Location security in not available in the Account Reconciliation user interface. Location security is available only in Data Management user interface.

Lock/Unlock POV from the Application page in Data Integration is only available for administrators. In the Data Management user interface, you can lock an individual location from the POV page as non-administrator.

When you are an on-premise Accounts Reconciliation Manager customer moving to Account Reconciliation, note the following in Data Management:

  • Using Account Reconciliation as a source for other than Oracle Enterprise Performance Management Cloud applications is not currently supported with Account Reconciliation.

  • Only numeric data may be loaded to the Account Reconciliation.

  • Drill-through is supported from Account Reconciliation to the drill-through landing page in Data Management. Account Reconciliation can also drill through to the data source in the on-premise Financial Data Quality Management, Enterprise Edition if the data has been first imported to Data Management using the hybrid integration feature. To drill through to the landing page, the Account Reconciliation profile segments must be mapped to the LOOKUP dimension in the Target Dimension Class on the Target Application page.

  • Integrating data from Oracle NetSuite is supported in Account Reconciliation.

  • Integrating data from the Oracle Financials Cloud is supported in Account Reconciliation.

  • When mapping a "Source Type" dimension in the Data Load Mapping option for Account Reconciliation balances, use the Target Value as either the source system or sub-system (subledger). These options are a categorization that define the sources of the data. For example, if you select source system, this option does not necessarily indicate that the source data is from the same source system but does indicate that the data is not from a subledger, such as Accounts Receivable (AR), Accounts Payable (AP), and so on.

  • Any Lookup dimension you add for mapping purposes should be of classification of "LOOKUP." Do not add any dimension of classification "Generic."

  • When mapping to a Reconciliation Account ID within Account Reconciliation, there are considerations for blank target segments. If there are blank segments in between two populated segments in the target reconciliation, Account Reconciliation treats each blank/null segment values in the middle of a Reconciliation Account ID as three blank spaces. Account Reconciliation also trims off the trailing NULL segments after the last populated segment.

    For example, a Grouped Reconciliation with the following Reconciliation ID: "001-null-null-1925 XXX" (the "null" in Account Reconciliation would be non-existent (void of characters) when viewing the Reconciliation/Profile.) The design of Account Reconciliation replaces the "null" at the database tier with three spaces for each blank/null segment in between the populated segments. The Target Mapped Profile in Data Management needs the following: "ACCOUNT ID 001- - -1925 XXX" to align with Account Reconciliation.

  • Account Reconciliation customers, who need to load bank file transaction (which use a BAI or Bank Administration Institute file format or a SWIFT MT940 file format) to the Transaction Matching module in Account Reconciliation, can use Data Management as the integration mechanism. Data Management supports a pre-built adapter for loading:

    • BAI Format Bank File Transactions
    • BAI Format Bank File Balances
    • SWIFT MT940 Format Bank File Transactions
    • SWIFT MT940 Format Bank File Balances

    For more information, see Integrating BAI, SWIFT MT940 or CAMT.053 Format Bank File Transactions and Balances.


    In addition, any other file format that Data Management supports, can also be used to import, map, and load to the Transaction Matching module.
  • As an integration mechanism, Data Management enables Account Reconciliation customers to load Reconciliation Compliance Transactions into Reconciliations. You can pull transactions directly from the Oracle ERP Cloud to the EPM Cloud including:

    • Balance Explanations

    • Source System Adjustments

    • Subsystem Adjustments

    • Variance Explanations

    For more information, see Loading Reconciliation Compliance Transactions.

  • In Transaction Matching, you can export adjustments or transactions as dual sided journal entries that can then be imported into your ERP system. Data Management is used as the mechanism to load the exported journal entries. For more information, see: Loading Exported Journal Entries.

  • Account Reconciliation customers can use up to 64 fields per transaction to load data using Data Management to Transaction Matching.

  • For additional features available to Account Reconciliation users, see the contents of this guide.

For information on loading general ledger and subledger balances in Account Reconciliation from a file using Data Management, see: Overview: Load GL and Subledger Balances from a File using Data Management in Account Reconciliation.