Re: reposting invoices

["Chris Travers" <..hidden..>]

On 7/7/07, Victor Sterpu <..hidden..> wrote:
> I must implement a way to repost invoices, mentaining the correct COGS.
> I'm thinking to do this by creating a new table where too keep all the
> necesary information.
> Are you interested in adding this functionality in ledgersmb?

No.  Reposting is not GAAP-compliant under any interpretation of GAAP.
You lose too much of a paper trail this way.
> Why do I need to repost a invoice?
> Suppose there is a wrong date, invoice number or even a price on a
> vendor invoice.
> To correct this I should make a reverse invoice, and then insert the
> correct invoice.
> But this will rezult in some wrong COGS posted.

It shouldn't.  You should get two reversing entries that cancel
eachother out (the new invoice and the reversing invoice).  Any other
behavior (even in 1.2) is a bug.  The reversing numbers are
meaningless in 1.2 but they should cancel eachother out.

> So the easiest way is to make it possible to repost invoices.

I am working on a solution for 1.3.  My general plan at the moment is
to try to create a more generic system.  This means:  that one
essentially creates a reversing invoice and then creates a new one
automatically.

However, I guess the issue at the moment is that we need to define
what correct COGS behavior is when an invoice is partially or
completely reversed (yes, you could issue a credit invoice, reversing
part of a sales invoice due ot goods being damaged in shipping, or
example).

My own sense (IANACPA) is that a credit invoice should essentially
reverse COGS from the back of the queue except when using serial
numbers to identify noncomparable items (which we don't upport yet).

Best Wishes,
Chris Travers