• In Invoice or Adjustment Batch Entry, when the Job number is selected from the Finder or Smartfinder, the Job Related Detail Distribution was not automatically added.

• In Edit Customer, if a statement was printed and transactions were cleared, it caused Data Integrity errors, in some cases.  The Confirmation, ‘Clear all paid transactions in the range specified?’, no longer appears.

• Multiple email addresses separated by semi-colons could not be imported for Customers or Ship to Addresses.

• In Import Invoices, if a Distribution Code was defaulted in the Import Template, it would override the imported G/L Account and Department.

• For Adjustments, the Entry Header Description was not printed on the Posting Journal.

• Receivables has been updated to send additional information to JobCost 9.3A including Doc Link, Accounting Date and Entry Description Line 2.

• For JobCost 93A: Customer Name has been added to the list of fields available to display in the finders/smartfinders for Job, Phase and Category.

• For JobCost, if the Revenue Tracking Level is Phase or Category, the Retainage Due Date will default from the Due Date of the Phase instead of the Due Date of the Job.

• If the Company Profile is set to use “North American Address?, Import Customers and Contacts/ShipTo will validate State/Province. If Country is imported, it will also be validated.

• If 'North American Address?' is selected, the states for Mexico will be normalized to the 2 character state.

• For JobCost, there is a new option in Create Write Off Batch, ‘Exclude JC update?’.  It is remembered by user. If selected, the Job number fields in the Adjustment Batch will be left blank.

• Create Write off batch has been updated for JobCost. When Job Related Credit Transactions are written off and transferred to Payables, the JobCost Billings account is credited instead of the Write off account.  When the Adjustment batch is posted, the Manual Check batch created in Payables will have a “JobCost” detail type instead of “Purchase” if Payables also has integration with JobCost turned on.

Please note:  if the ‘Revenue Recognition Method’ is Job, Receivables will only have the Job field to pass through to Payables. Payables posting will fail unless the Estimate in the Payables entry is properly selected.

• The Country list that will be normalized when 'North American Address?' is selected has been expanded to include more countries.

A new option has been added to the Company Profile, System Options tab to work with ‘North American Address?’: ‘Normalize Country To’. The options are: Full name, 2 character ISO, 3 character ISO and Never. For Import or Edit for Customers or Contacts/Shipto, if the Country is recognized, variations on Country codes are standardized based on this setting.

Eg. For the Default setting: Full name, CA or CAN become Canada.

·          Receivables (2022.11.16) Service Pack caused this Error Message: Internal error creating window class, in some cases. 

·          The issue of unsuccessful conversion to Receivables 9.3B when there are Balance Forward Customers has been resolved.

·          The issue of customer transactions not showing up in the DocStore Viewer for SalesCQ Quotes has been fixed.

·          In the Form Designer, added Blank on Zero (property on amount fields). Corrected a problem where the preview of checks to an Ultra High Resolution screen displayed shrunken in the upper left of the screen. The preview from the Specification Designer was also corrected.

·          New Specification codes have been added: C064, Default Payment Code; C065, Default Payment Code Description; D048, Payment Type Description.

·    The issue of unsuccessful conversion to Receivables 9.3B when there are Balance Forward Customers has been resolved.

·    The issue of customer transactions not showing up in the DocStore Viewer for SalesCQ Quotes has been fixed.

·    In the Form Designer, added Blank on Zero (property on amount fields). Corrected a problem where the preview of checks to an Ultra High Resolution screen displayed shrunken in the upper left of the screen. The preview from the Specification Designer was also corrected.

·    New Specification codes have been added: C064, Default Payment Code; C065, Default Payment Code Description; D048, Payment Type Description.

·    Receivables renders dialogs properly on Ultra High Resolution displays when the font size is anything other than 100% of normal on Windows 8.1 or higher.

·    When a ClickToPay Payment Processor was added with all the necessary information, the Maintenance menu did not show the Retrieve ClickToPay Payments function until the security group was visited or the dataset was reopened.

·    In Receivables 93A with Payments, if Credit Cards were deleted, the Preferred Credit Card was not cleared to blank, in some cases. To update Customers to have a blank Preferred Credit Card, Edit and OK the Customer.

·    In the Specification Designer, the C2P Image button shows when the Adagio Payments add-on has not been installed.

·    There was an Access violation when a new Receivables dataset was created.

·    When Adagio Time and Billing is integrated, the SmartFinder dictionary for customers had an error that caused incorrect results to be displayed.

·    New Customer codes have been added to the Designer: C093 Cell phone, C094 Toll free phone.

CLICK TO PAY

·    Receivables is now integrated with REPAY's ClickToPay. This allows you to place an image on a customer's statement. Your client can select the image to access outstanding invoices and pay them online using a credit card or ACH (for US Customers).

·    For data that is setup with ClickToPay, there is a new feature in the Statement/Letter designer for C2P Images. When you choose C2P Image from the button bar and insert the Image, you can choose the size of the REPAY ClickToPay image in the Specification. The sizes range from: Very Small to Very Large.

EDIT CUSTOMERS

·    A new company profile option 'Tax group verification' will give an error when attempting to save a customer master record with a blank tax group value. This option does not affect the tax group value on ShipTo Address records.

·    Default Project codes can be set for Customers on the Accounting tab. They may also be set for a Shipto address on the Shipto/Alerts tab. Import/Export has also been updated for Customers and Contacts/Shipto.

·    The GL Distribution grid within customer transaction inquiry now supports using the column editor to add, remove or rearrange columns.

·    Customers now have two new phone number fields, Cell phone and Toll free phone.

IMPORT/EXPORT

·    Export Customer Notes now has two new fields available to export, the Customer Name to make it easier to identify who the note belongs to, and a Note Number generated during the export to group note lines together.

·    Import and Export Customers now support the BankRec Receipt Allowed and Preferred Send Methods that were implemented with BankRec 9.3A.

·    Import and Export Customers now have additional fields to support enabling or disabling ClickToPay. 

INQUIRY

·       Customer email addresses are now available for finding customers, either from the customer list or within transaction entry. This includes using the Contact, Ship-to or any email field on the customer. If multiple emails separated by semi-colons are stored in a single email field, then any one can be used for finding the customer.

POSTING

·    When Batch Optional Fields are used, posted cash transactions retrieved into BankRec will maintain these values.

·    Posting payments from either Cash or Invoice batches now allows writing the Payment Type and Online Credit Card ID to the GL Transaction entry description, using new User Defined codes %pyt and %cci, respectively.

SECURITY

·    There is a new option in Security Groups, Options: Set batch ready to post.

The File Backup menu also has a new option for Related data.

Data conversion defaults these options to on.

·    When Adagio Payments is integrated, and user security is configured to allow editing Credit Cards but not editing Customers, the Customer Inquiry screen now has a new Edit CCs button, which allows adding and editing Online credit card numbers, but does not allow editing anything else.

SIGN ON

·    Warning on start-up will now be displayed if the dataset was used with Adagio Payments, but the Addon is not currently found. This is will disable the Adagio Payments features.

MISC

·    A new grid search process is available to use for most grids, accessible from the Control-F keyboard shortcut. Similar to filters, you can restrict displayed rows that meet defined search criteria.

·    Year End is prevented from running with a date prior to the last Period End.

·    Setting the Ready to Post batch status is now being logged in the SDAPPLOG file.

·    If you sign on in a future dated period, there is a Confirm message before you can choose to Run Period End

·    In Edit Styles, it is now possible to limit the list of Adagio Styles to those that are App specific and Generic. Make sure the program prefix is the first 2 characters of Style code description. If this option is selected, when you create a new filter, the Style codes available will be limited to match the application. 

REPORTS

·    Floating Date Ranges have been added to selected reports to simplify Date selection for Report Favourites, Report Sets and Automation.

