Acctivate Version 13

13.0

Fiserv integration with support for credit card terminals, improved Enter Payments window, improved Enter Purchase Order data entry grid, improved Enter Inventory Transaction and Inventory Count UI/UX, refreshed Create Drop Ship and Special Order window, integration with 3G Pacejet Shipping.

Version 13.0 is available as a preview for download

⭐ = Features and improvements

Database Maintenance

  • ⭐ Improve performance of "Database Verify" for hosted databases.
  • ⭐ When creating a database backup, the "Overwrite existing sets" option will default to checked.

General

  • ⭐ In the View Current Users window, add a Log off User button that allows system administrators to force log off workstations.

Installation

  • ⭐ When a database upgrade is required after installing an Acctivate update, all users must be logged out of Acctivate. A Force Log Out button has been added to the message box that appears if users are still logged in when a database verify is initiated. The button will only appear if all of the logged in users are are logged in with version 13.0 or later. This feature allows system administrators to forcibly log out other users, ensuring the database upgrade can proceed.

Inventory

  • ⭐ In the desktop version of Acctivate, support using a USB scanner to scan an inventory session barcode to populate the Session field in the Enter Inventory Transaction windows.
  • In the Enter Inventory Transaction windows, a session number will no longer be assigned until the session has been saved. This prevents session numbers from being incremented even when a session isn't saved.
  • ⭐ In the inventory transaction windows, the 'Lot/Serial #' column will appear in the grid only when a lot or serial product has been added to the transaction. Similarly, in the Enter Inventory Receipt window, the optional lot/serial attributes (such as expiration date, reference, and specification) will display only if they are configured to show.
  • ⭐ Improve the layout of the Enter Transaction windows by grouping related Transaction fields in a side panel. This also allows fields to move up when irrelevant fields are hidden, providing a better use of space.
  • Fix a bug in the Inventory Transactions windows where it was possible to save a blank row.
  • If the Transaction Date of an inventory transaction falls on or before the QuickBooks closing date, a warning icon will appear beside the Transaction Date. When clicked, it will display a message explaining the Transaction Date is within the closed accounting period.
  • Fix the error "Deleted row information cannot be accessed through the row." that would occur after deleting the only transaction in an Inventory session.
  • Fix an issue where attempting to refresh an Enter Inventory Transaction window for a session that has been deleted would cause a looping message prompt.
  • Fixed an issue where editing a specific inventory transaction from the Transaction List opened the first transaction instead of the selected one.

Inventory Assembly

  • ⭐ In the Enter Assemblies window, hide the Lot/Serial attribute fields (Expiration, Reference, and Specification) until a Lot/Serial number has been entered in. Previously, the fields always showed, but they weren't editable until a Lot/Serial number was entered. Until a Lot/Serial number is entered in, a warning icon will display next to the Lot/Serial field. When clicked, it explains that the attributes will be available for entry after entering a lot/serial number.

Inventory Count

  • ⭐ The Create Count window is now opened by clicking the New button in the Enter Count window.
  • Fix an issue where printing a Count Sheet would results in all count sessions being included, and printing a Count Variance would result in all posted count sessions being included.

Inventory Issue

  • Fix an issue where the Inventory Issue GL account would get reverted to the default for the warehouse if the GL Account was selected prior to selecting the warehouse.

Landed Cost

  • Fix an issue where the InventoryByWarehouseLot data view could calculate the AmtReceived and AmtIssued values for a lot or serial number incorrectly if a landed cost had been allocated to the lot or serial number.

Lookup

  • Make a change to mitigate a potential cause of the "Cannot find column..." error that may occur when using the lookup windows.

Payment

  • ⭐ Integrate with Fiserv for processing eChecks and credit cards entered into Acctivate, or process credit cards using a Fiserv supported credit card terminal.
  • ⭐ Improve the the Enter Payment window's user interface and user experience. The payment information fields have been reorganized so that common fields always show on the left side of the window and credit card or eCheck specific fields appear on the right side. The Enter Payment window is now always in an editable state with the ability to save changes once they're made. Finally, in companies that are integrated with Fiserv, the user can switch between keying a credit card or using a terminal to process a credit card.
  • ⭐ Change the layout of the Payment window to match the new layout of the Enter Payment window.
  • ⭐ Update the Payment Receipt form to match the new layout of Enter Payment window.

Purchasing

  • ⭐ Update the Purchase Order Window to have a configurable, single line grid.
  • ⭐ Improve the layout and functionality of the Create Drop Ship POs and Create Special Order POs windows.
  • Fix the errors "PO number ... could be not found." and "Object reference not set to an instance of an object." that would occur when opening an Inventory Receipt in the Transactions list or the Enter Receipt window for a receipt that was linked to a Purchase Order which has had its PO number changed.
  • ⭐ Add support for VAT Tax codes in the Create Reorders and Create Drop Ship/Special Order POs windows.
  • Prevent copying a Drop Ship Purchase Order since Drop Ship POs must originate from a Sales Order.
  • When creating Purchase Orders from the Create Reorders window, if a PO unit is invalid due to it's relationship with the product stocking unit being recently changed, provide a clear message rather than an "Attempted to divide by zero." error.

Reports

  • ⭐ Update the style of the default inventory transaction forms.

Sales Order

  • ⭐ n Acctivate companies with only one active warehouse, the Warehouse column is hidden by default in the Enter Sales Order window's detail grid. However, this column can be added to the grid using the 'Show Columns' menu.
  • ⭐ Update the style of the lot/serial number dropdown in the Enter Sales Order and Picklist windows to match the style used elsewhere. This updated dropdown style auto-sizes to ensure that its contents fit without requiring scroll bars.
  • ⭐ Change the Product ID and Price Code lookup button from an ellipsis to a magnifying glass in the Enter Sales Order window.

Shipping

  • ⭐ Integration with 3G Pacejet Shipping.

Synchronization

  • When creating Cost of Goods Sold journals in QuickBooks Online, the Location/Department assigned to the journal will be based on the invoice's Branch, rather than the invoice line's warehouse.
  • Fix the payment sync error "Exception changing record to other Key ' ...' System.InvalidCastException: Unable to cast object of type 'System.DBNull' to type 'Intuit.Ipp.Data.Line[]'" that would occur in QuickBooks Online companies when a payment wasn't applied to any invoices.

User Interface

  • ⭐ Limit each manager window (Sales Order Manager, Purchase Order Manager, Activity Manager, Inventory Manager) and each restock window (Create Reorders and Create Assemblies) to a single open instance at a time. If a user attempts to open a window that is already open, the existing instance will be brought to the foreground.

Web Store

  • When eBay throttles API requests, Acctivate will wait five minutes before trying again, rather than the usual ten seconds, ensuring there is sufficient time for the eBay servers to respond.
  • Fix an issue with the web store shipment sync where the shipped quantity for kit products may be overstated.
  • When querying for products by updated date with the BigCommerce v2 connector, the ISO 8601 date/time format will be used. This works around a reported BigCommerce issue where the documented date format may not work correctly.