web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

Job Queue Entry error - codeunit 260 Document-Mailing SENDINV remittance advice

(4) ShareShare
ReportReport
Posted on by 23
We are running BC version 24.4.22295.22393.
 
When our AP team process a payment run though 'Payment Journals', once happy with the selections they select 'Related >Payments >Send Remittance Advice' to issue the emails to our vendors. They then, immediately post the payment journal.
 
I believe what BC does is the 'Send Remittance Advice' action creates a 'Job Queue Entry' for each email to send and these are processed, in the background, shortly after creation.
 
However, because the 'Payment Journal' has been posted the records are not found when the 'Job Queue Entry' runs, thus resulting in an error condition.
 
I have asked the AP team to either -
1) Delay posting the journal until (an unknown length of time) has passed, to allow the 'Job Queue Entries' to process.
2) Don't send the remittances from the 'Payment Journal' but send them from the 'Vendor Ledger Entries' instead, after posting.
 
The team, however, are continuing to cause this error.
 
Other than creating an 'Exclude' permission to stop them using the 'Send Remittance Advice' from the 'Payment Journals', I don't know how to prevent the 'Job Queue Entry' error.
 
It does seem, to me, a bit illogical how this process works.
 
Can anyone please advise?
 
 
The error details are -
Error message:
The Gen. Journal Line does not exist. Identification fields and values: Journal Template Name='PAYMENT',Journal Batch Name='BACS',Line No.='20000'

Internal session ID:
d6317327-2b3f-4a3d-xxxx-90d19564e8c5

Application Insights session ID:
bb83604e-0e18-447b-xxxx-ca1877f6decd

Client activity id:
87fcb4b3-c30c-4e6e-xxxx-87bdb879f1e6

Time stamp on error:
2024-08-22T10:21:38.0528754Z

User telemetry id:
e10efd54-8cfe-4f2e-xxxx-0b96321142c7

AL call stack:
ErrorMessagesRecommendationExt(PageExtension 7900)."Description - OnDrillDown"(Trigger) line 10 - Error Messages with Recommendations by Microsoft

Custom dimensions:
[{"Item1":"ErrorCallStack","Item2":"\"Report Selections\"(Table 77).SendEmailInBackground line 10 - Base Application by Microsoft\\\"Document-Mailing\"(CodeUnit 260).OnRun(Trigger) line 4 - Base Application by Microsoft\\\"Job Queue Start Codeunit\"(CodeUnit 449).OnRun(Trigger) line 23 - Base Application by Microsoft\\\"Job Queue Dispatcher\"(CodeUnit 448).HandleRequest line 23 - Base Application by Microsoft\\\"Job Queue Dispatcher\"(CodeUnit 448).OnRun(Trigger) line 22 - Base Application by Microsoft\\"},{"Item1":"CreatedOn","Item2":"22/08/24 09:38"}]
 
 
I have the same question (0)
  • Verified answer
    Sohail Ahmed Profile Picture
    11,136 Super User 2025 Season 2 on at
    Maybe this will help you resolve it.
     
    You're correct — the Send Remittance Advice action triggers a background job queue using Codeunit 260 (Document-Mailing), which still references the Gen. Journal Line when the job runs.
     
    Issue:
     
    If the journal is posted too quickly, the Gen. Journal Line no longer exists when the job executes — leading to the error you're seeing.
     
    Suggested Fixes:
     
    1. Best Practice (Recommended):
    Send remittance advice from the Vendor Ledger Entries after posting. This ensures all data exists.
     
     
    2. Custom Solution:
    Modify the remittance logic to use posted data (Vendor Ledger Entry) instead of journal lines when running in the background.
     
     
    3. Temporary Workaround:
    Add a delay (custom queue buffer or manual pause) before posting, or prevent "Send Remittance Advice" in the journal using permission sets or page extensions.
     
     
     
    Yes, the current design is flawed for this sequence — customizing or changing the process is your safest path.
     
    Mark below checkbox to make this answer Verified if it helps you.
     
     
  • Suggested answer
    Khushbu Rajvi. Profile Picture
    20,275 Super User 2025 Season 2 on at
  • Gerardo Rentería García Profile Picture
    25,169 Most Valuable Professional on at

    Hi, good day
    I hope this can help you, and give you some hints.PRB: Remittance Advice Journal sent to wrong recipient using Zetadocs NAV Server Delivery

  • AN-01071315-0 Profile Picture
    23 on at
    Thank you @Sohail Ahmed, it seems my best approach is to restrict the ability to "Send Remittance Advice" in the journal with permission sets.
     
    The scenario @Gerardo Rentería García has suggested is quite a worry. Sending incorrect PDFs is quite a concern!
     
    How would I go about raising this as a bug with Microsoft, would I talk with our Dynamics partner/reseller, or could I go direct?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,143

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,694 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,067 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans