Re: Outstanding Report Issue in LSMB (all versions), proposing fix in 1.3.0

[Luke <..hidden..>]

On Thu, 21 Feb 2008, Chris Travers wrote:

> In the process of validating information for a migration to /trunk from
> SQL-Ledger, I have found some issues with the AR/AP outstanding report.
[.]
> 2)  SQL-Ledger always rounds .5 own, while we always round 0.5 up (as is
> traditional).  For this reason any invoice in SQL-Ledger which has half a
> cent tagged on will get rounded down (and not show up) while in LedgerSMB,
> it will get rounded up and cause a $0.01 discrepancy.

[OT]
As a side note: SL now allows the specification of precision, which can 
help with these kind of problems if you are willing to clutter your 
documents with fractions.  Having that available in LedgerSMB would be 
most nice.
Dreaming: if precision specification was available, having a checkbox or 
option in the total section which would 
allow the final result to be rounded in one direction or another, 
automatically adding or subtracting the necessary fraction in a safe way 
without having to use fractional line items to compensate, would be 
interesting.
[/ot]

> For obvious reasons, this makes validating numbers after a SL->LSMB
> migration to  be ... interesting.  The obvious solution is to hide invoices
> from the report which have less than half a cent outstanding or overpaid.
> This eliminates this issue.  However, for equally obvious reasons, it seems
> like a bad idea to do this for everyone.  Therefore I am proposing a value
> (set by the administrator in the defaults table) which specifies how much
> must be owed or owing on an invoice before it shows up in the report.  That
> value would be set to 0 by default with the advice that people migrating
> from SQL-Ledger might need to set it to 0.005 at least initially.
> 
> Additionally this could have the use of being set to filter out
> insignificant invoices.

Which IMHO is a more useful use for it in the long run.:)

> Another option might be to put the threshold option in the report criteria
> page so it could be set each run.
> 
> Any thoughts?

Do both.  Set the default in defaults, and allow it to be overridden on 
the report form.

Luke