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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

Journal Entry Batches are posted but still in Look up window

(0) ShareShare
ReportReport
Posted on by 10

I am new to this company and need to close Year End.  I had a window pop up to warn that A single-use batch or quick journal transaction has not been posted yet and do I want to continue closing?  I checked in Financial>Transactions>General>Lookup window and there are 3 batches from April, May and June.  All 3 show in the General Ledger for their respective months though.  Why is this happening?  Any input would be appreciated.  

Note:  The entry is something that occurs monthly to be recorded and differs by cents each month.  April, May, and June would have been handled by a temp employee that may not have known her way around using the system.  But I can not tell what is causing this or where to check.   And if it's ok to close year end.

Categories:
I have the same question (0)
  • Jeff Grant Profile Picture
    Microsoft Employee on at

    Hi Tammy,

    Based on your description there are a few possibilities of why the batches are in place.

    First, it may be user error with the user creating and saving the batch transaction initially but also creating and posting an individual transaction (without the batch) as well.  As the individual entry was already posted the batch entry was left in place and now causing the warning error during the GL YEC.

    Second, the initial transaction may have been made in a 'recurring' batch, which will create the same transaction content in successive time frames dependent on the recurrence frequency setting.  For example, if the frequency setting on batch is monthly the batch may contain the same entry for successive months when they really are not needed.

    Last, there could have been a processing issue during the batch posting that updated the GL but still left the batch shell in place in the SQL table (SY00500) holding the batch header data.


    In any regard, if you can verify the batch content has already been posted you should be able to pull up and 'Delete' each batch so you will no longer see the warning error prior to the GL YEC.


    Best Regards,
    Jeff
    Dynamics GP Support

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Abhilash Warrier Profile Picture

Abhilash Warrier 628 Super User 2026 Season 1

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 501 Super User 2026 Season 1

#3
Subra Profile Picture

Subra 437

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans