Error: "Posting to a future GL period..." multiple times on AP journals

The Sage 300 CRE Accounts Payable payment journals print future period warnings an excessive number of times.

The AP journals for Print Checks, Generate Electronic Payments, Record Manual/Print Quick Check, and/or Record Payments by Credit Card are printing repetitive future period warnings. This occurs in versions 24.1 and later.

Full error

"WARNING -- Invoice [invoice id], [prefix description] [prefix] - Posting to a future GL period ([date]). GL period for [date] is a future period for [prefix]. Payment generated for Vendor [vendor ID]."

The check date/payment date is for a future GL period.

Beginning with version 24.1, you can only enter payments to a closed period if you've selected Allow entry to closed period in GL Settings. See more information about this software change.

As part of this change, more warnings can appear on the journal when posting to a closed or future period. Because it validates the dates for each invoice/distribution, this results in many warnings on the journal.

Versions 26.1 and later

As of version 26.1, you can control when future period warnings begin printing on Accounts Payable invoice and payment journals.

1. Go to Accounts Payable, AP Settings, GL Entry Settings.
2. Set Print warnings for future GL periods on the journal after X months. This suppresses messages for a defined number of future periods.
3. Enter the number of months to delay printing future period warnings on journals. Warnings only print when the accounting date exceeds the number of future months.
   
   NOTE:

   Sage compares the accounting date to the current system date.

4. Enter 0 (zero) or leave the field blank to print all future period warnings.

Date calculation

Sage 300 CRE calculates the future periods by month and year, not by number of days.

This setting doesn’t affect future period pop-up warnings in tasks, which continue to display as usual.

Versions 24.1 to 25.2

There isn't a way to turn off the future period warnings on the journal currently. Verify the date used is the correct date. Make sure you close General Ledger periods in a timely manner.