Enhancements & Revisions

Adagio BankRec 9.2A

June 30, 2015

· The Edit and View Customers/Vendors functions have been updated to the most current functionality in Receivables and Payables 9.2A.

· BankRec 9.2A did not show transactions for Invoices9.2A in the Edit / View Customer functions.

· In the Edit and View Customer functions, when used with future 9.2A version of Receivables, changing the Sort By selection on Transactions tab from Date to Type/Doc No did not sort the grid.

· In Edit Vendor, when used with future 9.2A version of Payables, BankRec gave an error when the vendor was saved if the Invoice Number Format fields contained certain formatting characters.

· In BankRec 9.2A when integrated with Payables 9.2A, if the option to show Active Records Only was set on the Edit Vendors grid, the wrong vendors were displayed.

· When adding a vendor for Payables 9.2A in BankRec 9.2A, the finder on the Tax Group field in PO Options displayed the error ‘There is no data available for this field’.

· Viewing a PDF of an invoice that was created by Adagio PDF and then appended with scanned documents caused the Adagio PDF Viewer to crash in some cases. This has been corrected. However, the Viewer may not show the scanned PDF correctly. This will be corrected in a future release. In the interim, the document can be opened from your default PDF viewer by clicking the lower leftmost button on the Adagio Viewer.

· An error occurred if you had 2 copies of BankRec open with both in the retrieve function.

· If a user retrieved Payables transactions in Adagio BankRec at exactly the same time as another user was posting in Payables, it was possible to for two batches for the same transactions to be created in some cases. This is now prevented providing Payables is 9.2A (2015.06.09).

· A Payment Reversal included as part of a Reconciliation and not posted separately using Post Reversal created Ledger entries for the Reversal entry using the Statement instead of the date option selected for the Reversal (Check date or Login date).

· If the ‘Update Payables Check Reconciliation’ option in a bank is set to ‘Completed’, the Reconciled Checks Posting Journal in Payables showed the session date from BankRec as the reconciliation date instead of using the Statement date for a Cleared with Error transaction.

· The performance of the Bank Reconciliation report has been significantly improved when printed for a large number of transactions across a network and in particular when backdated.

· In BankRec 9.2A, the Bank Transactions report displayed Changed Date of 12/31/1899 if the field was blank.

· In BankRec 9.2A, the Reconciliation Worksheet report printed 12/31/1899 for Last Statement Date if the field was blank.

· In BankRec 9.2A, the Reconciliation Posting Journal displayed an error and did not print if the ‘Print G/L dist summary’ option was not enabled.

· BankRec allowed posting journals to be cleared. This is now prevented until Year End, as in other modules.

· In BankRec 9.2A for multi-currency databases, the Home amounts on the Bank Transactions report printed too small by a factor of 100.

· In BankRec 9.2A, the G/L Transaction report and the G/L Summary on the Batch Listing and Posting Journal were sorted incorrectly if you use G/L Departments, depending on the configuration of your Chart of Accounts.

· In BankRec 9.2A, some reports displayed an error similar to “Cannot open file \\\"\DATA\BRxxnnnnR.DAT\\\". The system cannot find the file specified.” on systems with many Windows users (approximately more than 100).

· Added new specification code for receipts:
C75 City, State/Province, ZIP/Postal (formatted)

· The ‘Print BR Receipts’ option in the customer and the ‘Request Receipt’ (for all customers) option in the Receivables Company Profile were not respected if the ‘Print receipts by default’ option was disabled in the BankRec Company Profile. This was also corrected when importing a deposit batch.

· If the ‘Check for duplicates’ option is enabled, when multiple NSF transactions are to be created where the same check number is used on separate receipts, there is now a warning that there is a duplicate Reference that must be corrected before generating the NSF batch.

· In BankRec 9.2A, if you previewed receipts and then printed them from the preview, there was an Access Violation error.

· In BankRec 9.2A, printing a receipt for a specification file with ‘# of Copies’ set to more than 1 displayed the error “List index out of bounds”.

· A fix made in the BankRec 8.1E (2013.11.27) Hot Fix that corrected problems importing bank reconciliation files in OFX format from certain banks in some cases was not included in BankRec 9.2A.

· BankRec 9.2A installed the Designer help for 8.1E.

· Creating a new database now sets the 'Prompt to consolidate GL' option to disabled.

· The Data Integrity Check (DIC) saves results for the last 9 previous runs in files BRWINERR01…09.dat (where .dat is your company data file extension). The current DIC information will always be in BRWINERR. If you do check/rebuild/check without closing the DIC function the results are appended to the same file.