NewProvince is only required for addresses in Spain
BeeL
Get startedMulti-NIFVeriFactuRulesStripeAPI referenceChangelog

Resuming a recurring template no longer re-invoices a period

Resuming keeps next_generation when it has not fallen due yet, instead of recalculating from today, which could issue a period twice or undo a skip.


ChangelogFixed

Resuming a paused template used to recalculate the next generation from the day you resumed. That could move it backwards. Take a template on day 15 that had already invoiced September and pointed at 15 October: resumed in late September, it went back to 15 September, and the next run issued a second invoice for a period already billed. It undid skips the same way.

Resuming now keeps the scheduled date whenever it has not fallen due yet.

What else changed

  • A date that has not fallen due is kept, and today counts as not fallen due. Only a date left in the past is moved, to the first occurrence after today. Periods missed while the template was paused are not backfilled.
  • If nothing is left to generate, because the date falls beyond end_date or max_invoices was already reached, resuming leaves the template COMPLETED.
  • Changing day_of_month on a paused template now moves next_generation straight away, as it already did on an active one. The response to that PATCH carries the new date, and resuming keeps it. Before, the new day was stored but only took effect when you resumed, counted from that day.
  • What to do. Check invoices generated just after a resume. A second invoice for a period already billed is a duplicate, and under VeriFactu it is corrected, not deleted.

Endpoints

  • PUT/v1/companies/{company_id}/recurring-invoices/{recurring_invoice_id}/statusMoving to ACTIVE keeps a next_generation that has not fallen due
  • PATCH/v1/companies/{company_id}/recurring-invoices/{recurring_invoice_id}day_of_month on a paused template moves next_generation immediately

Where to go next