Unfortunately, AR is the most unforgiving of the applications in my opinion.  I'm guessing the void may have occurred in a period that is closed in general ledger.  See knowledgebase article https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=20465&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=11522&cmd=displayKC&dialogID=681441&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true 

Find out the specifics on the accounting dates of the original invoice and the void and see if general ledger is closed for the accounting period of the void.  If so, follow the directions in the article "Enter an invoice to the incorrect void date and then void the new invoice with the correct void date"

Thank you for the advice I don't know if this will work, because the void was in the current year for an invoice that was billed in the prior year.

click the VOID tab to void the invoice

What isn't posting?  Is it the general ledger transactions?  GL - Tasks - Post Entries.  Then GL - Inquiry - Entries - New.  Do you see the transactions that haven't posted?  What is their accounting date?  Is general ledger closed for that accounting date?  The article above will reverse the void to the closed accounting period that you originally used and then you will have the original transactions and the reversing transactions not posting to the closed period but they cancel each other.  Then you can use the GL Task of Open / Close Posting Period to post the entries that are rejecting.

If unsure, copy your data folder to a Testing Company data folder and try it on the Testing Company first.

The general ledger is not posting the transaction. I get the following message "Note: Based on your setup, some transactions may not post for a prior period or a future period." I don't understand what this means. When I posted, the prior year periods were open as well as the current year periods.

The general ledger is not posting the transaction. I get the following message "Note: Based on your setup, some transactions may not post for a prior period or a future period." I don't understand what this means. When I posted, the prior year periods were open as well as the current year periods.

The message is telling you the rejected transactions cannot post because the accounting date is either in a "closed" period or a period in the future that is greater than 6 months from the Calendar/Fiscal Settings in General Ledger. 

General Ledger - GL Settings - Calendar/Fiscal Settings shows what period General Ledger is currently setting in.  For example, mine says period ending 06-30-2022, which is the "current period" that is open.  This means new transactions with an accounting date before June of 2022 need to post to a closed period and any transactions with an accounting date before June will not post because those transactions are in "the prior period" that is closed.  Therefore, these will continue to reject until I do something about them.   

Transactions with an accounting date of July 2022 or later are considered transactions in a "future period".  Transactions with an accounting date greater than six months beyond the current period (in this case January 2023)  won't post either until the GL Calendar/Fiscal Settings are within 6 months of the accounting date of the transactions because GL only will post up to six months in the future.  These will eventually post as time goes by and each month is closed, but your problem suggests that you want them to post into a current period to stay balanced.

So, if your void was done with an accounting date to a closed period or a period more than 6 months into the future the void will continue to reject until you fix it using the article, or, you let time go by and continue to close months and get within 6 months of the future accounting date of the void.  However, to get this to post into the current period, you will have to use the article. 

Hi Elaine,

Can you post a screenshot of that message? That's not the message we would expect to see in Sage 300 Construction and Real Estate.

Believe it or not - it appears to have fixed itself. There must have been some glitch that worked itself out.