·    39428 - The Overdue Receivables Report may now be printed for an 'As of Date' that is prior to the last Period End date.

·    The Cash and Invoice posting journal reports now have the payment method printing when one is selected for the entry.

·    Printing reports now is logged in the application log, in addition to accessing the print report screen from the menu.

·    Reports and forms printed to PDF now supports the AdagioV3PDF printer driver. 

AUTOMATION

·    In Automation, the SetSessionDate command has a new noun for: Yesterday.

·    Selecting a Favorite report layout for the Aged Trial Balance report did not properly refresh the SubTotal By label if the primary report was something other than Account Set. The report did print with correct subtotal amounts. Now, the label on the print report screen is correctly displayed.

·    The Cash Batch Listing report in Summary format incorrectly printed an Unapplied label with each entry.  This is now correctly suppressed when the payment amount is fully applied.

·    When Adagio Time and Billing is integrated, the SmartFinder dictionary for customers had an error and caused incorrect results to be displayed.  This has been corrected.

·    When printing a report set directly to the AdagioV3PDF driver, if you choose to cancel printing from the PDF Save As screen for a particular report, you are now prompted to cancel printing just that report ‘’or’ the entire report set.  This choice is written to the report log.

·    When printing Report Sets using either AdagioV2PDF or AdagioV3PDF as the specific printer instead of using PDF Document as the destination, the report log now stores the PDF file name and save location instead of simply ‘Printing to AdagioV3PDF’.

·    Fixed a problem where, in some cases, records were being duplicated on the Overdue Receivables and Projected Receivables reports when Summary was selected.

·    Fixed a problem in the Overdue Receivables, Projected Receivables and Customer Transactions reports where the range selected for File number was not respected.

·    You may choose to select more than one send method when printing receipts and create forms in all selected methods for Print, Email, Fax and PDF when you don’t choose to Match the customer’s Preferred Send Method.

·    Emailing forms using a Direct method that requires TLS/SSL encryption closed a Windows socket that prevented subsequent posting of transactions with online credit card payments using APS Payments.  The error ‘XML request to gateway failed’ was received.  This error no longer happens with this sequence of steps.

·    For APS credit card payments, when ‘Level 3 Processing?’ was set on the Credit Card Processor, an incorrect amount was sent as the ‘Shipping’ Total under Order Information in the APS Vault.

·    If an email address was added to a customer’s existing credit card, the APS Payments Vault was not updated with the new email address.  This did not affect the receipt sent from APS Payments.  It is sent using the email address from the Transaction ID.

·    If posting a batch found an entry with an error and moved it to a new Error batch, the posting sequence value was maintained which could cause confusion if the Error batch was later deleted.  Now the Posting sequence value is blank on Error batches.

·    For Online Credit Card payment transactions captured in an external application, captures were being imported as Pre-Authorizations.  Now, Transaction IDs for captures will cause an import error.

·    Entries retrieved by Subledger period into Ledger were not being retrieved into the proper period.  Posting in Receivables was not updating the Accounting date properly.

·    If a credit card had been deleted from the APS Payments Vault but not from within Adagio, it can be deleted from the Customer.

·    In Edit Credit Card Processor, for accounts with long passwords, each time the Processor was saved, the Password had to be re-entered.

·    In cash batch entry, the information totals were cut off in some cases.

·    In MultiCurrency data only, for Online Credit Card payments that are captured in an external application, in cash batch entry the payment field is no longer editable for sales and credits.

·    When printing statements, the AdagioV3PDF printer window opened and the path that the PDFs were being saved to was incorrect.  The PDF filename was also incorrect.  This has been fixed.

·    An Access Violation error when viewing a customer transaction could be caused by viewing customers and transactions within cash batch entry in a company integrated with Adagio DocStore.  This error no longer happens.

·    Posting was failing when an invoice with terms that had ‘Payment required’ set to ‘Full’ was partially settled with a discount amount.  Posting was not including the discount amount while determining that the invoice had been fully paid.

·    When Adagio DocStore is integrated, report sets can now be emailed to selected recipients with PDF or Excel file attachments for each report.

·    New automation command nouns have been added to allow attaching report set PDF/Excel files to the email with the automation log results. This allows reports from multiple applications to be attached on a single email. The EmailPDFAutoLog has Overwrite/Attach and Append/Attach nouns to include PDF/Excel files from report sets. A future 9.3A release of Adagio Console is required to use this feature.

·    For Adagio Payments users, added feature to have a credit card Receipt emailed to Customers by American Payment Systems (APS) during capture or sale processing when batches are posted. Added ‘Send Customer Receipt?’ option to the credit card Edit Processor function. Set it to ‘Always’ to send a receipt for all customers. Set it to ‘By customer card’ and set new 'Send receipt?’ on the customer credit card record in Edit Customer. The Username and Password for your APS account must be set in Edit Processor. Adagio OrderEntry 9.3A (2019.08.13) and future release of Invoices 9.3A (2019.08.27) support this feature.

·    If Credit Cards have been vaulted in American Payment Systems through another system, such as Webtelligence™ from North49 Business Solutions, rather than in Adagio, you can import sales with payments into an invoice batch using the Credit Card Vault Id. Adagio OrderEntry 9.3A (2019.08.13) and future release of Invoices 9.3A (2019.08.27) also have this ability.

Sales or credits processed in another system will pass through Receivables without any additional credit card activity being processed by Adagio. For a Pre-Authorization, the sale or credit will be captured when the Invoice or Cash batch is posted. Note: You cannot edit Payment amounts or anything credit card related in the imported transaction.

If the new credit cards are being added through importing batches, the Processor Code will default from the imported or defaulted Payment method. The Billing address will default from the APS Payments vault. The Credit Card Id, Description and Credit Card type will default from the APS Payments vault. If these fields are blank in the APS Payments vault, they will default to these settings:
   Credit Card Id - CARD01, CARD02, etc.
   Description - ‘Auto-added on import’ plus the import date.
   Credit Card - ‘Type’ - Other/Unspecified.

·    Added Import / Export Credit Cards functions. Import credit cards vaulted in American Payment Systems through another system rather than in Adagio. Takes Processor Code from the import template.

·    SalesCQ quotes are now shown on the Transactions tab in Edit and View Customer if SalesCQ data is present. Note: Drilldown to SalesCQ transactions screens is not available (that is only available in Edit Customer in SalesCQ). Item numbers are not formatted and show quantities with 2 decimals. The Quotes tab is only available in Edit Customer in SalesCQ.

Problems fixed

·    In cases of a multi-tabbed dialog where the DocStore functionality is only available on one of the tabs, the spectacle graphic is displayed on the tab to highlight it. In AR, Edit Customer shows it on the Customer tab.

·    A second DocStore view PDF button has been added to the Cash Entry screen. This will allow you to specifically look at the invoices to pay or the document attached to the cash entry.

·    You can edit the Customer credit cards from within batch entry unless you authorized a payment prior to choosing the Customer button. If you have, you will only have View instead of the Edit button.  

·    For Adagio Payments users, Cash entry did not clear or change APS credit card info on change of customer code.

·    In Cash entry, attempting to enter the same invoice number with the Direct method now gives an error and prevents the detail from being saved. Previously, it was allowed and could cause integrity errors.

·    In Invoice entry, it was possible to save an entry that was overpaid for a Miscellaneous Customer.

·    Invoice posting did not consider the Retainage Total and was incorrectly displaying an Error message (“Terms nnnnnn requires full payment”) when a fully paid Invoice with Retainage had a Terms code that had 'Payment required' set to 'Full'.

·    If multiple cash batch entries for the same customer had a duplicated check number, posting correctly moved the duplicates to an error batch but the applied and unapplied values did not display correctly. This has been fixed.

·    Processing improvements to speed up the Aged Trial Balance Report.

