I am working on an Italian e-invoicing workflow and I am using a custom field named “IBAN” to store the customer’s bank account details imported from italian eInvoice XML.
The configuration is as follows:
- A custom field called IBAN is defined on Purchase Invoices and is populated automatically when the XML is imported.
- The same custom field name (IBAN) is also defined on Payments, so that the information should be available when recording the payment.
The behaviour I was expecting is the following: when I view a Sales Invoice that already has the IBAN custom field filled in and I click on “New Payment”, the Payment form would inherit or copy the value of the IBAN custom field from the invoice to the payment.
However, this does not happen. The Payment is created correctly, but the IBAN field on the Payment remains empty, even though the IBAN field on the Sales Invoice is populated.
If this is not currently possible, would it be reasonable to consider it as a feature request, so that custom fields with the same name could optionally be inherited when creating a Payment from a Sales Invoice?
Any clarification or guidance on how to achieve this behaviour, or confirmation that it is not currently supported, would be greatly appreciated.