itronics wrote:

The logic behind this constraint is quite simple. The sales order is firm for both sides of transaction, so we cannot change the price in invoicing step, and therefore once issued invoice cannot have price changed. If you made a mistake in price during sales order receive you should void eventually issued invoices/deliveries, contact your customer , renegotiate the price andenter the delivery/invoice again.

Janusz

I think I see a critical bug here.  FA has a mechanism that allows you to change an invoice, but the change isn't reflected in Accounts Receivable or GL.  It seems to me that FA either must prevent changes to invoices or FA must account for them correctly.  FA allows changes to invoicing but the accounting of the change is wrong.

For us, the accounting system we choose MUST allow modification of an invoice after it is printed and the accounting for the change must be correct.  We are trying to convert from Peachtree which allows us to change an invoice up until we close the year;  I will not get buy in to change to a system that doesn't allow at least some mistake correction. Sad to say, we are only human and we make mistakes.  To void and start over is not acceptable from a business point of view (any complex transaction will have an error on the second try too!).

So I would like to propose (and we can do this) one of these:
1. that we make it an optional / admin feature to change an invoice and do all the correct accounting. (preferred)
2.  Maybe we just need a "VOID and reissue" button that voids the old transaction and creates a new order entry screen from the previous transaction. 

What do you think?

We looked at the top 15 Accounting systems on Source Forge and I think we like this best.  So we're trying to do a trial conversion from our existing system (Peachtree) and it was really very simple to do so far.

I am interested in taking the customer receivables suggestion one step further.  I've tested an import into debtor_trans of a type 10 and 13 record based on sample entries and it seems to work nicely.  I'm concerned that I'm going to get into trouble later as I enter new invoices; it seems the FA system may just duplicate my transaction numbers.  Is there a table of LAST-USED "debtor_trans.trans_no", "invoice number", etc. somewhere that I need to update. 

I'd like to start my invoice numbers with something higher than "1" anyway.  Is it possible to start at "90000", which would be more compatible with my existing invoices?

Where is the manual?