·    If you printed a large number of batches all at the same time, the error “Record Locking message: Unable to access record in A/R batch control file. This record is in use by [Resources Exhausted] in window [(1)]” appeared in some cases.

·    For MultiCurrency databases, there was an error printing the Customer Transactions report if Short Name was used in the sort criterion.

·    In Receivables 9.3A, the Customer Transactions report printed the matching date instead of the invoice date for applied details. This has been corrected.

·    Previously when emailing statements, a maximum number of 25 attachments was imposed to assist in preventing too many from being included and being blocked by the email server. The ‘Max attachments’ option has been added to Print Statements/Letters dialog screen. The default is 25.

·    If the Specification Options for Specification type, Statement, was set to print more than 1 in the '# of Copies', the details were always missing from the printed copies.

·    Receivables Statements were Auto-Attaching the oldest documents instead of the most current copy of a form. AR attached the original print instead of the (001) or (002) print of the specification.

·    If an invoice was retrieved from OrderEntry or imported with an APS credit card payment capture that had a duplicated check number for the customer, posting the invoice created an error batch entry that had to be deleted and re-entered. Now the check number can be edited to something unique and allow posting.

·    Importing ShipTo records was incorrectly stripping leading zeroes on the tax group.

·    Importing with Field offset was trimming the import field on the right instead of the left.

·    For Time&Billing datasets and customers that Bill by Docket, the Hdr-Docket Number field can now be imported for Cash Batch entries.

·    The 64-bit version of Adagio GridView (if available) is launched for custom Views added to the Inquiries menu.

·    If a user has access to the Maintain Automation Log feature, they also have the ability to view all of the automation logs for any user.

·    If the data path folder name contained a period, browsing to the folder and double clicking on the global file in File Explorer caused the application to try to create a new dataset with the extension set to the part of the folder name following the period character.

·    When Adagio DocStore is used, copying a customer with PDF documents attached to it no longer copies the attachments to the new customer.

·    If a customer has more than 25 unpaid invoices, and a statement is emailed that doesn't attach unpaid invoices, and an Additional PDF is also included, a false warning about exceeding maximum attachments was displayed, although the email was correct.

·    In Receivables 9.3A, if Adagio Time&Billing is used, the smart finder (F6) on the Customer Number field displayed an error.

·    The Customer ID# field has been included in the transaction report work file, so that it can be added to Modified Reports with Crystal Reports.

·    In Receivables 9.3A, the Inactive Customers report printed from the Mark Customers Inactive function did not print. The Deleted Customers report printed from the Delete Inactive Customers function did not print.

·    In Receivables 9.3A (2018.11.09), reports including the Aged Trial Balance, Overdue Receivables and Customer Transactions, did not print correctly when Adagio Time&Billing is used.

·    The OnHold Audit List report in the Calculate Customer Aging function displayed an error in some cases.

·    The Company Profile report showed the ‘Customer aging by’ option as Due Date when the actual setting was Doc Date.

·    On-line payment processing for very large batches (hundreds of transactions) containing credit card payments in Receivables or Adagio Invoices can take a significant amount of time to post (more than an hour in some cases). During this time an error message was displayed for any declined cards, requiring the operator to monitor the process. The option ‘Suppress declined msg on post?’ has been added to the Edit Credit Card Processors function. Any invoices with a declined card are placed in an error batch. A warning message at the end of posting with the count of declined cards is displayed.

·    Import Customer Notes failed in some cases when run by automation with Adagio Console.

·    In Receivables 9.2A higher, importing invoices in Detail Only format split details from the first invoice into 2 invoices if the Transaction Type was not imported or defaulted.

·    The database conversion to Receivables 9.3A changed the Send to for G/L Description 1 and 2 on the Integration tab of the Company Profile if they were set to User Defined.

·    Converting data to 9.3A, when there is no Ledger data and the G/L Transactions report had not been printed and purged, caused a problem printing the report after the conversion.

·    In Receivables 9.3A, the Customer Transactions report printed all customers when there was a range of Files for Adagio Time&Billing.

·    Added ‘Wait between emails (seconds)’ option in Email Setup. If your outgoing Mail Server limits the number of emails you can send, setting a delay between emails may increase the number of emails you can send all at once.

·    Create interest batch by Billing Cycle range selected all customers in some cases.

·    Automation of Import Customer Notes did not work in Receivables 9.3A.

·    The Credit Card Conversion utility program for vaulting credit cards did not vault cards in cases where a card’s payment method had not been set to either Category 3-Credit Card or 9-Online Credit Card. It now reports these errors.

·    The Customer Transactions printed with ‘Include applied detail’ did not show matching transactions if there were unapplied transactions in some cases.

·    The Email Queue Listing printed with a 'Last attempt date of 12/31/1899 instead of 'blank' for any email that had never been sent.

·    In some cases, MultiCurrency datasets with the Adagio OrderEntry option: ‘Adagio Receivables batch type’ set to ‘Retrieval’, the Home Equivalent Batch Total was calculated using the incorrect Rate Operation. This display issue did not affect customer transactions or Ledger entries.

·    When a user was editing a batch and another user printed a batch listing, a locking message was displayed for the second user in some cases.

·    The units were positive instead of negative when posting credit notes for a G/L account with units.

·    Optional Date fields did not work when sorting batches.

·    In Receivables 9.2A (2016.02.26), you could not edit the exchange rate on a MultiCurrency adjustment.

·    In Receivables 9.2A, the ‘Dist Set’ button was missing on the Cash Batch entry screen even though there were Distribution Sets on file.

Reports

·    The Adagio ePrint code %BTT (Batch Type) is now supported for Batch Listings and Posting Journals.

·    The Cash Batch Listing and Cash Posting Journal showed a line with “0.000000 Unapplied Amount = 0.00” for certain specific payment amounts and applications to invoices.

·    The Invoice Posting Journal printed the Disc Date and Disc % fields for credit notes, when in fact they do not apply.

·    After installing Ledger 9.2B (2016.08.10) or SysUpdater (160809), temporary files created on workstations by printing reports were not deleted in some cases, although this did not cause any problems.

Import / Export

·    When importing cash using a Detail Only template, if the H-Payment method field came before the H-Check number field in the file, the wrong payment method was used.

·    When importing batches, the Optional Field values were not read from the customer and placed in the resulting batch.

Miscellaneous

·    Additional entries made in the application log.

·    The email password for servers that require authentication is now encrypted in the file containing email settings for the ‘Direct’ email method.

·    When adding user-attached documents to entries in the email queue, after adding the first document, adding further documents attached a copy of the first document instead.

·    The Data Integrity Check rebuilds a certain type of error in customer alerts that could not be in Receivables 9.2A (2015.06.25) or higher.

·    In Receivables 9.2A (2016.02.26), if the last invoice batch (whether active, posted or deleted) had more than 100 entries, the Data Integrity Check froze the program (DataCare did not have this problem).

·    Receivables now renders dialogs properly on Ultra High Resolution displays when the font size is anything other than 100% of normal on Windows 8.1 or higher. All Adagio releases dated in September 2016 and later have this problem fixed. For releases prior to this date, the utility program SetScreenForAdagio.EXE is installed in the \Softrak\System folder to correct the problem.

·    The Service Pack install for Receivables 9.2A (2016.02.26) incorrectly displayed an error indicating the version of Receivables on the target machine was too old if 9.2A (2015.04.10) was installed, when that was in fact not the case.

·    The Service Pack install of 9.2A (2016.02.26) backed up files to the wrong path in some cases on some machines.

·    The snapshot made by the System Status function (chksys.exe) did not include station log files in some cases.

·    Installs a new Adagio Data Source (ADS) that prevents resource locking problems at large Adagio sites running 9.2 versions and improves application performance at these sites.

