·    Grids may be “banded” with a User Selectable color and banding frequency set under File | User Preferences. Filter Styles may be disabled and replaced with regular banding if desired.

·    The status bar at the bottom of the main window now shows activity of various steps when the program is starting up and the database is opening.

·    Supports Transport Layer Security (TLS) / Secure Socket Layer (SSL) for secure email servers when emailing receipt documents. Added option 'Use TLS/SSL' added to Email Setup function.

·    The number of Previously Opened databases (saved by user) has been increased from 25 to 100.

·    Updated splash screen with new Adagio logo and colors. Updated icon and toolbar button images.

Batch Entry and Posting

·    For Deposit Only batches, the receipt date was used as the date for GL transactions. The Deposit date is now used. If ‘Consolidate Bank Transactions’ is enabled in the Company Profile, there will be a single distribution to the Bank Account for the Deposit amount and multiple transactions to the offsetting accounts for each receipt. This allows easier reconciliation from Ledger to BankRec.

·    If you edit a Deposit Only batch and add a new receipt with a date later than the original Deposit Date, the Deposit Date of the batch will be automatically updated to the later date. The Deposit Date is also updated if you edit the date of an existing entry to a later date and if you retrieve and append transactions with later dates to an existing batch. Import Deposits also uses the latest receipt date as the deposit date.

·    For multi-currency databases, foreign currency banks can have a different Rate Type for deposits and payments. The Bank tab in Edit Banks now has Bank/Payment Rate Type and Deposit/Receipt Rate Type fields. Batches retrieved from Receivables, imported batches and batches created in reconciliation for imported bank statements (that cannot be edited to adjust the rate) now use the new Deposit/Receipt Rate Type.

Ledger Interface

·    BankRec 9.2A is fully compatible with the new feature in the Ledger 9.2A Retrieve Subledger Batches function, allowing separation of subledger batches on retrieve by Posting Sequence or Batch Number. For earlier versions of BankRec, if the subledger batch contains transactions for reversed checks, checks cleared with error, or NSF Checks, the Retrieval file cannot be separated by Batch.

Receivables and Payables Interfaces

·    For Adagio ePrint users, the Edit/View Vendor and Edit/View Customer functions in BankRec now support viewing PDFs of purchase orders and invoices.

·    If you retrieve receipts from Receivables to a ‘Deposit-Only’ batch, the Deposit Date of the batch will be set to the latest date of any transaction retrieved.

·    Supports new ‘Batch by entry’ option in Payment Methods in future 9.2A version of Receivables when receipts are retrieved (including payments originated in Adagio OrderEntry and Invoices). A new deposit batch is created for each receipt. Use this option to separate payments received by EFT into individual batches in BankRec.

·    Supports new ‘Print BR receipts?’ option on the Invoicing tab in customers added in future 9.2A version of Receivables. This enables the ‘Print Receipt’ option for receipts retrieved from Receivables, transactions entered in BankRec or generated in reconciliation, allowing you to selectively control which customers will have receipts printed in the BankRec batch.

·    Supports new ‘Sort by’ option on the Transactions tab in customers added in future 9.2A version of Receivables. This new option allows you to sort by date when transactions for both current and history are selected for display.

·    The Edit Customers function supports the new option ‘Require PO?’ on the Invoicing tab added for future 9.2A version of Receivables. Used to require you to enter a purchase order number in the PO Number field on the Header tab when entering an invoice in other modules.

Reports

·    Adagio BankRec’s standard reports are now created using Crystal Reports 2013, replacing the Crystal Reports 8.5 Print Engine (CRPE32.dll). The module’s management reports are now stored in \Softrak\BankRec\StandardReports. Revisions to these reports should be placed in \Softrak\BankRec\ModifiedReports. Custom reports to be added to the Reports menu should be stored in \Softrak\BankRec\CustomReports. Reports must be edited or created using Crystal Reports 2011 or 2013 and Adagio ODBC for access to the data files. Users will notice minor changes to some of the visual elements in the module and a new Print Preview window. The size and position of the Print Preview window are now remembered between sessions by user, so the Workstation options controlling this function have been removed. Exporting to an Excel spreadsheet from the print preview window has been significantly improved. Refer to the online Crystal help for details. The Report Tables Drive settings and Crystal tables in the \QRASP folder are not used by version 9.2A modules.

