Release 2026, May

The following enhancements and improvements to existing functionality have been released this month.

2026-05-28

User deletion across platforms

Sometimes when deleting a user in Visma.net, or Connect, or when modifying the user e-mail there, the changes were not reflected in the User table in Business NXT. This has been solved.

2026-05-27

<Ctrl+S> (Save) displaying browser's "Save as" dialog

Previously, when a field value was updated and Ctrl+S was pressed before leaving the field, the browser's "Save as" dialog was incorrectly shown. This has been solved.

Romanian characters in tables and memos

The Romanian characters Ș, ș, Ț, and ț are now replaced by S, s, T, and t instead of a question mark (?).

Incorrect VAT posting for documents with transaction status 1

Previously, in the Swedish VAT setup, transaction status 1 on supplier lines for workflow-imported EU invoices could cause incorrect VAT postings when using Cost % in VAT handling, resulting in wrongly distributed VAT amounts. Now, when you use the Update supplier transactions processing, including scenarios using the mapping tool, the VAT is correctly posted.

Payment number emptied after cancellation in Visma.net AutoPay

When a cancellation of a specific payment is performed by an approver in Visma.net AutoPay, or a rejection happens in the bank, the value in the Payment no. column in now remains in the Open supplier entry table.

Improved handling of Accounting document statuses

Handling of Accounting document statuses for batches created using Copy or Reverse with batch origin 14 - Previous batch has been improved. The Accounting document status is now updated only after a reversal batch has been successfully posted. Posted reversal batches automatically return the related document to the Incoming document table and makes it available for processing again. Deleted or non-posted batches no longer affect the document status.

Custom column name in lookup templates

When a layout was saved as a template, any fields with a custom column name was restored to the original name after signing out and in. This has been solved and the custom column names are now remembered.

2026-05-26

Updated default layout

In the Customers - New layout (13065), the table on the Delivery addresses tab was incorrectly joined. This has been solved.

2026-05-21

Lookup improvements

Some improvements related to lookups are now available:

  • Previously, it was possible to search and select a contact person in the Contact field on the order that wasn't assigned to (Contact for) the customer in Associate table. This has been solved.
  • With some lookups, several irrelevant tabs were shown. Now, only valid tabs for the specific lookup are displayed.

Export to Excel including DME content

Export to Excel now supports DME (Data Model Extensions) tables and columns.

2026-05-18

Correction for bank reconciliation statement when using currency pockets

For customers using currency pockets connected to their bank account, the closing balance is now fetched from the account statement transaction based on currency number filtering, when creating the bank reconciliation statement. This depends on that the correct Currency no. is set for each row ("currency pockets") for the common bank account number in the Bank partner table.

Correction of financial postings for production orders with expanded structures

To show correct order sum on the production order when a structure is expanded, production cost must be excluded from the total on either the structure header or the structure rows in the processing method, otherwise the cost is wrongly summed from both the header and the rows.

If the structure line was excluded, no batch was created with a correction of the cost of the production order when the receive invoice was processed on the purchase of an structure line product with price correction. As a result, the posting, when the receive invoice was processed on the production order, ended up on the Rounding account instead of in the Raw material inventory.

If the structure header was excluded, no batch was created with a correction of the cost of the sales order when the invoice was received for the production order. As a result, the cost of sales wasn't updated in the accounting.

This has been solved.

Entering non-existent product number

After first entering a non-existent Product no. on an order line and receiving an error message, and then entering a valid Product no., the information for that product, such as Description and Price, wasn't displayed until the row was saved. This has been solved.

Creating more than one credit note for an order copy

When creating an order copy with reverse prefix, Credit note is already created and suspended from additional credit note is set on the original order. Previously, this setting couldn't be unchecked. This has been solved.

Accrual accounting dialog not automatically displayed

When Accrual accounting is set on a General ledger account or Voucher type, and when one of these are used on a voucher line, the Accrual accounting dialog is now automatically shown after entering the amount.

Update of all companies when copying forms

Previously, when running the Copy form processing in the Form table and enabling Change to the new form no. on all document copies and open the old for editing in the dialog, the Form no. in the Order document table was updated for the active company only. This meant that the original form number remained linked to active order documents in other companies, leading to unintended layout changes when users modified the old form. This has now been solved, and the Form no. in the Order document table is updated for all companies.

Keyboard shortcuts not working when GAiA is open

When the GAiA assistant was open, most of the keyboard shortcuts didn't work. This has been solved.

2026-05-12

Enhanced document distribution using the Attach documents processing

Previously, files attached using the Attach documents processing in the Order table were visible in the side panel, but not included when printing, emailing, or sending documents via AutoInvoice from the Order table. This has been solved, and attachments are included across all distribution channels.

