Cash Management

Cash Ledger Transactions

A Cash Ledger Transaction that is created from the csv statement line now uses new Transaction Date field as the Transaction Date instead of the statement date.

Program/Business class/Process affected:

• BankStatementLine

Use these steps to test the enhancement:

1. Using a transaction date that is different from a statement date, import a CSV bank statement that will create a CashLedgerTransaction and CashLedgerGLDistribution. Alternatively, you can manually create a bank statement.
2. Verify that the CashLedgerTransaction Issue Date equals the transaction date.
3. Verify that the posting date on the CashLedgerTransaction and CashLedgerGLDistribution equals the transaction date.

JT-1501038

Infor Treasury File is populating Swift values in a field mapped to routing numbers in kyriba

You can now exclude the Bank Entity value from the Infor Treasury output file when the bank entity is using a non-routing number.

Program/Business class/Process affected:

• BankEntity
• ElectronicPaymentCreation_ElectronicPaymentCreation
• CBEE70PD
• CBEE70WS
• 11.0_post_CU80.faf

Use these steps to test the enhancement:

A new Exclude Entity Value From Payment File flag is added to external bank entity, which must be used when the bank entity is using a non-routing number such as a Swift number or IBAN. When that field is toggled on, the bank entity value/intermediary bank entity value is excluded from the Infor Treasury payment output file.

1. Sign in as Payables Manager and select Manage Vendors.
2. Pick a vendor to test with and on the Banking tab, verify that the Exclude Entity Value From Payment File is flagged on the Bank Entity.
3. Pick another vendor to test with and on the Banking tab, verify that the Exclude Entity Value From Payment File on the Bank Entity is not flagged.
4. Pick a Bank Transaction Code to test with and verify the Payment Output Option is set to Electronic File.
5. Verify that the Cash Payment Format Payment Format is set to Infor Treasury File.
6. Create a couple of invoices for both vendors and complete a payment cycle for the invoices.
7. Open the Payment Output File that is created for the first vendor and verify the Pay Bank Entity value is not populated, and therefore excluded from the file.
8. Verify for the second vendor that the Pay Bank Entity value is populated, and therefore included in the file.
9. Verify that the bank name and address is populated on both output files.
10. Do the same test above, but this time validate that when the vendor is using an intermediary bank that is flagged to exclude entity value from payment file, that the output file is excluding the Intermediary Bank Entity value. Validate that it is still including the bank entity name and address.

JT-1520688