NOTE: All third-party applications from Adagio Developer Partners must use the new ADS. You must check with your Adagio consultant or the developer to confirm their application is using ADS 1.12. 66.3503 or higher. Failure to ascertain this risks corrupting data if the application is writing to the Adagio data files concurrently with Adagio modules.

·    For MultiCurrency invoices, when a partial credit note was posted to a fully paid invoice for a multi-currency invoice, posting did adjustments to REGL in some cases. Posting credit notes no longer updates REGL.

·    For Receivables 9.2A, the following change was made. For credit notes entered directly in Receivables, if the ‘Calculate base for discount with tax included?’ option is disabled in the Company Profile, when credit notes are applied to invoices, the amount of the credit note before tax is applied to the Discount Base. However, credit note batches created directly in AR by OrderEntry or retrieved from other modules could not support this. A further changes has been made in AR to allow OE and other modules to support this change in future releases.

·    If the option ‘Allow posting to control account’ added for Receivables 9.2A was disabled, transactions posted in Adjustment batches used the wrong AR Control Account.

Reports

·    The Aged Trial Balance reported the Home Currency Balance for source currency customers incorrectly in some cases, when there were payments with discounts. It did not include the REGL.

·    For the %CMP code (Company Name) used by Adagio ePrint for folder names, spaces and other allowable punctuation characters are no longer stripped out.

·    In Receivables 9.2A for MultiCurrency databases, the Exchange Rate shown on the G/L Transactions report (in detail format) was 10 times too big.

·    In Receivables 9.2A, the Tax Tracking report did not show the Description for Distribution Codes.

·    In Receivables 9.0A and higher, customers with a customer code beginning with “Z” did not print on the Aged Trial Balance if the Number of Days range was changed from the default of 0 to 9999.

·    If JobCost data is present, the ‘Include notes’ option for the Overdue Receivables report did not enable the ‘Notes on/after date’ field on the report dialog but the ‘Include job details’ option (incorrectly) did.

·    In Receivables 9.2A, the Batch Status report did not list open or posted Recurring Charges batches.

·    The Revaluation Listing was missing customers when printed for a range of Control Account Sets.

·    In Receivables 9.2A (2015.06.25), the Cash Batch Listing report was missing the Detail, Type and Doc. Number field data.

Statements

·    Fields and objects on specifications can now have custom colors, with full control of hue, saturation and luminosity.

Import / Export

·    The Import / Export Customer functions now include fields for Adagio SalesCQ found on the Quotes tab in Edit/View Customer in SalesCQ.

·    Import ShipTo Addresses now defaults the Tax Group from the customer if that field is not included in the import file or set as a default in the template.

·    Corrected handling of invalid time fields in the Import Customer Notes function.

·    Import Invoices no longer requires certain fields. They are defaulted if not included in the template:
- The ‘Hdr-Transaction Type’ field is defaulted to Invoice, as this is usually the type of transactions being imported.
- The Hdr-Transaction Date is defaulted from the Session date.
- The Rate Type for MultiCurrency invoices is defaulted from the Control Account Set.

·    Import Invoices did not import a defaulted exchange rate correctly when importing MultiCurrency credit notes.

·    Import Invoices did not allow an Unapplied DN to be imported unless there was a payment.

·    Added ‘Show Alerts?’ field to the import and export customer functions.

·    Field values for Optional Fields with ‘Verify?’ option enabled were not verified when importing invoice and cash batches.

Miscellaneous

·    In Receivables 9.2A, after converting from an earlier version, if Adagio Ledger data was not present you could not retrieve into Ledger in another data set.

·    The Create Write-off Batch function now excludes future-dated transactions.

·    Future-dated applied transactions were not getting updated with the revaluation exchange rate by the MultiCurrency Revaluation function.

·    Receivables 9.2A did not correctly convert databases from version 8.1A (2007.09.29) or older.

·    In Receivables 9.2A (2015.06.25), the auto-workstation install on a new workstation that had not had vitalEsafe installed by a previous install ran again each time you started Receivables. Note: the vitalEsafe web based file storage service has been discontinued and this function has been removed from Receivables.

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

·    The performance of the Customer Transactions report has been significantly improved when printed for a large number of transactions across a network.

·    The Calculate Customer Aging function also calculates the customer statistics field 'Oldest Unpaid Invoice Date', which is the oldest invoice transaction with a non-zero balance. When the ‘Document Date’ aging option was used, the oldest invoice date was determined regardless of whether it had a zero balance or not.

·    The G/L Account and G/L Department fields are validated when importing batches, similar to validation in batch entry. This prevents batches accidentally being imported and posted with blank GL accounts.

·    After posting a cash batch in a MultiCurrency database, the Data Integrity Check reported an error indicating the computed home balance did not match the stored home balance for a transaction, when in fact there was no error. This was partially fixed in 9.2A and is now correct in all cases.

·    After deleting an Alert for a customer in some cases, the Data Integrity Check reported an error indicating an Alert was missing a summary record, when in fact there was no error.

·    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.

·    Added Filter criteria 'Before today' and 'After today' for Floating Date Range.

·    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.

·    The Column Editor screen can be sized. The size is remembered by module on the workstation.

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

Customers

·    Added an option to the Transactions tab to sort customer transactions by Date or by Type/Doc No. In previous versions, transactions were always sorted by Date when ‘Current’ or ‘Historical’ were selected and always by Type/Doc No. when ‘Both’ was selected. Also added an option to the screen to sort customer transactions ‘Ascending’ or ‘Descending’. In previous versions this selection had to be made by right-clicking on the grid. And when ‘Both’ was selected, transactions were always sorted ascending.

·    Added ‘Require PO?’ option on the Invoicing tab in Edit Customer. Enable to require a purchase order number to be entered in the Reference field on the Header tab in Adagio OrderEntry when entering a new order, and in the PO Number field in Adagio Invoices on the Header tab when entering an invoice. Requires OrderEntry 8.1F (2014. 09.30) or higher and Invoices 9.1A (2014.10.16) or higher. A default for new customers can be set on the Customer tab in the Company Profile.

·    Added ‘Print BR Receipts’ option to Invoicing tab in customer. Enable if you want to print a receipt in BankRec when payments for the customer are deposited. This enables the ‘Print Receipt’ option in the BankRec batch for receipts retrieved from Receivables, transactions entered in BankRec or generated in reconciliation. Also added ‘Request Receipt’ option to Integration tab in the Company Profile. Enable if you want a receipt to be printed for cash transactions sent to BankRec from Receivables for all customers. This option must be disabled to be able to enable the ‘Print BR Receipts’ option for individual customers. Requires BankRec 9.2A (2014.12.18) or higher.

·    Added ‘Batch by entry’ option in Payment Methods. Enable to create a separate deposit batch when receipts are retrieved in Adagio BankRec (including payments originated in Adagio OrderEntry and Invoices). This is very useful if you want all deposit entries using this Payment Method to appear in the Bank Reconciliation in BankRec as separate deposit entries, such as for payments received by EFT.

·    Added option ‘Allow edit of posted desc or reference?’ option to the System Options tab in the Company Profile. Enable the option to allow the Description 1 and 2 fields and the Reference field for posted transactions to be edited on the Transaction Details screen, accessed from the Transactions tab in Edit Customer. Use this option to allow correction or updates to these fields after posting.

·    The Terms Description is displayed next to the Terms field in Edit and View Customer. This allows you to see the description in View Customer and to see it in Edit Customer without opening finder on the Terms field.

Edits and Inquiries

·    An Invoicing Specs tab has been added to the Company Profile. This allows defaults for new customers to be set for Print, Fax and Email specifications, as well as Email Covers for Order Confirmations, Invoices and Credit Notes in Adagio OrderEntry, and/or Invoices and Credit Notes in Adagio Invoices. In addition, a default Picking Slip specification can be set for OrderEntry.

