I assume you are closing the statement cycle prior to printing statements? Do some customers have current data on their statements and others don't?
Do you have a customized Statements report in the Usr_Rpts folder? If so, try renaming that file and see if the statements show current invoices in the Print Preview.
How do the Statements Cycles look? Are the aging buckets correct?
Technical Support Engineer
**This posting is provided "AS IS" with no warranties and confers no rights.
Are you saying that a current invoice does not show at all on the statement or that it shows with a zero balance or are you saying the amount of the invoice is not in the current aging field on the statement?
In order for an invoice to show on the current statement it must have a non-zero balance or was paid by a payment or credit memo that is not part of the current statement and the invoice must have a statement date equal to the statement closing date for the statement cycle that the customer belongs to.
You can run a SQL query on ARDoc for the reference number of the invoice and look at the curydocbal value, the stmtBal value and the stmtdate value comparing it to the date showing on the AR Close screen for the statement cycle of the customer. You can also run a query against ARAdjust for that reference number in the adjdrefnbr field and see what credits have been applied to that invoice (if any) and what the adjgdocdate was for that credit application.
My guess is that you closed the statement cycle more than once on different days relegating the invoice to be a member of a previous statement close or that the invoice has been paid with a payment that is not part of the current statement or something along these lines as opposed to a problem with the software. The view for statements is complex looking at many factors to determine if the invoice is part of the current statement or part of the beginning balance.
that brings up another question. Is the customer set up for balance forward or open item statements?
Thanks to all. After additional research yesterday, they had not released a batch with some 12/31 invoices until after the Aging/Statement process. It was just confusing on the surface until I looked at the table data with the process dates. Re-aging solved the issue.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics