"Automatic Payment Forward" - what the hell?

[tereque]

hi Maf,


On 2013.08.14 12:00 AM, gnucash-user-request at gnucash.org wrote:
> Message: 8
> Date: Tue, 13 Aug 2013 11:13:37 +0100
> From: "Maf. King"<maf at chilwell.net>
> To:gnucash-user at gnucash.org, tereque<tereque at gmail.com>
> Subject: Re: "Automatic Payment Forward" - what the hell?
> Message-ID:<2122216.yVv0mS0dJ3 at calufrax.standbyevents.co.uk>
> Content-Type: text/plain; charset="utf-8"
>
>
> You'll need Derek to go into the mechanics, but AFAIK, the "automatic payment
> forward" happens if you book more payment than has been invoiced.
>
> Say you have a invoice for ?70, and payment comes for ?100.  you'll get an
> A.P.F of ?30.
generally I though something like that would be happening. Is there a 
way to either shut that automatic off, or control it's behavior? maybe 
Derek can switch the lights for us all here?

Actually my day to day situation is that customers never pay the exact 
amount invoiced to them, or sometimes the invoice amount has to be 
changed because some parts of an order are cancelled, etc ...

So I have to post/unpost/post invoices quite often. Even after payments 
had been made. Or a project (would be a 'job' in the terminology of GC) 
consists of several Invoices .... So I am trying to keep control of what 
actually happened.

> I think it comes about if you try to pay several invoices with one payment -
> whilst GC by default will allocate payments to the oldest invoice first
> (FIFO).  You can make one invoice "jump the queue", but not several.  EG. if
> invoices 1 to 5 are outstanding, you can allocate payment to no.3, but not 2
> and 4 - you'll pay 1 and part of 2.