·    Added ‘Request Receipt’ option to Integration tab in the Company Profile. Set if you want a receipt to be printed in BankRec for cash transactions sent to BankRec from Receivables for all customers. This option must be disabled to be able to enable receipts to be printed for individual customers.

·    Added ‘Exch. round. error misc rcpts' to the Integration tab in the Company Profile for multi-currency databases. Miscellaneous receipts are not associated with a customer and, therefore, not to a Control Account Set from which to take the Exchange Rounding Error account. Select the account and department to be used for exchange rounding errors when Miscellaneous Cash Receipts are used.

·    The Batch Inquiry functions now include the ability to print Batch Listings (both open and posted), print Posting Journals (open and printed), and Recover posted batches. Batches can be multiselected.

·    Excel Direct has been added to the Batch Inquiry functions.

·    Added several AR specific Styles for use in customer filters.

Batch Entry and Posting

·    The document number generated for invoice and adjustment batch entries now includes the year. The format is year, batch and entry number (YY-B-E). This avoids potential duplicate numbers with transactions entered in previous years.

·    The Payment Total is now displayed at the bottom of the invoice batch screen if any entries include payments.

·    The Total Applied is now displayed at the bottom of the cash batch entry screen. In the previous version, only the Total Unapplied was displayed. Knowing how much has been applied is useful when one check is split between two customers.

·    Cash batch entry now checks for a negative unapplied amount and displays the message: “Applied payment amount exceeds the check amount. Do you wish to continue and save the entry?” when the entry is saved. This also prevents accidentally leaving the Payment amount field at zero after applying cash to invoices.

·    Invoice and adjustment batch entry check for duplicate Document numbers in current and history. Cash batch entry checks for duplicate Check Number. If a duplicate is entered the entry cannot be saved. Posting still also checks for duplicates.

·    The customer name can now be edited for miscellaneous cash receipts (blank Customer code in invoice entry). In previous versions, it was set to ‘Miscellaneous Cash Receipts’. The edited name is retrieved in BankRec. It is also retrieved in Ledger when any of the G/L Reference, Description 1 or Description 2 Send To fields are set to Customer Name.

·    For credit notes entered directly in Receivables, if the ‘Calculate base for discount with tax included?’ option is disabled in the Company Profile, when credit notes are applied to invoices the amount of the credit note before tax is applied to the Discount Base. In all previous versions, the full amount of the credit note was applied.

·    The Distribution field is now hidden on the batch detail screens for all batch types if there are no Distributions on file. This speeds entry by eliminating an extra tab key or mouse click on each detail if you do not use Distributions. The Dist. Set button is hidden on the invoice batch entry screen if there are no Distribution Sets on file.

·    Added the option ‘Allow posting to control account’ to the Integration tab in the Company Profile. It is disabled by default to prevent you from (accidentally) entering GL accounts used in Control Account Sets GL account during batch entry. Batch posting also checks this. Most often this field will remain disabled so that posting to the AR control account is done by Receivables only. However, if you periodically post to the control account (say, when an amount is between departments), enable this option so you can do so.

·    The Job Description and Estimate Description can be shown in the Job/Phase/Category finder in batch entry.

Ledger Interface

·    Receivables 9.2A supports the new feature in the Ledger 9.2A Retrieve Subledger Batches function that allows separation of subledger batches on retrieve by Batch Number. The retrieval file cannot be separated by Batch Number for earlier versions of Receivables.

Specification Designer and Printing Statements

·    When printing a statement from within a customer, the Run Date defaults to the last statement date if statements have previously been printed for the customer. If the last statement date is more than 31 days older than the system date, the session date is used. New customers use the session date.

·    The ‘Auto-attach unpaid invoices’ option on the Statements tab in the customer has been changed to ‘Auto-attach unpaid documents’. All unpaid (non-zero) documents, including credit notes, are now attached to statements when this option is enabled.

·    New specification codes added to show the user who printed statements and the actual date:
     M37, current user code
     M38, current user name
…..M39, system date

Reports

·    Added ‘Summary only’ option to the Customer Transactions reports. Summarizes transactions and prints one line per customer, showing the total Invoices, Cash, Credit Notes, Debit Notes, Adjustments and Discounts.

·    Added an option to print a General Ledger Distribution Summary on batch listings.

·    All details for the Tax Tracking report are now always tracked. This way they are always available for reporting. The ‘Invoiced on tax tracking report’ option on the Tax Information tab in the Company Profile in previous versions has been removed. The selections for this option (‘Only details with Distribution codes’ and ‘All details’) are now available for on the Tax Tracking report dialog instead.

·    Posting Journals can no longer be cleared after printing. This avoids accidental clearing. Posting Journals are cleared at year end. The 'Allow Post Journal Purge?' option has been removed from the Company Profile.

·    When invoice batches including payments are posted, a cash posting journal is created as well as the invoice posting journal. If the option to auto-print posting journals is selected, the cash posting journal is now also printed.

·    A new ePrint code %CDT is available for Adagio ePrint users to put the Calculate/Aged as of date into either the PDF filename or folder name for reports such as Overdue Receivables and Aged Trial Balance.

·    Adagio Receivables 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\Receivables\StandardReports. Revisions to these reports should be placed in \Softrak\Receivables\ModifiedReports. Custom reports to be added to the Reports menu should be stored in \Softrak\Receivables\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. 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. It 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.

Maintenance and Miscellaneous

·    When you elect to clear history when running Period End or Year End, the ‘Clear Customer history up to’ date can now be edited. The date defaults to the last Period End Date less the number of days for which you elected to keep transactions in history. A warning appears if you enter a date newer than the calculated purge date. The date selected is displayed above in the list of functions that will be performed when you proceed.

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

Import / Export

·    Import and export templates created for Excel format now default the file extension to .XLXS rather than .XLS.

Problems Fixed

·    Several fixes were made for this release which will be listed at a later date in a Release Note on our website and the Readme help.

Enhancements and revisions in Adagio Receivables 9.1A (2014.07.23)

   Compatible with future release of Adagio Payables 9.2A.

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

   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.

   In Receivables 9.1A, if a batch containing duplicate transactions was posted as one of multiple batches posted at the same time, an error batch was not created in some cases.

   If the 'Default Ready to Post' option is on in the Company Profile, when the spacebar was pressed on the batch grid the prompt to mark the selected batch(es) Ready to Post displayed when it should not have. If you then marked the batch(es) not ready, and you also ticked the option 'Don't show this message again' on the prompt, the batch(es) could not be posted.

   When an adjustment batch created by the Create Write-off batch function having the ‘Create Payable check batch’ option enabled was posted, and 2 or more customers had checks generated in Payables, the vendor information was incorrect on the checks.

   Printing the Company Profile, Security Groups or User Preferences reports in the 9.1A (2013.10.29) Hot Fix displayed an error related to Crystal Reports and the reports did not print.

   Posting invoices to Balance Forward customers in Receivables 9.1A (2013.06.06) caused data integrity errors. Rebuilding in the Data Integrity Check fixed the resulting errors but it incorrectly doubled the applied amount in doing so. The customer balance will be correct but if you wish to correct transactions affected by this problem you will need to switch to Open Item and make manual adjustments.

   Posting multiple batches from the batch list was ignoring the 'Not Ready to Post' status.

   If you entered a detail in an invoice batch with a GL account and a department, then deleted the account but not the department and clicked OK rather than tabbing out of the account field, the entry was saved with a blank account. This entry could be posted and sent to the GL with a blank account field.

   You could not preview the statement for a customer in the Print Statements/Letters function if the Preferred Send Method was set to Email for the customer.

   If a customer does not have a payment method, the default bank account is now defaulted from the customer's Control Account Set when importing cash batches.

   When importing a cash batch in a single currency dataset, the Payment Source Currency was defaulted to blank.

   If your document numbers in Adagio Invoices are more than 8 characters in length, Adagio ePrint users could not view invoice and credit note document PDFs from customer transactions or attach them to statements.

   The 'Paperless Reports' setting available to Adagio ePrint users is no longer applied to forms such as statements.

   Printing a report caused 'ARPublicFavorite' to be inserted in the Style Finder. This caused all the styles listed below to use different colors/styles and could cause customer styles to be incorrect until Receivables was opened again.

   Added ExcelDirect button to the Contacts/Shipto grid in edit and view customer functions.

   An error occurred when converting data to 9.1A from a version earlier than 9.0A (2009.03.31) and the database was not converted.

   Adagio Time&Billing users with Adagio ePrint can now view a PDF of invoices (bills) from the transactions grid in the Edit/View Customer function.

   Added Phone and Fax to the Address Only option on the Customer List and Statistics report.

