Renewal payments now register automatically in your accounting system

When a subscription renews and the payment is charged automatically from the card, we now also register the payment itself directly in your accounting system - so the invoice shows as paid, not as “unpaid” or “upcoming”.

What’s new

• Dinero, Billy and e-conomic: The payment is automatically attached to the invoice on the acquirer account you’ve chosen in your accounting settings. Same behaviour you already know from the checkout flow and from manually registered payments.
• invoice.paid webhook: Now also fires when a renewal invoice gets paid, not only on checkouts and manual registrations. Integrations listening for the event now get a signal every time an invoice transitions to paid - regardless of how.
• “Invoice paid” notification: Now also sent to the team owner on renewals, not only on manual payments and new checkouts.

What hasn’t changed

The charge itself, the invoice and the receipt to your customer are unchanged - only the registration of the payment in your accounting system (and the related signals) was missing for renewals. If you have “Sync payments” disabled under your accounting settings, nothing new happens - we still respect that setting.

A small detail under the hood

To avoid double registrations if our system should fail and retry, we now send a unique marker with each payment to Dinero. If the same payment is already on the invoice, we skip it.