Skip to main content

Release notes

We use Semantic versioning for our releases which indicate through version numbers if breaking changes are shipped. A major version (e.g. 1 to 2) may include breaking changes. A minor version (e.g. 1.22 to 1.23), whilst not including breaking changes, may include major feature additions or upgrades. Patch versions (e.g. 1.22.8 to 1.22.9) are bugfixes and minor feature tweaks.

*Please note that not all release numbers will be noted here, releases that include only infrastructure changes will be assigned a version number but not documented here

Version 1.0.35​

2026-06-11 Changes from 1.0.34

New Schema Fields See schema here​

New Settings See settings here​

Documentation Update​

Minor Features / Improvements​

  • [OC2-199] We now better handle the timeouts on the rossum events which are limited to 30s, so we should be able to return a clearer message to the user in these situations rather than simply something went wrong
  • [ISD-506] MS7 / CR systems should now display the Registered Invoice Amount in the PO Details section, note that the Registered Invoice Quantity is still not available in the API.

Version 1.0.34​

2026-06-02 Changes from 1.0.33

New Schema Fields See schema here​

New Settings See settings here​

Documentation Update​

We have improved documentation around the timeout messages (TIME_000 / TIME_001 / TIME_002) on rossum events

Minor Features / Improvements​

  • [OC2-197 / ISD-447] Customer Request. You can now set arrivalDateOutput in the queue settings. If set, the arrival_date xml tag on ERP7/CR or the registeredDate for ERPx systems will be set to either:

    • rossumArrived the arrived_at date set on the document in Rossum.

    • export the export date.

    If not set, these export fields will not be included.

  • [OC2-201] Customer Request. You can now set allowAnyTaxCoding in the queue settings. Note that selecting a tax code that does not match the tax percent or currency on the invoice line will generate a ACL_004 warning or error because allowing this to go to ERP is likely to cause the import service to error the document as unbalanced. However this setting has been specifically requested by customers to allow them to capture the tax code prior to import, and update the purchase order with this tax code (using tools within Unit4)

    • If this is set to true, the system will always allow any tax code (that respects the invoice currency) and tax system to be manually selected in account coding, regardless of tax percentages, account rules, the document being a purchase order invoice or the settings in manualTaxCodeIds.
    • If this setting is not set, or is set to false the tax codes available will be limited by the manualTaxCodeIds and the tax rate and currency on the invoice.

Version 1.0.32​

2026-05-20 Changes from 1.0.31

New Schema Fields See schema here​

New Settings See settings here​

Documentation Update​

We have added some more questions and answers to our frequently asked questions.

Minor Features / Improvements​

  • [OC2-200] To avoid downstream issues with the ERP7 / ERPCR systems after the implementation of our single-line-match solution, the system will now pre-aggregate invoice lines for the same order and order line number. This is because the ERP7 / ERPCR import system is unable to handle multiple lines for the same order_id and line number. The line net, tax, gross and quantity will be aggregated and everything else on the line will be taken from the first line during the aggregation. ERPx remains unaffected by this change.

  • [OC2-192 / ISD-480] Restores previous behaviour where purchase order invoices will always use the tax code from the purchase order line

    This resolves an issue with the ACL_002 error stopping an invoice export for purchase orders when the percentage from the tax code on the order and the tax percentage on the invoice do not match. The most common scenario is when purchase orders are raised incorrectly without VAT but the invoice comes in with VAT. The system will now allow these invoices through again, HOWEVER THIS MAY CAUSE DOWNSTREAM ISSUES with the processing in ERP, the invoice will need to be manually handled.

    This is behaviour that is required by some of our customers who automate the updating of tax codes on the purchase order from the invoice.

    The system will raise the existing ACL_004 warning and we strongly recommend that this is elevated to an error in your settings if you do not want these invoices to post into Unit4 without intervention. A future development will allow for users to select any tax code on a purchase order line when the ACL_004 message is raised as an error, this is to enable downstream handling in the ERP system (such as an AG16 or Extension flow to update the purchase order).

Version 1.0.31​

2026-05-11 Changes from 1.0.29

New Schema Fields See schema here​

New Settings See settings here​

Documentation Update​

Minor Features / Improvements​

  • [OC2-193 / ISD-469 / ISD-442] Single Line PO matching We have implemented the first step of a solution to re-enable the matching of all invoice lines to one purchase order line, where the purchase order only has one line. This is a queue level setting which can be switched on by implementing the extension setting singleLineMatch. Please note that we plan on adding further flexibility to this setting in future releases.

  • [OC2-187] We now raise an elevatable warning message INL_014 if the purchase order line matched to an invoice line, is not status O

  • [OC2-190 / ISD-447] for ERPx systems we will now always export the product code from the matched purchase order line, rather than the invoice data, to ensure the system treats it as a matched line.

  • [OC2-146 / ISD-413] The code to generate the accounting information now accounts for the use of value matrices on tax code and tax system

  • [OC2-188 / ISD-468] Allow the invoice date to be over-written with the date of export from Rossum. New extension setting exportDateAsInvoiceDate