Enhancements and revisions in Adagio Receivables 9.1A (2013.06.06)

New Features

   Adagio ePrint users can view a PDF of invoices and credit notes from the transactions grid in the Edit/View Customer function. The documents open in the new Adagio PDF viewer. The PDF can be sized and zoomed. Clicking the next transaction in the grid opens it in the same viewer window.

   Adagio ePrint users can attach unpaid invoices when emailing, faxing or printing statements from the Print Statements function or when editing individual customers. When emailing, invoices are attached as PDFs. When faxing, they are appended to the end of the fax. When printing, the statement is printed, followed by the invoices.

   You can attach a PDF document, such as a promotional offer or product literature, when emailing, faxing or printing statements or dunning letters from the Print Statements / Letters function or from the edit customer function when sending a statement. For statements or letters in the email queue, you can attach other types of documents as well, such as Word or Excel. Attachments are shown in a tree view on the Edit Email Entry dialog. Right-click on the tree to add a document. Default folders for attachments can be specified in new fields 'Attachments statements folder' and 'Attachments letters folder' added on the Statement / Reports tab in the Company Profile. These folders are relative to the ePrint relative folder path (or to the data folder if ePrint is not installed). The defaults are \Attachments\Statements and \Attachments\Letters.

   The email queue grid can now show the total number of attachment files. The fax queue grid can now show total the number of pages in the fax.

   You can now create a Favorite report for the Print Statements/Letters function. This is useful for saving options when attaching paid invoices or other documents to statements or letters.

   You can now create a Favorite report for posting journals even when there are none on file to print. Added 'Last sequence only' option to print dialog for all posting journals. This option is remembered for Favorites and is useful when printing posting journals from a Report Set. Added 'Clear posting journals' option for posting journal Favorites in Report Sets.

   You can now create a Favorite report for batch listings even when there are no batches on file. When printing the Favorite directly or within a Report Set it defaults to the entire range of batches.

   Added Specific Due Date terms. Allows you set the due date to any date in the future. Adagio OrderEntry 8.1E (2013.03.22) or higher supports Specific Due Date terms. A future release of Adagio Invoices will support the Specific Due Date terms. Note: Specific Date Terms should not be used in until you have installed the OrderEntry and/or Invoices versions that support it, otherwise Due Date and Discount Date will not be correct in those modules.

   Added Tax Group and Tax Status to the customer defaults in the Company Profile.

   Added 'Oldest unpaid invoice date' field to the customer for use in filters. It is updated by the Calc Customer Aging function. The value written is the document date of the invoice, regardless of whether the function was done by Document Date or Due Date.

   Supports the Auto-fill GL account and department options in Ledger 9.1A. Supports Uppercase and Auto-fill Vendor options in the 'Payables vendor' field on the Accounting tab in the customer.

   Added the batch description to the window title of the batch entry grid window. Also added the description to the entry dialog window title. This helps you keep your place when entering transactions.

   The Spacebar now toggles the Ready to Post status on the batch grid.

   Added the option 'Don't show this message again' on the confirming message when batches are set Ready to Post, or Not Ready to Post.

   The Posting Sequence field is now one of the default fields on the Batch Status Inquiry grid.

   Added support for Job and Estimate styles in finders for Adagio JobCost users.

   If Receivables is integrated with Adagio JobCost at the Phase-Category level, the finder and smart finder for Job Estimates can now show the customer in the grid so you can see which jobs belong to which customers.

   Added %DST code for the User Defined format to send the Distribution Code to G/L Description 1 or G/L Description 2, set on the Integration tab in the Company Profile. If the Distribution Code is blank, then a blank is sent to the description. If Adagio JobCost is integrated the job number is used.

   Added the option 'Allow deletion of customers with history?' on the System Options tab in the Company Profile. It is enabled by default.

   Added the option 'Show description 2' to the Print/Consolidate GL Transactions report. Transactions with a second description take 2 lines on the report.

   If the 'Clear transaction detail by' option in the Company Profile is set to 'Period End', when a Report Set containing a Favorite to print statements is printed, the question 'Update Billing Cycles and Customer printed dates? is automatically answered Yes. If the option is set to 'Billing Cycle', the question  'Clear all paid transactions in the range specified?' is always answered No.

   Added 3 new expansion codes for Report Favorite filenames for Adagio ePrint users: %CMP (company name), %CNO (company number), and %EXT (data extension).

General New Features

   New splash screen with an updated look.

   The Data Integrity Check (DIC) now checks the Common Files as well as the AR files. Previously these files were only checked by DataCare.

   In earlier releases of Adagio we added the ability for Excel Direct to create a CSV file for use by other spreadsheet applications, such as Apache OpenOffice^TM Calc, for sites that did not have Excel installed. The spreadsheet program was launched and opened the CSV file created. Excel Direct can now use Windows "automation" (inter-process communication) to send data to other spreadsheet applications, the same way it interfaces to Excel, allowing all formatting to be retained in the resulting sheet. OpenOffice 3.3 or later and LibreOffice® 3.3 or later are supported. This interface must be manually enabled. The file SSI2XL.INI must exist in \softrak\system and must contain the section [Initialization] with an entry <computer name>-UseOpenOffice=1, where <computer name> is the name of the machine that this entry references. Refer to the Readme Help for further details.

   A 'Report set' button has been added to the toolbar.

   The Help | About function now has a Consultant tab showing the contact information for your Adagio consultant if they have enabled this option at your site.

   The Open Data screen can be sized horizontally to allow you to see the full data path.

   The F1 key now launches Help when no windows are open.

