Product feedback

We need to be able to give access to the footer personalisation and not the bank details modification (that are both today in the custom section) for security reasons.

Currently, the invoice footer applies on the billing entity level. While custom sections can be used on a customer level, the footer remains the same. It would be useful to be able to define the invoice footer itself for each customer, not just for the billing entity.

As we have an integration with Stripe payment, having an integration with Mollie as a payment provider. https://www.mollie.com (n.b. they already have an active ruby-client https://github.com/mollie/mollie-api-ruby )

Automatically end a subscription in Lago if the invoice isn't paid after x amount of retries.

As a user, I want to be able to sort plans in the interface based on their name, number of customers, number of charges or creation date (i.e. ascending/descending order). Example: plan with most customers on top or most recent plan on top. This initiative can cover all lists in Lago User interface.

Use case: Some subscriptions are terminated from orphaned organizations (that don't have members anymore to do anything). We want to terminate those subscriptions and then void the invoices that get drafted after termination. We want to avoid finalizing the invoice then issuing refunds, we prefer to have no transfer of funds.

Ability to pause and resume subscriptions (sometimes after several billing periods) via the API and user interface as well. If a subscription is paused, the customer should not be billed. If the subscription is resumed over the course of a billing period, fees should be prorated.

Allow to change standard billing period. Examples: 1) Bill client every 2 month 2) Bill client every 3 weeks

As an administrator, I want Lago to regenerate invoice PDFs when resending them via email so that the user's updated billing information appears on the current invoice.

Although billing data can be retrieved via the API, Finance teams need to visualize and export data from the API. This is highly important for revenue recognition reporting purposes.