Cash Management

This section contains enhancements in Financials and Supply Management.

Converting cash transactions with Stale Dated status

Add the Stale Dated status to the Cash Ledger Interface.

Select the new status and the records are automatically stale dated.

  1. Select Cash Ledger Interface and create a record. Select a record with the status of Stale Dated.
  2. Import the records of the corresponding run group.
  3. Verify that the status of the imported record is stale dated, and that distributions are identical to a record that was manually Stale Dated.

JR-3265678

Bank error message enhancement

The error message on the bank statement context page was difficult to read with red text on a blue background.

The error message is now displayed as a tag to provide consistency across error messages.

  1. Sign in as Application Administration and select Financials > Cash Management > Statement Processing > Bank Statements.
  2. Create a bank statement.
  3. Verify that the bank statement is not balanced.
  4. Confirm that new error message is displayed in Posting Status.

JR-3461340

Allow user defined fields in reconciliation match rules

Enhance the Bank Reconciliation Match Rules. User-defined fields can now be defined as variables in the statement line match field and system line match field.

The statement line match field and system line match field on BankReconciliationMatchRule and BankReconciliationTemplate were changed from AlphaUpper to Alpha. Users can now reference user-defined fields.

This syntax is used to reference a user-defined field in the statement line match field or system line match field: {lpl:UserDefinedField}. Related fields can also be referenced as follows: {lpl:CashLedgerTransaction.UserDefinedField}. Note: syntax is case sensitive and field name must be CamelCase.

  1. Verify that a UserDefinedField value on BankStatementReconciliation is substituted correctly when it is defined in the statement line match field or the system line match field {lpl:UserDefinedField}.
  2. Verify that a related UserDefinedField value is substituted properly when defined in the statement line match field or system line match field {lpl:CashLedgerTransaction.UserDefinedField}.
  3. Verify that all existing match rules that are defined in uppercase perform as expected.
  4. Verify that any new rules that are created in upper case or lower case perform as expected.

JR-3485513

Cash code position in the Reconciliation Balance page is updated for the statement date last received

The Reconciliation Balances page, when navigating from Bank Statement, is enhanced. The Cash Code Cash position run for the last day of the period is displayed when it is the last statement for the period and a cash code cash position record does not exist for the statement date.

BankStatement is modified to use the period end date when returning CashCodeCashPosition records when this criteria is met:

  • No cash code cash position records exist for statement date
  • Cash code cash position records exist for period end date
  • Statement is the last statement for the period
  1. Create a bank statement for a date that is earlier than the period ending date.
  2. Select Cash Accountant > Process Cash Ledger > Update Cash Code Cash Position.
  3. View the Current Cash Code Cash Position list on the Reconciliation Balances page.
  4. Verify the correct records are available.
  5. Create a Cash Code Cash Position for statement date.
  6. Verify that the Code Cash Position records for the statement date are returned.

JR-3436773