Improved interpretation of supplier information in XML invoices

Handling of invoices where XML namespace definitions vary within the document has been improved. Supplier information is now interpreted correctly and the supplier is identified or created as expected.

2026-05-08

Period keys supported on purchase orders

Previously, you could only use period keys for sales order lines. This meant that vouchers generated from purchase order lines required manual adjustment to perform accrual accounting on the posting. Now, you can also use period keys on purchase order lines.

2026-05-07

Missing line on pick list

When printing a pick list for an order line with the processing method One reservation line per unit at stock reduction, there was no line added for it on the pick list, which also resulted in no row in the Order document line table. This has been solved.

Supplier information missing on incoming invoices

In some cases, supplier information on incoming invoice documents wasn't read correctly, due to unexpected line endings in the XML file. The supplier is now identified correctly, and the document can be processed without errors.

Issues automatically downloading to AutoInvoice

The number of companies on-boarded in Business NXT has grown, causing longer execution times for the AutoInvoice download service and some time-outs when attempting to process downloads for all companies. This caused that the automatic download sometimes wasn't executed for some companies. This has now been solved, and all companies have been successfully processed by the automatic AutoInvoice download.

2026-05-06

Bank reconciliation improvements

The bank reconciliation logic and sorting has been improved, when using automatic reconciliation when there's a mix of plus/minus general ledger transactions.

Incorrect calculation of payments in foreign currency

Previously, the amount on the voucher line for incoming payments was incorrectly calculated when a payment was done in foreign currency, but the outgoing invoice was in domestic currency. Now, the exchange rate for the Currency no. to the currency payment is fetched from the Currency rate table, when the currency for the corresponding open entry is domestic currency.

Reservation of quantity cancelled

When a sales order line was split in multiple reservations, and Finish NOW on the order line was used to finish part of the total quantity, the not yet finished reservations were deleted, and the quantity was made available for reservation. This has been solved.

Decimal mismatch in quantity handling

In some cases, when using units with Quantity per unit <> 1, a split into decimals that caused a mismatch between Finished and Invoiced/realised on the order line would occur, meaning that a fraction of the total quantity remained impossible to invoice. This has now been solved, so that Finished and Invoiced/realised are identical when both completely finished and invoiced.
Note:
Even though the order line is correct, decimal issues may still be present in Reservation and Product transaction tables, causing Shipment to look wrong. Run the Regenerate stock balance processing, and if there are still shipments with tiny decimal values, correct these with a stock count in the Shipment table.

Issue sending invoices and printouts

Invoicing would stop with the error message "Registration date must be within 0 days of today's date", requiring the No. of days +/- rejection field in the Company information table to have a value higher than 0. This has been solved.

Values from joined tables on printouts when using supplier's product number and description

Previously, when inclusion of Suppliers product no. and description was enabled during printout, the Delivery alternative table was incorrectly prioritised for all line data, causing fields from joined tables in the print layout on Order line to appear blank. Examples of fields from joined tables could be the Information fields in the Product table. This has been solved.

Date incorrectly validated by the suspension date during printout

The Date field (= voucher date) in the order printout dialog should be validated by the fields No. of days +/- warning and No. of days +/- rejection in the Company information table, but it was wrongly validated by the suspension date. This has been solved.

Zero count displayed as blank during stock count

Previously, when a zero was entered into the Counted quantity field during stock take, it was displayed as a blank cell instead of the digit zero. This occurred during stock take in the Stock balance table, the Shipment table and the Item location table.

This made it impossible to see directly in the Counted quantity field if zero was entered or if the cell was skipped (no value entered at all). The value zero will reduce stock quantity to 0, but if the cell is skipped, it will keep the current stock quantity when running the Correct stock balances processing. This has now been solved, and the value zero is displayed if entered.

XML markup displayed in invoices

In some cases, CDATA technical markers were displayed in XML invoices as part of the invoice text, instead of only the correct invoice information. This has been solved.

Status update from Visma.net AutoReport when payment information is received

Support for fetching the latest status from Visma.net AutoReport also when the status is 11 - Payment information received has been added. The reason for this change is that there has been some issues where the status was updated to 11 - Payment information received, but the actual payment file from the tax authorities wasn't included. Now, if the status is 11 - Payment information received, but no payment file is present, the full information is re-fetched from Visma.net AutoReport.

Improved rule suggestion generation and text interpretation

Very short text fragments (for example two-letter combinations) are no longer interpreted, reducing noise and the number of irrelevant suggestions.

Searching using drop-down

Previously, the search in drop-down had a limit of 100,000 rows, making some processing actions impossible since not all rows could be selected. This has been solved, and all rows can be loaded and/or found with a search.