Update: Victoria Yudin correctly noted that there are times when posting reports are helpful or required, perhaps for training or identifying errors. Absolutely--posting reports are definitely necessary in certain situations, even in Fabrikam. I chose to turn off the posting reports in my test company because I am constantly doing repetitive testing of batch posting for my projects. I know that my data is fine, the transactions are fine, and everything posts fine, so in my situation, I don't need the posting reports or the report dialogs, and I turn everything off to avoid having to click Cancel constantly.
It's pretty sad when you know how many times you have to click the cancel button on the report dialog boxes after you post a certain Dynamics GP batch.
Finally, my laziness wanting to avoid constantly clicking a Cancel button finally overtook my laziness to disable all posting reports, and I finally spent 10 seconds to create the script to turn off all posting reports in Fabrikam.
I now need to make it a standard part of the GP installation process after I create the Fabrikam company.
Batches and posting reports...two anachronisms of the ERP world that GP will probably never abandon...
Ask a NetSuite consultant about their "batches" and "posting reports" if you want to see some puzzled reactions.