Version 1.0.29​

2026-04-30 Changes from 1.0.28

New Schema Fields See schema here​

  • discovered_po_line_tax_code

New Settings See settings here​

Documentation Update​

  • [OC2-171 / ISD-458] Added further information to the queues page regarding editing the Rossum schema.

Minor Features / Improvements​

  • [OC2-172] We have implemented a solution to re-enable the auto completion of order_id against all invoice lines, where an order_id is identified in the invoice header AND is found in ERP. This solution works alongside the fix that necessitated the removal of this behaviour in the first place. Please see the updated documentation on purchase order matching

  • [OC2-182] We have removed the error when the Unit Net or Unit Gross values are not filled in, existing line amount balance checks are not impacted. If you do wish these to be mandatory, you may update your queue schema to reflect this.

  • [OC2-169] We have enabled a compressGL setting which is ERPx ONLY If set to true this sets the flag when the invoice is exported. Unit4 describes this as: if set to true, the GL and tax rows are aggregated according to the GL analysis. The description entered for the GL row is not transferred to the General Ledger. (Behaviour can be replicated in ERP7 with the compress parameter on EI02).

  • [OC2-47 / ISD-412] Tax code may now be added to the schema under the discovered_po_lines section to display the tax code. Note where lines have split accounting with different tax codes, these will be shown as pipe separated e.g. 20|5

Version 1.0.28​

2026-04-23 Changes from 1.0.27

We will now be including two new sections in the release notes to assist with clearly seeing what new configuration may be required, these sections will include only changes since the prior version.

New Schema Fields See schema here​

  • split_percentage

New Settings See settings here​

Documentation Update​

Minor Features / Improvements​

  • [OC2-148 / ISD-422] Split coding purchase orders We have now improved the handling of purchase orders which have lines with split GL coding, or may be "split" due to Unit4 API errors (noted on ERPx). The system will now:
    • Deduplicate these order lines prior to attempting to match to invoice lines, increasing the match rate
    • Display multiple accounting lines (for information only) including the percentage split if the new field is included.
    • Not display multiple lines in the purchase order details section.

Please note that with all purchase order invoices, the coding and split will be dictated by the Unit4 system when the data is sent, therefore the export process will still only send one line per invoice line, the export will not split the analysis on the data sent to ERP.

  • [OC2-167 / ISD-447] Send accounting information in a different format when sending to ERP-X only.

  • [OC2-155] Increase allowed payload size and improve error reporting around "Payload Too Large" errors when dealing with very large invoices.

  • [OC2-165 / ISD-430] Fix false line rejections on rounding issues when line quantity is less than one.

Version 1.0.27​

2026-04-01 Changes from 1.0.26

Documentation Update​

  • We have expanded the troubleshooting documentation to help identify differences between data / messages generated via the extension vs the core Rossum system.

Minor Features​

  • [OC2-48 / ISD-237] Customer request to allow non-active suppliers to be matched in the OCR, but an error raised if this is the case. E.g. they wish to know the supplier exists and was the best match, but that it is closed.

    • Because ERP will error if suppliers at a status other than N or P are sent, we have also added an additional error message SU_017 if the best matched supplier is not at a valid status.
    • We have also added an additional warning message SU_018 (that can be elevated to an error) if the supplier is parked, although ERP will accept the transaction in this case
    • This new feature is OPT-IN and the existing behaviour will not be changed unless you add the extension setting validSupplierStatus to allow the system to import suppliers at different status codes.

  • [OC2-41] Better error reporting on invalid URL formats and invalid protocols for URLs set in settings / secrets. Additional error messages CF_003 and CF_004 to support this.

  • [OC2-127] Added a "manual override" at a line level.

    • On occasion you may find that the automated line-matcher overwrites input data making adjustments to line details more awkward. For this reason we have allowed for lines being entered in "manual mode". This can be set using the "Line Input Mode" dropdown in the UI. When this is set to "manual" no automated input will be attempted so be sure that the details entered are correct. Please see the documentation and screenshot here
    • To implement this change on an existing queue, you will need to add a new field line_input_mode with options of auto and manual, please see the setup (search for this field) in the required schema documentation

Version 1.0.26​

2026-03-26 Changes from 1.0.25

Documentation Update​

  • [OC2-120 / ISD-379] We have added another FAQ to explain that if the EI02 version number is not correctly included, this can cause a 500 error on the MS7 / CR SOAP request.

