Kofax ReadSoft Collector 6.5.0 Fix Pack 26
Build date: Feb 13, 2025
© 2025 Tungsten Automation. All rights reserved.
Use is subject to license terms.
Introduction
This release contains priority fixes driven by critical on-demand requests in Kofax ReadSoft Collector 6.5.0.26.
Note: To install Kofax ReadSoft Collector 6.5.0.26 successfully, an existing full installation of Kofax ReadSoft Collector 6.5.0 is required.
If you need to perform a full product installation, see the Kofax ReadSoft Collector Installation Guide for instructions.
Features added in this fix pack
271938: VAT table customization
The VAT table in the output PDF for XML invoices has been customized to match the KSEF portal.
271607: Additional XML tables
Collector supports additional XML tables for the Faktura_Tax XML profile that includes transport, new transport measure, factor bank account, intermediate shipment address, other registries, third-party data, buyer contact details, buyer entity, partial down payment, advance invoice, and deductions.
Issues resolved in this fix pack
ID | Issue | Solution |
---|---|---|
272250 | The copy of the email contained both processed and unprocessed attachments and no log file. | The retry mechanism is added while deleting the email attachments from the copied email. |
273282 | When the XML file received via email was processed and the "Add embedded image to the XML invoice" option was selected, the email body was not included in the invoice. | The email body is added to the invoices. |
Previous fix packs
This section includes the features added, issues resolved, and changes in behavior in the previously released fix packs. To see the details, click on the fix pack.
Issues resolved
ID | Issue | Solution |
---|---|---|
270121 | The "SilentTokenAcquisition" failed for a particular email account. | The string comparisons are handled correctly with the email address of the configured account. |
269760 | The OAuth token cache file did not work when multiple services were run. | The synchronization is properly managed. |
Features added
261599: Additional XML tables
Collector supports additional XML tables for the Faktura_Tax XML profile that includes additional descriptions, attachments, bank account numbers, corrected invoice data, goods lot number, load, order, other information, partial payment, payment terms, and warehouse document number.
257022: Additional tax amount rows
With the addition of two new tax amount rows, Collector now supports five different "tax base amount" and "tax amount" for the Faktura_Tax XML profile.
255105: ISDOC support
Collector supports the ISDOC file format with a new XML profile added to support it.
Issues resolved
ID | Issue | Solution |
---|---|---|
252613 | When the XML invoices included a PDF file with parentheses in the name, the PDF was ignored, and a blank image was generated. | The file names with valid special characters are now recognized. |
248874 | When the original email was sent with OFD attachments, the feedback email sent only the XML file without the email body attachments. | A property is added to maintain the original attachment. Note: This fix also applies to ReadSoft Invoices, and it is compatible with Invoices 6.2.0 Fix Pack 6 or later. |
Feature added
249026: Field order preference
The field order in the invoice fields for XML invoices can be changed as per preference.
Issues resolved
ID | Issue | Solution |
---|---|---|
252619 | When processing a Chinese OFD invoice with ReadSoft Collector 6.5.0.21,
the Amount Summary table was not created in the output PDF. |
The Summary table is displayed even if the invoice does not have line items. |
250910 | When UsePdfTableForLineItemDataForXML was set to 1 in the collector.ini file, incorrect data was created for line items in the generated image files. | A proper initialization of the local variable is executed. |
Features added
229996: Amount summary table
Similar to the XML invoice, only one amount summary table is now created. In previous versions, the amount summary table was created twice with identical values.
232784: Order of buyer and supplier fields
A new XMLInvoiceFieldOrderConfiguration.xml is added to the GlobalPath folder for XML invoices to change the order of fields in the Buyer and Supplier sections as per preference.
Note:
The order of fields in the Buyer and Supplier sections is as per the order set in the XML profile.
In the absence of any XML profile, the default field order is considered.
The first XML profile is considered if there are duplicate profiles with the same name.
Feature added
226837: New flag for new OFD format
A new flag, OFDTypeID, is added under a new section [OFD2.0] in collector.ini to specify the identifiers for the new format of OFD.
Flag value:
OFDTypeID = eInvoice,root (default)
Note: Irrespective of flag values in collector.ini, empty string("") will always be considered to determine the new OFD type.
Issue resolved
223432: Images were downloaded from the email, even though the "Do not download images referenced in the email body" option was selected.
Feature added
164736: OFD file format support
Collector supports the OFD file format.
Note: Collector only supports one page and one line-item extraction for the OFD file format.
Issues resolved
166996: The field order was changed in the "Supplier" and "Buyer" sections of the newly created PDF for POL XML invoices.
165392: The field label name "Tax code" was changed to "Supplier Tax Reg No" in the autogenerated XML invoice image.
163944: A single image from the PDF was used for all the XML files, even though each XML file had a distinct image in its respective PDF.
161844: The content of one field overlapped with the content of the other field in the newly created PDF from an email.
159284: The product version for Collector is now reflected in the Manager module and the Control Panel (this works only with 6.1.0.8, 6.2.0.3, and later versions).
Features added
161356: Upgrade from Azure Active Directory Authentication Library (ADAL) to Microsoft Authentication Library (MSAL)
You can upgrade from Azure Active Directory Authentication Library (ADAL) to Microsoft Authentication Library (MSAL) while using EWS with OAuth.
A new flag, UseMSALContextInEWS, is added to the [General] section in collector.ini. You can use this flag to choose ADAL or MSAL.
Flag values:
- 0 = ADAL is used.
- 1 (default) = MSAL is used.
Note: After installing this fix pack, re-authenticate any services that use EWS with an OAuth input source; otherwise, set the flag value to 0.
150844: Value outside a LineItem part
Use a value outside the LineItem part for a column in the LineItem table.
Issues resolved
163025: The newly created invoice image for the updated XML field did not have any value.
161018: System decimal setting affected importing an XML file.
160752: Some PDF files generated error messages during interpretation.
Features added
271938: VAT table customization
The VAT table in the output PDF for XML invoices has been customized to match the KSEF portal.
123704: Invoice appendix creation
Regardless of whether the AllPagesAreInvoicePagesInterpret flag is enabled or disabled, the invoice appendix is created while processing the XML invoices.
122515: Process digitally signed emails
Office 365 and EWS with OAuth input sources bypass Microsoft security to process digitally signed emails.
122509: VAT table support
XML invoices support the VAT table.
117773: XML Maintenance run
The XML Maintenance can be run from the Command Prompt or scheduled in the Windows Task Scheduler to automatically start and stop.
112831: "CC" field of an email
While converting an email to PDF, the "CC" field of the email is included in the converted PDF.
112304: Date format support
Limilabs supports the following date format while processing emails from Gmail:
"Date: Tue, 31 Aug 2021 14:22:31 +0870"
112152: Windows Server 2022 support
ReadSoft Collector supports Windows Server 2022.
109143: ReadSoft Collector settings
The ReadSoft Collector settings can be exported into a .sxprof file. Also, the ReadSoft Collector settings saved in a .sxprof file can be imported into the application.
101104: Configure automatic notification emails
ReadSoft Collector can be configured to send automatic notification emails when an error occurs.
99273: Email attachments
While processing emails, only the email attachments can be saved skipping the other information in the email, such as logo, title, and signature.
Feature added
122362: Verification skip for digitally signed emails
Office 365 and EWS with OAuth input sources skip verification of email attachment names while processing digitally signed emails.
Issue resolved
122863: The field labels in the XML invoices PDF incorrectly displayed Polish special characters.
Feature added
112580: "CC" field of an email
While converting an email to PDF, the "CC" field of an email is included in the converted PDF.
Issues resolved
26430313, 16576, 113600: When attempting to reconnect to an Office365 input source, the remote server connection failed.
113573: The Office365 input source connection failed when TLS 1.2 protocol was used.
Feature added
112044: Emails with an invalid date format
Emails that contain an invalid date format are moved to the configured error folder.
Issue resolved
110580: The email processing failed if the P7M file attachments were not ignored while processing email using the EWS and EWS with OAuth input methods.
Features added
103857, 14808: ZUGFeRD version 2.1.1 support
ZUGFeRD version 2.1.1 standard is supported.
100569, 14775: Impersonation with OAuth support
Impersonation with OAuth is supported.
Features added
100986: New input source for OFD files
A new input source type, OFD Files, is added to process OFD files.
73111: Email attachments display
A complete list of email attachments is displayed in ReadSoft Collector whether or not they are supported by ReadSoft Collector.
72766: Attachment folder
The attachment folder can be set to a specific job in the Job configuration > Email settings tab. In earlier versions, the attachment folder was set at the global level in ReadSoft Collector General settings, which was common to all the jobs.
50534: Digitally signed emails
ReadSoft Invoices can process digitally signed emails. The "How to handle digitally signed emails" option is added in the "Email settings" tab in the "Job configuration" dialog box in ReadSoft Collector. Select this option to move emails to the error folder if the digital signature validation fails.
Issues resolved
107011, 104756: The emails were not processed when IMAP Limilabs and Gmail with OAuth input configurations were used.
106436: The PDF conversion was not successful using Collector and Import.
100659: The Hebrew characters in an email image were not similar to the characters in the actual email.
99441, 97266: The PDF was not processed when the OmniPage engine was used.
65147: In the XML Maintenance plug-in, the custom fields added from the XML Maintenance > Layouts tab were not copied when the XML invoice profiles or XML invoice definitions were exported.
Issues resolved
26255252, 14856, 104833: When Limilabs API was changed to support OAuth, the group mail address was not supported.
26234483, 102854, 14708: While processing an email using the EWS input source, if a faulty attachment was detected, incorrect attachments were moved to the error folder instead of the error attachment.
Issue resolved
26200718, 100314: An email remained in the Working folder and was not processed when the application was unable to retrieve the sender details.
Note: Due to the SDK changes made to Atalasoft, Kofax ReadSoft Collector 6.5.0.9 supports Kofax ReadSoft Invoices 6.0.3.4 or later.
Features added
26179093, 13194, 98635: Database name and username encryption
The database name and username in collector.ini can be encrypted.
New flags, UseEncryptedDB and EncryptedDatabase, are added to the [General] section in collector.ini.
26157426, 13041, 96515: ZURGFeRD file larger than 64 KB
A ZURGFeRD file larger than 64 KB can be processed.
26095307, 12721, 73025: ReadSoft Collector email folder
The ReadSoft Collector email folder can be added to the job description. A new option has been added to the "Email settings" tab to select the email folder.
Features added
26068897, 12506, 71259: Email order processing
It is now possible to process email in order when using EWS and Office365.
65863: It is now possible to connect to Gmail using OAuth with IMAP in Collector. Now, all the OAuth input sources such as Gmail, Office 365, and EWS are added in a separate list under source type OAuth.
Issue resolved
26138042, 94833, 12779: A newly created file name included part of the original file name if an extra dot was included.
Features added
63972: ReadSoft Collector maintenance
Previously, if ReadSoft Collector maintenance was not performed frequently, the size of the database potentially grew large enough to cause connection time or command timeout errors, and the sync operation would fail as a result. This has been redesigned and a "Run maintenance" button is added so that both sync and delete are performed with a single click.
58478: ZUGFeRD 2.0 XML standard support
Support is added for the ZUGFeRD 2.0 XML standard.
58477: XML.p7m format support
Support is added for invoices in XML.p7m format.
57108: XSLT 2.0 support
Support is added for XSLT 2.0.
54825: Database maintenance simplified
The database maintenance is simplified with a “Run maintenance” button.
53386: Microsoft Office 365 and EWS with Oauth configuration
It is now possible to configure Microsoft Office 365 and EWS with Oauth as input sources.
Issue resolved
64853: The image layout was not correct on the image created for XML invoices. Lines overlapped at the end of the page.
Changes in behavior
Previously, help files were installed separately in CHM format on each computer where Kofax ReadSoft Collector was installed, and context-sensitive help calls were done locally. The help is now located on an online Kofax documentation server to which context-sensitive help calls are directed when you click a help button or press F1 in the program. In this case, Internet access is necessary.
Note: Context-sensitive help is available when ReadSoft Collector 6.5.0.6 or later is installed with ReadSoft Invoices 6.0.3 or later.
Features added
58388: Connect Microsoft Cloud resources (Office 365)
To connect to Microsoft Cloud resources (Office 365), Microsoft Graph REST API can be used.
54550, 10362: Collector database maintenance
ReadSoft Collector database maintenance is simplified with the addition of the Run Maintenance option.
52564, 28387, 10108: Import XML invoices with custom values
A custom value can be added when importing XML invoices.
Issues resolved
63149, 10809: The PDF files were interpreted multiple times if a .eml file was included as an attachment in the same email.
57396, 10507: The latest XML definitions could not be selected during the import if there were more definitions than could fit on the current screen.
57379, 10492: Attachment folder information was not updated in the log.
55734, 10450: Only one of the multiple emails that had an attachment with the same name could be processed if SaveMailContentToFile=1.
55680, 10451: It took considerable time to show the supplier list in the XML mapper.
55635, 10445: Emails were processed out of order.
54562, 10330: The output dimensions for the PDF body in Collector were incorrect for a sample PDF.
Features added
51940: Document filter upgrade
The perceptive document filter is upgraded to version 11.4.0.2822.
49322, 9670: Value outside lineitems
It is now possible to use a value outside lineitems as a condition to be able to extract them.
48591, 9551: XML invoice processing
It is now possible to process XML invoices even though they contain text/XML embedded as a file.
48335, 9512: XML invoice images
It is now possible to use different images for XML invoices depending on the situation (that is, embedded, from email, or newly created automatically).
46373: Finvoices 3.0 XML profile support
The Finvoices 3.0 XML profile is now supported.
45038: Supplier numbers
Supplier numbers are no longer duplicated when using SmartXML.
44759: TLS 1.2 support
TLS 1.2 is added as a SecurityProtocolType option for Exchange server communication in the [General] section of collector.ini.
41473: Email attachments separation
It is now possible to separate email attachments into multiple invoices if the invoices are separated by blank pages.
41284: Atalasoft for PDF creation
PDFSharp is replaced by Atalasoft for PDF creation.
41031: Microsoft SQL 2017 support
41031: Support is added for Microsoft SQL 2017.
39811: Child notes with a namespace
If a namespace is present, working with child notes is possible while using XSL.
28387: Block emails
Email from specific senders or entire domains can now be blocked.
Issues resolved
53248, 10169: Job name was not updated after rerouting an XML invoice to another profile.
50654, 9868: It was not possible to process digitally signed emails using EWS.
48234: Emails with broken PDFs are now moved to the error folder instead of causing Interpret to fail.
41931, 8740: In the XML maintenance plugin, XML invoices with "invoice object missing" status could not be deleted.
40473: It was not possible to filter fields in the XML Mapper.
29800, 8993: Changes to an XML definition in the XML mapper affected all XML invoices belonging to the parent XML profile.
Changes in behavior
The following flags are added to COLLECTOR.ini:
- SaveMailContentToFile and SaveMailContentFilePath in the [Settings] section.
- SecurityProtocolType in the [General] section.
Features added
48234: Emails with broken PDFs
Emails with broken PDFs are now moved to the error folder instead of causing Interpret to fail.
43458: Invoice page numbering
It is possible to have all the pages in an invoice be numbered using AllPagesAreInvoicePagesInterpret in connection with Kofax ReadSoft Collector.
42569: OAuth 2.0 protocol support
The OAuth 2.0 protocol is supported for Exchange Online Web Services.
Features added
40473: XML Mapper fields
Fields in the XML Mapper can be filtered.
39811: Namespace
If a namespace is present, working with child notes is possible while using XSL.
Issues resolved
43897, 43458, 8886: The AllPagesAreInvoicePagesInterpret setting was overridden in Kofax ReadSoft Collector.
41931, 8740: In the XML maintenance plugin, XML invoices with “invoice object missing” status could not be deleted.
29800, 8993: Changes to an XML definition in the XML mapper affected all XML invoices belonging to the parent XML profile.
Fix pack build numbers
Fix pack | Build number | Fix pack | Build number |
---|---|---|---|
26 | 6.50.24501 | 13 | 6.50.21279 |
25 | 6.50.24500 | 12 | 6.50.21215 |
24 | 6.50.24172 | 11 | 6.50.21131 |
23 | 6.50.24114 | 10 | 6.50.21061 |
22 | 6.50.24075 | 9 | 6.50.20329 |
21 | 6.50.23335 | 8 | 6.50.20295 |
20 | 6.50.23251 | 7 | 6.50.20195 |
19 | 6.50.23167 | 6 | 6.50.20090 |
18 | 6.50.23082 | 5 | 6.50.19346 |
17 | 6.50.22311 | 4 | 6.50.19217 |
16 | 6.50.22237 | 3 | 6.50.18355 |
15 | 6.50.22066 | 2 | 6.50.18267 |
14 | 6.50.21347 | 1 | 6.50.18164 |
Applies to
This fix pack is cumulative and includes the resolved issues released in previous Kofax ReadSoft Collector 6.5.0 fix packs.
Apply this fix pack to update any of the following versions.
- Kofax ReadSoft Collector 6.5.0
- Kofax ReadSoft Collector 6.5.0 Fix Pack 1 through Fix Pack 25
Compatibility
Kofax ReadSoft Collector 6.5.0.26 is compatible only with Kofax ReadSoft Invoices 6.1.0.5, 6.2, or later.
Files included
This fix pack includes the following files:
File name | Version |
---|---|
KofaxReadSoftCollector-6.5.0.26.zip | N/A |
ReadMe-KofaxReadSoftCollector-6.5.0.26.htm | N/A |
Install this fix pack
Refer to the Kofax ReadSoft Collector Installation Guide for instructions.
Remove this fix pack
Use the following procedure to remove this fix pack.
- Verify that the following applications/services are not running.
- Kofax ReadSoft Collector 6.5.0
- Kofax ReadSoft Collector Service
- Antivirus software
- In Control Panel, select Programs > Programs and Features > Uninstall or change a program.
- From the list of programs, in the Name column, select the item that corresponds to Kofax ReadSoft Collector 6.5.0.26.
- Right-click and select Uninstall.
- Restart any applications/services that were stopped before removing this fix pack.
Note: For best results, remove the fix pack during off-peak processing hours.