Skip to main content

Blackpurl Release Notes — Accounts Receivable Visibility, Unit Mileage on Deals, and Bug Fixes

This release adds Accounts Receivable balance visibility for charge account customers, unit mileage editing on deals, and resolves multiple reported issues.

What's New

Accounts Receivable Balances in Accounting Package Now Visible in Blackpurl

For dealerships using accounting integration and debtor accounts (Charge on Account), Accounts Receivable (A/R) balances from the accounting package are now visible directly in Blackpurl. Staff can see any outstanding balance while serving a customer and take payment on account without leaving the customer order.

The A/R balance is visible in the following locations:

Customer Order — Customer Information Section

An indicator appears in the customer header when an A/R balance is outstanding. The Customer section shows the balance amount and includes an option to receive payment on account directly from the customer order.

Shows an Invoice History section with blue header bar labeled 'INVOICE HISTORY' showing '1 Invoice'. Below is a table wi


Customer Order — Invoice History Section

The Invoice History section now includes a new A/R Balance column showing the outstanding balance associated with each invoice.

Customer Record

The customer record displays A/R balance details so you can review a customer's outstanding balance at any time outside of a customer order.

Reporting — Customer Invoice

The Customer Invoice report now supports filtering by A/R Balance (greater than 0) and includes an optional A/R Balance column you can add to the report output.

For full details on this feature, see Accounts Receivable (A/R) Balances in Blackpurl.

Unit Mileage on Deal Units

When units or trade-ins are added to a unit deal, the mileage field is now available on the deal screen and is pre-populated with the current mileage from the relevant unit record. You can edit both the mileage value and mileage type directly on the unit deal.

Key behaviours to be aware of:

  • Changes made to mileage on the deal do not alter the mileage on the source unit record.

  • When the deal is finalised, the updated mileage and mileage type are applied to the unit records generated from the deal — for example, when a trade-in is stocked, the stocked unit record uses the mileage entered on the deal.

  • Deal documents use the mileage fields from the deal rather than the source unit.

What's Improved

The following issues have been resolved in this release:

  • Fixed a customer creation issue when creating deals from DP360 leads.

  • Fixed an issue where the unit profit percent on unit records was not displayed when the price was zero.

  • Fixed a part inventory variance between Blackpurl and QuickBooks/Xero. This issue occurred only when a vendor invoice had all of the following conditions true for a part: a variance between the Vendor Receipt (VR) cost and Vendor Invoice (VI) cost; the item required a pre-sold cost adjustment; and other charges were allocated via Landed Cost Allocation (LCA).

  • Fixed an issue when selecting a Due In date for unit check-in.

  • Fixed an issue where shop supplies continued to be calculated on a job after the related labour was removed or altered by the Claim Response process.

  • Fixed an issue in reporting where the Preview/Apply button was hidden depending on screen resolution and browser zoom level.

  • Fixed an issue that caused a consignment to fail to sync to accounting when there were other uninvoiced items on the customer order.

  • Improved the appointment-to-job linking selector to show additional job details, including job section name and unit details.

  • Fixed ICU locale issues that prevented users from saving manually logged technician time.

  • Fixed an issue in the accounting integration category listing where a GL account number appeared in the list but the GL field was blank when editing the category. This occurred when GL accounts had been removed from QuickBooks/Xero but were still referenced on categories in Blackpurl.

  • Fixed a discrepancy in technician hours logged using job clocking. Clocking on and off jobs is now based on time in hours and minutes rather than seconds.

Did this answer your question?