Minor Features​

  • [OC2-143 / ISD-414] We have improved the matching of sort codes to account for non-numeric characters being included in ERP or in the incoming data.
  • [OC2-144 / ISD-417] We have added a length check for product code to the list of fields we check before the data is sent to ERP to avoid import issues in ERP.
  • [OC2-150] The system will now return warnings to the Rossum screen if any data is too long to be sent to ERP and will be truncated on export (Message code: INL_013)

Version 1.0.25​

Documentation Update​

We have added some further information to the orders page in the user guide section about the order matching.

We understand that the previous issue regarding false-positives when matching against single-line orders (fixed in 1.0.22) may have been masking some ERP7 functionality regarding the coding of additional lines.

These may previously have been matched incorrectly to an order line and therefore ERP would have taken the coding from this order line number.

With the fix in place, extra lines will require an account code to be passed to ERP7, but this will then be overwritten by the EI parameters (please refer to the Unit4 electronic invoicing documentation for further information). To assist with this feature OC2-135 below has been implemented

Minor Features​

  • [OC2-135] Allow the account code for additional (unmatched) lines on a PO invoice to be defaulted from the system parameter EI_SUPP_DEF_ACCOUNT (Note additional object access must be granted)

  • [OC2-133][ISD-404] Related to [OC2-126] We have made changes to further improve order matching and anticipate additional enhancements in upcoming releases.

  • [OC2-132] Add a new warning PO_008 (that can be elevated to an error) where additional / unmatched order lines are found on an invoice

Minor Bugfixes​

  • [OC2-131] Improved the handling of escalated warnings which would sometimes escalate in error.

Version 1.0.22​

Minor Bugfixes​

  • [OC2-125][ISD-396] Fixes an issue with manual overrides should the lines fail to match

  • [OC2-126][ISD-395] Reduce false-positives when matching against single-line orders.

Version 1.0.21​

Minor Features​

  • [OC2-91] Allow warning messages to be elevated to blocking errors. The extension can now be configured so that certain messages block an invoice from exporting. Please see the documentation for the new setting for elevating warnings. Adding to an existing system Please note you will need to configure the override_warnings field in your schema

  • [OC2-108] All messages (Error, Warning, Information) produced by the microservice will now have a code which can be looked up in the troubleshooting section.

Documentation Update​

We have made some important changes to the documentation system.

  • Added warnings for the appropriate strength and transmission of passwords
  • Added a file explaining some JSON basics for users who are not familiar
  • Implemented plugin-image-zoom (the same as the portal documentation) which allows users to click & expand images in the documentation
  • Translated to Norwegian and Swedish
  • Other minor improvements

Version 1.0.19​

Minor bugfix​

  • [OC2-113 / ISD-344] Fixed an issue where under certain circumstances, searching for duplicate transactions would fail in multi-company environments.
  • [OC2-114] Fixed an issue for MS7 where the call to lookup multiple purchase orders at once from ERP, was failing.

Minor Features​

  • [OC2-40] The system will now verify the maximum document size on the document type and error if the document being processed exceeds this size.

  • Documentation improvements

  • Improvements to pre-release tools and testing

Version 1.0.17​

Minor Features​

  • [OC2-96 / ISD-350] We have introduced a new extension configuration to allow users to set their own valid purchase order status and improved the messages around order matching back to ERP. Please see the extension configuration documentation and the user guide documentation

  • [OC2-98] We have fixed a bug with the new legal entity matching where under certain conditions the entity code was not being correctly applied to lines.

Version 1.0.14​

Minor Features​

  • [OC2-94] We have introduced the capability to map legal entities in ERP from Rossum identified customer names.

  • [OC2-90] We made some minor improvements to rounding logic

Version 1.0.13​

2025-11-27 Changes from 1.0.12

Minor bugfix​

  • [ISD-335] - When searching for suppliers manually, clearing the search box after a supplier has been returned, would incorrectly flag as "Supplier not matched". This patch resolves this.

Version 1.0.12​

2025-11-18 Changes from 1.0.11

Minor updates​

  • [OC2-43] - Improvement: Added a test extension function to test the connectivity back to the ERP system. Please see the documentation here

  • [OC2-80] - Improvement: purchase orders with a decimal / period are now excluded as non numeric and no longer passed into the search in ERP

  • [OC2-81] - Resolved an issue with mandatory default tax codes not being applied correctly to GL lines until the user opened the screen.

  • [OC2-82] - Improvement: ERPx v2 of the incoming-invoices API is now used

  • [OC2-83] - ERPx resolved an issue with the line numbers being sent sometimes causing an E status which was cleared when saving the invoice in ERPx.

  • [OC2-84] - Improved filtering on the pay recipients endpoint to avoid issues with the URL exceeding the maximum length

Version 1.0.11​

2025-10-21 Changes from 1.0.10

