RE: Incorrect Customer Statements
Lisa, you may already know this but just in case. The statement date on documents is set during the close statement cycle process. That process finds any documents that belong to customers who are members of the statement cycle(s) you are processing and do not have a statement date and sets the statement date to the date on the close statement cycle screen. That screen utilizes the current business date and is not a field that the user can modify. So, the only way that a statement date can be a future date, as I understand it, is if the business date was set to a future date at the time of the close statement cycle process or if the user ran some sort of update query to modify that date. Once a document gets a statement date, that date is not updated with any subsequent close statement cycle runs. The statement date on the document determines where the balance on that document is part of the balance forward amount (assuming you are using the balance forward presentation) or the document is "new" and shows in the detail section of a balance forward style statement. The include future documents does not affect the statement date value. It only affects where the process sets a statement date on a future document or not.
The statement date on the document should not be affecting the statement balance. That amount is the sum of the open documents whether they are "new" documents or documents that were part of a prior statement cycle and are not part of the balance forward amount.
When statements are printed for a customer, the process looks at the statement cycle that the customer currently belongs to and the last closed date for that statement cycle and shows detail on those documents that have a statement date equal to the last closed date. So, if there are documents out there with a statement date beyond the current closed date for that statement cycle that this customer currently belongs to, then those documents will not show on the statement. However, there balance is part of the statement balance thereby leading to the situation that you may be describing.
How those document got a future statement date is the real question. One possibility is that the database has more than one statement cycle id and, at some point, the customers with the issue were switched to a different statement cycle id and that statement cycle was closed with a future date. Then the customers were switched back to the original statement cycle id. The other possibility is that the business date was accidentally set to a future date and the statement cycle was closed while the business date was in the future and those documents ended up with that future statement date. As I said above, once a document gets a statement date that value is never changed with subsequent statement cycle closings.
the best solution I can think of is to run an update query to change those future statement dates to a valid statement date. If those documents have already appeared on a statement then use a past statement close date. If you want them to appear on the current statement, use the current statement close date. If you want those documents to show on the next statement, set the statement date to 01/01/1900.
Hope this helps.