@lubos, a recent forum topic revealed a bug, where custom fields for suppliers are showing twice on the Supplier Statement report. This raises the question, however, of whether custom fields defined for customers and suppliers should show at all on transaction forms when that custom field has not been defined for the form. I believe they should not. Here are a few examples of why that could cause problems:
A custom field for supplier bank information is created to support electronic payments. A business might want this to show on purchase invoices or bank payments. But it would almost certainly not want it to show on delivery notes given to drivers. So a custom field for bank information might be created under purchase invoices, but not delivery notes. Yet, because the field is created for the supplier, it will show on both.
A point of contact in a customer’s accounting department could be entered in a custom field. A business could want that to show on sales invoices, which go to the accounting department, but not sales quotes going to supply chain management. Again, however, because the field was defined for the customer, it will appear on both transaction types.
A custom field might be defined for delivery route information of a customer. This would be valuable on delivery notes, but not customer statements.
The best solution seems to be that custom fields checked to show on documents should only show when the particular document form includes that same custom field. This approach provides complete flexibility on where information appears.