PRB: Remittance Advice Journal sent to wrong recipient using Zetadocs NAV Server Delivery
This Zetadocs technical note applies to:
- Zetadocs for NAV versions 8, 9 and 9.1
- Dynamics NAV 2015 and later
- Zetadocs NAV Server Delivery
When sending a batch of remittance advices from the Payment Journal, the user finishes queueing up the job and immediately posts it. Zetadocs fails to deliver the batch with the following error “Error whilst creating PDF The Gen. Journal Line does not exist. Identification fields and values: Journal Template Name='PAYMENTS',Journal Batch Name='DEFAULT',Line No.=1” as the records no longer exist.
If the user does another payment run creating new entries in the Gen. Journal Line table and then retries the previously failed job, the retried job entries will be sent with the wrong PDF attached in the email.
Zetadocs uses the table key to identify records to be sent (in this case: Journal Template Name, Journal Batch Name and Line No.). If a job is stopped/fails half way through before having the chance to generate the PDF documents before they get deleted, Zetadocs will try to recreate them on retry by asking NAV to generate the Report with RecordID -> JournalTemplate,JournalBatch,LineNo.
As NAV reuses the keys after the records get posted, when Zetadocs asks for a report PDF for Record x it will match it against the wrong data and generate the wrong PDF, thus sending it to the wrong contact.
Zetadocs for NAV version 10.0 has added protection to avoid the issue by using secondary key validation.
This issue is resolved in version 10 of Zetadocs for NAV.
HOWTO: Send Remittance Advice reports using Zetadocs
Last updated: 10th January 2018 (JC/CR)
Keywords: Payment journal, ledger entries