Product feedback

Wallet and prepaid credits currently only apply to subscription invoices. To redeem credits against a one-off invoice today, users have to handle the bookkeeping themselves: create the invoice, manually deduct the amount from the wallet, and keep their own record linking the two transactions.

Customers modeling contracts with negotiated discounts on individual fixed charges want the same charge-level targeting that already exists for billable metrics.

It is currently not possible to apply coupons to one-off invoices. However, e-commerce companies make extensive use of one-off invoices, and often need to apply coupons (redeemable through promo codes). Example of a one-off invoice with coupon: Product 1 (add-on) = $50 Product 2 (add-on) = $80 Shipping fees (add-on) = $5 Promo code (coupon) = $10 Total invoice before tax = $125

I can´t seem to find a way to associate entitlements for add-ons. I want customers that have purchased add-ons to receive specific entitlements. Is this something that would make sense or am I misunderstanding the concept of add-ons?

Invoice line items render a single price only. When a discount applies, there's no way to show both the list price and the discounted price on the charge's own row, the discount only appears as a separate labeled line. Customers want both values visible inline on the line item.

As a user, I want to be able to define a billing interval for the subscription fee and each charge. The yearly plan currently supports monthly charges, but we would need more flexibility. For instance, for plan A: Yearly subscription fee; and Usage-based charge X billed quarterly. Another example for plan B: Monthly subscription fee; Usage-based charge X billed monthly; and Usage-based charge Y billed quarterly.

When an invoice is finalized in Lago and synced to Xero, allow the user to control whether it lands in Xero as a draft or as a finalized invoice. This makes the process smoother users who invoice in Xero and use Lago only as an upstream layer.

Add the ability to define OR logic across different filter conditions within a charge, so a single filter can price usage matching condition A or condition B (across different keys) without creating a separate filter combination for each case

Ability to sync data (e.g. customers, subscriptions, invoices, etc.) between Lago and Microsoft Dynamics 365.