Refunds...

Hi Dmitry,

I'm trying to do:

1. Select an invoice on Form1 / Sale Invoices tab and click on "Refund Selected Invoice" button to display selected invoice details on "frmCR_SaleRefund"

2. If required edit (partial refund ) and save the data displayed on "frmCR_SaleRefund" to "crSaleInvRefund" / "crSaleInvRefundItems"

3. Change the color or add some indication to the original invoice on Form1 / Sale Invoices tab on save of the refunds so  that  invoice has a refund indication.

I have commented out script lines produced errors and I couldn't correct..

Please see the updated sample project.

I understand Dmitry... Thank you for the reply.

It'd be nice to hear from other guys who has some experience/thoughts about implementing invoice refunds. Perhaps, there is a simpler/easier approach.

Derek, If you are around I'd love to hear your ingenious suggestions...

Hello Adam, EHW,
I'd been thinking about a similar approach and totally agree with EHW.  I might try
1.  deleting the CRSALEINVREFUND and CRSALEINVREFUNDITEM tables
2.  renaming (for clarity) SALEINV to TRANSACTIONHEADER and SALEINVITEM to TRANSACTIONITEM
This would simplify the structure greatly
3.  add a DB(debit)/CR(credit) indicator for each TRANSACTIONITEM record (with DB as the default)
4.  optionally add a 'REASON CODE' indicator (faulty, damaged, not required etc etc)
4.  use 2 tablegrids, filtered on the DB/CR indicator
With this approach,
5.  if the CR relates to an invoice, you simply add it as a new line to the existing invoice.
6.  if the CR is a general credit, it can be added as a totally new transaction unrelated to any invoice.
7.  from a reporting aspect, you could, for example, print out just the CR transactions if you need to issue a defacto Credit Note.
This option gives you greater flexibility but with simplicity - transactions that are wholly DB items, wholly CR items or a mix of DB and CR items - all using the same tables.
From a credit control point of view, it might also be useful to have an indicator against each TRANSACTIONITEM record to show if it's been paid, credit issued, in dispute etc etc (although in my experience, if one transaction item is in dispute, the entire transaction gets disputed - or maybe that's just how it works in the UK).
If I get a spare hour, I'll mock something up, as much for my own interest, to see how it might look.
Regards,
Derek.

Hi Adam, EHW and anyone else,
Please find attached one option for handling refunds (using just one table to hold both DB and CR transactions, as outlined by EHW). 
It's a clone of an old project so it doesn't look too much like yours but the principle of using either different tablegrids to split off invoices and credit notes (refunds) or (as I've done in this example) using the same tablegrid with a real-time filter, is basically the same. 
I prefer this way because it's quick and easy to set up and also means you can see ALL transactions, just DB transactions or just CR transactions all on the same grid - but you could choose to show 3 discrete grids all on the same screen if you wanted.
It's just 'play data' but it should work - the script is a bit messy but most of it is just for cosmetic reasons or better ease of use for users.
Hope this gives you some ideas.
Derek.