What's New in 2026.9

Additional forms are now available under the PM License Type. License Type is set in VA User Profile. For more information, see License Types.

Forms added in 2026.9 for the PM License Type

The AP Vendor Spend Analysis - ePayments report (#1316) now appends additional data to the end of each vendor row in the report. It retrieves the value from the Add'l Info field (APVM.AddlnInfo) in the Payment Address section of the AP Vendors form.

Users typically export this report as a .csv file and send it to Corpay for analysis.This information may be used by Corpay to facilitate payment processing.

The GL Balance Sheet (#1270) and Income Statement (#1268) reports Launcher windows now have a new field. The Whole Dollars (Y/N) field lets you choose whether the currency/monetary/dollar values in the generated report will round to the nearest whole dollar (Y) or not (N). This field defaults to N.

The HQ Super Clearing House form has a new dropdown field, SAFF Header Standard, to specify the SAFF file header format based on your clearing house. This update does not require you to change your usual file generation routine.

For more information on the field, see SAFF Header Standard.

To provide a more consistent data-entry experience, the dropdown options on filing status fields have been aligned into a single list across multiple Payroll forms and HR Resources. For more information, see File Status.

The active Contract number and its description are now displayed above the grid in the JC Contract Recipients Detail form. Assuming you have access, you can open this form using the Recipients button in two separate forms: JB Contract Info and the JC Contracts form, JB Info tab.

To ensure cost-to-complete projections remain accurate, closing a Job Purchase Order now automatically reconciles committed units and costs in Job Cost (JC) with the Purchase Order (PO) item lines. For more information, see the Purchase Order Features section of these release notes.

Reconciliation adjustments post with a typical PO Close entry source, though are listed with a newly introduced description: JC Cmtd Adj. These entries appear on JC detail logs and commitment reports.

The Received By field in the PO Initialize Receipts form no longer has a default value. The field remains optional and is still intended to indicate the person receiving the purchase order. Enter a short identifier of your choosing (initials, first name, etc.), not the Vista username.

During PO Close, Vista compares the sum of job-related commitments in JC against the PO totals (at the PO, Item, and Line level). If variances exist—due to rounding, cost changes, tax redirections, or transactional sequence—Vista generates an automatic adjustment entry in JCCD to align total and remaining commitments.

User workflows do not change with this update. Simply close POs using your standard process, and Vista handles the JC commitment alignment in the background.

Reconciliation adjustments post with a typical PO Close entry source, though they are listed with a newly introduced description: JC Cmtd Adj. These entries appear on JC detail logs and commitment reports.

To improve system performance when auditing changes made in Vista's bPREH table (related to PR employee data), we have updated the VA Audit Log Viewer form.

• Additional search criteria, such as the Beginning and Ending field values for the Table, Date, and User fields. The new Action field lets you focus on specific types of data updates. For more information, see the Action Help page.
• Search results are now limited to the top 1,000 records. Above the grid, you'll see a status once the search completes: The number of rows/records found, if any, and the Time the search completed.
  Note: If you cannot find the specific entry you are looking for, simply narrow down your search criteria; for example, by shortening the date range or specifying a username.
• Like the existing functionality of the grid's filter bar, the form's search fields now support use of the wildcard % character in a search term. For example, using bPR% in a Table field will look for any table that starts with bPR.

This release introduces a third License Type for users in VA User Profile. The Consultant type is intended for 3rd-party consultants needing short-term access to Vista without requiring additional paid licenses. Consultant licenses are tracked in usage counts, but they do not count against contracted license limits. Security setup (form, report, data, attachment type) for these users must still be handled in the usual manner.

Additionally, standard Vista reports #973, VA License Usage By Day, and #1338, VA User License Allocation, now account for Consultant license usage.

• The Info tab has been simplified and reorganized with a number of fields moved to a new dedicated tab, called Form & Report Options.
• The Licensing section near the top of the form now includes the Consultant license type for at-a-glance tracking.