·    An updated version of Adagio PrintTool (PT) is installed in \Softrak\PrintTool. PT allows you to print / preview custom reports without needing to run Crystal Reports itself or without placing the report on the Custom Reports menu in an Adagio module, and allows reports to be placed on the Windows desktop. PrintTool 9.2A prints custom reports created with Crystal Reports 2011 or 2013 only. Adagio ODBC must be installed to create custom reports but is not required to print custom reports. Your Adagio dealer or consultant can create custom reports for you and deploy them at your site. PT allows you to specify a report to print on the command line using the /r parameter. This allows Adagio automation batches to print custom reports (to printer – a future release of PT will allow automation batches to print custom reports to PDF). PT does not require registration with Softrak Systems but does use Adagio Lanpak licenses. Note: PT does not print reports created with Crystal Reports 8.5 for Adagio. Existing version 8.5 custom reports must be converted before they can be printed by 9.2A.

·    New ePrint code %CDT is available to put the Calculate/Aged as of date into either the PDF filename or folder name for reports such as Bank Reconciliation, Bank Transactions and Cash Flow.

·    You can now have a Report Favorite for the Deposit Slip report. This allows you to save the Bank and the printer location. However, as a Bank Reference must be entered when the report is printed, the report cannot be used in a Report Set.

·    The System Status function (chksys.exe) does additional checking of the Crystal Reports runtime and Adagio ODBC drivers used to print reports in Adagio 9.2A.

Problems Fixed

·    BankRec 8.1E (2013.11.27) corrected the message BankRec displayed if you attempted to import a bank reconciliation file in OFX format where a block within the file exceeded a size limit. This happened for some banks that removed CR/LFs from their version of the file. However, this caused a problem with size limits of the file that could be imported. The limit has now been removed and most or all large files can now be imported.

·    BankRec 8.1E (2013.11.27) corrected a problem in earlier releases of 8.1E when Importing Payments where the GL Account and Department, and the Distribution Code could not be imported (were set to blank). The correction did not work in some cases.

·    For checks reversed in BankRec, the G/L distribution details for transactions viewed in the vendor were displayed 100 times larger than actual. This was a display issue only.

·    When using the Validate function within Statement Rules to import a bank statement file, if you used Make Rule for an imported record, the finder was not active on the GL account, Distribution, bank, customer or vendor fields.

·    When entering a GL Account / Department, validation did not work and no warning was given when you entered a Department that did not exist for an Account if that Department did exist for the next highest Account. For example, you had account 8000-150 and the next account in the chart is 8001-250, then entering 8000-250 did not give a warning.

·    If a Payables check was reconciled with a Cleared with Error status using the Completed integration option in the Bank, and you logged into BankRec with a date different than the reconciled statement date, the date of the transaction sent to Ledger from Payables was incorrect. This could result in the date of transactions sent to Ledger by BankRec and Payables being in different periods or fiscal years.

·    Checks cleared with error in BankRec for banks configured with Update Payables Check Reconciliation set to ‘Completed’ caused the Data Integrity Check in Payables to report orphan details in the Transaction GL Details file.

·    Payment and receipt entries in batches created in reconciliation for vendors / customers that are not in the bank currency, used currency information from the bank rather than the vendor / customer and thus were not converted from the bank currency in some cases.

·    Import in header/detail format of receipts for customers not in the bank currency used the wrong rate type if these fields were not contained in the import template.

·    Email codes were not expanding in the email subject.