Minor updates​

  • [OC2-79] - Improvement: We have improved the documentation around timeouts, added error code: TIME_000

Version 1.0.10​

2025-10-21 Changes from 1.0.9

Minor updates​

  • [OC2-74] - Improvement: the API / IDS / SOAP Urls can now be configured in extension settings rather than secrets so they are more visible

  • [OC2-17] - New Feature: Pay Recipient (factor) checks are now in place. There are two new extension settings to enable these, you will also need to grant access for your OCR user to the object accounting/supplier payment recipients

    • payRecipientCheck: If this is set to true the system will flag an INFO message against the matched supplier, if a pay recipient is identified as set on the supplier record. This will be upgraded to a WARNING message if the pay recipient is not status N.
    • payRecipientBankCheck: If this is set to true, the system will match the bank details AND currency from the invoice to those from the pay-recipient (instead of those on the supplier masterfile).
info

Please note to enable this you will also need to grant access for your OCR user to the supplier-payment-recipient object in ERP.

Version 1.0.9​

2025-10-20 Changes from 1.0.8

Minor updates​

  • [OC2-75] - Improvement: better handling of the container management process on our servers.

  • [OC2-76] - MS7 resolved an issue with the invoice date not being correctly applied.

  • [OC2-77] - MS7 resolved an issue with long descriptions causing EI02 to fail (Line description is now truncated to 255 characters).

  • [OC2-56] Improvement: messages file handling.

    • Implemented a new parameter to configure what level of messages are sent to the ERP system attachMessagesDocument
    • We have renamed the messages text file to zzzz_messages... when it is sent to ERP. ERP is displaying documents in alphabetical name order, so in some instances the messages file was shown as the first file rather than the invoice file.
    • Downgraded the Warning "Tax amount is non-zero and ignoreTax is switched on. Tax will be zero'd on submission." to an Info message.

Version 1.0.8​

2025-10-01 Changes from 1.0.7

Minor updates​

  • [ISD-292] - Resolved an issue where the bank account field was not being flagged when it didn't match the supplier record.

  • [OC2-50] - Improved the message on the IBAN mismatch, making reference to the "normalised field" which is the one the application checks

  • [ISD-293] - Resolved an issue where the OCR data was too big to pass to the extension. Caused when the ERP system had a significant number of account / attribute / tax options and there were a number of lines on the invoice.

Version 1.0.7​

2025-09-17 Changes from 1.0.6

Minor updates​

  • [ISD-284] - MS7 resolved an issue with account rules with autofill via relations, where the related attribute id was being sent in the XML rather than the attributes attribute_id

Version 1.0.6​

2025-09-17 Changes from 1.0.5

Minor updates​

  • [ISD-277 OC2-68] Minor improvement, we have enabled the system to replicate v1 functionality to send either the first line description, or a timestamp as the invoice description. There is a new extension setting to handle this: firstLineAsDescription.

  • [OC2-46] Minor bugfix for MS7 to correct the "messages" text file not being correctly attached to the invoice transaction. On ERP7 we need to wait for the EI02 to run and the transaction number to be generated before the indexes can be updated. This file will now appear as a second attachment with invoices and include any info and warning messages. We will be expanding the ability to configure this further at a later date.

  • [OC2-63] Minor improvement to coerce the erpVersion to lowercase to avoid configuration issues

  • [OC2-63] Minor bugfix for MS7 to appropriately handle erpcr as a setting

  • [ISD-275] Minor bugfix for MS7 on trying to match up a Rossum login to a Unit4 user to send back in accountable (searching in Unit4Id was fine but when relying on addresses, all addresses had to contain the email, this is switched to any). This field ends up in the ext_ref on acrtrans.

Version 1.0.5​

2025-09-09 Changes from 1.0.5

Minor updates​

  • Minor bugfix for MS7 to correct attribute_ids being sent in the XML
  • Minor bugfix to correct an api request for multiple attributes, where closed values may have been shown as options.

Version 1.0.4​

2025-09-08 Changes from 1.0.4

Minor updates​

  • Minor bugfix for MS7 to send 0 rather than empty string if tax value and tax rate are not provided.
  • Minor bugfix where one field was still passed as net when the ignoreTax parameter was on

Version 1.0.3​

2025-09-02 Changes from 1.0.2

Minor updates​

The configured transaction type in the Rossum Extension will now be passed into MS7 systems on the EI02 parameter: vt_pre_reg_i (Tt Incoming Invoice)

Version 1.0.2​

2025-08-13 Changes from 1.0.1

Minor updates​

Additional error logging when we can't connect to the ERP system at all.

Version 1.0.1​

2025-08-06 Changes from 1.0.0

Minor updates​

Ensure bank details checks on suppliers also check the SWIFT/ BIC code