What’s new?




Unit adjustment enhancements

  • User now has the option to specify if they want to use a Customer (sits under Accounts Receivable in your accounting package) or a Vendor (sits under Accounts Payable in your accounting package) when processing unit cost adjustment against the unit

  • User can now also specify the tax code to be used on this accounting transaction so that the Bill, Credit Memo or Invoice can also include sales tax

  • For tax included pricing customers (Australia and New Zealand), the adjustment amount is always considered as a pre-tax value and taxes are calculated as being in addition to that value

  • For further information, please review this article - How to Process a Unit Cost Adjustment



New Chart of Accounts restrictions

  • A new General Ledger mapping restriction has been implemented for QuickBooks.

  • For the Dealerships using QuickBooks are your accounting package, this means that in our Accounting Integration section, the user will no longer be able to map to one of the restricted sales tax General Ledgers in QuickBooks


New Import PickList format - HLSM CSV



What’s improved?


  • Release - Numerous Forms have been released for specific Dealerships.  You will be contacted directly if it is your dealership's forms
  • Resolved -  issue with Website product management where a product was getting stuck in syncing status when a CO was created for a Shopify sale
  • Performance Improvements - have been implemented when creating a CO when the customer has active orders
  • Resolved - an accounting issue for taxes on customer invoices when the name of a tax rate was change after the CO was created

  • Resolved - User Interface (UI) issue with the message count icon being misshapen for low outstanding count values

  • Resolved - issue with temporary units not being assigned the correct notes value from the Model / Sub model definition

  • Resolved - issue with the deal documents not having consistent totals caused by the incorrect handling of changes to a kit header price

  • Resolved - issue with additional blank page being included in the invoice preview when multiple jobs are included in it

  • Resolved - a number of issues which caused the submission of Parts Inventory to not be submitted to BRP:

    • Getting error "Some error occurred - JSONObject["SFUsername"] not a string" while file posting to heroku.

    • Part inventory failure notification generated due to 503 info error log - although file posted to BRP successfully.

  • Resolved - issue with the user not being able to manually add payroll time clocking entries which was caused by auto-fill from the browser making it appear as though a time clocking user had been selected even though it was not

  • Resolved - issue with the user not being able to manually add payroll time clocking entries which was caused by auto-fill from the browser making it appear as though a time clocking user had been selected even though it was not