Tungsten ReadSoft Invoices 2025.1 Update 8
Build date: October 14, 2026
© 2026 Tungsten Automation. All rights reserved.
Use is subject to license terms.
Introduction
This release contains priority updates driven by critical on-demand requests in Tungsten ReadSoft Invoices.
Note: To install Tungsten ReadSoft Invoices 2025.1.8.0 successfully, an existing full installation of Tungsten ReadSoft Invoices 2025.1 is required.
If you need to perform a full product installation, refer to the Tungsten ReadSoft Invoices Installation Guide for instructions.
Feature added in this update
278993: Identify PDF signatures as per Portuguese legal requirements.
ReadSoft Invoices detects signatures in PDF and TIFF files to meet Portuguese new mandatory law.
This feature is disabled by default. To enable it, select the "Check for signature" checkbox on the Interpret job description settings.
Once invoice interpretation is complete, the signature detection result is stored in the invoice as a user-defined variable, EIESIGNATUREDETECTED, with a value of Yes or No, indicating whether a signature was detected.
Issues resolved in this update
| ID | Issue | Solution |
|---|---|---|
| 279192, 279090 | Interpret failed when attempting to process specific PDF files. | The OmniPage SDK is updated to 25.1.5.0 hotfix. |
Previous updates
This section includes features added and issues resolved in previous updates. To see the details, select the update.
Issues resolved
| ID | Issue | Solution |
|---|---|---|
| 278677 | QR code interpretation failed when the EngineForBarcode flag was set to 1 (default value). | Interpretation is handled correctly. |
| 278371 | Stopping the PM Service during invoice processing with a SAL license resulted in a Tungsten.ReadSoft.LicenseService assembly load failure. | SAL licensing DLLs are added to the PM Service installer. |
| 278310 | The Remote Scan did not delete the ZIP files accumulated in the scanning station after they were transferred to the FTP. | The ZIP files created in the temp folder are cleared. |
Features added
278166, 277651: Multi-session support
ReadSoft Invoices supports multi-session invoice processing.
278034: Amazon WorkSpaces certification
ReadSoft Invoices is certified for use with Amazon WorkSpaces.
278014: Dynamic XFA PDF support
ReadSoft Invoices supports Dynamic XFA PDF documents.
277733: Azure Virtual Desktop (AVD) certification
ReadSoft Invoices is certified for use with Azure Virtual Desktop (AVD).
Issues resolved
| ID | Issue | Solution |
|---|---|---|
| 278240 | After a database created in Invoices 5.8 was upgraded to Invoices 2025.1, some invoices failed to process unless the invoice definition was deleted. | Error codes are cleared after logging. |
| 278179 | The Interpret module stopped responding when invoices or emails were processed through services, leaving the invoice in Scanned status. | The Kadmos label pop-up is handled correctly. |
| 278016 | The Erase filter was not applied for last-page identification during the first interpretation. | Erase filters are handled correctly. |
Features added
277652: Federal Information Processing Standards (FIPS) support
ReadSoft Invoices supports Federal Information Processing Standards (FIPS).
277554: HANA 2025 support
ReadSoft Invoices supports HANA 2025.
277480: Disable "Save XML Profile" option
A Disable Save XML Profile checkbox (default: clear) is added under user configuration in the Optimize module access rights. When selected, it restricts saving XML profiles, preventing unauthorized or unintended updates to XML profiles based on user configuration.
277209: SQL Server 2025 support
ReadSoft Invoices supports SQL Server 2025.
277055: SQL MultiSubnetFailover support
ReadSoft Invoices supports SQL MultiSubnetFailover to enable faster failover detection and reconnection in "Microsoft SQL Server Always On Availability Group" environments, which helps maintain a stable connection to the database.
Prerequisites:
Use the listener name as the server value in eiglobal.ini.
Example:
[Database]
Server=tcp:listenername (such as, Server=tcp:listener1)
- Ensure that the databases are created with MSOLEDBSQL or MSOLEDBSQL19 as the provider.
Procedure:
Under the [Database] section in eiglobal.ini, set EnableMultiSubnetFailover = 1, MSOLEDBSQL = 1 or MSOLEDBSQL = 2.
276913: Google Cloud Platform (GCP) support
ReadSoft Invoices supports the Google Cloud Platform (GCP) and Google Cloud SQL.
276868: Relational Database Service (RDS) support
ReadSoft Invoices supports Amazon managed Relational Database Service (RDS) and Amazon Elastic Compute Cloud (EC2).
Issues resolved
| ID | Issue | Solution |
|---|---|---|
| 277547 | The Greek dates were incorrectly interpreted. | To resolve the configuration issue, update the following.
|
| 277435 | PDF creation failed during transfer when the "Save email body text as an invoice appendix" setting was enabled in the Interpret Collector job configuration. | The OmniPage SDK is updated to version 25.1.4.0. |
| 277046 | For a specific PDF, the asterisk (*) was incorrectly captured as a single quotation mark ("). | |
| 276933 | The Interpret module extracted incorrect data for a specific field. | |
| 276641 | The buyer field was incorrectly captured for a specific invoice profile. |
Features added
277035: Session timeout for Network and Azure users or groups
Network and Azure users or groups who have enabled Multi-Factor Authentication (MFA) to sign in to the ReadSoft Invoices modules can enable and configure session timeout to enhance security.
Note:
- This feature does not apply to local users.
- This feature does not apply when you run the Interpret or Transfer modules as a service.
- If a user configures a job and a session timeout occurs during processing, the job continues to run in the background.
Procedure
- Under the [Options] section in eiglobal.ini, set EnableSessionTimeOut to 1 to activate the session timeout. (Default: 0)
Set SessionTimeOutinSec as needed. (Default: 300 seconds)
Note: You cannot set the session timeout to less than 300 seconds.
When the user attempts to access the Invoices module after a configurable period of inactivity, a dialog box appears indicating that the session has timed out and that the user must reauthenticate using OTP to continue.
- In the dialog box that appears, select OK.
An OTP dialog box appears.
- Enter the OTP from the authenticator app on your device.
- Select Submit OTP.
Your access to the application is restored.
276727: Transfer bank account number of choice to PDAP
You can transfer a bank account number of your choice to PDAP for a supplier that has multiple bank account numbers.
Note: The bank account number cannot be more than 18 characters.
Procedure:
- Under the [Options] section in eiglobal.ini, set TransferBankAccountNumber = 1. (Default = 0, which means the transfer is not enabled.)
- Enable Master Data and choose a supplier from the list to view multiple bank account numbers.
- Select the supplier with the bank account number that you want to transfer.
- Configure the EICCBANKACCOUNTNUM field in the Process Director (PD) to view the transferred bank account number.
Issues resolved in this update
| ID | Issue | Solution |
|---|---|---|
| 277223 | A specific PDF could not be processed during import, resulting in an error. | The OmniPage SDK is updated to version 25.1.3.0. |
| 277206 | The Interpret module generated unreadable image files with a black background. | The OmniPage SDK is updated to version 25.1.3.0. |
| 277150 | The Interpret module became unresponsive when processing rotated invoices (originally created in the landscape orientation and then rotated to portrait). | The OmniPage SDK is updated to version 25.1.3.0. |
| 277115 | The Manager module became unresponsive during the database upgrade due to a large number of users in the user definition table. | The BLOB memory exception is handled. |
| 277036 | Filtering suppliers containing special characters did not work. | The special characters are now correctly managed. |
| 276956 | Keyword detection did not function correctly for certain invoices. | Unicode support is added. |
| 276828 | The field values were duplicated when line items were drawn or roped around in the Verify module. | The text is read from the word directory (or list of words) to prevent duplication. |
| 276777 | The default DEU invoice profile incorrectly interpreted the year 2025 as 2005. | The Year object in the GermanDate.dcl file is updated to support years up to 2029.
Note: Replace the existing GermanDate.dcl file in the DEU (German) country profile with the shipped version. |
| 276693 | Special characters appeared in the XML output in the Verify module. | The OmniPage SDK is updated to version 25.1.3.0. |
| 275736 | The description was not completely captured when a line was deleted and re-added using the Add Row option in the line-item table. | The data updation is handled correctly. |
Features added
275595: Improved buyer identification for XML invoices
You can add a new flag, EnableStrictXMLBuyerNameMatching, under the [Options] section in eiglobal.ini to match the XML buyer exactly with the default identifier fields (Name1, Name2, NameSupplement1, and NameSupplement2) in the master data. The system selects the buyer and sets the status to complete only if there is an exact match; otherwise it does not select the buyer.
Additionally, you can configure buyer identification fields under [BuyerIdentification] section in eiglobal.ini. The system matches the configured fields and at least one default identifier field.
Flag values:- EnableStrictXMLBuyerNameMatching = 0 (Default)
- EnableStrictXMLBuyerNameMatching = 1 (Matches the buyer exactly)
Issues resolved
| ID | Issue | Solution |
|---|---|---|
| 276672 | Incorrect identifiers appeared on invoice definitions after they were updated by the LearnIdentifiersUsingSingleItemFields flag in eiglobal.ini. | The correct values are assigned to the identifiers. |
| 276652 | Strange characters appeared in the text for a particular PDF after it was imported into the Verify module. | The OmniPage SDK is updated to version 25.1.2.0. |
| 276642 | When invoices with a PO number beginning with YM were integrated into PDAP, the Verify module failed to recognize the PO number and displayed Cyrillic characters in the PO number. | The OmniPage SDK is updated to version 25.1.2.0. |
| 276593 | The country code was missing after importing suppliers with the country code XK. | Both the 2-digit (XK) and 3-digit (XKX) country codes are supported. |
| 276533 | The year 2025 in Japanese invoice dates (Reiwa era) was incorrectly interpreted as 2015. | If the date on Japanese invoices has a 1-digit or 2-digit year (Reiwa era), set an offset value of -2018 in the eiglobal.ini file.
Example: [YearOffset] YearOffset2=JPN -2018 Note: Replace the shipped “InvoiceDateAndDueDate.dcl” in the Japanese country profile. |
| 276528 | PDF invoices containing security restrictions could not be processed. | Processed the invoices by flattening the PDFs. |
| 276526 | When the first page of an invoice did not contain a barcode, the UDV value (BarcodeSeparator) in the Verify module was returned incorrectly for multiple invoices. | The return type handling to process invoices without a barcode is corrected. |
| 273685 | The QR code could not be captured for a particular Swiss profile. | A fallback mechanism is added to reprocess the QR code with Atalasoft. |
| 272985 | Some PDFs with text on a blue background were incorrectly captured and appeared black in the extracted PDF in the Verify module. | The OmniPage SDK is updated to version 25.1.2.0. |
| 259757 | The Israeli currency symbol, the Shekel(₪), was incorrectly recognized. | The language selection is properly managed to handle the OCR selection. |
| 229352 | When the Greek character set was used for processing invoices, the digit "0" was incorrectly recognized as letter "O". | The OmniPage SDK is updated to version 25.1.2.0. |
| 102476 | For some invoices, the Scan module detected the barcode incorrectly. | The OmniPage SDK is updated to version 25.1.2.0. |
Features added
275666/272268: Kofax License Server upgrade
The Kofax License Server has been upgraded to version 2025.2.0.
274856: Windows Server 2025 support
ReadSoft Invoices 2025.1 supports Windows Server 2025.
264699: Supplier details for XML invoices
The Verify module displays supplier details such as name, tax number, street, postal code, city, and other relevant information for the XML invoices.
274277: Support for multiple alias buyer names
ReadSoft Invoices supports multiple alias buyer names. You can update the alias buyer information using a text file.
Issues resolved
| ID | Issue | Solution |
|---|---|---|
| 275563 | The ReadSoft Invoices modules became unresponsive after uninstalling the ReadSoft Invoices 6.2.0.10 patch. | The BLOB readings and writings are properly handled. |
| 275560 | The values could not be captured correctly due to the absence of space between the titles and their values. | A new flag, DiscardTextBeforeColonForCHNBuyerFields, is added to the [Interpret] section in eiglobal.ini. This flag discards the text before the colon (:) in the "BuyerName" and "BuyerVATRegistrationNumber" fields for invoices processed through the Chinese profile. |
| 274826 | The Scan module failed when attempting to start the module using the command line parameters. | The function that calls the location and handles the null reference object is changed. |
| 274760 | The Interpret module failed to capture the data during the OCR process when invoices were handled using the Thailand profile. | The OmniPage is updated to version 25.1.0.0. |
| 273278 | The Verify module did not respond when the Arrow button was used to navigate through fields. | The field grid navigation functionality is corrected. |
| 271951 | Vertical text near a line item impacted the capture of the line-item value. | A new checkbox, "Ignore vertical text while creating the line(s)", is added at the Interpret level. |
| 270802 | Unreadable text appeared in the output image of a particular PDF after processing. | The OmniPage is updated to version 25.1.0.0. |
| 269971 | ReadSoft Invoices stopped responding when invoices were rerouted for a particular invoice profile. | The memory is freed up to solve the unresponsiveness. |
| 261308 | The "All time total" counter was not updated for a particular invoice definition. | The counter is increased when the invoice is approved. |
| 166107 | OCR SDK "1" (italic font) was read as "7" at the line-item level for some PDFs. | The OmniPage is updated to version 25.1.0.0. |