CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion (Moderator: Donald Lobo) »
  • Possible rounding errors for accounting package integration?
Pages: [1]

Author Topic: Possible rounding errors for accounting package integration?  (Read 838 times)

AJA

  • Guest
Possible rounding errors for accounting package integration?
July 10, 2010, 12:15:11 pm
As far as I can tell, CiviCRM stores payments in a 2-digit-after-decimal format. Is there a setting to change how this works? If not, this method of storing payments could cause accounting errors.

According to http://community.freshbooks.com/forums/viewtopic.php?id=5084
Quote
SAP is the (de facto) financial industry standard and they use NUMBER(16,5) for storing currency fields in the database.  Other billing etc systems I've worked on have used similar sizes.  It is totally incorrect to use only two decimal places to store financial amounts.

And
Quote
The way a field is PRESENTED is different to the value stored.  The value $123.45678 is what is stored in the database.

The value presented on the report is $123.46.

Which means there should be 5 digits after the decimal point in the contribution fields in the DB, the front end should be the only place where a value is rounded.

I'm running into an issue integrating Ubercart with the current CiviCRM version, the contribution API refuses to accept properly formatted payment quantities.

Anyone else having this issue?

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion (Moderator: Donald Lobo) »
  • Possible rounding errors for accounting package integration?

This forum was archived on 2017-11-26.