This issue was discussed at our last Melbourne User Group meeting. The invoice in Verify will have a 000 extension. Readsoft ask that you send the corresponding.pdf file to them. They will update the Invoices module to make it compatible with new versions of PDF writer programs.
However, the problem Accounts Payable face is that Verifiers often delete the blank invoice document not realising that the original document was never scanned properly. The vendor then does not get paid, or resends their invoice via email only for it not to be processed by the system again.
So how can you determine which vendors are emailing problematic PDF documents?
One thing you can do is search your Email Attachments folder in your global path for all files named *.000, over a specified date range and with a file size up to 2kb. These are likely to be your problem invoices.
Take a snap shot of the search result (we had 20 of them since 1 April 2014) and then locate the corresponding PDF document which will be in the same folder.
Note that the email attachment folder has numerous sub-folders, so get the create date of the 000 file, and search that folder for the file name without the extension. For example, if the file name is IPL_800000.000 then search for IPL_800000* and you will find the corresponding PDF quickly.
This exercise revealed that we had 20 files with a size up to 2kb which were sent by three vendors only. I then wrote a rule in Lotus Notes to move any emails from these vendors into a new email folder called "To be printed and scanned".
So while we are waiting on the patch from Readsoft, we are endeavouring to field problematic invoices into their own folder.
Readsoft has recommended we run a PDF to TIFF standalone converter on these PDFs. However, I think it will be quicker for Accounts Payable to print the invoice and put it on the scanner, than try and find the corresponding PDF in the Email Attachments directory. The structure of this directory is complex and requires a bit of IT knowhow to get around it.
The common denominator of two of the PDF properties are the source application was File Maker (one was version 11.0.v3 and the other 10.0.v1). Both used a DLI add-in. Both had the font type: TrueType CID. It is likely Readsoft cannot decode this font type.
The other PDF which failed used PDFib 3.03 (Win 32) as the Producer and the Application to create the PDF was blank.
It would be good to hear if you have any other PDFs which are failing so we can approach Readsoft as a collective.