For the same reasons, it is wise to use “currency” field-types in your SQL database if it has them ... and if its implementation of that field-type is not merely “in name only.”   For example, in the well-known case of Microsoft Access (JET), currency is implemented as a scaled integer:   the value is multiplied by 10,000, so that there is a fixed 4-digit accuracy.   Since Perl does not (AFAIK...) have direct support for such a data-type, you might not wish to do a long series of calculations involving currency in Perl, whereas a CALC SUM() query (since it is being carried out by the SQL engine) would retain accuracy.

Ironically enough, there are countless examples out there of spreadsheets which have numeric-precision issues of this type.