Hi Adrien
You're better off building from current maint. It'll be in
Reports/Experimental.
Thx for beta testing.
On Wed, 6 Nov 2019 at 16:00, Adrien Monteleone <
adrien.montele...@lusfiber.net> wrote:
> Christopher,
>
> I have some AR cleanup in-progress and your revised owner-report would
>
> On Jul 19, 2019 w29d200, at 3:56 AM, Christopher Lam
> wrote:
>
> Wish to canvas opinion on what is considered best practice for the
> following real-data simulations, for rebuilding owner-report and
> aging-report. This illustrates current buggy behaviour.
>
> * I have a $100 customer
Christopher,
I have some AR cleanup in-progress and your revised owner-report would come in
handy matching up payments to invoices. I’ll be happy to report back any
testing issues I encounter while using it.
I can’t seem to find your link in the list threads, can you provide a current
link?
On 19/07/2019 09:56, Christopher Lam wrote:
Wish to canvas opinion on what is considered best practice for the
following real-data simulations, for rebuilding owner-report and
aging-report. This illustrates current buggy behaviour.
* I have a $100 customer invoice, posted- and due-dates 6 weeks
> On Jul 23, 2019, at 10:11 AM, Derek Atkins wrote:
>
>
>
>> In any case I'd think both owner-report and aging must be consistent.
>
> MAYBE.. But not necessarily. The aging report is more for the
> business, whereas the customer report is designed to actually be sent to
> the customer.
Christopher Lam writes:
> In this case, I think there is a strong argument that credit-notes must be
> ignored in the generation of aging-table? And this would apply for customer/
> job/vendor/employee aging tables, therefore only applying payment using
> credit-note will reduce the balances?
In this case, I think there is a strong argument that credit-notes must be
ignored in the generation of aging-table? And this would apply for
customer/job/vendor/employee aging tables, therefore only applying payment
using credit-note will reduce the balances? Advantage is there will be no
Christopher Lam writes:
> Yes, I agree. On that count aging.scm wins.
> What about Credit-Notes; should they automatically be applied to invoices in
> the aging-table?
> Sneak preview next gen aging report:
>
Yes, I agree. On that count aging.scm wins.
What about Credit-Notes; should they automatically be applied to invoices
in the aging-table?
Sneak preview next gen aging report:
https://user-images.githubusercontent.com/1975870/61539513-36ba3780-aa2b-11e9-89d8-c1c35d945a04.png
On Fri, 19 Jul 2019 at
Christopher Lam writes:
> A corollary query is how to report on overpayments in the aging-table
>
> * the Customer Report counts overpayments as negative amounts
> * the Receivables Aging report shows $0 owed by customer
IMHO, this behavior is correct. If the Customer has overpaid then you
Wish to canvas opinion on what is considered best practice for the
following real-data simulations, for rebuilding owner-report and
aging-report. This illustrates current buggy behaviour.
* I have a $100 customer invoice, posted- and due-dates 6 weeks ago.
* I have a $50 credit-note to same
11 matches
Mail list logo
