Release 2026, April

Generating order from structure head

It wasn't possible to generate a purchase order from the structure head on an expanded structure in a sales order, when the structure head product was set as not to expand on Purchase in Processing method. This has been solved.

Stock transfer order with shipments containing cost price addition

When Cost price addition % was used in the Product table, the cost price on stock transfer order was wrongly increased with the cost price addition %. This has been solved.

Expanded administrator capabilities

The user interface for schema activation for customers and for moving companies into schema is now available to all administrators.

Contact CX for details about how and when to employ this functionality.

Activation/deactivation of Master Data Management

The Master Data Management integration can now only be activated or deactivated from Business NXT Admin.

Resetting the Master Data Management service in Visma.net Admin will no longer have any effect on the integration (no imports will start). When the integration is enabled and the status of the Master Data Management service is disabled in the MDM Integration Status Check report, using the option from there to reactivate it will trigger also a restart for all data imports.

See also: Enabling Master Data Management in Business NXT and Disabling Master Data Management in Business NXT

Exclusion of tables for Master Data Management

When entire tables are excluded for Master Data Management in the Company information table, the data sync will use the Export to Master Data Management function instead of Resend to Master Data Management (restore operation).

Missing matching of open entries by CID reference

Starting early April 2026, when receiving an XML file (VIP file) with incoming payments from Visma.net AutoPay, some open customer entries weren't matched with the correct CID reference even though it was part of the specific payment. This has been solved.

New default layout

A new default layout for reporting of Finnish VAT has been added.

Refresh of browser tab (F5)

Previously, when refreshing the browser tab by pressing F5, all open layouts except the active one were closed. Now, all open layouts are kept.

Incomplete texts in Price/discount processing dialog

In the Price/discount processing dialog in the Company information table, some of the texts weren't displayed correctly. This has been solved.

Missing parameter when calculating delivery date added

The option Update empty order line delivery date if sales order delivery date is entered is now available in the Calculate delivery date processing dialog in the Company information table.

Missing supplier numbers from certain accounting documents

Previously, supplier numbers were missing from accounting documents when processing EHF (XML) invoices. The problem was caused by inconsistent XML namespace handling, which prevented correct supplier identification. Now, XML namespaces are handled consistently, and suppliers are correctly identified.

Result of updated cost price posted to wrong account

In a production order, if a structure part exempt from warehousing changed cost price after the structure had been finished, the accounting for this change would be posted to the rounding account instead of the correct cost accounts. This has been solved.

Withdraw picked serial number product

When a structure line product was set up as a serial number, which means to be picked without reservation with the One reservation line per unit at stock reduction option, and it was reserved manually or with the Reserve serial no. at picking option in Processing method, the order line incorrectly got a value in the Picked field, and not in the Picked without reservation field. This made it impossible to withdraw the picked quantity if needed. This has been solved.

Permission to change status in Product transaction

A new processing, Update temporary costs, has been added in the Product transaction table. This processing will enable users to adjust the temporary cost status, which means setting it on or off. By default, the processing isn't activated for any users, and should only be activated for specific superusers. See also: Update temporary costs

Lookup in column from underlying table

Visible columns from underlying tables are read-only by default. It's now possible to do lookups from these columns by selecting Enable lookup in the column header in design mode. You can then do a lookup, or enter a search value directly in the column (the active column, the relation column, and the Name column will be searched for a match).

Warning message for the Combination matrix

When the Combination matrix was set up and a post in the Voucher table was entered with a non-existing combination, no warning message appeared when moving to another post. This has been solved.

Improved contact lookup in Organisational unit tables

The lookup in the Organisational unit tables now matches the behaviour in the Order table, showing two tabs: One with contacts linked to the selected customer/supplier and another with all associates.

Withdraw picking without reservation processing available in the Order line table

You can now use the Withdraw picking without reservation processing in the Order line table to withdraw reservations for products with serial numbers.

Accurate pick list status

When all reservations on a pick list are finished, the pick list now gets status 4 - Finishing completed instead of remaining in 2 - Reserving completed when the lines are finished on the line level.

Cost prices on allocated sales order

When purchase orders were generated from a sales order line together with the Update order costs setting in the Company information table, any change on the purchase order line (unit or dates) wrongly removed the cost prices from the allocated sales order line. This has been solved.

Entry rules now working for all columns

For columns where the default value is fetched from an underlying table (like values from the Product table suggested on the Order line table), these values overwrote values defined in entry rules. In addition, entry rules didn't work for the Quantity field in the Order line table. This has been solved.

Not possible to restrict access to Design

Previously when no design mode access was granted in Access management, it was still possible to create a new layout. This is now also restricted and no design mode functionality can be used.

Adding new cost units using the + key

Suggest next primary key using + now suggests the next available number in the Organisational unit 7 - Organisational unit 12 (R1-R12) tables.

Preview button always enabled in the Send dialog

Previously, the Preview button in the Create and send documents dialog wasn't enabled when more than 10 orders were selected for printing, unless you had selected Merge documents or Zip documents. Now, the Preview button is always enabled, and if the preview creates more than 10 PDF files, the output will automatically be zipped.

Duplicate invoices downloaded from AutoInvoice

Under certain circumstances, running the Download incoming document processing, manually, scheduled or automatically, could result in duplicate invoices. This has been solved.

Premature setting of Finish date

When initially saving a purchase or production order with order lines, the newly created product transactions would also have Finish date set. This has been solved.

