Open navigation

November 2026 release (8.150) - Rillion prime

Print article

The November 2026 release (8.150.0) includes a number of application corrections and changed application functionality

Application refers to changes and corrections made in the Rillion prime application that are visible or noticeable to the end user.

Operational refers to changes and corrections made behind the application that end users will not notice but are important to consultants and partners.



Note: We are now extending the rollout of our updated Mobile web pages to all existing customers who have not yet received the new version.



APPLICATION

New or changed functionality

Prime web

  • Timestamps shown in your local time zone

Dates and times in Rillion Prime — such as last login, invoice change history, and approval or processing times — are now displayed in your own local time zone. The time is automatically adjusted for daylight saving. You no longer need to manually calculate the difference between server time and your own time zone. The date format (day/month/year order and separators) follows your Rillion language setting. Note, this does not apply for Master (yet).

Invoice

  • Dynamic flow correctly skips the first authorizer when they have already accepted the account posting

When a company requires account posting lines to be accepted before authorization, the approval flow now correctly handles the case where the person who accepted the lines is the first authorizer in the flow. Previously, dynamic flow would add the same role to the flow again unnecessarily, creating an extra authorization step. The flow now proceeds without the redundant step.

Invoice Log

  • Invoice Queue deletions are now recorded in Show Captured Invoices

When an invoice is deleted from the Invoice Queue before it has been transferred, the Reports → Show Captured Invoices report now shows who deleted it and when. The entry appears in the Error column, for example: "Deleted from Invoice Queue by Donald on 11/03/2026 12:09:02". This requires the InvoiceLog setting to be active on the environment.

  • Bulk update account coding in the invoice log

Correcting account coding across many invoices used to mean opening and editing them one by one. Now you can search by account, objects or VAT code, select the invoices you want, and replace, fill in or clear values in a single action. This saves time on corrections and keeps coding consistent across invoices. Available to users with level 3 (Delete) permission to manage the invoice log. Opt-in for the first release, so contact us to have it switched on.

Reports

  • Reports now export in .xlsx format

When you click "Open as Excel" in Prime, reports are now downloaded as proper .xlsx files. Previously they were saved with an .xls extension but contained an older XML format, which caused a security warning in Excel and was blocked by some organisational security policies. The old format also had a row limit of 65,536. All of these issues are resolved with the new format.

AI Matching

  • Apply default objects by company setting if AI failed to predict mandatory object

For an invoice with AI-generated posting line, and AI failed to predict a mandatory object, resulting to invoices getting stuck before transfer.

Prime now applies default values for object set on reference, supplier, account or object, when object is mandatory by account setting.

To have Prime apply the default values, the company setting "Use specified default object values to complete account posting string" needs to be switched on.

If Prime adds default objects it is noted in the AI explanation. The object field does not get a confidence level, in order to separate it from AI generated values.



Corrections

Account Coding

  • Invoice saved with a different asset when two assets share the same code

Fixed an issue where selecting an asset on an invoice and then saving could result in the system switching to a different asset that happened to have the same code. The correct asset is now retained when saving.

  • Account coding lines with notes not fully combined on invoice transfer

Fixed an issue where identical account coding lines were only partially merged during invoice transfer when the lines contained a note. All matching lines, including those with notes, are now correctly combined into a single line on transfer.

Buyer

  • Free Text Requisition accepted an inactive or expired supplier

Fixed an issue where typing a supplier number directly into the Supplier No. field on a Free Text Requisition bypassed the validity date check, allowing an inactive or expired supplier to be accepted. The supplier's validity is now checked correctly when entering the number manually, consistent with the behaviour of the supplier lookup popup.

Contract

  • Account posting not returned when matching to an inactive contract

Fixed an issue where matching an invoice to a contract that was no longer active failed to provide the expected account posting. The account posting is now correctly returned regardless of the contract's active status.

Invoice

  • Invoice number search in Show Invoice report failed with leading or trailing spaces

Fixed an issue where searching for an invoice by serial number in Reports → Show Invoice returned no results when the search term had a leading or trailing space. Spaces are now automatically removed before the search is performed.

  • Linked invoice reference validated on every save even when unchanged

Fixed an issue where the linked invoice reference was validated on every save action — including Unknown, Sign, and Reject — even when the link had not been changed. The reference is now only validated when it is first set or when it is modified, which removes unnecessary processing and avoids lookup failures caused by role-based restrictions.

Invoice Log

  • Linked credit note reference not populated after XML import

Fixed an issue where the linked supplier invoice number — used to link a credit note to its original invoice — was not populated in the Invoice Capture log after an XML import. Imported invoices and credit notes that carry a LinkedSupplierInvoiceNo field now correctly display the linked invoice reference, provided exactly one matching invoice exists for the same supplier and company.



OPERATIONAL

Corrections

AI Matching

  • Objects containing a comma could be misidentified in AI matching

Fixed an issue where object codes containing a comma could be confused with other objects during AI matching validation. The object code is now correctly handled in the validation logic, preventing misidentification.

  • Allow zero amount invoices to be sent to AI matching

Invoices with amount 0 were never sent to AI matching. They now are, when amount, VAT and all fee amounts are 0. The AI result is used only if it can be applied safely. Invoices with an amount behave as before.

Master

  • Empty XML import file caused an error in invoice import

Fixed an issue where submitting an empty XML file to the import process caused an unhandled error. The import now safely handles empty files without raising an error.



For a complete overview, please go to Updates & Changes. Filter on 8.150.0 for the full list.

NB! This requires login with username and password to Rillion Support 

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.