balance forward vs open item customer statements

diane@gn
diane@gn Member Posts: 9
edited 2006-08-06 in Navision Attain
We ran the customer statement report for a Canadian customer (we are in the US) using a statement style of Open Item and Balance. We have a discrepancy between the two reports, in Total amounts, ranging from $7 this month all the way to over $15000 6 months ago. What is the best way to go about trouble shooting this issue in order to resolve the problem? Thank you in advance for your kind attention.

Comments

  • Savatage
    Savatage Member Posts: 7,142
    What are ALL the other options you chose?

    If you do it for another customer - is that customer off too or just this one?
    Harry Ruiz
    http://www.BiloBeauty.com
    http://www.autismspeaks.org
  • Alex_Chow
    Alex_Chow Member Posts: 5,063
    You will need to print Customer Account Detail report and compare it with Detail Trial Balance Report.

    This is often caused by users directly posting into your G/L A/R accounts.
    Confessions of a Dynamics NAV Consultant = my blog
    AP Commerce, Inc. = where I work

    Getting Started with Dynamics NAV 2013 Application Development = my book
    Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
  • Miklos_Hollender
    Miklos_Hollender Member Posts: 1,598
    For finding out direct postings in thr G/L, filter the G/L entry for "System-created entry = no and the appropriate G/L Account No. Generally, it's a good idea to create a new report by a Save As to Detailed Trial Balance and filter it for System-created entry = no, that report will show the results of manual postings. It will be slow, but it's just a control report, running it once in a while to spot possible wrong postings.

    Besides that, another reason can be that the filters are different in the two reports, either the hardcoded ones or the ones set by the user. You can debug it by placing ERROR(RecordVariableOrDataItem.GETFILTERS); in the code of the reports at strategic places - usually OnBeforeDataItem triggers - and comparing them. Or better yet, make it a standard that you put textboxes with SourceExpression = RecordVariableOrDataItem.GETFILTERS into the header of reports - thus both the users and you can always see how the data that is shown in the report is filtered.

Categories