Fixes

[VA-7803] - PO Planner is not running by category
[VA-10028] - Product Backorder/Unshipped Listing
[VA-10173] - email customer statement does not populate email address
[VA-10178] - purchase order import issue-ship date handling
[VA-10213] - cannot import payment receipts
[VA-10228] - Re: Sales tax on Invoice report
[VA-10230] - Some kits are not pushing to Shopify
[VA-10249] - Cannot add shipping service to FedEx setup
[VA-10261] - Logging a Kit as a Product for WooCommerce sync
[VA-10271] - Historical Invoices show on the Transactions tab in the Customer Page

Release Notes

[VA-10150] - Allow the user to choose custom fields for selected reports to show as additional fields

User-Configurable Custom Field Columns in Liquid Reports

Summary

Allow users to add custom field columns to standard Liquid Reports as a personal preference, without requiring developer intervention. Users can select which custom fields they want to see, and the system dynamically injects the necessary SQL at render time.

Problem Statement

Current Situation:

Users define custom fields on various models (Order, CustomerShipTo, Part, etc.)
Custom field names are firm-specific and cannot be anticipated
To show custom fields in reports, developers must create firm-specific SQL files and migrations
This is not scalable - each firm requesting custom fields in reports requires developer intervention

Goal:
Enable self-service custom field column configuration for reports, eliminating the need for developer involvement.

Solution Overview

Component	Description
Report-Level Enablement	Configure which reports support custom field columns and which models can be extended
Per-User Configuration	Users select which custom fields they want to see (personal preference)

Criteria

User can view the "Add Custom Field Column" button on reports where supports_custom_fields = true
The user can select a model (e.g., Order, Ship-To) and see available custom fields for that model
The user can add a custom field column with an optional custom title
Custom field column data appears in the report results after adding
The user can remove a custom field column
The user can reorder custom field columns
Configuration is per-user (other users do not see the columns)
System handles deleted custom fields gracefully (sanity check)
All custom field types are supported (Text, Select, Date, Number, Checkbox)
Query performance remains acceptable (3 queries total, regardless of custom field count)

We will enable the option for the reports below

Phase 1

Report	SQL File	Custom Field Models
Sales Order Listing	sales_order_listing.sql	Order, CustomerBillTo
Invoice Listing	invoice_listing.sql	Invoice, CustomerBillTo
Purchase Order Listing	purchase_order_listing.sql	Order (PO), Supplier
Customer Bill To Listing	customer_bill_to_listing.sql	CustomerBillTo
Product Listing	product_listing.sql	Part/Product
Supplier Listing	supplier_listing.sql	Supplier
Open Order Items	open_order_items.sql	Order, CustomerBillTo, Part
Shipment Receipt Listing	shipment_receipt_listing.sql	Order (PO), Supplier, Part

[VA-10164] - Verve Culture: User request enables the system not to add KIT to a PO

Versa has updated the Purchase Order line item so the user should not be able to add a kit parent to a PO product, as it is a kit parent.

[VA-10232] - Allow the user to override the beginning balance of a new reconciliation

In case a closed reconciliation has a new transaction/ modified transaction causing the reconciliation ending balance to be out of balance with the gl balance, the user can override the balance of the next reconciliation to address the imbalance.
This is used in cases when the previous fiscal period cannot be touched, and an adjustment must happen in the current period. The user can enter a new beginning balance as an override, and this is used as the beginning balance.

[VA-10233] - User can import historical trail balance from getting started

Versa has added a feature that will enable users to import Historical Trial Balances.

[VA-10235] - Add a new setting to let the user choose which entity to be included in consolidated financial reports

Versa has added a new check box in the entity edit page; users can check a check box to include the entity in consolidation.
When the setting is off, the entity is not included when running consolidated financial reports.

Improvement

[VA-10030] - Add services to report or report database

Versa has added services to the report database

Wishlist

[VA-10009] - Batch Builds for production build

Versa has enabled a new feature that allows users to create and complete builds in one batch

[VA-10153] - Allow kit inventory to be sent to Amazon as it does for Shopify

Versa will be sending the KIT Inventory to Amazon as it does for Shopify

Version 26W13 Released