hello!

we do use the "address" field to include, at the end, the VAT number.. this field is after all a "free" field so you can insert anything..
but maybe it's a good idea to make the VAT number a separate field

about due date: in our system, due dates are applied to payments. doesn't it work for you?

in any case, we're preparing an upgrade of the component that will be out soon, we will try to include these 2 new fields

Thanks for the offline payment plug, will start to use soon.

About the VAT number. Might be handy if it's a seperate field ;-)

About due date and payment... please explain how you see this, how your 'flow' is in this ...
Because our flow is the following :
- make an invoice and set a due date by which the invoice needs to be payed by the customer. If the due date is not met it should flag red, or late, or whatever en you must be able to resend.
- a payment is only booked when the money is received, by bank, paypal, ... and a payment booking doesn't need a due date for us...

Thx.

hello

about "due date": we make it work pretty much the same way, with the differecen that the due date is actually applied to the PAYMENT, not the invoice (because is the "payment" which actually needs to be paid before a certain date..)
and, the payment, if not paid on time, is flagged (red) as "past due date"...

so, I understand we have the same items (invoices, payments), but we use them in different ways, although they are pretty much the same.

in our case, a payment is a thing that YOU create (for instance, an invoice can be splitted into multiple payments), and when created is "not paid". it gets the status of paid when

a) the user actually pays it online (paypal), and the payment is marked as paid automatically, or
b) when you, the admin, manually mark it as paid (for instance, if it was paid with bank transfer)

makes sense?

Ok, now i get it... It's another approach than mine, but i think i can manage that one as well ;-)

Thx for explaining.