Problems Fixed

    When the 'Auto print posting journal after post' option is enabled, if an error batch was created when you posted, the Print Posting Journal report dialog did not automatically appear.

   Posting an unapplied Debit Note to a Balance Forward customer who has a negative total balance caused an integrity error.

   Entering a Due Date earlier than Invoice Date is prevented in batch entry.

   Corrected a problem with deleting a distribution of unapplied cash (UP) entries in a cash batch if there was CA transaction in the grid.

   When integrated with Adagio Time&Billing, if you entered an invoice for a customer with Billing Method set to 'By File' for which no Files (Dockets) had been created yet for the customer, you could not save or cancel the batch entry.

   When you Find a customer by Document Number, the finder and smart finder have been improved when there are duplicate document numbers for different customers.

   Customer names containing '&' displayed with '&&' in batch grids.

   The transaction grid in Edit Customer now correctly sorts misdated transactions, where a date was accidentally entered in the year 2020 or beyond.

   Location codes in Adagio Inventory and OrderEntry can only be uppercase. Edit Customer and Customer Ship to was not forcing the field to uppercase.

   When Adagio Time&Billing is integrated, the Import Customers function now allows the Billing Method field to be changed on an existing customer with outstanding transactions, as editing the customer allows this.

   When adding a Ship To address in a customer, the Tax Group is defaulted from the customer. A Ship To can be saved without a Tax Group.

   The 'Print 0 balance customers' option on the Aged Trial Balance report did not include all applicable Balance Forward customers with zero balance.

   Transactions posted in Adagio Invoices did not print on the GL Transactions report if Adagio Ledger data was not present.

   After converting to Receivables 9.0C and if Adagio Ledger data was not present, depending on the version you converted from, if you printed the GL Transaction report there was an error and the report did not print. If a batch was posted after conversion, the report printed and contained the new transactions but transactions from posting in the earlier version did not appear on the report.

   Customers with an extended character (example: É) in the name and thus the short name, did not print on reports in some cases.

   The Edit Report Sets menu choice was missing in Security Groups.

   Codes embedded in Report Favorites (such as %USR for User) were not being saved in some cases.

   If ‘Clear transaction detail’ is by ‘Billing cycle’ and Statements were printed and transactions were cleared for an earlier date than the last ‘Transaction last cleared’ date or, if ‘Clear transaction detail’ is by ‘Period end’ and a Period End was done for an earlier date than the ‘Date of Last Period End’, there may be transactions in History that are dated after the new ‘Transaction last cleared date’/ ‘Date of Last Period End’. They will not be included in backdated aging reports that are dated after the new ‘Transaction last cleared’/’Date of Last Period End’. If you do this same set of steps with 9.1A, the ‘Transactions last cleared’/’Date of Last Period end’ will not be set to an earlier date.

   If the Last Year End date was non-blank in the Company Profile, when running Year End this date was the default for Transaction Clearing Date, for clearing completed transactions from current to history, rather than the sign-on date or the last period end date. . If this occurred, the backdated Aged Trial and statements may not include prior period Transactions. And there will be transactions in history that are dated after the ‘Transactions last cleared’/’Date of Last Period end’ date.

   Corrected a problem with the Time fields when importing customer notes if the time format was "h:mm".

   The error 'Floating point division by zero' occurred if you imported an Excel file that has a header row but with no data (rows).

   When exporting customers by Account Set, Billing Cycle or Report Group the section range did not work correctly. Exporting by range of customer was not a problem.

   The default width of the 'Inv email' field in customer import template was 30 instead of 160.

   The Alt-X key (vs. clicking the Excel Direct button) exported the grid contents to Excel even if user security prevented it.

   When recurring charges have been generated to the Maximum Amount specified in the customer, the Create Recurring Charge Batch function no longer generates a zero dollar invoice.

   Installing the Adagio SalesAnalysis 9.0B (2013.01.26) Service Pack caused a problem using the smart finder for customers in Adagio SalesCQ. In the event this happened, installing this release of Receivables corrects the problem.

   When creating a new multi-currency database or when enabling multi-currency for a single currency database, you are forced to enter a Default Rate Type. This prevents problems retrieving batches in Ledger if the a Rate Type was not set. Note: this means new sites (and for new databases) must run the Adagio MultiCurrency program first and set up a least one Rate Type before creating a Receivables database. This should be done anyway to add a home currency with code that meaningfully matches your currency, such as CAD or USD.

   Installs an updated version of the Adagio Data Source (ADS) that corrects the OpLocks Setting shown in station log files <computer name>.log in \Softrak\System\StationLogs. It was reported as Enabled instead of Disabled in some cases.

New Features

   Compatible with Adagio Time&Billing 8.1C. Supports Docket Active status and Docket Styles in grids and finders in customers, batch entry and ranges on aging reports. Supports Staff Active status in finders in customers and ranges on aging reports.

   The Receivables program icon is more consistent with the look of other Adagio icons and the size of the "ar" letters has increased, making the icon easier to recognize at a glance.

Problems Fixed

   The filename of Statements printed to PDF using Adagio ePrint was missing the first character of the customer number.

   If the 'Validate before importing?' option was enabled and you imported a batch in Excel format that contained an error, an empty batch was created.

   If you printed and consolidated the G/L Transaction report, and you do not have Adagio Ledger, the pre-consolidation entries were not removed from the report and the report totals were doubled.

   Report Favorites allow saving Reports with specific options chosen. Click the Favorite button (a star icon) on any report dialog to create a Favorite. Favorites for a report can be accessed from the report dialog in a drop-down field. Favorites can be private to the Adagio user or public for use by all users. Private Favorites are yellow, Public Favorites are blue. Added Favorite Reports and Print/Delete Favorites functions to the Reports menu. Multiple favorites can be defined for the same report.

   Report Sets allow the grouping of Report Favorites into a single print job that will run unattended. Report Sets may be printed to printer or PDF files (when Adagio ePrint is used). Report Sets may be launched from a command file or a scheduled Windows task by running Invoices.exe with the parameter /R followed by the Report Set (ex. /RDayEnd). A progress dialog lists the reports in the Report Set, the printing status of each, the destination folder, filename and conflict strategy. A log is generated that records the printing status of each report in the set. Use Report Sets to automate the printing of all your daily or month end reports.

   Added 'Append by type' option to Payment Methods for the BankRec interface. Payment methods set to ‘Batch by date’ always created batches by date and by payment method. Now, if you have ‘Append to existing batch’, but do not have ‘Batch by date’, you can choose ‘Append by type’. This allows you to separate out the checks you deposit into two separate batches – checks drawn on the depositor’s (your) bank and checks drawn on other banks. It also allows you to separate checks and EFT payments of the same date for the same bank. To use this option you must have Adagio BankRec 8.1D or higher.

   Added Payment Methods report.

