Did you read the blog post I referenced and all the articles it references?
Basically, you're querying financial data and creating reports that I assume will affect amounts and bills and using a hint that the SQL documentation clearly states
Allowing dirty reads can cause higher concurrency, but at the cost of reading data modifications that then are rolled back by other transactions. This may generate errors for your transaction, present users with data that was never committed, or cause users to see records twice (or not at all).
Depending on the financial laws in your country, that could cause your company some serious problems, basically they could be completely misrepresenting how much money those collection agencies should be collecting.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability