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.

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