Erroneous setting of previous count date when running the Correct stock balances processing

Prev. count date would be changed when running the Correct stock balances processing in the Shipment table, even if no value had been set in Counted quantity. This has been solved.

Purchase orders from multiple purchase estimates with rows from the same supplier

Generating purchase orders from multiple purchase estimates that included rows from the same supplier didn't work correctly, and could cause primary key errors. This has been solved.

Support for multiple logos

Using multiple image files (for example logos) printed on the same order document is supported. This has already been available for a while.

Future incurred cost not calculated on structure head product

When using Do not include totals: Sales costs in a sales structure head exempt from warehousing, all incurred cost columns on the structure lines were set to 0, except Inc. cost, regardless of accumulation of sales cost. This has been solved.

Delivery alternative number missing on purchase order structure lines

The value in the Del. alt. no. field was missing on expanded structure lines on purchase order when the structure head product was generated from a purchase estimate or from a sales order. This has been solved.

Missing order number on vouchers when doing stock count on location level

Postings on freight and customs account during stock take

When using the setting 16 (Account debit/credit freight 1-4 and customs on purchase) for VAT and accounting processing, postings from stock take incorrectly included account debit/credit freight 1-4 and customs if a value existed in the Freight or Customs field on the shipment. As a result, the total cost of the item wasn't booked into accounting. This has been solved.

Order status update when pick list is printed

When using the processing method One reservation line per unit at stock reduction, which means picking without reservation, the order status wasn't updated during pick list printout. This has been solved.

Economic purchase quantity not fetched from Delivery alternative table when generating purchase order

When generating a purchase order from a sales order, and using the Purchase gen. processing setting Purchase economic order quantity from delivery alternative or stock balance in the Company information, only Econ. purch. qty in the Stock balance table would be considered, disregarding the equivalent field in the Delivery alternative table completely. This has been solved.

Generating production orders from purchase estimate when using Aggregate products

When generating production order from multiple estimate lines with the same product and using Aggregate products in the Generate purchase/production orders dialog, the expanded structure on the generated order lines wasn't correct. This has been solved.

Time to next requires order confirmation to be run twice

On order lines with Time to next set, new rows wouldn't automatically be ready for order confirmation, requiring two attempts to get Confirmed set on the order line. This has been solved.

Structure not expanded with Time to next on structure head

When using Time to next in combination with a sales structure, when invoicing the order, the structure head would be added to a new order line, but not expanded. This has been solved.

Scheduling tasks to run on Sundays

Previously, you couldn't schedule new tasks or reschedule existing tasks to run on a Sunday. This has been solved.

Inserting rows on filtered columns

When inserting a row above or after the selected row in a column with filters, the new row was added the bottom of the table. This has been solved.

Landscape printouts

You can now select print orientation Landscape in the Send dialog.

In design mode, you can define the default orientation for each document type under Design > Table settings > Printout.

Incorrect calculation of sales order with justified exchange rate

When having Justify exchange rate set in Order options on a sales order, and the order contained a structure, the structure head's amount in currency would be incorrectly recalculated during the exchange rate update. This has been solved.

Adding order number to voucher during post cost of sales corrections

The order number wasn't added on the voucher line when the Post cost processing was performed on product transactions from sales corrections. This has been solved.

With the setting GL trans. per order, when posting from product trans. in the Accounting processing field in the Company information table, the order number is now added on the voucher line.

VAT- and accounting information in the Account set selection dialog

Previously, when double-clicking the Account set field in the Order line table, the Account set selection dialog incorrectly showed entries from the VAT- and accounting information table. The dialog now correctly displays values from the Text table (Text type 18) both in the Order and Order line table.

Account set improvements

Several issues related to account set have been solved.

The setting Firstly get account set from... below is made in Order processing 2 in the Company information table, where the default setting is Firstly get account set from Invoice customer / Supplier.

• When Firstly get account set from Invoice customer / Supplier was enabled, and Account set was defined for the customer in the Associate table, Account set on the generated purchase/production order line was wrongly fetched from the sales order line.
• When Firstly get account set from Stock was enabled, and purchase orders were generated from the Purchase estimate or Purchase estimate line table, the Account set from the Associate table was incorrectly used. Now, Account set from the selected Warehouse table is used.
• When Firstly get account set from Structure was enabled, and Account set was set up in the Structure table, generated purchase orders from sales order or purchase estimate didn't get Account set added from the Structure table into the expanded structure. Structure line products wrongly inherited Account set from the order head.

Registering quantity with Order option Credit note set

If the Order option Credit note was set, and you attempted to register a quantity that was less than -1, you couldn't set a quantity between 0 and -1. This has been solved.

Improved filtering for Contact 2 on orders

Contact 2 now shows contacts for Invoice customer no. when set, and displays a list of all associates if not set.

Wrong open customer entry matched when unstructured payment references

When receiving incoming payments from Visma.net AutoPay, Business NXT uses advanced methods to support the users for automatic matching of the corresponding open entries. Related to this, some situations have been reported where matching of wrong open entries have happened. Additional checks have now been implemented, which reduce the risk of matching by incorrect payment references.

Data model extensions (DME)

Data model extensions allow you to extend and enhance the capabilities of the core data model. In a modular approach, they make it possible to add or modify data elements, relationships and functionality, tailored for your specific business needs.

Data model extensions can also be accessed through the GraphQL API.

In Business NXT, you can add a limited number of data model extensions without any additional cost.

See also: Data Model Extension (DME)