Problems Fixed

   In Receivables 9.0B (2011.07.27), cash transactions with a blank Payment Method were missing from the batch sent to the BankRec batch, unless an earlier entry with a Payment Method had been posted in the same batch or in a batch posted earlier in the same session.

   In Receivables 9.0B, posting Debit Notes to Balance Forward customers caused data integrity errors.

   An error occurred if you had more than 9,999 batches (for any batch type) in the same year. Note: the maximum number of batches allowed in a year is 65,535.

   The Payment Method was not remembered between entries in Cash Batch entry.

   If the 'Validate closed periods' option was set to 'Disallow', when there was an unposted batch from OrderEntry you could not post the batch and received an error indicating (incorrectly) that the fiscal period was closed for the date of the batch transactions.

   In Receivables 9.0B (2011.07.27), after printing and clearing the Batch Status report for the entire range of batches, if there were no open batches, when you ran a Data Integrity Check (DIC) before creating a new batch it  reported an error stating the next batch number should be 1. If you did a rebuild, everything appeared to fine. However, when you created new batches they became populated with the transactions from the original batch of the same number. This is now prevented. Note: if you only printed and cleared the Batch Status at Year End this was not a problem.

   When the batch status information is cleared after printing the Batch Status report or by Period End, batch records for the associated batches are now also deleted. This may take a few minutes on a large database across a network. A progress bar is shown during this time. If the entire ranges is selected and there are no open batches this process will be instantaneous. When the batch status information is cleared at year end this process is also instantaneous. The Data Integrity Check now detects and removes orphan batch records for which there is no corresponding batch status record.

   The Overdue Receivables report in Summary format formatted negative numbers differently in different columns.

   If your Ledger data was created with version 9.0x and you had never used Ledger 8.1A or earlier versions, after printing the G/L Transactions report in Receivables, the Consolidate G/L Transactions dialog did not show the 2 options to consolidate by Fiscal Period.

   The Company Name did not print on the Aged Trial Balance and other aging reports if there were no transactions in the range selected.

   Several minor problems and inconsistencies with other modules related to ePrint functionality in Receivables have been corrected in this release. This includes some small new features. If you are using Adagio ePrint, Receivables 9.0C or higher is recommended.

   The error message displayed when a user attempts to log in when the Security Group for the user does not exist indicated a different Security Group than the one actually missing for the user.

   When installing Adagio to a computer or server where no Adagio modules had previously been installed, if you installed an Adagio module that does not use the Crystal print engine first (such as Lanpak or GridView), when you installed Receivables you received the error "Adagio has been established on destination folder: [x:\SOFTRAK]. Yet the install cannot detect the corresponding Reports Tables..." and were unable to proceed. If the first module installed uses the Crystal print engine there was no problem.

   When running any Adagio module that installs vitalEsafe (or WebSafe as it was previously known as) on a Windows 7 (or Vista) station, in some cases the auto-workstation install ran every time you started the application, even if you had done a workstation install. This happened if the user was not an Administrator on their own machine (the default for a new computer) but rather a Standard user, and User Account Control (UAC) was on, and you had not installed any module with a release date of October 2011 or later and done a workstation install for it on the station. This has been resolved. To resolve this problem for ALL other modules, install any module with a release date of October 2011 or later and do a workstation install for it on the station.

   Installs the AdagioPDF printer driver. All reports and printouts from Adagio can be printed to the AdagioPDF printer to create a PDF document in the data folder.

   Supports the features in Adagio ePrint. When ePrint is installed you can print reports to PDF files in configurable folders determined by the Report Type (General, Transaction or Audit). Statements print to a separate, configurable folder. Fields can be embedded to establish the file and folder names (User, Session Date, System Date, Time). Click the ePrint button (red "EP" icon) on any report dialog to print the report to PDF. The Paperless Reports option forces all reports to be printed to PDF. Reports can be printed to PDF and attached to an email (MAPI) with a single button click.

   On the Open database dialog you can now use Alt-B to open the browse and Alt-F (for Favorites) to open the previously opened list. In previous versions you had to use the mouse to select the folder buttons.

   Alt-X now selects the Excel Direct button on grids where it is available. In previous versions you had to use the mouse to select Excel Direct.

   The vitalEsafe upload progress dialog has been improved and the progress bar now accurately shows the percentage. It is no longer necessary to install the vitalEsafe patch.

   Grids, filters, and finders now show the lookup values instead of the raw data values for typed fields. For example in customer grids the Account Type shows Open Item and Bal Forward instead of No and Yes.

   Account Styles and Filters were added in Ledger 9.0D. They are now supported in GL account finder grids in Receivables.

   Added the field 'Send to BankRec' to Payment Methods to allow explicit control on a bank by bank basis as to whether cash transactions flow to Adagio BankRec. In previous versions all transactions went to BankRec, to the bank specified in the 'Default BankRec Bank' field in the company profile, if the bank in the Payment Method was blank. A Payment Method having the 'Send to BankRec' off must be used for any transaction you do not want to send to BankRec. When the option is off the 'BankRec clearing' field label changes to 'Account/Dept'.

   Job Phase and Category fields have been added to the Overdue Receivables, Projected Receivables, and Aged Trial Balance reports when printed in detail form.

   The maximum number of columns for Charts has been increased from 5 to 12.

Problems fixed

   When you copied a customer, the amounts in the aging bucket values (visible only on grids and in GridView) were copied to the new customer even though the new customer has no transactions or balance. Note: this did not affect the aging reports or aging fields shown on the customer screen.

   When adding customers, the Payables Vendor field from the previously added customer was defaulted for the next customer instead of being set to blank.

   When opening the customer edit or inquiry functions, it was possible to very quickly press the F5 or F6 keys to open the finder or smart finder before the customer grid was open, in particular on a network with slower performance. When a customer was selected from the finder an access violation error was displayed.

   The width of the 'Total days to pay' field on Customer Statistics tab was increased, allowing room to fully display the field.

   Changes to the column sizing in the customer smart finder grid were not saved in some cases.

   The Find did not work correctly for selecting a customer with a leading zero in the Name field, such as for a numbered company.

   On a customer grid, if you select a filter that has sort fields, the fields are added to the grid automatically. If the filter is then turned off those additional columns were not removed.

   The smart finder did not work for customers in Receivables 9.0B if Adagio Time&Billing data was present.

   In Receivables 9.0B, when you added a new customer "on the fly" during batch entry an "Access Violation" error was displayed when you clicked OK to save the new customer, although the customer was added.

   When you posted an adjustment batch containing a duplicate transaction, the next batch number was not updated in the batch control, resulting in the loss of the transactions in the next batch entered and posted. This has been corrected and the Data Integrity Check will detect and rebuild this condition.

   Entering an inactive customer in cash batch entry no longer forces you to make the customer active because you must always be able to accept a payment from customers.

   If you attempted to rename a retrieved batch when the 'Allow edit of retrieved/imported batches?' option was off, you could not edit the company profile afterwards and received a message saying it was locked.

   Posting a multi-currency Revaluation in Receivables 9.0A or 9.0B caused integrity errors in some cases.

   When the Job Tracking Method was 'Job only' the job number did not print on the Customer Transactions report.

   The Customer List and Statistics report did not select customers correctly for a range of 'Start date' in some cases.

   If your Ledger data was created with version 9.0x and you never used Ledger 8.1A or earlier versions, after printing the G/L Transactions report in Receivables, the Consolidate G/L Transactions dialog did not show the 2 options to consolidate by Fiscal Period.

   After printing or previewing a multi-currency report that prints in landscape, reports that print in portrait printed in landscape instead.

   Customer Notes could not be imported in Receivables 9.0B as the import function did not accept the date field in any of the available formats.

   The Note Detail field is no longer a required field for when importing customer notes and can be defaulted.

   If you exported customers by range of Billing Cycle or Account Set and you had a filter applied on the customers grid no customers were exported.

   When importing a cash batch, the Payment Method defaults from the customer if the field is not included in the template. If the Payment Method is in the template but the field in the import file is blank it is not defaulted from the customer.

   When importing customers, new values for optional fields in the import file were not added to the list of Values for the Optional Field even though the 'Add on the fly?' option was enabled.

   There was an error in the auto-import on startup in some cases for templates that specified a spreadsheet with an .XLXS extension (but not .XLS), even though the import worked without error when run manually for the same import template.

   The Import Contacts/Shipto function was trimming leading zeros from the Contact/Shipto Code, even though they are allowed and supported in Adagio Invoices and OrderEntry.

   Security Groups did not have an option for disabling Edit Customer Filters.

   The Adagio command line parameters on an icon did not take precedence over the remembered user logon options if the /u parameter was after /d and /e. Thus desktop icons used to open different databases did not work.

   Manual Check batches created in Payables by the Create Write-off Batch function now support the new date, time and user stamp fields in the Payables 8.1C batch status.

   For filters based on a range of a right-justified field (such as customer number, single segment item number, vendor number, etc.), additional records were selected that should not have been. For example, if the range is from 1 to 2, then not only would records 1 and 2 be selected, but also 10, 11, 100, 101 etc. You will need to edit and save any such existing filters to correct them.

   Turning on the 'Clear customer history up to' option in both the Period End and Year End functions cleared the transactions but did not clear the related details within the Receivables GL Distribution Details table, leaving "orphan" records in the table. (Note: the Maintenance | Clear History function did clear these details.) The orphan records caused an error if you later posted a cash receipt with the same (i.e. a duplicate) document number to a customer. The Data Integrity Check (DIC) detected and rebuild these errors after a posting. The DIC (in Receivables but not DataCare) now detects ALL orphan records and removes them when you do a rebuild so the error will not be repeated with future postings. While the DIC is rebuilding, progress is not shown (the number of orphans deleted is not updated). This may take several minutes. In some cases, the first DIC run after installing 9.0B (2011.07.27) or higher may detect and rebuild a large number of errors caused by the orphan records. This is not a cause for concern.

   There was an application integrity error in the Customer Alert Details in the 9.0B sample data.

Customer