Credit Hound release notes

Version: 6.12

Release Date: 15/07/2020

Major Additions:


  • Support for Microsoft Dynamics 365 Business Central on-premises 2020 Release Wave 1 -version 16 (#45836)

Minor Additions:


  • Added new filter for the ‘Actual Resolved Date’ of a dispute on the Dispute Analysis, Dispute Analysis (with Notes) and Dispute Analysis Summary reports (#31282)
  • Added consistency between the fields required for the user information in the Startup Wizard and Credit Hound Manager (#32827)
  • Updated the title of the ‘Sage 200 Connection Details’ dialog in Credit Hound Manager (#41408)

Bug Fixes:


  • The transaction Disputed Amount fields on Chase Letters are not populated (#41562)
  • When an Account Note is added while other accounts are open, the note is displayed in all open accounts (#42876)
  • Stop Count statistic does not update in the Chase Screen after putting an account On Stop (#42877)
  • In some instances, unable to resolve disputes after adding a transaction note (#42878)

Version: 6.11.1

Release Date: 29/01/2020

Minor Additions:


  • Addition of a progress indicator during database migration. (#13569)

Bug Fixes:


  • A ‘SQL Deadlock’ error is shown when a user is in the Chase Screen and Self Chasing is running at the same time. (#41559)
  • No matching records when running a rule with an Analysis Code Criteria value that contains an apostrophe. (#41560)

Version: 6.11

Release Date: 13/12/2019

Major Additions:


  • Support for Microsoft Dynamics 365 Business Central on-premises Release Wave 2 (version 15). (#29172)
  • Support for ageing method “Start Period Ageing on the first day of the month after Transaction date”. (#36607)

Minor Additions:


  • Ability to use Windows Environmental Variables within the Credit Hound Manager – ‘Archives’ folder and file paths for viewing Invoices and Credit Notes. (#40058)

Bug Fixes:


  • When placing an account on/off Stop in Credit Hound, the Sage 50 ‘Customers On Hold Report’ is not updated. (#38903)
  • Errors with failing to migrate the company databases when upgrading to Credit Hound v6. (#39210)
  • Tab characters in Customer Names, Contact Names and Transaction References cause a ‘Red X’ and an 'Object Reference not set to an instance of an object' error when running rules or going into the Chase Screen. (#40056)
  • Self Chasing fails to run due to missing files in the Server installer. (#40057)
  • The ‘Account.ShortName’ field is not being populated when added to letters. (#40605)
  • The ‘Transaction Dossier’ report’s ‘Between’ filter for Overdue days returned incorrect results. (#41003)
  • The turnover figure is misaligned by a month for the Sage 50 connector. (#41167)

Version: 6.10

Release Date: 10/09/2019

Major Additions:


  • Support for Sage 50cloud Accounts v26 (#36547)

Version: 6.9

Release Date: 12/07/2019

Major Additions:


  • Introduced the ability for System Integrators to integrate with the Generic Accounting System without the use of SQL Server Integration Services (SSIS) packages. (#32570)

Note:


  • Please refer to the System Integrator documentation “Credit Hound - Using the Generic Accounting System without SSIS Packages” for details on how to connect Credit Hound to a Generic Accounting System without the use of SSIS packages.

Bug Fixes:


  • When using the option ‘Sync outstanding transactions only’ for a Dynamics NAV dataset, the Who Has Paid Me report does not show all payments. (#34771)
  • Duplicate key error when synchronising certain Additional Reference fields from Sage 200. (#28520)

Version: 6.8

Release Date: 18/04/2019

Major Additions:


  • Support for contacts at transaction level, for Dynamics NAV / Dynamics 365 Business Central and the Generic Connector. (#26358)

Note:


  • If you would like your letters to be addressed to the transaction contact, please change your letter address field from Account.PostalAddressBlock to Account.Contact.PostalAddressBlock.
  • A set of standard letters (that can be imported into Credit Hound) addressing the transaction level contact are available on the Partner Portal.

Minor Additions:


  • Re-added the help documentation to the Windows Start menu. (#17282)

Bug Fixes:


  • The automated ‘Write a To-Do’ Rule Action does not create To-Do’s in 10-minute intervals. (#31467)
  • Account Notes do not save when adding them during a manual chase and then producing a follow up letter. (#28607)
  • In some instances, the ‘Head Office Account’ setting in the Consolidated Chasing screen cannot be removed. (#32332)

Version: 6.7

Release Date: 18/02/2019

Major Additions:


  • Support for Sage 300 ERP 2012 to 2019 (#27011)
  • Ability to enable or disable the options to send letters at the end of a manual chase (#24284)

Bug Fixes:


  • For Dynamics GP – When upgrading from versions of Credit Hound prior to v5.1 to Credit Hound v6, the upgrade failed with an issue caused by transaction types (#30356)
  • Filter does not work on the Accounts List and Aged Debt list when using round brackets (#31969)

Version: 6.6

Release Date: 24/10/2018

Major Additions:


  • Support for Microsoft Dynamics GP 2018 (#25796)
  • Support for Sage 50cloud Accounts v25 (#26072)
  • Sage 200 Winter Enhancement compatibility

Minor Additions:


  • Updated criteria on Chasing Letter 2 rule from 'Transaction Amount' to Transaction Outstanding Amount' (#24287)
  • Added tooltip on the Self Chasing icon to indicate an error condition (#27821)
  • Introduced user validation checks on Credit Hound Server installer (#8808)
  • Added support for TLS 1.2 (#27516)

Bug Fixes:


  • DPI settings cause Self Chasing sequence status error (#19615)
  • The removal of users that are assigned to Self Chasing Sequences or To-Do items causes errors (#14471)
  • Upgrading/importing a rule with the ‘Transaction Reference’ criteria returns an error (#26629)
  • A null AccountSource field when migrating company from Access to SQL caused the ‘Who Has My Money’ widget to be displayed incorrectly / problems with changing account category and group (#26350)
  • Not all history items are reflected within the Account History view of the chase screen (#27009)
  • Deleted transactions appear on letters produced via Rules & Actions - Write Letter Action – Advanced (#28100)
  • Dynamics GP Transaction Contacts – Transaction level contacts who are also default contacts on accounts could receive multiple letters (#28413)

Version: 6.5.1

Release Date: 08/08/2018

Bug Fixes:


  • Credit Hound crashes when printing a letter (#25984)
  • App Pool settings get overridden on upgrade (#25985)
    Potential problem when creating a company or logging in due to website authentication. Changed anonymous authentication to use App Pool identity (#25981

Version: 6.5

Release Date: 03/08/2018

Major Additions:


  • Support for Microsoft Dynamics NAV 2018 (#17413)
  • Rules and Actions performance improvements (#12075)
  • Enabled multiple level consolidated accounts (#17421)

Minor Additions:


  • Added ability to resize the Rules and Actions windows (#5936)
  • Increased the maximum allowed value in Account Limit Criteria to 10,000 (#14099)
  • Added a dialog to display error details when running Rules and Self-Chasing (#15824)
  • Added the ability for a Manager user role to configure Consolidated Chasing hierarchy (#24323)
  • Improved security by disabling export accounts option for Limited Users (#24322)
  • Introduced the ability to view other users To-Do's items by user role (#24325)

Bug Fixes:


  • Self Chasing – Automated To-Do’s for Consolidated Chasing - Level 2 accounts were not created (#16581)
  • Error when running rules with Account Group criteria when the current user is not part of any account groups (#9229)
  • Auto Complete could not complete Disputes related to To-Do items which were resolved before being paid (#17483)
  • Errors caused by duplicate account category names (#17642)
  • Errors caused by duplicate account group names (#17935)
  • Account Limit Criteria on rules - when ordering by Account Reference, accounts with no transactions aren't filtered out (#14098)
  • Sage 50 - Incorrect transaction due date after synchronisation for existing transactions (#21279)
  • Credit Hound business terms displayed as ‘Not configured’ on the chase screen (#23137)
  • Inconsistent chase history displayed for accounts in a foreign currency that are part of a consolidated chasing hierarchy (#21831)
  • Report designer - The fields ‘CreatedOn’ and ‘Company Extension’ display incorrectly on letters (#21275)
  • Credit Hound Manager – Business Terms; The “User Defined” selection option is not always remembered and switches back to "Accounting" option (#23041)
  • Address Line 4 data is missing when copying a contact (#23060)
  • Contact middle name is missing when copying a contact (#23059)

Version: 6.4.1

Release Date: 14/11/2017

Major Additions


  • Sage 200 Summer 2018 enhancements


Bug Fixes

  • Sage 50 – The Clear Audit Trail option (potentially) causes the following problems: (#19499)
    1. Chase history could be lost
    2. Due dates on transactions could be incorrect
  • Incorrect label on synchronisation progress (e.g. 'Task 6 of 5') when running optimised sync (#19600)
  • BI user type unable to view Promised Cash on homepage widget or BI user type shown incorrect Promised Cash on homepage widget (#19587)
  • Chasing letter 2 – worded incorrectly (#19611)
  • Synchronisation process will not delete transactions that have been deleted in the host system (#20038)
    Note: This would only occur if a transaction was deleted in the host system at the time of migration (this would impact all connectors)

Click here for older Release Notes