Invoicing for recurring payments

As I understand you can increment the basket invoice and that'd be sufficient enough so instead of completely overriding the invoice number you'd have the below.

Yes that could be a workaround to keep the basket invoice which is already incrementing and to add a payment increment. That would fit both annual and monthly invoices.

This should allow you to enforce whatever ordering system you need for payment rows and you already have the display output via query field.

We already use the query field for our administration needs in the front end and this works fine.

Would this fit your needs?

Unfortunately no because the goal is for the customer to get a legal invoice with an incremented number. That's not our need but a legal requirement for all people that would use the recurring system of CBSubs for less than yearly subscription. I think that the french law for invoicing numbering scheme is the same as european requirements regarding unique compulsory sequential number for each invoice

So what we would need is to display the invoice at each new payment with the incremented invoice number so that the customer can print or pdf it. This is the only way to be compliant with the legal rules.

How can we combine your _cbsubs_payments update query with a display of the corresponding invoice ? I think this would be the best path to combine a payment row update and to follow by a display of invoices based on _cbsubs_payments tables instead of _cbsubs_baskets. Is it feasible ?

Maybe that you could alter the present invoices template to add a substitution for _cbsubs_payments invoice field ?

We don't have any invoices for payment rows. We only have invoices for baskets as they're one in the same. Best I can suggest is put together an endpoint to output whatever information you need using CB Auto Actions and a Code action with Method set to PHP then code the entire output. You'd then need to link to that auto action in your query field usage per payment row so you can pass the payment id. The below for example might accomplish this.

Global
Triggers: None
Type: Code
User: Self
Access: All Registered Users
Conditions
1: [get_payment] Not Empty
Action
Method: PHP
Code: Output
Display: return

Next be sure you modify the query field as given in a previous reply to the following.

Row:
Be sure to replace AUTOACTION_ID_HERE with the ID of your new auto action created above. This should cause the invoice numbers for the payment rows to link to that auto action. That auto action then loads the payment, loads it baskets, overrides the basket values, then outputs the basket invoice with the payment details overriding it. This doesn't store anything so the original baskets are still safe. Combine this with my earlier proposal of an auto action to update the payment row invoices to be incremented and this entire package should provide exactly what you need.

The link you provided states you can outsource invoicing. Have you considered just using the email receipts that Stripe can send? PayPal with account-only purchasing also provides a full invoice record for them. To enable this for Stripe login to your dashboard and navigate to Settings > Email Receipts.

That is a nice suggestion that we will try right now on the dev server and let you know.
BTW is there any possibility with CB to output directly the result to PDF ?

Regarding Stripe, I thought about it but the problem is that we have also a manual gateway for some offline payments, and Stripe does not support yet full edition of the invoice to show our company details.

BTW is there any possibility with CB to output directly the result to PDF ?

No, but I guess you could add &tmpl=component&print=1 to the URL to make it a Joomla print view.

and Stripe does not support yet full edition of the invoice to show our company details.

You could add your necessary details to an image then set that as the logo within Settings > Branding. Beyond that it already outputs business name and business contact information so I'm not sure what more you'd need to add to it.

This should do the job

Last question :
How can we change this code to make also viewable by mods ? and not only by user ?

You'll need to add a moderator check. Below should work.