So how do we cope with regulatory rules for issuing an invoice for a recurring payment received ?

That's not good to have a system behave this way, it means that only payment gateways would issue invoices or that we have to issue manual invoices for all recurring payments, thus completely defeating the purpose of recurring payments and propose invoice features in front end to the customer/subscriber.

Most professional gateways would not issue invoices as this is not their purpose. Ingenico does not.
Further even if they would do it, the invoice numbering would not follow the rule that invoice numbering should be incremental.

By the way, we will pay for the development of a payment gateway for Slimpay with our developers and give it to you for CBsubs, but this invoice point needs to be addressed quickly as it is a serious flaw to develop sales and a problem for regulatory rules.

We use Ingenico for recurring payments
Is there a solution to keep the aliases registered at ingenico and trigger manual payments from our side ?
Would setting Ingenico gateway to "enable single payments only" keep the aliases/credit card and allow us to reuse them when triggering a manual renewal ?
Our customers registered their credit card for this and we cannot ask them to refill credit card field and redo the payment process each time. We would need to do it with their payment (credit card) data directly ?

Any solution ?

I stopped the recurring function in the gateway but got messages from CBSubs indicating that it's not possible to make recurrent payments for the customers

How can I stop these emails from CBSubs ?

Did you have an update about this generation of invoice for recurring payments ?

Regards
Jean