<div dir="ltr"><div>Hi Manuel,</div><div><br></div><div>Thank you for your reply. Some clarifications below...</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">It depends on what sort of computation you'll be doing upon those<br></span><span style="font-size:12.8px">monetary values and on the expectations of your users.  It's typical<br></span><span style="font-size:12.8px">that payment processing applications sacrifice precision and instead<br></span><span style="font-size:12.8px">prefer to deal in exact quantities</span></blockquote><div class="gmail_extra"><br></div><div class="gmail_extra">Is there a document which explains common use-cases for monetary values and best-practices for dealing with them? Any guidelines for which **Haskell** data-types to use for what kind of monetary calculations? </div><div class="gmail_extra"><br></div><div class="gmail_extra">Here is what we are doing in our app:</div><div class="gmail_extra"><br></div><div class="gmail_extra">* Powering web-based e-commerce checkout flows</div><div class="gmail_extra">* Allowing store owners to input tax rates</div><div class="gmail_extra">* Allowing end-customers to see product prices in different currencies (so, currency conversion)</div><div class="gmail_extra">* Various reports to see total sales, total receivables, and total payables (basically a **very** small subset of small-business accounting)</div><div class="gmail_extra">* Exporting data to full-fledged accounting systems, like Quickbooks and Xero.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Based on this use-case, which Haskell data-type would you suggest?</div><div class="gmail_extra"><br></div><div class="gmail_extra">-- Saurabh.<br><div class="gmail_quote"><br></div>
</div></div>