The feedback the dev team needs really isn't about running reports.  It's about how the Service Date needs to be the actual posting date on which revenue is recognized.  The lack of functionality really isn't in the software realm, it's in the understanding how accounting actually works realm.  If they can't use the Service Date as a revenue recognition date, the software team feedback should be to mask off the Service Date feature altogether, because to provide the Service Date feature absent it being the record date for charges, you're representing that your app does something that it doesn't do.  The faster solution would be to mask off Service Date and change the label in the app called Delayed Charge Date to be Posting Date so users accurately understand what the app does and doesn't do.