I’ve just been looking through a couple of our recurring invoice profiles, which have values set in the “Invoice Name” field (also trying to make use of your variable system, eg: “Hosting services ||MONTH|| ||YEAR||”).
However, on the actual invoices created from the profile, I’m seeing that it’s acting as though the invoice name field was unset, and thereby truncating the first item’s description as the name for child invoices.
Am I interpreting the behaviour of the recurring profiles “invoice name” field (not the “short reference” field) incorrectly, meaning this is a feature request - or is there something going wrong here?
The invoice name field was previously the first 35 characters of the top line. We later allowed this field to be edited and called it the “Invoice Name”. I think on any kind of copy operation (like recurring invoices) it repopulates from first line rather than translates from the original name.
We could probably change this to take from the original rather than repopulate, however if you have recuring invoice tokens in there (which you do in your case), they won’t get translated.
If it could be changed to duplicate the invoice name from a recurring profile, that would be appreciated.
As it is the invoice name, either from the field or the first 35 chars, that gets passed to payment gateways as a description, it causes less confusion with the customer if we can pass a fitting short description over – and makes life a little easier when looking through transaction logs; and of course when looking through the invoice lists in QF.
I would say that the ability to include variables would be helpful (as a feature suggestion), but if that’s too complex to bring across, just a static name that carries to child invoices would suffice.
I’m sure we can translate the name, I’m not sure about the tokens? It’s possible to translate them but the resulting name would likely end up truncated as the limit for this field is only 35 characters. If that’s a reasonable sacrifice we can probably do it.
@leyton this has now been implemented. The system should be taking the name of the invoice from the original rather than deriving it from the first line.