Enhancements & Revisions


Adagio Payables 9.3B


March 21, 2020


    ·   During conversion to 9.3B, this Error message may have appeared if there were problems with the existing System Check Run: ‘Error adding record to System Checks Header, record already exists’.  Conversion now warns that the data is damaged and continues.  The message is: ‘Your system check file is corrupted and cannot be converted. Please delete your system check run after conversion.’

    ·   The 9.3B conversion warning message: ‘Error finding record with assigned check number, this record will be skipped’ now has an option to: ‘Ignore this error for remainder of conversion’.

    ·   In the initial release of Payables 9.3B (2020.02.17), copying individual batch entries did not correctly create the new entry in new batches. This has been corrected.

    ·   In the initial release of Payables 9.3B (2020.02.17), printing advices for cash invoices and prepayments did not correctly set the decimals for currency amounts. This has been fixed.

    ·   Changing the Bank Code on a System Check Run after the payment list was generated, caused data integrity errors.

    ·   When editing Email Setup, the Wait Between Emails setting was not being read correctly and was being reset to zero. This has been fixed

    ·   Integrity Check was incorrectly reporting an error 'System check sequence x totals do not match details' in some cases where a Vendor had an outstanding Credit Note

    ·   Fixed a problem where, if a vendor had only unmatched invoices and credit notes, the invoice printed on the advice and other reports for the next vendor in a system check run and integrity errors were reported

    ·   When the Style List was restricted to only app specific and generic styles, the style dropdown field did not display the correct font and color. This has been fixed.

    ·   A locking error may have been encountered in batch entry if the Find Vendor function had been used on a Filtered Vendor Lit. This may account for some data integrity errors regarding open invoice batch computed vendor amounts.

    ·   For the Caribbean and Scotiabank, a Scotia CSV Recipient Upload EFT Batch Format has been added to the list of EFT Batch Formats.

    Notes:

    If this Format is being used, you cannot also have an EFT provider that uses the Telpay format. Telpay requires Vendor Address formatting for Canada.

    The Recipient account currency is defined on the EFT Provider. There is also an option to include a memo for each record.

    For the Vendor, on the Accounting tab, the firt 9 characters of the bank ID field are the Routing Number (Designated Bank’s ABA number). The rest of the bank ID is the Branch Transit number (if required) and the Recipient’s account number. If the Bank requires the Account number to have leading zeros, they much be entered in the Bank ID.

    The EFT Bank Account Type is set on the EFT tab.

    ·   Payables 9.3B added restrictions to payments for On hold and Inactive vendors. This has been relaxed.  If a document has a ‘Forced’ status, it will be included in a System Check Run.

    ·   In 9.3B, Prepayments with a ‘Forced’ status were not included in a System Check Run if the Prepayment date was after the Check date.


© Copyright Softrak Systems Inc. All rights reserved.