Reconciliation Matching Rules

Reconciliation Matching rules help you match bank statement lines and system transactions to minimize the need for manual intervention.

Define bank statement automatic reconciliation matching rules and assign them to bank statement automatic reconciliation rule sets. After you assign the rule sets to the bank account, the Autoreconciliation process picks up the reconciliation matching rules to achieve a higher match rate.

Specify the following for each matching rule:

• Transaction Sources: Payables, Receivables, Payroll, Journals, or External.

• Matching Type: One to One, One to Many, Many to One, Many to Many, or Zero Amount. The following table explains the different matching types available in Oracle Fusion Cash Management:

  Matching Type	Description
  One to One	A bank statement line is matched with a system transaction and reconciled against each other
  One to Many	A bank statement line is reconciled against many system transactions
  Many to One	Many bank statement lines are grouped and reconciled against a system transaction
  Many to Many	Many statement lines are grouped and reconciled against many system transactions
  Zero Amount	Zero amount system transactions not reported in bank statements

• Grouping Attributes: Used to group bank statement lines and system transactions based on the matching type you select. The combination of the attributes you select also determine what you can use as the matching criteria. You can use date, transaction type, and reconciliation reference as matching criteria only after you select these as grouping attributes. The following table displays the required grouping attributes for a selected matching type:

  Matching Type	Statement Line Grouping Attributes	System Transaction Grouping Attributes
  One to One	Not applicable	Not applicable
  One to Many	Not applicable	Grouping attributes required
  Many to One	Grouping attributes required	Not applicable
  Many to Many	Grouping attributes required	Grouping attributes required
  Zero Amount	Not applicable	Not applicable

  Note:

  • During automatic reconciliation of zero amount system transactions, the transactions are grouped by transaction date and transaction source selected in the reconciliation matching rule.
  • The zero amount system transaction date is used as cleared date of the reconciliation group.

  In Many to One matching, the grouping attributes are used to group bank statement lines. In One to Many matching, the grouping attributes are used to group system transactions.

  The following is a list of common grouping attributes that can be used to group bank statement lines:

  • Transaction date

  • Structured payment reference

  • Transaction currency

  • Transaction type

  • Reconciliation reference

  • Bank transaction code

  • Transaction code identifier

  • Counterparty bank account

  • Value date

  • Value date in string format

  The following is a list of common grouping attributes that can be used to group system transactions:

  • Bank deposit number

  • Transaction date

  • Business unit

  • Counterparty bank account

  • Counterparty name

  • Journal batch name

  • Journal line description

  • Journal name

  • Payment file identifier

  • Payment process request name

  • Payment instruction identifier

  • Payment server order number

  • Logical group number

  • Payment method

  • Structured payment reference

  • Receipt batch number

  • Receipt class

  • Reconciliation match date

  • Reconciliation reference

  • Remittance batch number

  • Unique remittance identifier

  • Transaction currency

  • Transaction Type

  • Transaction source

• Matching Criteria: Includes a list of commonly used matching attributes. You can simply select the attributes to include them in the matching rule you selected. The selected attributes define the matching conditions between the bank statement lines and the system transactions to be matched successfully when they're reconciled.

  Note:

  On the Create Reconciliation Matching Rule page, the delivered setting for the matching type is One to One, and the check boxes for Reconciliation Reference, Date and Transaction Type are enabled. When you change the matching type to One to Many, Many to One, or Many to Many, the check boxes are disabled.

  The matching criteria attributes are:

  • Amount

  • Date

  • Reconciliation reference

  • Transaction type

• Advanced Matching Criteria: Enables you to specify additional matching logic or filtering conditions that must be true for the bank statement lines and system transactions to match successfully. Consider the following:

  • You have the option to enable or disable the Case Sensitive Comparison check box while creating a condition.

  • The data types on either side of the expressions, must be the same and correspond to each other when selected to match in the criteria. For example, if the attribute Statement Booking Date is selected on one side, then Transaction Date can be selected as the matching criteria. Date is the data type that's the same and corresponds to your search.

  • For literal expression type, the operand value should match the database value. For example: Statement.Transaction Type equals ACH

  The list of statement attributes available in the Create Condition page differs according to the matching type you select. The following lists some of the common statement attributes:

  • Statement.Account servicer reference

  • Statement.Additional entry information

  • Statement.Booking date

  • Statement.Check number

  • Statement.Clearing system reference

  • Statement.Contract ID

  • Statement.Counterparty bank account

  • Statement.Customer reference

  • Statement.End to End ID

  • Statement.Instruction ID

  • Statement.Reconciliation match amount

  • Statement.Reconciliation reference

  • Statement Structured Payment reference

  • Statement.Transaction ID

  • Statement.Transaction currency

  • Statement.Transaction type

  • Statement.Value date

  • Statement.Value date in string format

  The list of transaction attributes available in the Create Condition page differs according to the matching type you select. The following lists some of the common transaction attributes:

  • Transaction.Bank Deposit Number

  • Transaction.Business Unit Identifier

  • Transaction.Counterparty Bank Account Identifier

  • Transaction.Counterparty Name

  • Transaction.Counterparty Site

  • Transaction.Journal Batch Name

  • Transaction.Journal Line Description

  • Transaction.Journal Line Number

  • Transaction.Journal Name

  • Transaction.Logical Group Number

  • Transaction Payment Process Request Name

  • Transaction Payment Server Order Number

  • Transaction Payment File Identifier

  • Transaction Payment Instruction Identifier

  • Transaction Payment or Receipt Method

  • Transaction.Payment Reference

  • Transaction.Receipt Batch Number

  • Transaction.Receipt Class

  • Transaction.Reconciliation Match Amount

  • Transaction.Reconciliation Match Date

  • Transaction.Reconciliation Reference

  • Transaction.Remittance Batch Number

  • Transaction Structured Payment Reference

  • Transaction.Status

  • Transaction.Transaction Currency

  • Transaction.Transaction Date

  • Transaction.Transaction Number

  • Transaction.Transaction Source

  • Transaction.Transaction Type

  • Transaction.Unique Remittance Identifier

You can select one or multiple transaction sources in a rule. Consider the following:

• If multiple sources are selected in a one to one or many to one matching rule, the autoreconciliation program looks for a matching transaction across the selected sources.

• If multiple sources are selected in a one to many or many to many matching rule, the program first finds all available transactions across the selected sources and then applies grouping rule to the whole data pool. This means that the statement lines can be reconciled to a group that includes transactions across the different sources.

• If you want transactions included in a group to be from the same transaction source then you can specify Transaction Source as a grouping attribute.

  Note:

  • Cash Management supports the journal reconciliation reference import using spreadsheet-based tools such as, file-based data import and the Oracle Fusion ADF Desktop Integration.
  • Once the required setups are completed the reconciliation reference is uploaded and stored to the journal lines.